The specified ShellId is incorrect or the shell no longer exists on the server.

Hi,

I have been looking of a solution of this problem, that started from a new installation of Exchange 2013 (CU8 installed).

I get this errors after 30 seconds in (run as admin) management shell.

Starting a command on the remote server failed with the following error message :

[ClientAccessServer=SERVER,BackEndServer=server.xxxx.com,RequestId=9d3d4900-3e71-4344-b607-72c54351ec3e,TimeStamp=8/16/2015 1:57:55 PM] [FailureCategory=WSMan-InvalidShellID] The request for
the Windows Remote Shell with ShellId B39DBE1D-CED0-4F26-A8AE-8AB7F939E8F4 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 retry the operation. For more information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OperationStopped: (server.xxxx.com:String) [], PSRemotingTransportException
    + FullyQualifiedErrorId : JobFailure
    + PSComputerName        : server.xxxx.com

Sofar I found this problem listed in an MS article about language cookies, solved with CU3.

August 16th, 2015 2:46pm

Hi,

I saw other similar thread that reinstalling could solve it, you can try it.

Reinstalling can correct the format of the Time and Date strings for EMS connection cookies.

Best Regards.

Free Windows Admin Tool Kit Click here and download it now
August 17th, 2015 5:25am

Hi Jaxk,

Check if using imlicit remoting works as a workaround.

Connect to Exchange using remote Shell:

https://technet.microsoft.com/en-us/library/dd335083%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

Also check for error in the eventvwr.

Is it a multi-role or single role. Do you see any issues with EAC

What is the PShell version

$host.version		
August 17th, 2015 5:47am

Hi Satyajit,

Exchange is installed with multi role, there are no issues with EAC,  however a bit sluggish.

Server is a E5 v3 Xeon, installed on SSD, so it should be fast enough, or is Exchange 2013 a huge resource hog?

Using remote shell, same result; the first command works fine but with the second command ShellID not found

Host version is 4:

Name             : ConsoleHost
Version          : 4.0
InstanceId       : e07927fc-8e99-459b-ae79-317a1a74246f
UI               : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture   : en-GB
CurrentUICulture : en-US
PrivateData      : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
IsRunspacePushed : False
Runspace         : System.Management.Automation.Runspaces.LocalRunspace

Free Windows Admin Tool Kit Click here and download it now
August 17th, 2015 10:52am

Hi Jaxk,

It could be the slowness causing some throtting, I expect some EventLogs atleast to start with.

Exchange is a huge resource hog, primarily on the disk part. Just having SSDs are not enough.

Have you tested the IOPs using Jetstress, before deployment, make sure you are within the limits.

Jetstress Field Guide:

https://gallery.technet.microsoft.com/Jetstress-Field-Guide-1602d64c

August 18th, 2015 3:15am

Hi,

There was not other solution to reinstall Exchange as it became unworkable with a non functional command shell. Exchange was installed on a physical server, now installed ESXi 6.0 on the server, Exchange installed on a VM with 12GB Ram and it responds fast and no issues with the missing shell ID.

Thanks for all help.

Jack 

Free Windows Admin Tool Kit Click here and download it now
September 6th, 2015 1:09am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics