Neotys status codes

JavaScript compilation failed: invalid syntax.

JavaScript execution failed. Typically, the script used a variable or a function that does not exist.

The script flagged the JavaScript Action as having failed (Call to context.fail() method)

JavaScript execution succeeded.

Generator internal error while processing the Adobe Flex/AMF request. This error code covers all the errors that may occur while preparing an Adobe Flex/AMF request prior to it being sent to the server. The most common error is caused when NeoLoad attempts to play back an Adobe Flex / AMF request that was incorrectly converted to XML format during recording, and has not been repaired.

Generator internal error while processing the AMF response. This error code covers all the errors that may occur while decoding an Adobe Flex / AMF response after reception. The most common error is caused by a response containing Adobe Flex/AMF externalizable objects that could not be decoded. For more information about externalizable objects, see Post-recording wizard.

An AMF error message was returned by the server and the error code contained in the message does not appear in the AMF error message exclusion list.

The server shut down the streaming channel prematurely.

At least one assertion failed on the server response to the request.

Error during the execution of the command.

Action interrupted during runtime.

The "command" parameter is not specified.

There was an issue parsing the parameters.

There was an error while creating the connection to the destination.

An error occur when loading Custom Action.

Custom Action internal error.

API Key not allowed by the server.

Error. No more details.

Session ID does not exist.

Invalid Argument value.

Current License do not include Data Exchange API module.

No running test.

There was an issue parsing the parameters.

There was an error while disconnecting from the destination.

Generator internal error while processing the GWT request. This error code covers all the errors that may occur while preparing a GWT request prior to it being sent to the server. The most common error is caused when NeoLoad attempts to play back a GWT request that has been incorrectly converted to XML format during recording and has not been repaired. To fix the problem, see Google Web Toolkit: Handle external libraries.

Generator internal error while processing the GWT response. This error code covers all the errors that may occur while decoding a GWT response after reception. The most common error is caused by a response containing GWT objects that could not be decrypted. For more information about GWT objects, see Google Web Toolkit requests.

A GWT error message was returned by the server. To troubleshoot the issue, please check the following:

• The version of the JAR in NeoLoad must match exactly the JAR in your application on the server. A different build of the same code will not create the same JAR.

• All dynamic attributes must be variabilized.

• Access the server manually in a browser to verify whether a part of the server is no longer working.

Generator internal error while processing the Hessian request. This error code covers all the errors that may occur while preparing a Hessian request prior to it being sent to the server. The most common error is caused when NeoLoad attempts to play back a Hessian request that has been incorrectly converted to XML format during recording and has not been repaired.

Generator internal error while processing the Hessian response. This error code covers all the errors that may occur while decoding a Hessian response after reception. The most common error is caused by a response containing Java objects that could not be decrypted. For more information about Java objects, see Hessian requests.

A Hessian error message was returned by the server.

HTTP connection problem.

Invalid configuration for request.

The request has no configured server. It is necessary to check the server field of the request.

Generator internal error while processing the Java Serialization request. This error code covers all the errors that may occur while preparing a Java Serialization request prior to it being sent to the server. The most common error is caused when NeoLoad attempts to play back a Java Serialization request that has been incorrectly converted to XML format during recording and has not been repaired. To fix the problem, see Java Serialization: Handle external libraries.

Generator internal error while processing the Java Serialization response. This error code covers all the errors that may occur while decoding a Java Serialization response after reception. The most common error is caused by a response containing Java objects that could not be decrypted. For more information about Java objects, see Hessian requests.

A Java Serialization error message was returned by the server.

This error has many underlying causes so please reach out to NeoLoad Support, through your NeoLoad Support Portal, for further assistance.

This error has many underlying causes so please reach out to NeoLoad Support, through your NeoLoad Support Portal, for further assistance.

The link or form could not be extracted from the previous request. The previous request contains an error.

The request that failed has the "Link/Form extractor" type in NeoLoad. This means that the request must extract its dynamic information from the previous page (designated by the 'referrer').

The link or form could not be extracted from the previous request. The definition does not match any link or form in the previous request.

The request that failed has the "Link/Form extractor" type in NeoLoad. This means that the request must extract its dynamic information from the previous page (designated by the 'referrer'). NL-LINKEXTRACTOR-02 means that the NeoLoad definition of the request is not properly designed to extract its dynamic information from the previous page. Please check the request definition and validate the regular expressions that may have been used.

The link or form could not be extracted from the previous request. The previous request was not played.

The request that failed has the "Link/Form extractor" type in NeoLoad. It means that the request must extract its dynamic information from the previous page (designated by the 'referrer'). The NL-LINKEXTRACTOR-03 error means that the preceding request (designated by the "referrer") was not played. This usually indicates a problem with the Virtual User configuration or that a previous error prevented the referrer being played.

The NL-MEDIA-ENGINE-01 error occurs when a Load Generator fails to detect automatically the average bitrate of a media content.

To elude the issue, it is necessary to specify the average bitrate of the media:

1. Select the media action in the Virtual Users tree.

2. Click Simulation Parameters.

3. Select the option The average bitrate of the media is and enter the bitrate value. To compute the bitrate value, click Compute the average bitrate. Then enter the parameter of the media: size and length.

Miscellaneous I/O error when connecting to the server.

The "java.net.NoRouteToHostException: No route to host: connect" error probably indicates that an incorrect network interface has been used. Check the Load Generator advanced network settings.

The "java.net.SocketException: Connection reset" error may occur when the server is overloaded.

Error when connecting to server (bind error).

Indicates an error occurring locally when attempting to bind a socket. This is usually due to the Load Generator not being able to open any more sockets on the local system. For more information about system settings to check, see Troubleshooting.

Error when connecting to the server. Indicates a server-side error occurring when attempting to bind a socket. This is usually due to the server being shut down or not being able to open any more sockets.

If the error details are "java.net.ConnectException: Connection timed out: connect" for all the requests, it would suggest that the Load Generator cannot access the application. You can verify this behavior by trying to access the application on the Load Generator machine.

An error occurred while encrypting the Oracle Forms request. This error may have a number of causes: the error details will give more indications as to the error probable source. Generally, the error arises when the Virtual User tries to encrypt an Oracle Forms request where the dynamic encryption key negotiation with the server has previously failed.

An error has occurred while decrypting the Oracle Forms response. The Oracle Forms server returned an error indicating that it did not understand the request, or that the response sent back by the server could not be decrypted correctly.

An unknown handlerId has been found while creating the Oracle Forms request. During runtime, a list of all existing handlerIds is maintained. Each time a CREATE or a DESTROY DataMessage is received, the handlerId is added or removed from this list. A handlerId is declared as unknown if it is not within the list of all existing handlerIds. For more information, see Examples of recording.

There was an issue parsing the parameters of the Perfecto script.

There was an issue while executing the script. Please verify the Perfecto URL (it should end in /services/). Please verify any proxy settings. Note that proxy settings are set using additional Perfecto action settings, not in NeoLoad preferences.

There was an issue while parsing the script results.

There was an issue sending the results to NeoLoad.

Generator internal error while processing the XML request. This error relates to problems that may arise in the Generator while preparing the XML request prior to sending. The error details will pinpoint whether the problem is due to the replacement of variables or to the conversion from XML to binary format.

Generator internal error while processing the XML request. This error relates to problems that may arise in the Generator while preparing the binary response after its reception. The error details will pinpoint whether the problem is due to the conversion from binary format to XML.

XML HTTP requests whose conversion to XML has failed cannot be played back. During recording, certain XML requests may not have been converted to the XML format correctly. These requests are notified visually in the User Paths. This kind of request sometimes can be produced by the Adobe Flex/AMF module. The requests flagged as containing an error must be repaired according to the instructions in the documentation supplied with the XML module generating the request.

There was an issue parsing the parameters.

There was an error while publishing the message to the topic.

There was an issue parsing the parameters.

There was an error while receiving the message from the queue.

There was an issue parsing the parameters.

There was an error while receiving the message from the topic.

NeoLoad could not follow the sendRedirect directive for the previous request (302 Moved Temporarily). Previous request not found.

The request that failed has the "HTTP redirect" type in NeoLoad. This means that the request must follow the redirection directive of the previous request. The redirection is valid when the previous request returns the HTTP status code 301, 302, 303 or 307, and headers containing the header named "Location". NL-REDIRECT-01 means that the previous request (designated by the 'referrer') has not been played. Please check the referrer of the request that failed (click the "Advanced..." button and select the "Advanced settings" tab) and check in your Virtual User that the 'referrer' request is being played before the request that fails.

NeoLoad could not follow the sendRedirect directive for the previous request (302 Moved Temporarily). Location header missing in previous request.

The request that failed has the "HTTP redirect" type in NeoLoad. This means that the request must follow the redirection directive of the previous request. The redirection is valid when the previous request returns the HTTP status code 301, 302, 303 or 307, and headers containing the header named "Location". NL-REDIRECT-02 means that the previous request (designated by the 'referrer') had an HTTP status code of 301, 302, 303 or 307 but no header named "Location" when played back. The web application should be fixed.

NeoLoad could not follow the sendRedirect directive for the previous request (302 Moved Temporarily). The previous request did not issue a redirection (no 302 status)

The request that failed has the "HTTP redirect" type in NeoLoad. This means that the request must follow the redirection directive of the previous request. The redirection is valid when the previous request returns the HTTP status code 301, 302, 303 or 307, and headers containing the header named "Location". NL-REDIRECT-03 means that the previous request (designated by the 'referrer') did not have an HTTP status code of 301, 302, 303 or 307 when played back. First, please verify that the referrer of the request that failed is in fact the appropriate request (click "Advanced..." button and select the "Advanced settings" tab). Next, investigate why the previous request did not return the expected status code. Typically, an invalid parameter has been sent and the previous request has failed with '200' as the HTTP status code.

NeoLoad could not follow the sendRedirect directive for the previous request (302 Moved Temporarily). The previous request contains an error.

The request that failed has the "HTTP redirect" type in NeoLoad. This means that the request must follow the redirection directive of the previous request. The redirection is valid when the previous request returns the HTTP status code 301, 302, 303 or 307, and headers containing the header named "Location". NL-REDIRECT-04 means that the previous request (designated by the 'referrer') failed.

Internal Generator error during processing of the Adobe RTMP request. This error code covers all errors that may occur while preparing an Adobe RTMP request before it being sent to the server. The most common error is caused when NeoLoad attempts to play back an Adobe RTMP request that was incorrectly converted to XML format during recording and has not been repaired.

Internal Generator error during processing of the RTMP response. This error code covers all errors that may occur while decrypting an Adobe RTMP response after reception. The most common error is when the response contains externalizable Adobe RTMP objects that could not be decrypted. For more information about externalizable objects, see Post-Recording Wizard.

An RTMP error message was returned by the server.

This error message is displayed when SWF verification is enabled for the application. The server does not allow NeoLoad to correctly simulate the RTMP scenario.

The server took too long to respond to the client connection or RTMP request. The default maximum connection and response time is 60 seconds. These settings may be changed in the <install-dir>\conf\Controller.properties file. Locate the "[RTMP]" category (create it if it does not already exist) and the "socket.read.timeout" and "socket.connection.timeout" parameters (the values are in milliseconds: 60.000 equals 60 seconds).

This error has many underlying causes so please reach out to NeoLoad Support, through your NeoLoad Support Portal, for further assistance.

This error has many underlying causes so please reach out to NeoLoad Support, through your NeoLoad Support Portal, for further assistance.

Unexpected Load Generator error when playing the request. This error can occur when the client request body and/or the server response body does not contain any data. Some applications may not strictly respect the HTTP protocol, so it is not necessarily an error.

The Virtual User requested a unique value in a variable but no values were available at that time. This indicates there aren't enough values available for the load being simulated.

There was an issue parsing the parameters.

There was an error while sending the message to the queue.

There was an issue parsing the parameters.

There was an error while sending the message to the queue.

Generator internal error while processing the Siebel request. This error code covers all the errors that may occur while preparing a Siebel request prior to it being sent to the server.

Generator internal error while processing the Siebel response. This error code covers all the errors that may occur while decoding a Siebel response after reception.

A Siebel error message was returned by the server.

This error has many underlying causes so please reach out to NeoLoad Support, through your NeoLoad Support Portal, for further assistance.

This error has many underlying causes so please reach out to NeoLoad Support, through your NeoLoad Support Portal, for further assistance.

There was an issue parsing the parameters.

The type of SQL statement is invalid.

There was an error while creating the connection.

There was an error while executing statements.

This is not an error. A variable used by the request has used up all its values and is programmed to stop the test in this event. No error has occurred.

There was an issue parsing the parameters.

The variable was not found.

There was an issue initializing the DataExchange API client.

There was an issue parsing the parameters.

The entry value is not a double-precision number.

There was an issue initializing the DataExchange API client.

There was an issue parsing the parameters.

There was an error while subscribing to the topic.

There was an issue parsing the parameters.

There was an error while unsubscribing from the topic.

The Load Generator has triggered an error while executing the WebSocket channel.

An internal error occurred while processing the WebSocket request.

A value has been added to the shared queue.

A value in the shared queue has been consumed to a variable.

The variable value has been modified.