Link to home
Start Free TrialLog in
Avatar of mohammad hossein
mohammad hossein

asked on

error in load queue viewer

Hi,

when i try to open queue viewer, get this error

 
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] The request for
the Windows Remote Shell with ShellId ECFD473B-D499-4240-A55C-FA997829CD90 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.
what I do ?

Tanx
Avatar of Hani M .S. Al-habshi
Hani M .S. Al-habshi
Flag of Yemen image

Any updates recently ?
Avatar of mohammad hossein
mohammad hossein

ASKER

i dont no
What is your Exchange server version. Check all Exchange services are running using test-servicehealth command.
Exchange 2013

Now the Exchange toolbox does not open and show this error:


FX:{714FA079-DC14-470f-851C-B7EAAA4177C1}

The attempt to connect to http://server name/PowerShell using "Kerberos" authentication failed: Processing data from remote server xmail.ncc.org failed with the following error message: [ClientAccessServer=server,BackEndServer=server name,RequestId=d9183e88-3191-4150-94f1-f7762fa024e4,TimeStamp=10/10/2018 12:12:59 PM] The request for the Windows Remote Shell with ShellId 4D184CDB-5EF4-4109-AF67-48277E5621FC 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.





at Microsoft.Exchange.Management.SnapIn.ConnectionRetryDiscoverer.DiscoverConnectionInfoInternal()
   at Microsoft.Exchange.Management.SnapIn.ConnectionRetryDiscoverer.DiscoverConnectionInfo(SupportedVersionList& supportedVersionList, String slotVersion)
   at Microsoft.Exchange.Management.SnapIn.PSConnectionInfoSingleton.DiscoverConnectionInfo()
   at Microsoft.Exchange.Management.SnapIn.PSConnectionInfoSingleton.GenerateMonadConnectionInfo()
   at Microsoft.Exchange.Management.SnapIn.PSConnectionInfoSingleton.GetMonadConnectionInfo(SerializationLevel serializationLevel)
   at Microsoft.Exchange.Management.SnapIn.ExchangeHelpService.Initialize()
   at Microsoft.Exchange.Management.SnapIn.ExchangeScopeNode.OnExpand()
   at Microsoft.ManagementConsole.NodeSyncManager.ProcessRequest(NodeRequestInfo info, IRequestStatus requestStatus)
   at Microsoft.ManagementConsole.SnapIn.ProcessRequest(Request request)
   at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)
   at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)
   at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo)
   at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest()
   at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)


What i do?
First, thing what i will do, is to reboot the server and check again.
Hi
I reboot it but  there was no change

this error

FX:{7F96F1BD-0EDA-4cb0-8393-632B83BD54EE}

The attempt to connect to http://server/PowerShell using "Kerberos" authentication failed: Processing data from remote server xmail.ncc.org failed with the following error message: [ClientAccessServer=server,BackEndServer=server,RequestId=93d4276d-20d8-4f01-ab92-61e9119fcea1,TimeStamp=11/4/2018 8:07:54 AM] The request for the Windows Remote Shell with ShellId D877137B-9026-468E-87F4-EA89D063A67E 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.



   at Microsoft.Exchange.Management.SnapIn.ConnectionRetryDiscoverer.DiscoverConnectionInfoInternal()
   at Microsoft.Exchange.Management.SnapIn.ConnectionRetryDiscoverer.DiscoverConnectionInfo(SupportedVersionList& supportedVersionList, String slotVersion)
   at Microsoft.Exchange.Management.SnapIn.PSConnectionInfoSingleton.DiscoverConnectionInfo()
   at Microsoft.Exchange.Management.SnapIn.PSConnectionInfoSingleton.GenerateMonadConnectionInfo()
   at Microsoft.Exchange.Management.SnapIn.PSConnectionInfoSingleton.GetMonadConnectionInfo(SerializationLevel serializationLevel)
   at Microsoft.Exchange.Management.SnapIn.ExchangeHelpService.Initialize()
   at Microsoft.Exchange.Management.SnapIn.ExchangeScopeNode.OnExpand()
   at Microsoft.ManagementConsole.NodeSyncManager.ProcessRequest(NodeRequestInfo info, IRequestStatus requestStatus)
   at Microsoft.ManagementConsole.SnapIn.ProcessRequest(Request request)
   at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)
   at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)
   at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo)
   at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest()
   at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)
2-Go to the IIS manager then Application Pools and change the MSExchangePowerShellAppPool Identity from ApplicatonPoolIdentity to Local System.  HIghlight the MSExchangePowerShellAppPool Identity line and check the Advanced Settings for the Process Model.  Change to Local System.
Resolutions:

Method 1:

  1. Close all MMC/EMC instances before proceeding.
  2. Open Registry Editor (regedit) as the user you run the EMC under.
  3. Go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\ExchangeServer\v14\AdminTools
  4. Look for value NodeStructureSetting.
  5. If it is there, back it up and then remove it.
Method 2:

  1. Close all MMC/EMC Instances before proceeding.
  2. Open Powershell or Powershell IDE as the user you run the EMC under and execute the following command:.
  3. Remove-ItemProperty -Path HKCU:\Software\Microsoft\ExchangeServer\v14\AdminTools\ -Name NodeStructureSettings
  4. Close Powershell

After performing either of the methods above to remove the registry entry you should be able to open the Exchange Management Console and it will discover another Exchange server and connect.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.