Messages 27101 Through 27120

Note: If an error code within the above range does not appear in this list, it is considered an Internal Error, for which no specific user troubleshooting guidelines are available.

Message Code 27102

The FragmentId, FragmentIdPrefix and FragmentIdSuffix arguments are mutually exclusive

More than one query-related argument ("FragmentId", "FragmentIdPrefix", "FragmentIdSuffix") has been specified.

Troubleshooting

  • Specify one fragment-related argument only.

Message Code 27103

The Query, QueryPrefix and QuerySuffix arguments are mutually exclusive

More than one query-related argument ("Query", "QueryPrefix", "QuerySuffix") has been specified.

Troubleshooting

  • Specify one query-related argument only.

Message Code 27104

The Url and UrlPrefix arguments are mutually exclusive

More than one URL-related argument has been specified.

Troubleshooting

  • Specify one URL-related argument only.

Message Code 27105

The Path, PathSuffix and PathPrefix arguments are mutually exclusive

More than one path-related argument has been specified.

Troubleshooting

  • Specify one path-related argument only.

Message Code 27106

The Host, HostSuffix and HostPrefix arguments are mutually exclusive

More than one host-related argument has been specified.

Troubleshooting

  • Specify one host-related argument only.

Message Code 27107

The Url* arguments are mutually exclusive with the Scheme, Host*, Port, Path*, Query* and FragmentID* arguments

The "Url" or "UrlPrefix" arguments cannot be specified with any of the other arguments detailed in the message.

Troubleshooting

  • Specify either a "URL", "URLPrefix", or one or more of the other arguments only.

Message Code 27114

The 'net layer set for the script' Net layer has not been initialized

The web_switch_net_layer function, intended for WAP replay only, requests switching to a Net layer that has not been initialized.

Troubleshooting

  • Check the net name argument. Note that if a WinInet replay has been requested, you cannot switch to the Sockets layer and vice versa. See Run-Time Settings > Internet Protocol: Preferences, and in the Advanced area select the WinInet replay instead of Sockets (Windows only) check box.

Message Code 27117

Binary=1 is mutually exclusive with BodyBinary, BodyUnicode and RAW_BODY_START

The Binary=1 argument is intended for use with the Body argument only. Other body-related arguments cannot be specified together with Binary=1.

Troubleshooting

  • Remove the Binary=1 specification, and, if you have a Body argument, change it to BodyBinary.

Message Code 27118

SaveOffset ('argument value') plus SaveLen ('SaveLen value') exceeds the found value length ('value length') for parameter 'parameter'. SaveLen='bytes' is used

A preceding web_reg_save_param for the parameter specified a SaveOffset argument value and a SaveLen argument value. This requests that the first "SaveOffset" bytes of the found value be skipped and that SaveLen bytes be saved to the parameter. However, the sum of SaveOffset and SaveLen exceeded the length of the found value. Thus, fewer bytes than requested were saved. Possible reasons include:

  • The found value is not the intended one, due to inaccurate arguments to web_reg_save_param.
  • The found value is not the intended one, due to navigating to a wrong page, or a different page being returned.
  • The specified SaveOffset is incorrect.

Troubleshooting

  • Check if the found value is the intended one, and is in the correct page.
  • Check the values of SaveOffset and SaveLen are correct.

Message Code 27119

SaveOffset ('argument value') exceeds the found value length ('value length') for parameter 'parameter'. An empty string is saved

The SaveOffset exceeded the length of the found value, and an empty string was saved in the parameter. Possible reasons include:

  • The found value is not the intended one, due to inaccurate arguments to web_reg_save_param.
  • The found value is not the intended one, due to navigating to a wrong page, or a different page being returned.
  • The specified SaveOffset is incorrect.

Troubleshooting

  • Check if the found value is the intended one, and is in the correct page.
  • Check the value of SaveOffset is correct.