Quantcast
Channel: Windows Performance Toolkit forum
Viewing all articles
Browse latest Browse all 1161

FSCT fails with two Windows clients

$
0
0

I am running a simple configuration with 1 Server (non-Windows server), One Windows 7 and one Windows XP clients and  One Controller (Wink2K8 R2). The DC is W2k3. So the test is running in the Domain mode. I pass through all preparation commands successfully. Run Client fails with Controller time out with Error receiving 'ready' message.

This is Message on the Controller:

C:\fsct>fsct run controller /server phaethusa /password Mypass /volumes \\phaethusa\fsroot1 /
clients "cl-07,CLIENT6B" /min_users 1 /max_users 4 /step 1 /duration 300 /workload HomeFolders
server's name: phaethusa
server's password: Mypass
volumes: \\phaethusa\fsroot1
clients' names: cl-07,CLIENT6B
min users: 1
max users: 4
sweep step: 1
test's duration: 300
workload to use: HomeFolders
Executing: rd /s /q running
Executing: rd /s /q running complete.
Executing: md running\signals
Executing: md running\signals complete.
Running the test (workload: HomeFolders).
Running iteration for 300 seconds with 1 users [warmup: 30s].
Performance Counter thread started for phaethusa
Performance Counter thread started for CLIENT6B
Performance Counter thread started for cl-07
Error receiving message.
Unknown winsock error.
Error receiving 'ready' message.
Error waiting for client cl-07 to get ready.
Error initializing iteration.
Error running iteration.
Error running test.
Error running the controller.
Closing network connection

This is the message on the first client (Windows 7):

C:\fsct>fsct run client /controller VZTCX2270M2-07B /server phaethusa /password Mypass /
timeout 10 /verbose verbose
controller's name: VZTCX2270M2-07B
server's name: phaethusa
server's password: Mypass
timeout (in minutes): 10
Waiting for the controller to connect.
Waiting for a connection.
Loading scenarios (scenarios\*.dll)
Loading scenario: CmdLineFileDelete.dll
Loading scenario: CmdLineFileDownload.dll
Loading scenario: CmdLineFileUpload.dll
Loading scenario: CmdLineNavigate.dll
Loading scenario: ExplorerDragDropFileDownload.dll
Loading scenario: ExplorerDragDropFileUpload.dll
Loading scenario: ExplorerFileDelete.dll
Loading scenario: ExplorerNavigate.dll
Loading scenario: ExplorerSelect.dll
Loading scenario: WordEditAndSave.dll
Loading scenario: WordFileClose.dll
Loading scenario: WordFileOpen.dll
Running test.
Communication thread started.
Waiting for iteration data.
Creating users.
Sending 'ready' message to the controller.
Waiting for a 'start' signal from the controller.
Error receiving message.
The connection has been dropped because of a network failure or because the peer system fai
led to respond.
Error receiving start message.
An error occurred while waiting for the 'start' signal from the controller.
Error running test.
Error running client.
Closing network connection
Command execution failed.

This is the message on the Second client (Win XP)console:

C:\fsct>fsct run client /controller VZTCX2270M2-07B /server phaethusa /password Mypass
 /timeout 10 /verbose verbose
controller's name: VZTCX2270M2-07B
server's name: phaethusa
server's password: Mypass
timeout (in minutes): 10
Waiting for the controller to connect.
Waiting for a connection.
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Profile file not created [\\VZTCX2270M2-07B\controllershare\running\signals\CL-07.profile
.cfg].
Timeout during waiting for profile file.
Error running client.
Closing network connection
Command execution failed.

I did not prepare this Client to use the configuration file! I am not sure why It is looking for profile file. 

I think the controller fail to communicate with the clients but I am not sure why!

Any Idea why?

Thanks,

Kam


Viewing all articles
Browse latest Browse all 1161

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>