This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with Rational® Performance Tester.
Find more information about the error messages.
Failed to attach the annotation to the test.
This document contains information about what's new, installation instructions, known issues in IBM® Rational® Performance Tester and contact information of IBM Customer Support.
This document includes information about hardware and software requirements for IBM® Rational® Performance Tester.
This guide provides an overview and describes the task flows to get you to start with Rational® Performance Tester. This guide is intended for new users.
This section contains the tutorials which explains the main features of Rational® Performance Tester.
This section describes about the sample project which can be used with Rational® Performance Tester to test the functionality of an application.
This guide describes how to install Rational® Performance Tester. After you install the product, you can perform administration tasks such as license configuration and integration with other products. This guide is intended for administrators.
This guide describes how to create test scripts in Rational® Performance Tester and enhances tests by applying different test elements such as dataset, variables, and verification points. This guide is intended for testers.
This guide describes tasks that you can perform on schedules, test execution with custom code, and Extending Rational® Performance Tester to support other protocols. This guide is intended for testers or test execution specialists.
This guide describes how to keep track of the performance of the application by evaluating the test results. This guide is intended for test managers.
This topic provides information about how to troubleshoot several problems with IBM® Rational® Performance Tester.
%1 terminating due to exception: %2
Transaction [%1] has been aborted.
User group [%1] was not found.
RMSE0003W There are currently no selected counters for the source named {0}.
RMSE0004W The source named {0} is no longer available.
RMSE0005W The source named {0} is reporting the error message {1}.
The server does not support resource monitoring labels.
The JAR %1 referenced in preferences could not be found. Preferences on the cloud workbench will be cleared.
Error occurred while instructing Rational® Performance Tester engine to enable real-time protocol data for user: %1. It's possible that no data will be seen for this user in the Protocol Data view.
Error occurred while instructing Rational® Performance Tester engine to disable real-time protocol data for user: %1. It's possible that data for this user will continue to be displayed in the Protocol Data view.
example of translatable error message %1
Unknown authentication scheme '%1' discovered in HTTP 401 response, ignoring.
Unrecognized authentication header '%1' discovered in HTTP 401 response, ignoring.
No authentication headers found in HTTP 401 response, ignoring.
The server requested NTLM authentication but no NTLM authentication context was supplied with this request. Authentication is not possible.
NTLM authentication failed for this request. Verify that the NTLM authentication context values for this request are correct.
Host name '%1' can not be resolved.
Encountered error while updating dynamic cookie cache while interpreting 'Set-Cookie' header with value '%1' sent from web-server '%2' retrieving URI '%3'. Explanation message: '%4'. Cache not updated to include this cookie value.
Unexpected challenge(HTTP status code=401) received during HTTP playback to web-server '%1' retrieving URI '%2'. This behavior differs from the behavior recorded during test creation. For authentication to playback correctly a challenge must be recorded during test creation.
Authentication failed during HTTP playback to web-server '%1' retrieving URI '%2'. Probable cause: username '%3' and/or password '%4' incorrect.
Exception occurred during attempt to write request to web-server '%1' getting url '%2'. Explanation: %3
General un-handled exception occurred during socket I/O read from web-server '%1' retrieving URI '%2'. Explanation message: '%3'.
A read time-out occurred during a socket I/O read from web-server '%1' retrieving URI '%2'. Since this URI is the primary request for the current page all secondary requests will be skipped and the next page will be attempted. Current time-out value of '%3' milliseconds should be increased if long delays are expected on this page.
A read time-out occurred during a socket I/O read from web-server '%1' retrieving URI '%2'. This secondary request will be skipped. Current time-out value of '%3' milliseconds should be increased if long delays are expected on this request.
A connect time-out occurred during a socket I/O connect to web-server '%1' attempting to retrieve URI '%2'. Since this URI is the primary request for the current page all secondary requests will be skipped and the next page will be attempted.
A connect time-out occurred during a socket I/O connect to web-server '%1' attempting to retrieve URI '%2'. This secondary request will be skipped.
Unexpected challenge(HTTP status code=407) received while accessing HTTP proxy '%1' retrieving URI '%2'. This behavior differs from the behavior recorded during test creation. For authentication to playback correctly a challenge must be recorded during test creation.
Authentication failed accessing proxy-server '%1' retrieving URI '%2'. Probable cause: username '%3' and/or password '%4' incorrect.
An error occurred during decoding of content received from web-server '%1' attempting to retrieve URI '%2'. Explanation message: '%3'.
Error encountered during the process of URI substitution for host=%1 and URI =%2 . Data correlation supplied a malformed URI=%3 . Explanation: %4. If you attempted to perform a custom data substitution on this URI ensure it has proper URI syntax. If you did not perform a custom data substitution then an internal may have been encountered and you should contact product support for further problem determination.
An error occurred during encoding of an annotated execution history event property. Explanation message: '%1'.
An error was encountered during transform of response data. %1
Exception occurred during attempt to write request to proxy-server '%1' getting URL '%2' on host '%3'. Explanation: %4.
An error was encountered during un-transformation of request data. %1
Unable to successfully establish a connection to web-server '%1' retrieving URI '%2'. Web-server closing the connection after connection was just established.
Unexpected exception occurred during connection close to web-server '%1' retrieving URI '%2'. Explanation: %3.
HTTP parsing error encountered while retrieving URI '%1' from web-server '%2'. If this URI is the primary request for the current page all secondary requests will be skipped and the next page will be attempted.
IP aliasing is enabled but no IP address was found for virtual user %1. Verify correct network interface name(s) are specified.
Exception occurred during attempt to connect to proxy-server '%1' getting URL '%2' on host '%3'. Explanation: %4.
Unable to authenticate with the proxy-server. Possible solution: re-record test due to possible proxy-server '%1' authentication changes.
Web-server '%1' unexpectedly closed the connection while in the process of retrieving URI '%2'. The response body MAY be incomplete due to a missing "chunk". If missing chunk was last (zero length) chunk, data is complete.
Infinite redirection loop detected getting URL '%1'. If this is expected and understood increase RPT_VMARGS rptMaxRedirection parameter. Redirected history %2
Unexpected server redirection occurred getting URL '%1'. We were redirected to the same URI which issued this request. Redirected history %2
%1
Exception thrown while creating connection variables
Exception thrown by the launch configuration core
Exception thrown during an update to a launch configuration
The data source type %1 is not expected
SAP Calendar dialog could have unpredictable behavior during playback, set the date directly in the field using string format.
SAP GUI Application creation failed
Rational® Performance Tester/SAP: Unable to start SAP GUI, please check SAP GUI installation.
Connection with SAP GUI existing session or shortcut not allowed during schedule execution.
Setting the log verbosity left me with %1 users
A Test cannot be launched on the specified Driver
A Test could not be launched on Driver: %1. The Test Execution Framework was not able to deliver an Executor. This is an internal error, please contact support. For more information, see the Troubleshooting section of the online help.
A Test could not be launched on Driver: %1 due to an internal error. Please see Problem Determination Log. For more information, see the Troubleshooting section of the online help.
An error has been encountered while launching a Test on Driver: %1. Please see Problem Determination Log. For more information, see the Troubleshooting section of the online help.
An error has been encountered while launching a Test on Driver: %1. An Executor was not returned and neither was an error message. This is an internal error, please contact support.
An error has been encountered while launching a Test on Driver: %1. There are no Data Processors present. This is an internal error, please contact support.
An error has been encountered while launching a Test on Driver: %1. Data Processors have not been configured correctly. This is an internal error, please contact support. For more information, see the Troubleshooting section of the online help.
A Test could not be launched on Driver: %1. The Test Execution Framework encountered an Exception. This is an internal error, please contact support.
An error was encountered while launching a Test on %1.\nPlease examine your Deploy Directory: %2, the error could be caused by one of the following:\n\n1. The Deploy Directory path must be absolute (start with Drive Letter or "/").\n2. The Deploy Directory path must be valid for the Target Operating System.\n3. The IBM® Agent Controller must have authority to this directory.\n4. An error was encountered while deploying to this directory.
An error has been encountered while launching the test. A required dataset %1 is missing or invalid in your project.
An error has been encountered while launching the test. A required dataset %1 has been replaced. One or more test(s) are referencing a different version of the dataset.
ready
not ready on port
Check Agents Failed
%1 deployment directory %2 format not compatible for operating system %3. For more information, see the Troubleshooting section of the online help.
Timed out after %1 seconds waiting for the license server. Check network connectivity to the license server and ensure the license server is running. For more information, see the Troubleshooting section of the online help.
Virtual users have exited prior to stage completion. At the end of stage %1 there were %2 users running when %3 were expected. A common reason for this is a schedule which has assigned an insufficient amount of work (for one or more User Groups), to keep the associated virtual users active for the full amount of time specified by the stage duration(s). Review the schedule for sufficient workload. When using multiple stages it is strongly recommended to use infinite loops to ensure that virtual users always have enough work scheduled regardless of the total duration of all the stages. Another possible reason is that one or more virtual users exited upon encountering a serious error; consult the Test Log or Common Base Event XML log on the agent for more information. Also see the Troubleshooting section of the online help.
Exception encountered adding or removing users.
The schedule has no user group.
The RPT_VMARGS option rptPre811PageResponseTimes is specified on at least one location and is missing from at least one other location. Please ensure that either all locations include this option or none do. See "adjusted page response time for increased accuracy" in the help for more information.
Run Completed (%1)
Run Terminated (%1)
%1: %2
Location template file %1 is not found (referenced from location file %2)
Found location template [%1] for [%2] (instances found: %3)
%1 remote location(s) associated with location template [%2]
Cannot change stage duration if Until Finished specified
Duration time specified is less than what has already elapsed
Schedule must be in the Running state to change stage duration
Agent %1 not ready, time of last contact: %2
No successful contact
Unknown host '%1'
Unable to complete deployment to agents because of an unexpected error in the publish phase. %1
Agent version %1 incompatible on host %2. Minimum agent version %3 required.
Error encountered
Failed to delete file %1
Rational® Service Tester for SOA Quality is licensed to only support single user execution. Please adjust the number of Users to 1 in the schedule and rerun. Contact IBM® regarding the use of __PT_RR_SHORTNAME__ for your load testing needs..
Wrong type of project '%1'.
Unable to access test variable initialization file. Make sure the specified file path is accessible: %1
Error while processing XML file containing variable initializations. Make sure the file contains valid XML of the expected format: %1
Error while gather test variable initializations. No variable initializations will be honored for this run.
Error processing license request for feature '%1'. This feature will not be available.
Setting Variable [name='%1', value='%2', source='%3', user group='%4', location='%5']
Unexpected I/O error while communicating with workbench %1
The file path specified for the Zip Utility is invalid.
Could not get the classpath for project '%1'.
Undefined
%1: Request delivered
%1: successfully added %2 to the configuration file
%1: successfully removed %2 from the configuration file
%1: %2 is already in the configuration file
%1: Request timed out
%1: Agent not ready
%1: Agent not known
%1: Unknown host exception
License type: %1
License valid: %1
Unable to replace dataset '%1' with '%2': %3.
The dataset '%1' doesn't exist.
The dataset '%1' is incompatible with existing dataset '%2'.
The regular expression you provided does not find the highlighted string. \nThe string found was: %1
Unable to attach requirements report into RQM result, because the default requirements report has been deleted. You can recreate the default reports by click restore defaults button on the Default Reports preference page.
Unexpected error while releasing system resources for test log export. This may cause an increased memory footprint, until Rational® Performance Tester is restarted.
The password saved for an encrypted column in dataset "%1" was invalid. Set a new password in the Automation Security preference page.
The feature %1 used in test %2 is not supported in the current installation/platform.
No sample time closely matches request at time=%1
A statistical adapter is missing reference to the target result.
Local on premise agent %1 not in contact with this workbench.
See Error Log for more details.
There was an error while updating the workspace after downloading remote files.
Modify majordomo.config on %1 and configure it to poll this workbench.
Remote Launch Status: %1
Project is NULL
Exception occurred while creating and unzipping project: %1
Error running schedule. Could not find schedule %1 in project %2.
Provision time (MM:SS): %1
Launch time (MM:SS): %1
Execution time (MM:SS): %1
Results transfer time (MM:SS): %1
------------------------------------\nError Dialog\n%1: %2\nConsult workspace error log ({workspace}/.metadata/.log) for further information.\n------------------------------------\n
The Usage Metrics version %1 required by the licensed component %2 is not available.
The licensing system failed to return Usage Metrics enablement for component %1.
No RTCP instance is available to report Usage Metrics. No Usage Metrics will be reported for this execution.
No RTCP instance is available to report Usage Metrics. Per license policy, execution cannot happen unless a RTCP is defined and running.
TPTP Datapools and Datasets cannot coexist in the same test. Test run aborted.
An IOException was encountered while creating the Annotation File on Driver: %1
An IOException was encountered while creating the Execution Log File on Driver: %1 :: %2
Driver %1 returned an unrecognized response: %2. The last command sent was: %3
While waiting for an acknowledgement from the Driver, an unrecognized response was received.
The workbench was waiting for an Acknowledgement from the IBM® Agent Controller on Driver %1 and none was received.
Error while processing a message from the IBM® Agent Controller.
Execution failure. No status received from location %1 in %2 seconds. Workbench memory usage at %3 percent of the configured JVM heap. Possible location or workbench overload. For more information, see the Troubleshooting section of the online help.
The Driver: %1 has encountered a communication error. Please refer to Problem Determination Log for more details. For more information, see the Troubleshooting section of the online help.
The Driver: %1 has become unresponsive, possibly due to an out-of-memory condition. At last notification this Driver was using %2 percent of its allocated memory. Please refer to the "Increasing memory allocation" Help topic for information on how to increase memory allocation. For more information, see the Troubleshooting section of the online help.
The Driver: %1 is running %2, however the user selected %3 as the Drivers operating system.
Error while transferring file on Driver: %1. Transfer FROM: %3 TO: %2
The '%1' Protocol/Feature is not supported on the %2 platform, so the Test %3 can't be executed on location %4. For more information, see the Troubleshooting section of the online help.
The operating system (%1) for location %2 is not recognized. Please use an operating system that matches or begins with the name of one of the recognized platforms: %3
No valid license key for %1 Protocol/Feature found. The Test %3 cannot be executed. For more information, see the Troubleshooting section of the online help.
Execution on the %1 Platform requires a license and no valid license key (%2) was found to enable it, so the Test %3 can't be executed on location %4. For more information, see the Troubleshooting section of the online help.
The specified operating system (%1) for location %2 is inconsistent with the actual platform (%3) running at that location. Please update the operating system to match and then try again. For more information, see the Troubleshooting section of the online help.
After deploying File: %2 to Driver: %1, %3 Byte(s) where found on the socket. Please refer to the Problem Determination Log for more details.
An IOException ocurred while deploying File: %2 to Driver: %1. Please refer to the Problem Determination Log for more details.
A SocketException ocurred while deploying File: %2 to Driver: %1. Please refer to the Problem Determination Log for more details.
An UnsupportedEncodingException ocurred while deploying File: %2 to Driver: %1 Please refer to the Problem Determination Log for more details.
An IOException ocurred while deploying File: %2 to Driver: %1.\nA possible cause is that the IBM® Agent Controller was started by a non-root user. \nThe Agent Controller needs to be started by the root user.
An InactiveAgentException has occurred while deploying to Driver: %1. Please refer to the Problem Determination Log for more details. For more information, see the Troubleshooting section of the online help.
Send RATEGENERATORS to: %1, string '%2'
The workbench received notification that the execution process on Driver %1 has terminated.
Communication with Driver %1 has been lost, possibly due to an out-of-memory condition. At last notification this Driver was using %2 percent of its allocated memory. Please refer to the "Increasing memory allocation" Help topic for information on how to increase memory allocation. For more information, see the Troubleshooting section of the online help.
Error during initialization of annotation transfer progress listener.
Non-fatal internal exception occurred during code generation optimization. Code generation will not use meta-cache.
The license required for the '%1' Protocol/Feature and %2 virtual users could not be checked out, so the Test %3 cannot be executed. For more information, see the Troubleshooting section of the online help.
The '%1' Protocol/Feature is disabled due to a licensing configuration error.
%1 Failure checking out license for '%2' Protocol/Feature and %3 virtual users. The Test %4 cannot be executed.
%1 The '%2' Protocol/Feature is not supported on the %3 platform, so the Test %4 can't be executed on location %5.
Timed out after %1 seconds while waiting for the license server. Ensure that network connectivity to the license server exists and that the license server is running. For more information, see the Troubleshooting section of the online help.
A hang has been avoided during execution history receipt with %1 by a forceful load test executor state change
A session on driver %1 did not release promptly. Please check the agent controller.
The testLog event loader thread in the workbench has ended before processing all testLog events from %1. The testLog may be incomplete.
The test executor for %1 has been artificially set to HISTORY_COMPLETE because the testLog event loader thread is not longer running.
Remote debug never received event %1, process exit value %2
Temporary dataset file %1 not created.
Temporary dataset data are not generated: %1
An InactiveAgentException has occurred attempting to send [%1] to driver %2
The CommandHandler for %1 has encountered an exception while processing %2
Driver %1 has reported a NOK. The last command sent to that driver was: %2
Driver %1 has reported a NOK with the message: %2. The last command sent to that driver was: %3
Driver %1 has reported a %2 status
The AgentCommandListener for %1 has encountered an exception while processing %2
Driver %1 has reported that it is no longer receiving messages from the workbench. The previous message received from this driver, %2 milliseconds ago, was %3. At present no commands have been sent to this driver.
The ResponseHandler for %1 has encountered an exception while processing %2
Failure attempting to launch test execution.
The process executing the test has ended unexpectedly.
The communication path for returning test results from %1 has not been established. Check network connectivity between that machine and the workbench including any firewalls.
%1% %2/%3 files %4/%5 bytes deployed
Rational® Performance Tester has detected the presence of an invalid Virtual Tester license key. If you have recently upgraded Rational Performance Tester, note that this is a new check performed by release 7.0.1 or later, and instructions for replacing invalid Virtual Tester license keys should have already been sent to you. You must replace all invalid Virtual Tester license keys before Rational Performance Tester will allow execution of a schedule run that requires a Virtual Tester license. If you need further assistance, please contact your IBM® sales representative or Technical Support to replace the invalid Virtual Tester license key(s).
The specified license server's version level is not compatible with this version of Rational® Performance Tester.
Unable to verify system time.
Unable to locate license directory.
License has expired.
Invalid license file.
Unable to find a license supporting %1 virtual users.
Unable to retrieve data from the test.
Failed to store test data into annotations.
Unable to open test annotation to read data.
Failed to create a temporary file to save test data.
Failed to load test. Path %1 is invalid.
Failed adding element from an un-registered feature %1.
Cannot load a test created by a future version %1. Please upgrade your install.
Test %1 is of an older version %2.
Error creating metadata cache.
Error reading metadata cache for %1.
Failed to add annotation to execution history for file %1
Unexpected error in data validity check of LoadTimeEObjectConsumer
Failed to add properties to parent id %1
Failed to delete temp file %1
Unexpected exception in container complete loader. Heap growth likely.
Execution Variables - Output
Unable to start the agent communication service because of an error: %1. RPT will not be able to execute schedules.
RPT is unable to execute a schedule because one of the ports(%1) it uses to communicate with the agents has been taken by another RPT(or other server) process. Ensure only one RPT instance is running.
Unable to stop the agent communication service because of an error: %1
Agent communication service listening on ports(%1)
The dataset service failed to shutdown cleanly. Please shutdown the java process that contains dataset-service in its command line.
The combination of transformer and feature you have selected is invalid. Transformer (%1) was not expecting data type (%2).
The combination of feature and transformer you have selected is invalid. Feature (%1) was not expecting data type (%2) to be returned by transformer (%3).
Transformer (%1) has experienced a fatal error. Additional information (%2).
Feature (%1) has experienced a fatal error. Additional information (%2).
No class can be found for the specified transformer id (%1). Please check to make sure you have installed this transformer.
Class definition missing. Please add jar that contains definition of (%1) to the classpath of the test project.
The transformation raised a GWT serialization exception: %1
The Silverlight decoder raised an exception: %1
The Silverlight encoder raised an exception: %1
The GraniteDS transformer made an error when encoding or decoding: %1
The time to extract references seems excessive. It was %1 milliseconds.
Loop iteration started late by %1 millseconds
An exception occurred while logging an event to Jaeger.
Start of RPT project resolve. Repository=<%1>, Bootstrap=<%2>
Attempting to resolve asset=<%1>
End of RPT project resolve. No detected errors
Downloaded asset %1 from remote repository, local asset created.
Using local cached version of asset %1.
RPT testsuite=<%1> found the following dependencies=<%2>
Exception occurred while uploading Mobile report.
An error occurred when generating the HTML/zip report.
Adapter unable to start test because Rational® Performance Tester is already executing a test.
Error encountered parsing RQM adapter preferences: %1. Please enter proper credentials in the Eclipse Quality Adapter preference page (Windows->Preferences).
Project <%1> could not be found during RQM import.
Test log is unavailable, no test results returned to RQM.
Statistics log is unavailable, no statistic results returned to RQM: %1
Display unavailable, no Rational® Performance Tester HTML reports will be attached to RQM execution results.
Start RQM Execution Request Project=%1 Name=%2
Start RQM Import Request Project=%1
End RQM Execution Request
End RQM Import Request
Unable to interpret RQM configuration file %1. If file was hand edited make sure parameters are the correct format. If you are unable to get this file into the correct format, please erase and re-configure.
Invalid RQM connection parameter: %1. Adapter was not launched.
Adapter was stopped while a test was executing. The results of this test may be unreliable.
Adapter was stopped while preparing to run an RQM script. There are no results for the attempted test script run.
Testsuite '%1' or project '%2' does not exist. Ensure workspace started by adapter contains project and testsuite.
%1 Reason: %2
The RQM Adapter has been disconnected.
The RQM Adapter has stopped.
Unexpected error occurred while executing RQM test script.
Unexpected error occurred while processing an import request from RQM.
Error occurred while update the run status back to the RQM server. This may cause the RQM test progress page to contain inaccurate data.
Unable to attach the following file to the RQM results. This may cause the attached HTML report not to render correctly. File name: %1
Error occurred while registering the adapter: %1.
Error occurred setting the default adapter name. Please set the name in the Eclipse Quality Adapter preference page (Windows->Preferences).
Multiple test runs were detected when the stop request was received from RQM.
Was unable to perform stop request from RQM. Likely the run was already shutting down when the request came in.
Request to stop the test is being delayed until the appropriate run state is reached.
A request to stop the currently running test has been received by RQM.
Successfully issue a stop command to the running test. Please wait for the test to end.
Error attempting to stop a test.
Unable to create directory %1 no further information. Ensure user has permission to create directory in that location.
Error occurred while attempting to automatically update pre-8.0 asset %1 for RQM execution.
RQM remote resource access is not supported for pre-8.0 SOA assets. Please update your entire SOA project to 8.0 or greater before sharing.
Launch was aborted: %1
Unable to download remote asset %1 into local workspace. Remote repository %2. Ensure RQM system has connectivity to the remote repository and the file exists.
Unable to browse %1 in remote repository %2. Ensure RQM system has connectivity to the remote repository and the directory exists.
Error occurred reading the adapter connection file.
Error occurred saving the adapter connection file.
Unable to complete import operation because the specified path is not in the adapters workspace. Try specifying the only the project name.
The specified script <%1> is not in the workspace currently being used by the adapter. You can only execute scripts which are in the adapters workspace.
The script path specified by RQM does not seem to be valid. Please ensure the RQM test script has a script path which contains the project and script name.
Run verdict is inconclusive because no performance requirements exist in the last user stage for the associated VU Schedule.
Run verdict is inconclusive because there are zero performance requirements in the last user stage of the associated VU Schedule.
No time range was generated for the user stage of the associated VU Schedule. Performance requirements reported to RQM will be based on the default time range.
Error occurred while setting the RQM project area. Make sure a valid project area is specified on the Quality Manager Adapter preference page. The adapter is attempting to connect to RQM using the default project area.
Error occurred while retrieving list of project areas. Please verify Quality Manager connection information. See error log for more details.
Error occurred calling for the web analytics dash-board link.
Error occurred while translating RQM server execution variables to Rational® Performance Tester.
Error connecting RTW adapter and successful connecting RPT adapter. This suggest RQM does not support RTW script type introduced in 4.0.3. If RTW adapter is not required it can get disabled by adding -DrtwStartAdapter=false in eclipse.ini.
Unable to interpret expression <%1> from RQM control file <%2>. Ignoring. Reason <%3>
Unable to browse to <%1>. Make sure it exist on the shared location.
Error occurred while completing test generation
Error occurred while processing a packet at test generation
WSDL Exception raised while processing WSDL source
Error while generating test from Axis recording
Error occurred while setting classpath entry for recorder
I/O exception occurred while resolving keystore or truststore path
Error occurred while launching web services HTTP proxy
Error occurred while launching axis client recorder agent
Exception thrown while creating a wizard page control
Exception thrown while parsing URL: %1
Exception thrown while finishing the axis recording wizard
Exception thrown while looking for an available port
Exception thrown while adding SOA Tester certificate to the trustore %1
A proxy authorization %1 is used without any proxy
No free name can be found; reusing %1
Resource file %1 not found in workspace %2
Workspace location cannot be determined
Cannot retrieve the operation name from the envelope %1
Core exception thrown using org.eclipse.debug.core plugin
Exception thrown during launch configuration update
Exception thrown while resolving a bundle entry path
Exception thrown while identifying localhost IP address
Exception thrown while creating a substitution: %1
Exception thrown while creating a reference: %1
Unknown format. Skipping the test generation for: %1
Skipped call: %1
Skipped request: It could be that provided password was not ok
Attachments not generated.
Could not find project for URI: %1
Loading XSD Schema failed: %1
Error while generating test from Generic Service Client: Can't show wizard
An error has occurred: %1
Unhandled Security Algorithm '%1'
Unable to serialize data
Unable to deserialize data
Unable to open editor for '%1'
Parse Error in '%1'
Unable to create resource '%1'
Failed to export source text '%1'
A connection error occurred on '%1', please check the URL or the network configuration
Exception raised during data harvest execution
Exception raised during data substitution execution
Exception raised on harvest data management
Exception raised on substitution data management
Exception raised during WebSocket read action
Exception raised during WebSocket write action
Unable to get WebSocket connection
Unable to read from a closed connection
An exception occurred in %1
Information: %1 (%2)
Warning: %1 (%2)
An error occurred while importing external schema %1
Unable to correlate automatically
An exception %1 occurred in %2
Exception raised during WebSocket connection creation.
Unknown Segment Offset/Length for Segmented Dataset: %1
Bad Dataset Mode: %1
Dataset not initialized: %1
End of non-wrapped dataset reached: %1
Dataset with multiple Equivalence Classes cannot be segmented
segmented DatapoolMap null: %1
No registered data correlation handler for this IKAction
Pattern matching failed for: regex (%1) str (%2)
Skipping substitution, reference value was null. original string: (%1) offset: (%2)
Data Correlation: Failed Substitution\nReference[%1]\nSubstitution[%2]\n\nDetails:\n\nA failed reference occurred in a prior request. Since the reference named [%3] was null, we were unable to substitute a new value for the substituter named [%4], original string [%5] at offset [%6] and this request may have failed. Please inspect prior requests for the reference failure and corrective guidance to avoid this in the future.\n\nFor more information search the help for the data correlation topics.
Data Correlation: Failed Extraction\nReference[%1]\n\nDetails:\n\nWe were unable to extract the value for the reference named [%2], with the regular expression [%3]. This could mean a later request will fail. Please compare the response in the test log to the corresponding response in the test to look for differences that could cause this failure. These differences are often due to problems with the request and may be caused by missing or incorrect correlations.\n\nFor more information search the help for the data correlation topics.
Dataset %1 is accessed using different dataset modes by different tests.
Setting variable %1 to value %2.
Engine shutdown problem joining workers
Failed to report exception
Schedule failed to load
Unable to create test
Setting log level to %1
Attempt to add object to Schedule which is not a UserGroup
Virtual User %1 experienced error %2
Connect timeout for action %1 (%2) user %3
Read timeout for action %1 (%2) user %3
Connect exception for action %1 (%2) user %3
Read exception for action %1 (%2) user %3
Iterating over keys exception
CancelledKeyException
NullPointerException
UserGroup exception
User Group %1 does not implement createTesterWorkload()
Worker caught throwable
Connection leak, I/O state %1
Exception finishing connection for action %1 (%2) user %3
Finish read get buffer interrupted for action %1 (%2) user %3
Finish read exception for action %1 (%2) user %3
Engine thread startup exception
Engine request to report exception
Exception creating cache file, cacheFileName: %1, extension: %2, dir: %3
User %1 experienced exception %2
User %1 caught exception trying to report severe error.
Engine hard stop after %1 second timeout
%1 received request to stop
Forced stop of action %1
No IP address was found for the local host
Ignoring invalid network interface %1
Could not find any usable network interfaces
SyncPointSubsystem Unknown sync point: %1
%1 STOPUSERS users=%2 stagger=%3 timelimit=%4 active users=%5
%1 had %2 non-sampled users asked to stop active users=%3
%1 had %2 sampled users asked to stop
%1 after wait for compliance active users=%2 target=%3
%1 abandon user %2
%1 abandoned %2 users
%1 end stop %2 users SUCCESS active users=%3
%1 end stop %2 users FAIL active users=%3
%1 occurred in %2. Message: %3
Exception while reading test variable initialization file: %1
Exception while initializing virtual users test variables.
Unable to get Kerberos ticket from KDC for server %1.
Failed to load test from '%1' due to exception: %2
%1 terminated due to exception: %2
IKAction: %1 (%2) caught Exception in preFinish() for %3 (%4)
IKAction: %1 (%2) caught Exception in postFinish() for %3 (%4)
KernelChannel connect(), exception while trying to bind to local address %1: %2
An error occurred while attempting to handshake with the server using protocol %1 and cipher suite %2. This type of failure is often related to a mismatch between the requested protocol or cipher suite and the ones the server is expecting or may be related to a server's request for a client digital certificate. If the server is configured to accept only 256-bit ciphers, contact IBM® Support for information on US export restrictions related to the exportation of strong encryption. Playback of tests utilizing these ciphers is not supported.
The digital certificate RCS file '%1' was not found or was corrupt: %2
digital certificate alias
The server rejected the client's digital certificate.
The server closed the connection abruptly. This is probably due to an overloaded server or to a problem negotiating a digital certificate or cipher suite. Check the web server's SSL error log for more details.
Schedule or Test not found. May not have compiled. - %1
Runner Exception occurred
Communications Error: Invalid Logging Level
Communications Error: Invalid TestLog Level for %1 events
Communications Error: Invalid Statistics Level or Interval
Runner Exception occurred - See problem determination log
Communications Error: Invalid Dataset information
Communications Error: No communication from the workbench in %1 milliseconds. For more information, see the Troubleshooting section of the online help.
Attempt to change statistic interval ignored.
Think: requested time %1 milliseconds, actual time %2 milliseconds
Delay: requested time %1 milliseconds, actual time %2 milliseconds
Schedule completed. See Performance Report, Verification Points Report, and/or Percentile Report to further evaluate the results of this run according to your success criteria.
Communications Error: Invalid Stop timeout
Additional events from %1
Communications Error: Invalid RunStagger information for %1 (pairCount)
Communications Error: Invalid RunStagger information for %1 (pair %2)
Failed to start users for user group: %1.
Additional execution history events from %1 are available, but they have been stored separately upon user request. See file %2. Refer to the most current version of the product release notes for information on how to access and view them.
Failed to write message to workbench [%1]
Failed to remove users for user group: %1.
Failed to add users for userGroup: %1 numUsers=[%2] startId=[%3]
Failed to add users because the runner is not in a runnable state.
failed to add desired number of users
failed to reach target number of users ramping down
not runnable or command failed
failed to set the DataView state of user %1[%2] to %3.
DataView command %1 is not yet implemented.
DataView command %1 is not recognized.
MessageEventFilter command parsing error in token %1[%2] of command [%3]
The testLog message event filter specified by [%1] cannot be constructed. This filter element will be ignored.
Operating System Info: name [%1] architecture [%2] version [%3]
Cannot open execution history cache file [%1], execution history will not be cached
Error closing execution history cache file [%1]
Error reading %1 bytes from execution history cache file [%1]
Error writing %1 bytes to execution history cache file [%2]
Error opening execution history cache file [%1] for reading
Error testing execution history cache file [%1] for available input
Unexpected EOF reading %1 bytes from execution history cache file [%2]
Exception processing execution history event
Error reading execution history cache file [%1]
Error writing to TestLog cache file [%1]
Error closing TestLog cache file [%1]
Cannot open testLog cache file [%1] for random access writing, the testLog may contain bad data.
Error removing testLog event from cache file [%1]. Writing %2 bytes at offset %3.
Error writing to TestLog [%1]
Error opening execution history annotation file [%1]
Error writing %1 bytes to execution history annotation file [%2]
Error flushing/closing history annotation file [%1]
Error deleting history annotation file [%1]
Warning: Statistics delivery thread running behind statistics interval by %1 milliseconds
Warning: Statistics delivery thread over slept by %1 milliseconds
Error: Statistics delivery thread over slept by %1 milliseconds
Error: Statistics collection time too long: %1 bytes %2 milliseconds
Warning: Statistics collection time too long: %1 bytes %2 milliseconds
Error: Statistics write time too long: %1 bytes %2 milliseconds
Error: Could not create agent measurements file %1.
Error: Statistics collection thread was interrupted
Error: A severe error occurred when processing statistics.
Error: A severe error occurred when sending statistics.
Error: A severe error occurred when closing statistics.
Statistics sub-system error: %1
Statistics sub-system warning: %1
Statistical counter descriptors file not found: %1.
Statistics sub-system message: %1
Problem in statistical counter descriptors file: %1.
Submitted value %1 is out of range of allowed values for the counter type %2.
In order to use this method, the runtime type of the counter must be either STATIC or RATE.
Mismatch between runtime type %1 and static counter type %2.
No static declaration found for counter %1.
Attempt to create an undeclared counter %1 (type %2) over a declared counter of a different type (%3).
Test execution completed with no reported problems
%1 ERROR verdicts reported
%1 FAIL verdicts reported
%1 INCONCLUSIVE verdicts reported
All reported verdicts PASSed
%1 ERROR verdict reported
%1 FAIL verdict reported
%1 INCONCLUSIVE verdict reported
%1 FAIL verdict roll-up
%1 ERROR verdict roll-up
%1 INCONCLUSIVE verdict roll-up
%1 PASS verdict roll-up
%1 ERROR verdicts reported from driver %2
%1 FAIL verdicts reported from driver %2
%1 INCONCLUSIVE verdicts reported from driver %2
%1 ERROR verdict reported from driver %2
%1 FAIL verdict reported from driver %2
%1 INCONCLUSIVE verdict reported from driver %2
duration
%1 was successfully invoked. This does not indicate the pass/fail verdict of the test itself, only that the invocation of the test was successful. Expand to inspect verdicts.
%1 was invoked. This does not indicate the pass/fail verdict of the test itself, only that the invocation of the test was successful. No verdicts will be reported from the test.
The %1 testLog level was pushed from %2%3 to %4%5.
The %1 testLog level was popped from %2%3 to %4%5.
The %1 testLog level was changed from %2%3 to %4%5.
Transaction [%1] started %2 milliseconds after start of test run.
Transaction [%1] stopped %2 milliseconds after start of test run. Elapsed time: %3 milliseconds.
Transaction [%1] aborted.
Transaction [%1] is already started.
Transaction [%1] has not been started.
Execution Variables - Input
Null user group name.
Unable to find target loop named '%1'. Error handler did not complete properly.
Error encountered while loading Native Library: %1
A required customer-supplied file was not found. Please check the "external_files" folder and your installation instructions for: %1
Unable to apply dataset swap: %1
Unable to apply Open Tracing context. The root Jaeger span will be unparented. %1
Transaction times for this run do not include failing transactions, according to workbench Test Execution preferences.
Environment variable INTEGRATION_TESTER_AGENT_HOME not set to Rational® Integration Tester Agent installation location, or does not contain expected RunTests(.exe) program.
Error unzipping __IT_PRODUCT_NAME__ project.
__IT_PRODUCT_NAME__ library not found.
Error processing messages received form the __IT_PRODUCT_NAME__ client.
Some tag values are missing.
Open __IT_PRODUCT_NAME__ resources has been disabled in Test > __IT_PRODUCT_ACRONYM__ Integration preferences
Missing message for log entry '{0}' in class: {1}
Cannot get Log key '{0}': SecurityException raised
Cannot initialize Log key '{0}'
Warning: field '{0}' is not defined in class: {1}
Warning: cannot get check message versus log key mapping for '{0}' of class {1}, SecurityException raised
Unexpected exception, please check Error Log view: {0}
unexpected exception
Error getting persistent property '{0}'
Error setting persistent property '{0}'
Cannot reload resource '{0}'
Failed to encode model to clipboard.
Failed to decode model from clipboard.
None of the attribute providers own attribute id '{0}'.
Missing IRuleUIProvider extension point for '{0}'
Missing IConditionUIProvider extension point for '{0}'
Cannot save editor '{0}'
Missing IRulePassUIProvider extension point for '{0}'
Missing IRuleArgumentUIProvider extension point for '{0}'
Missing IRuleArgumentContainerUIProvider extension point for '{0}'
Try rule failed
Try rule failed: '{0}'
Cannot load file '{0}'
You can find the additional error messages.
This guide describes, additional topics to gain more knowledge about Rational® Performance Tester.
You can find the link to view or download the content of the release notes, system requirements, and persona guides of Rational® Performance Tester as a PDF file.
You can take certain actions to ensure that your installation is secure, customize your security settings, and set up user access controls.
This document provides information about copyright, trademarks, terms and conditions for the product documentation.