- PRXE0101W
%1 terminating due to exception: %2
- PRXE4943W
Transaction [%1] has been aborted.
- PRXE4951I
User group [%1] was not found.
- RMSE0003W
RMSE0003W There are currently no selected counters for the source named {0}.
- RMSE0004W
RMSE0004W The source named {0} is no longer available.
- RMSE0005W
RMSE0005W The source named {0} is reporting the error message {1}.
- RMSE0006W
The server does not support resource monitoring labels.
- RPAC0001W
The JAR %1 referenced in preferences could not be found. Preferences on the cloud workbench will be cleared.
- RPHD1032E
Error occurred while instructing __PT_ACRONYM__ 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.
- RPHD1034E
Error occurred while instructing __PT_ACRONYM__ 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.
- RPHE0001E
example of translatable error message %1
- RPHE0010W
Unknown authentication scheme '%1' discovered in HTTP 401 response, ignoring.
- RPHE0011W
Unrecognized authentication header '%1' discovered in HTTP 401 response, ignoring.
- RPHE0012W
No authentication headers found in HTTP 401 response, ignoring.
- RPHE0013W
The server requested NTLM authentication but no NTLM authentication context was supplied with this request. Authentication is not possible.
- RPHE0014W
NTLM authentication failed for this request. Verify that the NTLM authentication context values for this request are correct.
- RPHE0100W
Host name '%1' can not be resolved.
- RPHE0101W
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.
- RPHE0102W
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.
- RPHE0103W
Authentication failed during HTTP playback to web-server '%1' retrieving URI '%2'. Probable cause: username '%3' and/or password '%4' incorrect.
- RPHE0104W
Exception occurred during attempt to write request to web-server '%1' getting url '%2'. Explanation: %3
- RPHE0105W
General un-handled exception occurred during socket I/O read from web-server '%1' retrieving URI '%2'. Explanation message: '%3'.
- RPHE0106W
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.
- RPHE0107W
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.
- RPHE0108W
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.
- RPHE0109W
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.
- RPHE0110W
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.
- RPHE0111W
Authentication failed accessing proxy-server '%1' retrieving URI '%2'. Probable cause: username '%3' and/or password '%4' incorrect.
- RPHE0112W
An error occurred during decoding of content received from web-server '%1' attempting to retrieve URI '%2'. Explanation message: '%3'.
- RPHE0113E
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.
- RPHE0113W
An error occurred during encoding of an annotated execution history event property. Explanation message: '%1'.
- RPHE0114E
An error was encountered during transform of response data. %1
- RPHE0114W
Exception occurred during attempt to write request to proxy-server '%1' getting URL '%2' on host '%3'. Explanation: %4.
- RPHE0115E
An error was encountered during un-transformation of request data. %1
- RPHE0115W
Unable to successfully establish a connection to web-server '%1' retrieving URI '%2'. Web-server closing the connection after connection was just established.
- RPHE0117W
Unexpected exception occurred during connection close to web-server '%1' retrieving URI '%2'. Explanation: %3.
- RPHE0118W
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.
- RPHE0119E
IP aliasing is enabled but no IP address was found for virtual user %1. Verify correct network interface name(s) are specified.
- RPHE0120E
Exception occurred during attempt to connect to proxy-server '%1' getting URL '%2' on host '%3'. Explanation: %4.
- RPHE0121E
Unable to authenticate with the proxy-server. Possible solution: re-record test due to possible proxy-server '%1' authentication changes.
- RPHE0122W
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.
- RPHE0123W
Infinite redirection loop detected getting URL '%1'. If this is expected and understood increase RPT_VMARGS rptMaxRedirection parameter. Redirected history %2
- RPHE0124W
Unexpected server redirection occurred getting URL '%1'. We were redirected to the same URI which issued this request. Redirected history %2
- RPIB0007E
%1
- RPKG0090E
Exception thrown while creating connection variables
- RPKG0100E
Exception thrown by the launch configuration core
- RPKG0101E
Exception thrown during an update to a launch configuration
- RPKG0110E
The data source type %1 is not expected
- RPSF0172E
__PT_ACRONYM__/SAP: Unable to start SAP GUI, please check SAP GUI installation.
- RPTA0000W
%1
- RPTA0001I
Setting the log verbosity left me with %1 users
- RPTA0002E
A Test cannot be launched on the specified Driver
- RPTA0003E
%1
- RPTA0004E
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.
- RPTA0009E
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.
- RPTA0010E
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.
- RPTA0011E
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.
- RPTA0012E
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.
- RPTA0013E
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.
- RPTA0014E
A Test could not be launched on Driver: %1. The Test Execution Framework encountered an Exception. This is an internal error, please contact support.
- RPTA0015E
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 __VENDOR_NAME__ Agent Controller must have authority to this directory.\n4. An error was encountered while deploying to this directory.
- RPTA0016E
An error has been encountered while launching the test. A required dataset %1 is missing or invalid in your project.
- RPTA0017E
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.
- RPTA0018E
ready
- RPTA0019E
not ready on port
- RPTA0020E
Check Agents Failed
- RPTA0021E
%1 deployment directory %2 format not compatible for operating system %3. For more information, see the Troubleshooting section of the online help.
- RPTA0023E
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.
- RPTA0024E
Exception encountered adding or removing users.
- RPTA0025E
The schedule has no user group.
- RPTA0026E
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.
- RPTA0025I
Run Completed (%1)
- RPTA0026I
Run Terminated (%1)
- RPTA0027I
%1: %2
- RPTA0031E
Location template file %1 is not found (referenced from location file %2)
- RPTA0032I
Found location template [%1] for [%2] (instances found: %3)
- RPTA0033I
%1 remote location(s) associated with location template [%2]
- RPTA0034E
Cannot change stage duration if Until Finished specified
- RPTA0035E
Duration time specified is less than what has already elapsed
- RPTA0036E
Schedule must be in the Running state to change stage duration
- RPTA0037E
Agent %1 not ready, time of last contact: %2
- RPTA0038E
No successful contact
- RPTA0039E
Unknown host '%1'
- RPTA0040E
Unable to complete deployment to agents because of an unexpected error in the publish phase. %1
- RPTA0041E
%1
- RPTA0042E
Agent version %1 incompatible on host %2. Minimum agent version %3 required.
- RPTA0043E
Error encountered
- RPTA0100W
Failed to delete file %1
- RPTA0518E
An error has been encountered while launching the test. A required dataset %1 is missing or invalid in your project.
- RPTC0003E
Wrong type of project '%1'.
- RPTC0004E
Unable to access test variable initialization file. Make sure the specified file path is accessible: %1
- RPTC0005E
Error while processing XML file containing variable initializations. Make sure the file contains valid XML of the expected format: %1
- RPTC0006E
Error while gather test variable initializations. No variable initializations will be honored for this run.
- RPTC0008I
Setting Variable [name='%1', value='%2', source='%3', user group='%4', location='%5']
- RPTC00020E
Unexpected I/O error while communicating with workbench %1
- RPTC1001W
The file path specified for the Zip Utility is invalid.
- RPTC1002W
Could not get the classpath for project '%1'.
- RPTC1009I
Undefined
- RPTC1011I
%1: Request delivered
- RPTC1012I
%1: successfully added %2 to the configuration file
- RPTC1013I
%1: successfully removed %2 from the configuration file
- RPTC1014I
%1: %2 is already in the configuration file
- RPTC1015I
%1: Request timed out
- RPTC1016I
%1: Agent not ready
- RPTC1017I
%1: Agent not known
- RPTC1018I
%1: Unknown host exception
- RPTC1019I
%1: %2
- RPTC1020I
License type: %1
- RPTC1021I
License valid: %1
- RPTC1030E
Unable to replace dataset '%1' with '%2': %3.
- RPTC1031E
The dataset '%1' doesn't exist.
- RPTC1032E
The dataset '%1' is incompatible with existing dataset '%2'.
- RPTE0005W
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.
- RPTE0011W
Unexpected error while releasing system resources for test log export. This may cause an increased memory footprint, until HCL OneTest™ Performance is restarted.
- RPTE0147E
The password saved for an encrypted column in dataset "%1" was invalid. Set a new password in the Automation Security preference page.
- RPTH0130I
No sample time closely matches request at time=%1
- RPTH049E
A statistical adapter is missing reference to the target result.
- RPTI0069E
Local on premise agent %1 not in contact with this workbench.
- RPTI0070E
See Error Log for more details.
- RPTI0071I
There was an error while updating the workspace after downloading remote files.
- RPTI0072E
Modify majordomo.config on %1 and configure it to poll this workbench.
- RPTI0072I
Remote Launch Status: %1
- RPTI0073E
Project is NULL
- RPTI0074E
Exception occurred while creating and unzipping project: %1
- RPTI0075E
Error running schedule. Could not find schedule %1 in project %2.
- RPTI0110I
Provision time (MM:SS): %1
- RPTI0111I
Launch time (MM:SS): %1
- RPTI0112I
Execution time (MM:SS): %1
- RPTI0113I
Results transfer time (MM:SS): %1
- RPTI0141E
------------------------------------\nError Dialog\n%1: %2\nConsult workspace error log ({workspace}/.metadata/.log) for further information.\n------------------------------------\n
- RPTI0142E
The Usage Metrics version %1 required by the licensed component %2 is not available.
- RPTI0143E
The licensing system failed to return Usage Metrics enablement for component %1.
- RPTI0144W
No RTCP instance is available to report Usage Metrics. No Usage Metrics will be reported for this execution.
- RPTI0145E
No RTCP instance is available to report Usage Metrics. Per license policy, execution cannot happen unless a RTCP is defined and running.
- RPTI0146E
TPTP Datapools and Datasets cannot coexist in the same test. Test run aborted.
- RPTJ0063E
An IOException was encountered while creating the Annotation File on Driver: %1
- RPTJ0075E
An IOException was encountered while creating the Execution Log File on Driver: %1 :: %2
- RPTJ1002E
Driver %1 returned an unrecognized response: %2. The last command sent was: %3
- RPTJ1003E
While waiting for an acknowledgement from the Driver, an unrecognized response was received.
- RPTJ1004E
The workbench was waiting for an Acknowledgement from the __VENDOR_NAME__ Agent Controller on Driver %1 and none was received.
- RPTJ1005E
Error while processing a message from the __VENDOR_NAME__ Agent Controller.
- RPTJ1006E
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.
- RPTJ1007E
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.
- RPTJ1008E
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.
- RPTJ1009E
The Driver: %1 is running %2, however the user selected %3 as the Drivers operating system.
- RPTJ1010E
Error while transferring file on Driver: %1. Transfer FROM: %3 TO: %2
- RPTJ1011E
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.
- RPTJ1012E
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
- RPTJ1013E
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.
- RPTJ1015E
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.
- RPTJ1016E
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.
- RPTJ1017E
An IOException ocurred while deploying File: %2 to Driver: %1. Please refer to the Problem Determination Log for more details.
- RPTJ1018E
A SocketException ocurred while deploying File: %2 to Driver: %1. Please refer to the Problem Determination Log for more details.
- RPTJ1019E
An UnsupportedEncodingException ocurred while deploying File: %2 to Driver: %1 Please refer to the Problem Determination Log for more details.
- RPTJ1020E
An IOException ocurred while deploying File: %2 to Driver: %1.\nA possible cause is that the __VENDOR_NAME__ Agent Controller was started by a non-root user. \nThe Agent Controller needs to be started by the root user.
- RPTJ1021E
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.
- RPTJ0121I
Send RATEGENERATORS to: %1, string '%2'
- RPTJ1022E
The workbench received notification that the execution process on Driver %1 has terminated.
- RPTJ1023E
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.
- RPTJ1024E
Error during initialization of annotation transfer progress listener.
- RPTJ1025I
Run Completed (%1)
- RPTJ1026I
Run Terminated (%1)
- RPTJ1030E
Non-fatal internal exception occurred during code generation optimization. Code generation will not use meta-cache.
- RPTJ1041E
The '%1' Protocol/Feature is disabled due to a licensing configuration error.
- RPTJ1042E
%1 Failure checking out license for '%2' Protocol/Feature and %3 virtual users. The Test %4 cannot be executed.
- RPTJ1043E
%1 The '%2' Protocol/Feature is not supported on the %3 platform, so the Test %4 can't be executed on location %5.
- RPTJ1044E
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.
- RPTJ1100I
A hang has been avoided during execution history receipt with %1 by a forceful load test executor state change
- RPTJ1101E
A session on driver %1 did not release promptly. Please check the agent controller.
- RPTJ1102W
The testLog event loader thread in the workbench has ended before processing all testLog events from %1. The testLog may be incomplete.
- RPTJ1103W
The test executor for %1 has been artificially set to HISTORY_COMPLETE because the testLog event loader thread is not longer running.
- RPTJ1104E
Remote debug never received event %1, process exit value %2
- RPTJ1141E
Temporary dataset file %1 not created.
- RPTJ1142E
Temporary dataset data are not generated: %1
- RPTJ1200W
Failed to delete file %1
- RPTJ1220E
An InactiveAgentException has occurred attempting to send [%1] to driver %2
- RPTJ1221E
The CommandHandler for %1 has encountered an exception while processing %2
- RPTJ1240E
Driver %1 has reported a NOK. The last command sent to that driver was: %2
- RPTJ1241E
Driver %1 has reported a NOK with the message: %2. The last command sent to that driver was: %3
- RPTJ1242E
Driver %1 has reported a %2 status
- RPTJ1244E
The AgentCommandListener for %1 has encountered an exception while processing %2
- RPTJ1245E
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.
- RPTJ1261E
The ResponseHandler for %1 has encountered an exception while processing %2
- RPTJ1270E
Failure attempting to launch test execution.
- RPTJ1271E
The process executing the test has ended unexpectedly.
- RPTJ1280E
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.
- RPTJ1400I
%1% %2/%3 files %4/%5 bytes deployed
- RPTK0000I
%1
- RPTK1001E
__PT_ACRONYM__ has detected the presence of an invalid Virtual Tester license key. If you have recently upgraded __PT_ACRONYM__, 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 __PT_ACRONYM__ will allow execution of a schedule run that requires a Virtual Tester license. If you need further assistance, please contact your __VENDOR_NAME__ sales representative or Technical Support to replace the invalid Virtual Tester license key(s).
- RPTK1016E
The specified license server's version level is not compatible with this version of __PT_ACRONYM__.
- RPTK1019E
Unable to verify system time.
- RPTK1020E
Unable to locate license directory.
- RPTK1021E
License has expired.
- RPTK1022E
Invalid license file.
- RPTK1023E
Unable to find a license supporting %1 virtual users.
- RPTL0001W
Unable to retrieve data from the test.
- RPTL0002W
Failed to store test data into annotations.
- RPTL0003W
Failed to attach the annotation to the test.
- RPTL0004W
Unable to open test annotation to read data.
- RPTL0005W
Failed to create a temporary file to save test data.
- RPTL0006W
Failed to load test. Path %1 is invalid.
- RPTL0007W
Failed adding element from an un-registered feature %1.
- RPTL0008E
Cannot load a test created by a future version %1. Please upgrade your install.
- RPTL0009I
Test %1 is of an older version %2.
- RPTL0010E
Error creating metadata cache.
- RPTL0011E
Error reading metadata cache for %1.
- RPTR0000W
%1
- RPTR0001W
Failed to add annotation to execution history for file %1
- RPTR0002W
Unexpected error in data validity check of LoadTimeEObjectConsumer
- RPTR0003W
Failed to add properties to parent id %1
- RPTR0004W
Failed to delete temp file %1
- RPTR2001E
Unexpected exception in container complete loader. Heap growth likely.
- RPTR2003W
Execution Variables - Output
- RPTS1000E
Unable to start the agent communication service because of an error: %1. RPT will not be able to execute schedules.
- RPTS1002E
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.
- RPTS1510E
Unable to stop the agent communication service because of an error: %1
- RPTS1001I
Agent communication service listening on ports(%1)
- RPTX0001E
The combination of transformer and feature you have selected is invalid. Transformer (%1) was not expecting data type (%2).
- RPTX0002E
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).
- RPTX0003E
Transformer (%1) has experienced a fatal error. Additional information (%2).
- RPTX0004E
Feature (%1) has experienced a fatal error. Additional information (%2).
- RPTX0005E
No class can be found for the specified transformer id (%1). Please check to make sure you have installed this transformer.
- RPTX0006E
Class definition missing. Please add jar that contains definition of (%1) to the classpath of the test project.
- RPTX0007E
The transformation raised a GWT serialization exception: %1
- RPTX0008E
The Silverlight decoder raised an exception: %1
- RPTX0009E
The Silverlight encoder raised an exception: %1
- RPTX0010E
The GraniteDS transformer made an error when encoding or decoding: %1
- RPXD0022W
The time to extract references seems excessive. It was %1 milliseconds.
- RPXE0061I
Loop iteration started late by %1 millseconds
- RPTX1010I
Start of project resolve. Repository=<%1>, Bootstrap=<%2>
- RPTX1011I
Attempting to resolve asset=<%1>
- RPTX1012I
End of project resolve. No detected errors
- RPTX1017I
Downloaded asset %1 from remote repository, local asset created.
- RPTX1018I
Using local cached version of asset %1.
- RPTX1019I
testsuite=<%1> found the following dependencies=<%2>
- RPTX1081E
Exception occurred while uploading Mobile report.
- RPTX1082E
An error occurred when generating the HTML/zip report.
- RPTX2001E
Adapter unable to start test because __PT_ACRONYM__ is already executing a test.
- RPTX2002E
Error encountered parsing RQM adapter preferences: %1. Please enter proper credentials in the Eclipse Quality Adapter preference page (Windows->Preferences).
- RPTX2003E
Project <%1> could not be found during RQM import.
- RPTX2004E
Test log is unavailable, no test results returned to RQM.
- RPTX2005E
Statistics log is unavailable, no statistic results returned to RQM: %1
- RPTX2006W
Display unavailable, no __PT_ACRONYM__ HTML reports will be attached to RQM execution results.
- RPTX2007I
Start RQM Execution Request Project=%1 Name=%2
- RPTX2008I
Start RQM Import Request Project=%1
- RPTX2009I
End RQM Execution Request
- RPTX2010I
End RQM Import Request
- RPTX2011E
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.
- RPTX2012E
Invalid RQM connection parameter: %1. Adapter was not launched.
- RPTX2013E
Adapter was stopped while a test was executing. The results of this test may be unreliable.
- RPTX2014E
Adapter was stopped while preparing to run an RQM script. There are no results for the attempted test script run.
- RPTX2015E
Testsuite '%1' or project '%2' does not exist. Ensure workspace started by adapter contains project and testsuite.
- RPTX2016I
%1
- RPTX2017E
%1 Reason: %2
- RPTX2018W
%1
- RPTX2019I
The RQM Adapter has been disconnected.
- RPTX2020I
The RQM Adapter has stopped.
- RPTX2021E
Unexpected error occurred while executing RQM test script.
- RPTX2022E
Unexpected error occurred while processing an import request from RQM.
- RPTX2023W
Error occurred while update the run status back to the RQM server. This may cause the RQM test progress page to contain inaccurate data.
- RPTX2024E
Unable to attach the following file to the RQM results. This may cause the attached HTML report not to render correctly. File name: %1
- RPTX2025E
Error occurred while registering the adapter: %1.
- RPTX2026E
Error occurred setting the default adapter name. Please set the name in the Eclipse Quality Adapter preference page (Windows->Preferences).
- RPTX2027W
Multiple test runs were detected when the stop request was received from RQM.
- RPTX2029W
Was unable to perform stop request from RQM. Likely the run was already shutting down when the request came in.
- RPTX2030I
Request to stop the test is being delayed until the appropriate run state is reached.
- RPTX2031I
A request to stop the currently running test has been received by RQM.
- RPTX2032I
Successfully issue a stop command to the running test. Please wait for the test to end.
- RPTX2033E
Error attempting to stop a test.
- RPTX2034E
Unable to create directory %1 no further information. Ensure user has permission to create directory in that location.
- RPTX2035E
Error occurred while attempting to automatically update pre-8.0 asset %1 for RQM execution.
- RPTX2036E
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.
- RPTX2037E
Launch was aborted: %1
- RPTX2050E
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.
- RPTX2051E
Unable to browse %1 in remote repository %2. Ensure RQM system has connectivity to the remote repository and the directory exists.
- RPTX2055E
Error occurred reading the adapter connection file.
- RPTX2056E
Error occurred saving the adapter connection file.
- RPTX2057E
Unable to complete import operation because the specified path is not in the adapters workspace. Try specifying the only the project name.
- RPTX2058E
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.
- RPTX2060E
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.
- RPTX2061W
Run verdict is inconclusive because no performance requirements exist in the last user stage for the associated VU Schedule.
- RPTX2062W
Run verdict is inconclusive because there are zero performance requirements in the last user stage of the associated VU Schedule.
- RPTX2063W
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.
- RPTX2070E
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.
- RPTX2071E
Error occurred while retrieving list of project areas. Please verify Quality Manager connection information. See error log for more details.
- RPTX2072E
Error occurred calling for the web analytics dash-board link.
- RPTX2073E
Error occurred while translating RQM server execution variables to __PT_ACRONYM__.
- RPTX2074E
Error connecting adapter and successful connecting adapter. This suggest RQM does not support script type introduced in 4.0.3. If adapter is not required it can get disabled by adding -DrtwStartAdapter=false in eclipse.ini.
- RPTX2075E
Unable to interpret expression <%1> from RQM control file <%2>. Ignoring. Reason <%3>
- RPTX2077E
Unable to browse to <%1>. Make sure it exist on the shared location.
- RPTX2079W
Errors attempting to load available SmartCard aliases. See documentation on how to configure your system to use SmartCard to authenticate to Quality Manager.
- RPWF0011E
Error occurred while completing test generation
- RPWF0012E
Error occurred while processing a packet at test generation
- RPWF0021E
WSDL Exception raised while processing WSDL source
- RPWF0032E
Error while generating test from Axis recording
- RPWF0051E
Error occurred while setting classpath entry for recorder
- RPWF0052E
I/O exception occurred while resolving keystore or truststore path
- RPWF0056E
Error occurred while launching web services HTTP proxy
- RPWF0066E
Error occurred while launching axis client recorder agent
- RPWF0071E
Exception thrown while creating a wizard page control
- RPWF0072E
Exception thrown while parsing URL: %1
- RPWF0074E
Exception thrown while finishing the axis recording wizard
- RPWF0075E
Exception thrown while looking for an available port
- RPWF0076W
Exception thrown while adding SOA Tester certificate to the trustore %1
- RPWF0081W
A proxy authorization %1 is used without any proxy
- RPWF0082W
No free name can be found; reusing %1
- RPWF0083E
Resource file %1 not found in workspace %2
- RPWF0084E
Workspace location cannot be determined
- RPWF0085E
Cannot retrieve the operation name from the envelope %1
- RPWF0101E
Core exception thrown using org.eclipse.debug.core plugin
- RPWF0102E
Exception thrown during launch configuration update
- RPWF0103E
Exception thrown while resolving a bundle entry path
- RPWF0104E
Exception thrown while identifying localhost IP address
- RPWF0111E
Exception thrown while creating a substitution: %1
- RPWF0112E
Exception thrown while creating a reference: %1
- RPWF0121W
Unknown format. Skipping the test generation for: %1
- RPWF0122W
Skipped call: %1
- RPWF0123W
Skipped request: It could be that provided password was not ok
- RPWF0124W
Attachments not generated.
- RPWF0130W
Could not find project for URI: %1
- RPWF0131W
Loading XSD Schema failed: %1
- RPWF0132E
Error while generating test from Generic Service Client: Can't show wizard
- RPWF0140E
An error has occurred: %1
- RPWH0007W
Unhandled Security Algorithm '%1'
- RPWH0009W
Unable to serialize data
- RPWH0010W
Unable to deserialize data
- RPWH0012E
Unable to open editor for '%1'
- RPWH0014E
Parse Error in '%1'
- RPWH0015E
Unable to create resource '%1'
- RPWH0016E
Failed to export source text '%1'
- RPWH0017E
A connection error occurred on '%1', please check the URL or the network configuration
- RPWS0001E
Exception raised during data harvest execution
- RPWS0002E
Exception raised during data substitution execution
- RPWS0003E
Exception raised on harvest data management
- RPWS0004E
Exception raised on substitution data management
- RPWS0005E
Exception raised during WebSocket read action
- RPWS0006E
Exception raised during WebSocket write action
- RPWS0007E
Unable to get WebSocket connection
- RPWS0008E
Unable to read from a closed connection
- RPWY0002E
An exception occurred in %1
- RPWY0003I
Information: %1 (%2)
- RPWY0004W
Warning: %1 (%2)
- RPWY0005E
An error occurred while importing external schema %1
- RPWY0006E
Unable to correlate automatically
- RPWY0007E
An exception %1 occurred in %2
- RPWZI0002E
Exception raised during WebSocket connection creation.
- RPXD0001E
Unknown Segment Offset/Length for Segmented Dataset: %1
- RPXD0002E
Bad Dataset Mode: %1
- RPXD0003E
Dataset not initialized: %1
- RPXD0004E
End of non-wrapped dataset reached: %1
- RPXD0005E
Dataset with multiple Equivalence Classes cannot be segmented
- RPXD0006E
segmented DatapoolMap null: %1
- RPXD0007F
No registered data correlation handler for this IKAction
- RPXD0017W
Pattern matching failed for: regex (%1) str (%2)
- RPXD0018E
Skipping substitution, reference value was null. original string: (%1) offset: (%2)
- RPXD0019E
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.
- RPXD0020E
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.
- RPXD0021E
Dataset %1 is accessed using different dataset modes by different tests.
- RPXD0021W
Setting variable %1 to value %2.
- RPXE0001W
%1
- RPXE0010W
Engine shutdown problem joining workers
- RPXE0011W
Failed to report exception
- RPXE0012W
Schedule failed to load
- RPXE0013W
Unable to create test
- RPXE0014W
Setting log level to %1
- RPXE0015W
Attempt to add object to Schedule which is not a UserGroup
- RPXE0016W
Virtual User %1 experienced error %2
- RPXE0017W
Connect timeout for action %1 (%2) user %3
- RPXE0018W
Read timeout for action %1 (%2) user %3
- RPXE0019W
Connect exception for action %1 (%2) user %3
- RPXE0021W
Read exception for action %1 (%2) user %3
- RPXE0023W
Iterating over keys exception
- RPXE0024W
CancelledKeyException
- RPXE0025W
NullPointerException
- RPXE0027W
UserGroup exception
- RPXE0028W
User Group %1 does not implement createTesterWorkload()
- RPXE0029W
Worker caught throwable
- RPXE0030W
Connection leak, I/O state %1
- RPXE0031W
Exception finishing connection for action %1 (%2) user %3
- RPXE0033W
Finish read get buffer interrupted for action %1 (%2) user %3
- RPXE0035W
Finish read exception for action %1 (%2) user %3
- RPXE0036W
Engine thread startup exception
- RPXE0037W
Engine request to report exception
- RPXE0038W
Exception creating cache file, cacheFileName: %1, extension: %2, dir: %3
- RPXE0039W
User %1 experienced exception %2
- RPXE0040W
User %1 caught exception trying to report severe error.
- RPXE0041W
Engine hard stop after %1 second timeout
- RPXE0042I
%1 received request to stop
- RPXE0043I
Forced stop of action %1
- RPXE0044W
No IP address was found for the local host
- RPXE0045W
Ignoring invalid network interface %1
- RPXE0046W
Could not find any usable network interfaces
- RPXE0047E
SyncPointSubsystem Unknown sync point: %1
- RPXE0048W
%1 STOPUSERS users=%2 stagger=%3 timelimit=%4 active users=%5
- RPXE0049W
%1 had %2 non-sampled users asked to stop active users=%3
- RPXE0050W
%1 had %2 sampled users asked to stop
- RPXE0051W
%1 after wait for compliance active users=%2 target=%3
- RPXE0052W
%1 abandon user %2
- RPXE0053W
%1 abandoned %2 users
- RPXE0054W
%1 end stop %2 users SUCCESS active users=%3
- RPXE0055W
%1 end stop %2 users FAIL active users=%3
- RPXE0056W
%1 occurred in %2. Message: %3
- RPXE0057E
Exception while reading test variable initialization file: %1
- RPXE0058E
Exception while initializing virtual users test variables.
- RPXE0059E
Unable to get Kerberos ticket from KDC for server %1.
- RPXE0060E
Failed to load test from '%1' due to exception: %2
- RPXE0100W
%1 terminated due to exception: %2
- RPXE0102W
IKAction: %1 (%2) caught Exception in preFinish() for %3 (%4)
- RPXE0103W
IKAction: %1 (%2) caught Exception in postFinish() for %3 (%4)
- RPXE0104W
KernelChannel connect(), exception while trying to bind to local address %1: %2
- RPXE2501E
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 __VENDOR_NAME__ Support for information on US export restrictions related to the exportation of strong encryption. Playback of tests utilizing these ciphers is not supported.
- RPXE2550E
The digital certificate RCS file '%1' was not found or was corrupt: %2
- RPXE2552I
digital certificate alias
- RPXE2900E
The server rejected the client's digital certificate.
- RPXE2901W
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.
- RPXE4000W
Schedule or Test not found. May not have compiled. - %1
- RPXE4001E
Runner Exception occurred
- RPXE4002E
Communications Error: Invalid Logging Level
- RPXE4003E
Communications Error: Invalid TestLog Level for %1 events
- RPXE4004E
Communications Error: Invalid Statistics Level or Interval
- RPXE4005E
Runner Exception occurred - See problem determination log
- RPXE4006E
Communications Error: Invalid Dataset information
- RPXE4007E
Communications Error: No communication from the workbench in %1 milliseconds. For more information, see the Troubleshooting section of the online help.
- RPXE4008E
Attempt to change statistic interval ignored.
- RPXE4008I
Think: requested time %1 milliseconds, actual time %2 milliseconds
- RPXE4009I
Delay: requested time %1 milliseconds, actual time %2 milliseconds
- RPXE4010I
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.
- RPXE4011E
Communications Error: Invalid Stop timeout
- RPXE4013I
Additional events from %1
- RPXE4014E
Communications Error: Invalid RunStagger information for %1 (pairCount)
- RPXE4015E
Communications Error: Invalid RunStagger information for %1 (pair %2)
- RPXE4016E
Failed to start users for user group: %1.
- RPXE4017I
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.
- RPXE4018E
Failed to write message to workbench [%1]
- RPXE4019E
Failed to remove users for user group: %1.
- RPXE4020E
Failed to add users for userGroup: %1 numUsers=[%2] startId=[%3]
- RPXE4021E
Failed to add users because the runner is not in a runnable state.
- RPXE4022E
failed to add desired number of users
- RPXE4023E
failed to reach target number of users ramping down
- RPXE4024E
not runnable or command failed
- RPXE4025E
failed to set the DataView state of user %1[%2] to %3.
- RPXE4026E
DataView command %1 is not yet implemented.
- RPXE4027E
DataView command %1 is not recognized.
- RPXE4028E
MessageEventFilter command parsing error in token %1[%2] of command [%3]
- RPXE4029E
The testLog message event filter specified by [%1] cannot be constructed. This filter element will be ignored.
- RPXE4050I
Operating System Info: name [%1] architecture [%2] version [%3]
- RPXE4100W
Cannot open execution history cache file [%1], execution history will not be cached
- RPXE4101E
Error closing execution history cache file [%1]
- RPXE4102E
Error reading %1 bytes from execution history cache file [%1]
- RPXE4103E
Error writing %1 bytes to execution history cache file [%2]
- RPXE4104E
Error opening execution history cache file [%1] for reading
- RPXE4105E
Error testing execution history cache file [%1] for available input
- RPXE4106E
Unexpected EOF reading %1 bytes from execution history cache file [%2]
- RPXE4107E
Exception processing execution history event
- RPXE4108E
Error reading execution history cache file [%1]
- RPXE4109E
Error writing to TestLog cache file [%1]
- RPXE4110E
Error closing TestLog cache file [%1]
- RPXE4111W
Cannot open testLog cache file [%1] for random access writing, the testLog may contain bad data.
- RPXE4112W
Error removing testLog event from cache file [%1]. Writing %2 bytes at offset %3.
- RPXE4120E
Error writing to TestLog [%1]
- RPXE4150E
Error opening execution history annotation file [%1]
- RPXE4151E
Error writing %1 bytes to execution history annotation file [%2]
- RPXE4152E
Error flushing/closing history annotation file [%1]
- RPXE4153E
Error deleting history annotation file [%1]
- RPXE4200W
Warning: Statistics delivery thread running behind statistics interval by %1 milliseconds
- RPXE4201W
Warning: Statistics delivery thread over slept by %1 milliseconds
- RPXE4202E
Error: Statistics delivery thread over slept by %1 milliseconds
- RPXE4203E
Error: Statistics collection time too long: %1 bytes %2 milliseconds
- RPXE4204W
Warning: Statistics collection time too long: %1 bytes %2 milliseconds
- RPXE4205E
Error: Statistics write time too long: %1 bytes %2 milliseconds
- RPXE4208E
Error: Could not create agent measurements file %1.
- RPXE4209I
Error: Statistics collection thread was interrupted
- RPXE4210E
Error: A severe error occurred when processing statistics.
- RPXE4211E
Error: A severe error occurred when sending statistics.
- RPXE4212E
Error: A severe error occurred when closing statistics.
- RPXE4213E
Statistics sub-system error: %1
- RPXE4214W
Statistics sub-system warning: %1
- RPXE4215E
Statistical counter descriptors file not found: %1.
- RPXE4215I
Statistics sub-system message: %1
- RPXE4216E
Problem in statistical counter descriptors file: %1.
- RPXE4217E
Submitted value %1 is out of range of allowed values for the counter type %2.
- RPXE4218E
In order to use this method, the runtime type of the counter must be either STATIC or RATE.
- RPXE4219E
Mismatch between runtime type %1 and static counter type %2.
- RPXE4220E
No static declaration found for counter %1.
- RPXE4221E
Attempt to create an undeclared counter %1 (type %2) over a declared counter of a different type (%3).
- RPXE4900I
Test execution completed with no reported problems
- RPXE4901I
%1 ERROR verdicts reported
- RPXE4902I
%1 FAIL verdicts reported
- RPXE4903I
%1 INCONCLUSIVE verdicts reported
- RPXE4904I
All reported verdicts PASSed
- RPXE4905I
%1 ERROR verdict reported
- RPXE4906I
%1 FAIL verdict reported
- RPXE4907I
%1 INCONCLUSIVE verdict reported
- RPXE4908I
%1 FAIL verdict roll-up
- RPXE4909I
%1 ERROR verdict roll-up
- RPXE4910I
%1 INCONCLUSIVE verdict roll-up
- RPXE4911I
%1 PASS verdict roll-up
- RPXE4912I
%1 ERROR verdicts reported from driver %2
- RPXE4913I
%1 FAIL verdicts reported from driver %2
- RPXE4914I
%1 INCONCLUSIVE verdicts reported from driver %2
- RPXE4915I
%1 ERROR verdict reported from driver %2
- RPXE4916I
%1 FAIL verdict reported from driver %2
- RPXE4917I
%1 INCONCLUSIVE verdict reported from driver %2
- RPXE4918I
duration
- RPXE4920I
%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.
- RPXE4921I
%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.
- RPXE4930I
The %1 testLog level was pushed from %2%3 to %4%5.
- RPXE4931I
The %1 testLog level was popped from %2%3 to %4%5.
- RPXE4932I
The %1 testLog level was changed from %2%3 to %4%5.
- RPXE4940I
Transaction [%1] started %2 milliseconds after start of test run.
- RPXE4941I
Transaction [%1] stopped %2 milliseconds after start of test run. Elapsed time: %3 milliseconds.
- RPXE4942I
Transaction [%1] aborted.
- RPXE4944W
Transaction [%1] is already started.
- RPXE4945W
Transaction [%1] has not been started.
- RPXE4948W
Execution Variables - Input
- RPXE4950I
Null user group name.
- RPXE4952E
Unable to find target loop named '%1'. Error handler did not complete properly.
- RPXE5301E
Error encountered while loading Native Library: %1
- RPXE5305E
A required customer-supplied file was not found. Please check the "external_files" folder and your installation instructions for: %1
- RPXE5330E
Unable to apply dataset swap: %1
- RPXE5500W
Unable to apply Open Tracing context. The root Jaeger span will be unparented. %1
- RPXE5501W
Transaction times for this run do not include failing transactions, according to workbench Test Execution preferences.
- RRIT0001E
Environment variable INTEGRATION_TESTER_AGENT_HOME not set to HCL OneTest™ API Agent installation location, or does not contain expected RunTests(.exe) program.
- RRIT0002E
Error unzipping __IT_PRODUCT_NAME__ project.
- RRIT0003E
__IT_PRODUCT_NAME__ library not found.
- RRIT0004E
Error processing messages received form the __IT_PRODUCT_NAME__ client.
- RRIT0005E
Some tag values are missing.
- RRITUI1002W
Open __IT_PRODUCT_NAME__ resources has been disabled in Test > __IT_PRODUCT_ACRONYM__ Integration preferences
- DCRC0001E
Missing message for log entry '{0}' in class: {1}
- DCRC0002E
Cannot get Log key '{0}': SecurityException raised
- DCRC0003E
Cannot initialize Log key '{0}'
- DCRC0008W
Warning: field '{0}' is not defined in class: {1}
- DCRC0009W
Warning: cannot get check message versus log key mapping for '{0}' of class {1}, SecurityException raised
- DCRC0010E
Unexpected exception, please check Error Log view: {0}
- DCUI0001E
unexpected exception
- DCUI0003E
Error getting persistent property '{0}'
- DCUI0004E
Error setting persistent property '{0}'
- DCUI0006E
Cannot reload resource '{0}'
- DCUI0007W
Failed to encode model to clipboard.
- DCUI0008W
Failed to decode model from clipboard.
- DCUI0009E
None of the attribute providers own attribute id '{0}'.
- DCUI0010E
Missing IRuleUIProvider extension point for '{0}'
- DCUI0011E
Missing IConditionUIProvider extension point for '{0}'
- DCUI0012E
Cannot save editor '{0}'
- DCUI0013E
Missing IRulePassUIProvider extension point for '{0}'
- DCUI0014E
Missing IRuleArgumentUIProvider extension point for '{0}'
- DCUI0015E
Missing IRuleArgumentContainerUIProvider extension point for '{0}'
- DCUI0016E
Try rule failed
- DCUI0017E
Try rule failed: '{0}'
- DCUI0998E
Cannot load file '{0}'