Problem:-> Test run aborted due to error
Virtual users have exited prior to stage completion.
Explanation
In a schedule with multiple stages, at the end of a stage that is configured with n virtual users, there were fewer than n virtual users running. The schedule did not assign enough work to the virtual users to keep them active for the duration of the stage, or the virtual users stopped because of an a different error. The workload problem can occur if you use multiple stages but do not enclose the workload in an infinite loop.
System action
Solution :->
On the workbench computer, examine the workload for each user group in the schedule. Check that the entire workload is inside an infinite loop, so that the virtual users always remain active regardless of the stage duration.
If the tests already use infinite loops, then the agent computers might have encountered errors while running tests. To determine why virtual users stopped before the stage completed:
- Examine the test log for error or exception messages.
- Increase the test log level and decrease the number of users. Try running the schedule again. Examine the test log for error or exception messages.
- Simplify the workload by running one user in one stage. Check to see whether the single user takes the expected amount of time to complete all actions. If not, examine the test log and problem determination log for error or exception messages.
Problem:-> No local agent controller
Local computer is not running the Agent Controller.
Explanation
The agent controller coordinates schedule playback between the workbench and agent computers. The agent controller is not running on the local computer.
System action
Solution :->
Make sure that the agent controller is installed and running on the workbench computer. On Windows computers, the agent controller is a process called ACWinService. On Linux computers, the agent controller is a process called RAServer.
To start the agent controller, do one of the following steps:
1. At a command prompt, change to the directory AgentController\bin in the product installation directory.
>cd “C:\Program Files\IBM\SDP70Shared\AgentController\bin”
net start "IBM Rational Agent Controller"
- On Linux, change to the directory AgentController/bin in the product installation directory; then enter this command:
./RAStart.sh
Problem:-> Connection refused
Connection refused on host computername
Explanation
The agent controller can be configured to restrict playback to the local computer only. If the agent controller on an agent computer is configured for local playback only, it will not accept connections from other agent controllers.
System action
Solution :->
Make sure that the agent controller is configured correctly.
To configure the agent controller on Windows:
2. At a command prompt, change to the directory AgentController\bin in the product installation directory.
>cd “C:\Program Files\IBM\SDP70Shared\AgentController\bin”
3. Type net stop "IBM Rational Agent Controller" to stop the agent controller.
4. Type SetConfig.bat to run the configuration utility.
6. Type net start "IBM Rational Agent Controller" to start the agent controller.
To configure the agent controller on Linux:
1. At a command prompt, change to the directory AgentController/bin in the product installation directory.
2. Type ./RAStop.sh to stop the agent controller.
3. Type ./SetConfig.sh to run the configuration utility.
4. Accept all of the default values except for network access mode. Set network access mode to ALL.
5. Type ./RAStart.sh to start the agent controller.
Problem:-> Unable to connect to license server
Solution :->
1) Check if "FLEXlm License Manager" service is running in Services [Control Panel>Administrator>Services: WinXP/Win2000].
Start->run then type services.msc press <Enter>
Restart this service "FLEXlm License Manager"
2) Launch Rational License Administrator and check if all the floating licenses are served properly [Menu Item: Setting >Client Server Config >check if Use License Server Option is checked. Check if correct server name is entered and then click on show licenses]
3) Check if Installation manager is configured for the same server.
Once above steps are verified, launch RPT go to help>license Status and check the expiration date [Should be same as seen in license server] and then run you're schedule.
Problem:-> Start recording aborted, The Agent Controller on localhost: 10002 is unavailable
When you start a recording in RPT, the following error message can occur:
Start recording aborted.
Reason:
IWAT3034E The Agent Controller on localhost:10002 is unavailable.
IWAT3035E Confirm the Agent Controller is still running, and verify the location in Window > Preferences > Test.
Solution :->
This problem typically indicates that the installation of the Remote Agent Controller (RAC) is not correct. If it is and if the IBM_Agent_Controller directory is present, RAC does not start because of other issues. The following suggestions could help to overcome the problem:
- Check RPT Windows > Preferences > Test.
- The Agent Controller local port should be 10002.
- Check the serviceconfig.xml file
Path :-> C:\Program Files\IBM\SDP70Shared\AgentController\config
Open the serviceconfig.xml and verify the followings
- Make sure that the Agent Controller uses port 10002
- One of these two lines must exist:
- Check the C:\Windows\System32\drivers\etc\host file.
- Make sure it contains the exact line:127.0.0.1 localhost
- Bring up RPT
Windows > Preferences > Profile and Logging > Hosts.
- Select the localhost: 10002 selections in the Default Hosts list.
- Click the Test Connection button.
Look for a line like:
TCP hostname:10002 hostname:0 LISTENING 3528.
Hostname is the actual name of the computer. The right-most value in this line (3528 above) should match the process ID (PID) for the RAService.exe process.
- From a command prompt, run the command
Note any error message that appears.
Make sure, that no firewall or other security application prevents it to start.