SBS 2011 Server keeps auto rebooting after RPC server error and exchange errors

Hi Everyone,

Have a strange one here. We have a SBS2011 server that just keeps failing and eventually auto rebooting on it own, I have review the system logs and they are as follows:

1) It starts to fail with some DistributedCOM-Event ID 10009 errors

2) Then Service Control Manager error - event ID 7031 - The RPC Endpoint Mapper service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 120000 milliseconds: Restart the service.

3) That is when everything then goes haywire as we get as then we get another event ID 7031 when the service fails to restart

4) Then other dependent services start to crash with event ID's 7001, 7023, 7032

5) Then group policy errors with event ID 1007

6) Then schannel errors with event ID 36870 then eventually a kernel-power error and the server auto reboots

After the reboot system takes a while to come back online but eventually works again for a while but repeats these errors approximately every 1 hour

This is a VM server running on Esxi 5.0.1 and has all the latest VM drivers installed.

I am not sure what to do next as we are not getting any hardware issues on the unit (in heath status in VMWare) and it does not seem to be a resource or performance issue. Also have run chkdsk /f from safe mode and no issues found. All we have been able to determine is once the RPC service fails there is little we can do except reboot the server manually through a command prompt.

Any help you could provide with be great.


Who is Participating?
Mike LazarusConnect With a Mentor Act! Evangelist - CRM ConsultantCommented:
You might also look at this for the RPC issue:;en-US;2401588
Adam BrownConnect With a Mentor Sr Solutions ArchitectCommented:
Is your server up to date on updates? Make sure all of the latest Windows server 2008 R2, Exchange 2010, and SBS 2011 updates and service packs are installed on the server and see if that resolves the issue.
TheSonicGodAuthor Commented:
Thanks for the suggestion acbrown2010,

I have run all the updates that were available and SBS2011 SP1 was already installed for this server.

I rebooted the server after the updates and it would not even let me log in. I forced a reboot again and now that it is back up I reviewed the logs and there are about 1000 warnings in the system logs for the time I could not login - which all say about the same - they are as follows:

Source: WAS  Event ID: 5009  Desc 1:  A process serving application pool 'SBS Web Applications application pool' terminated unexpectedly. The process id was '7888'. The process exit code was '0xffffffff'.

Desc 2: A process serving application pool 'MSExchangeServicesAppPool' terminated unexpectedly. The process id was '9000'. The process exit code was '0xffffffff'.

Desc 3: A process serving application pool 'MSExchangeOWAAppPool' terminated unexpectedly. The process id was '1060'. The process exit code was '0xffffffff'.

The process id number changes on each entry. I reviewed the logs further going back to when the system locked up prior to the updates to see if these errors were also there and for some of the lockup there were and for the other reboots they were not there only the prior errors as listed in prior entry.

Ran Windows Server Solutions Best Practices Analyzer 1.0 and it advised that Exchange SP2 was not installed on this server so I tried to install it and it fails on the first part of the install 'Configuring Prerequisite'  - it fails with the error Service (WinMGMT) cannot be configured due to the following error: 'Access is Denied' - I was running it as the domain admin so it is not a security access issue,

Searched for this error online and there is nothing - not sure where to go next.

thanks in advance for your replies.

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

Gary ColtharpConnect With a Mentor Sr. Systems EngineerCommented:
I have seen querky issues like this with a corrupt paging file. You can try removing the paging file through the performance settings, rebooting and readding a system managed paging file.


TheSonicGodAuthor Commented:
Thanks for your suggestion gcoltharp.

Prior to updating the pagefile, the server was rebooted and came up with a File Name Warning - "There is a program in your computer called "C:\Program" which could cause certain applications to not function correctly.  Renaming it to "C:\Program1" would solve this problem.  Would you like to rename it now?" - Rename OR Ignore

fie name warning error on startup
Checked the folder, nothing was in  it (0 bytes), clicked on rename.

The page file was removed and server rebooted - it ran for about 45 minutes and the server rebooted again.

Thanks in advance for any replies ...
Gary ColtharpSr. Systems EngineerCommented:
suspicious... antivirus installed on this server?
TheSonicGodAuthor Commented:
blew away all pagefile settings and left it turned off - Exchange services as currently down again but server did not auto reboot this time - diagnosing further now
Mike LazarusAct! Evangelist - CRM ConsultantCommented:
1. Dcom error - 
2. SCM7031 is a password issue - 
3. Can't login
4. Expected
5. GpPol1007 -
6. Schannel36870 - If the private key is not configured with the proper ACL for the network service, you usually see this. This is old, but might give an idea -

I'd start with the link in #2 to sync the passwords
compdigit44Connect With a Mentor Commented:
1) Any setting changes to the server lately both at the OS and VM level?
2) Is a AV running on the server.
3) Is the a memorydump file generated?
4) Have you tried to vmotion the VM to another host?
5) Are you using a SAN? IF so, any error on the host HBA or CNA?
6) Does the VM & host have ample memory?
TheSonicGodAuthor Commented:
Hi Everyone,

Thanks for all your help - we were able to resolve the issues by disabling IPv6 and installing the hotfixes from the posting from GLComputing

Here is another article that describes what our issues were as well as how to fix it.

The quick fix was to disable IPv6 the correct way for the SBS 2011 server using this article

Apparently once the hotfixes are installed as well as SP1 (we already has this installed) you can re-enable IPv6 but we have just left it disabled at this point. We would like a few good backups and a few days of being stable before experimenting more.

Thanks again for everyone's help and assistance with this matter.

All Courses

From novice to tech pro — start learning today.