Users have been started, but they don't show as available for my load test. How do I fix this?

This article discussed a couple of causes for this issue along with suggested fixes.

Problem:

After starting rUsers, AppLoader is not showing any rUsers as available to start a load test. 

AppLoader Image:

rUsers are not connecting to AppLoader (360001914994)_image001

 

rUserManager Image:

Notice the users are connected, but listed in light blue.  This indicates that rUserManager could not recognize the status of VStation, whether it is running or not. The rUser will display in green if the connection is successful and VStation is running.

rUsers are not connecting to AppLoader (360001914994)_Screenshot_1

Cause #1:

After cleaning the injector logs and starting users again, we notice that the ruser001.log in the injector machine has the following lines:

[Date & Time Stamp] [Thread #] Starting Player Thread
[Date & Time Stamp] [Thread #] Starting Receiver Thread
[Date & Time Stamp] [Thread #] Component: PLAYER --- Waiting for the receiver to be ready
[Date & Time Stamp] [Thread #] Component: PLAYER --- Waiting for the receiver to be ready
[Date & Time Stamp] [Thread #] Component: PLAYER --- Waiting for the receiver to be ready
[Date & Time Stamp] [Thread #] Component: PLAYER --- Waiting for the receiver to be ready
[Date & Time Stamp] [Thread #] Component: PLAYER --- Waiting for the receiver to be ready
[Date & Time Stamp] [Thread #] Component: PLAYER --- Waiting for the receiver to be ready
[Date & Time Stamp] [Thread #] Component: PLAYER --- Waiting for the receiver to be ready
[Date & Time Stamp] [Thread #] Component: PLAYER --- Waiting for the receiver to be ready
[Date & Time Stamp] [Thread #] Component: PLAYER --- Waiting for the receiver to be ready
[Date & Time Stamp] [Thread #] Component: PLAYER --- Waiting for the receiver to be ready
[Date & Time Stamp] [Thread #] Could not connect to 127.0.0.1:9008
[Date & Time Stamp] [Thread #] Error: socket connect failed with Sockets Error Code: 10061

The Injector application can not communicate with the users. The main reason is that the VStations are not able to open a connection to the port indicated in the vstation.ini to communicate with the Injector process

Fix #1:

The fix for this is to open any port on the Injector machine and dedicate it to the Injector-VStation communication. The default port is 9008, but any TCP Port value is fine as long as it is open on the Injector server.

Ask the security team in your company to open one port on the server, and use that in vstation.ini:

//The port number that the injector will listed on Default is 9008
injectorlistenport=9008

Cause #2:

It could be that after cleaning the logs folder on the Injector machine and starting the users, we notice that we can't find a log file for each user e.g. ruser001.log. Moreover, Windows Task Manager does not list VStation.exe as a running process on each of the users that we started. Instead, we find VStationW.exe is running on each of these users.

This means that the process VStationW.exe is not capable of running VStation.exe on that user (which could be due to a security policy on the server).

Fix #2:

We can make VStation.exe run on each of the users by opening the registry edit program, and updating one value in it. Follow the steps below to do that:

  1. Login as an administrator on the injector machine
  2. Make sure that all other users are logged off (use Windows Task Manager)
  3. Open Registry Editor (regedit.exe) by typing it in the search box in windows
  4. From the "Edit" menu, select "Find"
  5. Type the value "rUser AutoStart" and click on the "Find Next" button
  6. Make sure that the current value of that registry key is pointing to "VStationW.exe" executable
  7. Replace "VStationW.exe" with "VStation.exe"
  8. Click OK and close the Registry Editor

 

rUsers are not connecting to AppLoader (360001914994)_Screenshot_1 - 1

 

rUsers are not connecting to AppLoader (360001914994)_Screenshot_2

 

rUsers are not connecting to AppLoader (360001914994)_Screenshot_3

 

rUsers are not connecting to AppLoader (360001914994)_Screenshot_4

 

rUsers are not connecting to AppLoader (360001914994)_Screenshot_5