SysUA
asked on
Processing data for a remote command failed, category WSMan
Hi all,
For some time now I've been experiencing severe issues with our Exchange 2016 Servers, which are set up in coexistence with 2010 at the moment for migration. Moving mailboxes to 2016 is no problem at the moment, but since updating to CU 4 and .NET 4.6.2 (and on some servers CU 5 as well) I am unable to run even a simple set- or enable-mailbox command on those 2016 servers. Some example commands I try to run are:
Set-Mailbox "sttetest2010" -ThrottlingPolicy "limitrecipientrate5000" (this is an Exchange 2010 hosted mailbox)
Enable-Mailbox "sttetest2016" -Database "MAILDB06" (this is an Exchange 2016 database on the same server - EX06 - I ran the command on, for an existing active directory account "sttetest2016")
The error I get when running those commands always is:
Processing data for a remote command failed with the following error message: [ClientAccessServer=EX06,B ackEndServ er=ex
06.ad.ua.ac.be,RequestId=7 9c44d8e-73 7c-418b-93 da-7ac2d12 acdd5,Time Stamp=19/0 6/2017 11:36:42] [FailureCategory=WSMan-Oth
ers] For more information, see the about_Remote_Troubleshooti ng Help topic.
+ CategoryInfo : OperationStopped: (ex06.ad.ua.ac.be:String) [], PSRemotingTransportExcepti on
+ FullyQualifiedErrorId : JobFailure
+ PSComputerName : ex06.ad.ua.ac.be
I get this sort of message on every Exchange 2016 Server I have, regardless of CU version. I've been doing some searching and digging into this, uninstalled .NET 4.6.2 and reinstalled it (since crash dump pointed to .NET files and the w3wp.exe process) but nothing seems to help. I haven't tried removing and reinstalling IIS, because I am not sure how well Exchange will respond to that :)
I have added log entries and crash dump to this post in hopes that you Gurus can help me out. Many thanks for taking a look at this, I am at a loss...
applicationlog.txt
systemlog.txt
MSExchange-Management-log.txt
Report.txt
For some time now I've been experiencing severe issues with our Exchange 2016 Servers, which are set up in coexistence with 2010 at the moment for migration. Moving mailboxes to 2016 is no problem at the moment, but since updating to CU 4 and .NET 4.6.2 (and on some servers CU 5 as well) I am unable to run even a simple set- or enable-mailbox command on those 2016 servers. Some example commands I try to run are:
Set-Mailbox "sttetest2010" -ThrottlingPolicy "limitrecipientrate5000" (this is an Exchange 2010 hosted mailbox)
Enable-Mailbox "sttetest2016" -Database "MAILDB06" (this is an Exchange 2016 database on the same server - EX06 - I ran the command on, for an existing active directory account "sttetest2016")
The error I get when running those commands always is:
Processing data for a remote command failed with the following error message: [ClientAccessServer=EX06,B
06.ad.ua.ac.be,RequestId=7
ers] For more information, see the about_Remote_Troubleshooti
+ CategoryInfo : OperationStopped: (ex06.ad.ua.ac.be:String) [], PSRemotingTransportExcepti
+ FullyQualifiedErrorId : JobFailure
+ PSComputerName : ex06.ad.ua.ac.be
I get this sort of message on every Exchange 2016 Server I have, regardless of CU version. I've been doing some searching and digging into this, uninstalled .NET 4.6.2 and reinstalled it (since crash dump pointed to .NET files and the w3wp.exe process) but nothing seems to help. I haven't tried removing and reinstalling IIS, because I am not sure how well Exchange will respond to that :)
I have added log entries and crash dump to this post in hopes that you Gurus can help me out. Many thanks for taking a look at this, I am at a loss...
applicationlog.txt
systemlog.txt
MSExchange-Management-log.txt
Report.txt
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER