PSRemoting Failure Scenario
Posted: Tue Nov 09, 2010 2:28 am
I'd like some input on a failure scenario involving PSRemoting.
Basic scenario:
I have an executable which interrogates a database for modular test specifications. By providing arguments to the executable I can ask it to run all or subsets of the tests. I have automated the remote execution of this executable using invoke-command of a PowerShell script which in turn executes a Start-Process of the executable with arguments.
Configuration details:
Domain: All systems are in the same domain and the executing process is using domain administrator credentials
Initiating server: Windows Server 2003 R2, fully patched
Client server: Windows Server 2008 R2, fully patched
Enable-PSRemoting has been run on all systems.
No PSSession option changes have been made, the defaults are involved so far in all diagnostics.
Problem Description:
When the executable is instructed (via the command line arguments) to remotely execute a certain number of test cases it fails with a "Not enough storage is available to complete this operation." error.
Diagnostic information:
Successful tests
When the same request (executable with the same command line arguments) is made LOCALLY (from a PowerShell prompt) on the remote client server (no remoting involved) the process completes successfully. This is regardless of the volume of tests selected.
When the subset of test cases is requested individually using REMOTING they succeed.
Failed tests
When remoting is involved and the volume of tests reaches a certain number (not huge, we're talking about around 7).
Failure behavior is consistent (the result that is, the exact failure point varies between servers and between runs on a particular server) when the test is run using remoting against different client systems (one running Windows Server 2008 R2, the other running Windows Server 2003 R2 32-bit)
Summary:
Remoting between these systems works but fails when the number of tests increases. All tests succeed when run locally.
The clue provided at runtime is "Not enough storage is available to complete this operation."
I have researched the PSSessionOptions but any promising settings I've come across seem to be set to unlimited by default.
If anyone has any suggestions I'd appreciate hearing them.
Thanks
Basic scenario:
I have an executable which interrogates a database for modular test specifications. By providing arguments to the executable I can ask it to run all or subsets of the tests. I have automated the remote execution of this executable using invoke-command of a PowerShell script which in turn executes a Start-Process of the executable with arguments.
Configuration details:
Domain: All systems are in the same domain and the executing process is using domain administrator credentials
Initiating server: Windows Server 2003 R2, fully patched
Client server: Windows Server 2008 R2, fully patched
Enable-PSRemoting has been run on all systems.
No PSSession option changes have been made, the defaults are involved so far in all diagnostics.
Problem Description:
When the executable is instructed (via the command line arguments) to remotely execute a certain number of test cases it fails with a "Not enough storage is available to complete this operation." error.
Diagnostic information:
Successful tests
When the same request (executable with the same command line arguments) is made LOCALLY (from a PowerShell prompt) on the remote client server (no remoting involved) the process completes successfully. This is regardless of the volume of tests selected.
When the subset of test cases is requested individually using REMOTING they succeed.
Failed tests
When remoting is involved and the volume of tests reaches a certain number (not huge, we're talking about around 7).
Failure behavior is consistent (the result that is, the exact failure point varies between servers and between runs on a particular server) when the test is run using remoting against different client systems (one running Windows Server 2008 R2, the other running Windows Server 2003 R2 32-bit)
Summary:
Remoting between these systems works but fails when the number of tests increases. All tests succeed when run locally.
The clue provided at runtime is "Not enough storage is available to complete this operation."
I have researched the PSSessionOptions but any promising settings I've come across seem to be set to unlimited by default.
If anyone has any suggestions I'd appreciate hearing them.
Thanks