The following table lists possible error codes you might receive while using the ATLAS step type example and the corresponding descriptions.

Error Code Description
-17001 The test program set (TPS) cannot continue execution because the NI ATLAS Step Type ActiveX server is in an unrecognized state. Unload the server from TestStand and restart the execution.
-17205 The TPS cannot be executed because the PAWS Run-Time System (RTS) is in a bad state or cannot be initialized. Terminate the current instance of the PAWS RTS and run the TPS again.
-17208 The specified TPS file was not found. Ensure that the file path is correctly specified so TestStand can locate the file and its directory.
-17401 The TPS cannot be executed because another TPS exists and is currently running on the requested host. Only one instance of the PAWS RTS can exist on a host at any time. Wait for the currently running TPS to complete execution or terminate the execution before executing another TPS.
-17500 The execution failed because the RTS reported an error. The RTS error displays as part of the error message.
-17501 An unexpected error occurred.
-17600 The TPS cannot be loaded because the RTS was interrupted during the load process. Check the TPS and PAWS RTS for errors and try running the TPS again.
-17601 No TPS file was specified for execution. Use the Edit ATLAS Call dialog box to select a file to call before executing the step.