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

SBS2008 Boot Problem - Some Services Not Starting


We have an SBS2008 box that has been built for around two years and has been performing well - no issues, clean event logs etc.

We went through our usual monthly MS patching routine and rebooted the server only to find that when it rebooted, some services failed to start, including DNS, Event Log Service and NetBios Helper. Also, if you try to log in right after the Ctrl-Alt-Del prompt comes up, you get an error saying that you can't log in as the Netlogon process isn't available. Wait a little longer, and you can log in. Safe Mode returns the same results.

The only way that we can restart the server normally, is to change the default system locale from UK to US, reboot the server (comes up as it should), change the default system locale back to UK, reboot the server, and it comes up as it should. This is clearly not a good situation.

Server has Exchange 2007, Symantec BESR 10, AVG 2011 Business Edition, APC Powerchute installed. The internal Sharepoint site is up and running. It has one NIC. We have a second LoB server (Windows 2008) that is a member of the domain. Nothing too complicated.

We use Symantec BESR for backups and have put the image onto another machine which displays the same problems. On this machine we have tried the following:

Event Log only has one error relating to DCOM not being able to communicate with another server, but that is a firewall issue on the other server
dcdiag - returns no issues
sfc /scannow - no integrity violations
SBS2008 BPA - nothing found
MS IT EHS - only found one issue under File Replaication Service and SYSVOL Admin (The file could not be written on the server01.mydomian.local server - See KB249256 but this is not relevant to our environment
Checked the C:\windows\winsxs\ folder for pending.xml - nothing found

One other thing that we think may cause the issue is the version of APC Powerchute that we have seems to cause a lot of problems. It won't uninstall through Control Panel and we have posted to their forums to ask for manual uninstall instrucions.

Does anyone have any solutions that may help in getting our server to boot normally, and also does anyone know how our strange workaround (found through Googling) gets us round the issue of services not starting?

  • 3
  • 2
1 Solution
How many updates went in? Any major patches?

As that's what you went through, I'd roll the server pack to prior to your monthly routine, and take it from there.

I have no idea why the system locale would make any difference to the boot process - very odd workaround, I think I'll add this to my KB for that alone!

I can only imagine that one of the patches that's gone in had corrupted the system at some level. I've found some odd M$ articles, but they're on NT server (!)


I would also try removing invasive software such as the AV and see how this affects it - but certainly get the machine back to before those updates went on!
Since the event log service dont start when the default system UK there wont be any relevant events that would provide some leads.

Probably you could move the contents of the C:\Windows\System32\winevt\Logs to another folder and restart the server? If there is any corruption with these files, this step would fix this issue.

One other way that I can think of to find the cause is to use Process Monitor with boot logging enabled and then reboot the server. However the logs would quite a large amount of information that would need to be looked after the reboot and it is time consuming. Incase you do this make sure that you stop Process Monitor right after you login as it would continue logging.
e-mattersAuthor Commented:

Thanks for the feedback.

We keep a monthly rolling backup on this server, and we duly rolled it back to before the updates took place on a test box and the same thing happened. We then went back to the earliest backup we have which was before the last set of updates, and again the same thing happens. The last time that we did updates a system restart wasn't required, which means that this issue could have been around for a while without us realising it.

I know that I won't expect to see anything in the event logs during bootup if the service doesn't start, but I mentioned this as sometimes there may be other entries in the log that might give a pointer to the problem happening. There is nothing in this case. The server runs clean of errors in the logs. I will try moving the logs but I don't believe that corruption here is an issue as the "locale swap" solution gets us in and we are able to view all the logs without issue.

I've seen the article that you mentioned but sadly it didn't provide a solution. As for removing software, we have msconfig-ed a bare boot with all third party stuff removed, and still the same problem.

We have also amended the registry as per http://support.microsoft.com/kb/2004121 with no improvement.

I think that timeouts have a part to play in the problem, because if you restart the server half a dozen times to replicate the problem, you get a different mix of services not starting. Sometimes DNS starts, sometimes it doesn't. Sometimes NetBios Helper starts and sometimes not. Event Log Service never starts.

I am waiting to get the uninstall procedure for the APC Powerchute software to see if it is this that causes problems, as there were two others that reported boot issues with this software installed.

Process Monitor Boot Logging is a good idea and I will try that this weekend. I forgot you could run it to log the boot process.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Keep us updated - if it is the APC software causing the issue I'll bank this for my KB for sure as we keep an eye on literally dozens of servers with this installed!
e-mattersAuthor Commented:

We have found the culprit, and also why changing the locale seemed to work.

It appears that it was a Group Policy setting that was applied as per:


Thanks for taking the time to offer solutions.
e-mattersAuthor Commented:
I have chosen my solution as it was the one that resolved the problem.
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

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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