none
starting a command on remote server failed.. RRS feed

  • Question

  • WinServer 2008R2, Ex2010 SP2 UR4 (yes, amazing that it got there. thank you!)

    Running EMS locally

        • Starting EMS is no problem
        • Running a short .ps1 script is no problem
        • Running another script within 10 seconds or so is also no problem
        • Running a script again after about 30 seconds, the "PSSession" appears to "time out" and causes this error message below:

    "Starting a command on remote server failed with the following error message : The request for the Windows Remote Shell
    with ShellId 03E93262-693D-41E3-944A-18072D6DEFBF failed because the shell was not found on the server. Possible
    causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct
    ShellId or create a new shell and reissue the request. For more information, see the about_Remote_Troubleshooting Help"

    Exiting and Restarting the EMS works just fine - for another 30 seconds or so

    Remote Troubleshooting help offers no clue to this error and searching the web also yields no quick and easy response. Also no Red Dots in Windows logs - just Powershell Log Event ID: 403 "Engine state is changed from Available to Stopped....."

    Note:

    If I execute EMS remotely from a Win7 64-Bit box then all is "normal".

    Background:

    1. The Server was a clean install 4 months ago. It is "the" DC and has Ex2010 OWA.
    2. I reinstalled the Ex Management Tools on the Win7 Remote Box after the UR4 install.

    Why the short - 30 second - EMShell Session?

    Thanks for any helpful solutions or pointers.....


    "If I'd asked my customers what they wanted, they'd have said a faster horse." ~ Henry Ford

    Monday, September 3, 2012 3:48 PM

All replies

  • Starting EMS is no problem

    Running a short .ps1 script is no problem

    Running another script within 10 seconds or so is also no problem

    Running a script again after about 30 seconds, the "PSSession" appears to "time out" and causes this error message below:

    Hi,

    If you just run the 3rd script after 30 seconds, does it work?

    How about running single cmdlet directly?

    "The Server was a clean install 4 months ago. It is "the" DC and has Ex2010 OWA."

    Did you install Exchange 2010 CAS server on the DC server? Though it is supported, however, it is not recommended.

    If you do the same tasks on another Exchange server, what's the result?

    Please make sure you have installed UR4 on all Exchange server 2010.

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Frank Wang

    TechNet Community Support

    Tuesday, September 4, 2012 8:09 AM
  • Hi Aspasa,

    Any updates?


    Frank Wang

    TechNet Community Support

    Tuesday, September 11, 2012 8:00 AM