VTS/IS Error Messages
The HTML server embedded within VTS/IS can generate error messages under certain conditions. All error messages are generated using the standard HTML error reporting method, giving an error number and explanatory text.
Note: The explanatory text messages are defined in Setup.ini, and so may be customized if required. Information on customization of the text messages can be found in "VTS Programmer's Guide: Customization of HTML Error Responses".
An example of an error response is shown below:
The table shown below identifies the possible error codes and messages that VIC users may encounter.
|
Error Code |
Message | |
|
400 |
Protocol not "HTTP" or request header malformed. PageList request issued for a non-VTS application. | |
|
401 |
Originating IP address is on a DENY list or is not on an ALLOW list. AppsList request issued, but user not authenticated by the VTS Security Manager. PageList request issued, but user not authenticated by the VTS Security Manager. VTS-BIN request issued, but user not authenticated by the VTS Security Manager. Note: You may receive a 401 error code if no VTS application is running (i.e. the VTS Security Manager cannot authenticate against any user accounts), or if the application you are requesting is not running. | |
|
403 |
This request would exceed the number of licensed connections. | |
|
404 |
GUID or application name in request specifies an unknown application. A request was received for a file that could not be located. | |
|
500 |
Unused. | |
|
501 |
The HTTP request specified an unimplemented method (only "Get" is implemented). | |