• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 475
  • Last Modified:

SBS 2011 Issue with WinRM and Exchange Management tools

I have been a user of Experts Exchange for years, and have never actually posted a question I don't think.  Usually get answer by searching, here or elsewhere.

I have a customer with a Windows SBS 2011 Server, with Exchange SP1 (14.01.0438.000)  There is some configuration that I wouldn't duplicate (server is running the hyper-v role with a SQL virtual machine for an LOB app) but everything was working fine until recently.

Recently we noticed an issue when running the Exchange Management Console.  Note there does not appear to be any issue with Exchange, mail is flowing properly, and client access is unaffected.

Exchange console will work for a couple of minutes, then begin failing with the following error.
---------------------------
Microsoft Exchange
---------------------------
Starting a command on remote server failed with the following error message : The Windows Remote Shell cannot process the request; the selector value 71647AC2-C621-4F37-9BD5-0FC725414D59 specified in the request was not found. For more information, see the about_Remote_Troubleshooting Help topic.
---------------------------
OK  
---------------------------

The Exchange Shell exhibits the same behavior.  Will work for a couple of commands (even big ones like Get-MessageTrackingLog) then will error with same error as above, the selector value appears to be different every time the error occurs.

If I close the Exchange Console or the Management Shell and open it it will again work for a few minutes.

Can't find any good information on repairing / installing WinRM 2 and Powershell 2 since they come preinstalled on server.

Tried upgrading to WinRM 3 and Powershell 3 and problem was worse (powershell / Exchange management shell would not work at all, complaining about wrong version of modules).  After removing update it reverted to previous behavior.

Have removed and reinstalled the WinRM IIS Extensions, no change

SFC / Scannow found no issues.

Have considered upgrading to Exchange 2010 SP3, but I don't want to worsen the issue and it doesn't really feel like an Exchange issue to me, seems more based in WinRM and Powershell.  However, I have not been able to duplicate the issue just running commands in Powershell 2.0.
This is the exact error, but the resolution (opening firewall exception for winrm-iis-ext) didn't work for me.
Similar Issue
0
rmryan80
Asked:
rmryan80
  • 4
  • 3
2 Solutions
 
Simon Butler (Sembee)ConsultantCommented:
Upgrading to Exchange 2010 SP3 is the first thing I would do here.
It effectively reinstalls the product and will resolve a lot of problems.
After you have done that, install the latest rollup and see if the problem continues.

If it does, run the fix my network wizard in the SBS management console. I would also run the SBS BPA for SBS 2011 and ensure that doesn't flag anything.

Simon.
0
 
rmryan80Author Commented:
Thanks, Simon.  I will plan on this upgrade one night this evening or this coming weekend.  Was leaning that way but slightly leery.

Rich
0
 
Simon Butler (Sembee)ConsultantCommented:
I have lost count the number of times I have seen the service pack roles problems, that is now the first thing I do if I have a problematic server. I don't see any point in troubleshooting something I know could be fixed by the service pack - either because it is a bug, or because of the way that the server pack installs.

Simon.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
rmryan80Author Commented:
Okay, update time.  I spent a lot of hours working on this one evening last week, and the problem still exists.

Upgrade Exchange to 2010 SP3, then Rollup 8v2.  Applied all current Windows updates.  Re-ran SBS wizards "connect to internet" then "internet address wizard" and then "trusted certificate" to re-apply the 3rd party SSL certificate.  And this thing fought me every step of the way.  Exchange upgrade bombed out halfway through, had to troubleshoot that (left Exchange essentially uninstalled, all files removed etc.  Little scary).  SBS wizards failed to run, had to troubleshoot that.  Once all of that was running properly, the server was running better than I remember it running in a while.  I probably fixed all sorts of issues.  But not the original issue.

The Exchange shell and console still bomb out after a short time with the "selector value not found" message.  The only reference I found to that message from Microsoft was an indication that perhaps I was running a pre-release version of WinRM 2.0.  Not sure how I could be on SBS 2011.  I tried a hotfix that was created to address an issue with the Windows Remote Management service hanging, and it would not apply to SBS 2011, although it stated it was for Server 2008 R2.

An upgrade to WinRM and Powershell 3.0 causes both the shell and the console to fail immediately rather than letting me get a couple of commands in, so removed it again.

The next thing I'm going to try is to remove the Quickbooks client application that my customer installed himself and for some reason thinks needs to be on the server (and running) to host the database.  Will leave only the database manager app.

Will also re-run the BPA.
0
 
Simon Butler (Sembee)ConsultantCommented:
Sounds like the server may not have been setup with the wizards in the first place, or changes made outside of the wizards. I have seen that a lot with SBS servers, they seem to get abused.

The other thing I would suggest that you try is a new Windows Profile. Try logging in to the server with another user who has admin rights.

Simon.
0
 
rmryan80Author Commented:
I apologize for abandoning the issue, I didn't intend to, other priorities got in the way and I didn't get back to this issue until now.  I have resolved it.

I had already tried running as a different user, and in fact I then tried installing the Exchange 2010 Management tools on a separate server and still had the problem on the 2nd server, which I really didn't expect.

I finally resorted to comparing IIS app pool settings after finding a vague reference in a Microsoft Technet article to a different (but similar) error being caused by configuration of the MSExchangePowerShellAppPool (maximum worker processes).  What I finally found was that the PrivateMemoryLimit setting for the app pool had been set to 128000KB.  I compared that to what I found on both another SBS 2011 machine and a standalone Exchange 2010 server and found that both had that setting at 0 (unlimited).  After making the change to 0, I am now able to use both the Exchange Console and the Management Shell successfully.

Thank you Simon, for your assistance.

Rich
0
 
rmryan80Author Commented:
The ultimate resolution was my own through research and troubleshooting, but Simon certainly helped me get there.
0
 
HallidaysCommented:
You legend, we have been struggling with this for a while and setting the PrivateMemoryLimit to 0 it works perfectly.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

On-Demand: Securing Your Wi-Fi for Summer Travel

Traveling this summer?Check out our on-demand webinar to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now