Windows SBS Server 2003 - Services won't start


I have a problem with a Windows SBS 2003 server.  The server performed a reboot and ran a chkdsk which replaced a load of "invalid security ids".  When this finished and the server came back up nearly all the services won't start up.  When I try to start them manually it says other dependancies are preventing the server from starting.  

Does anyone have a solution for fixing this?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Larry Struckmeyer MVPCommented:
Server performed a reboot?  Meaning the power failed or ?.  

You can trace the dependencies for each service that won't start to see if the one at the bottem of the chain will start and all those dependent to start, but my guess is you need to restore from backup.  You might also open a case with MS, but realize that they reserve "restore from backup" as a solution to cases with no other solution.

Sounds like you need a new/bigger UPS or it will happen again, assuming power failure was the cause.
Peter1985Author Commented:
I've managed to get most services running by changing RPC service to LocalSystem.  However, any services still set to NT AUTHORITY\NetworkService fails to start with access denied.  

Everything else seems to be working, is there no way of fixing this without doing a restore?
Larry Struckmeyer MVPCommented:
Can you give us a short list?  I have a SBS 2003 here I can check the default settings in Services.  However, random check shows local system to be the norm.
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

Peter1985Author Commented:
DHCP Client
Distributed Transaction Coordinator
DNS Client
License Logging
Performance Logs and Alerts
remote Procedure Call (RPC) Locator

I've now noticed that the SBS sends a message that it will shutdown in 60 minutes and then it shuts down 60 minutes later.
Larry Struckmeyer MVPCommented:
Auto shutdown is indicitive of not having all the FSMO roles.  Are there any other DC's in the domain?  This could get a little complicated for this forum, but you would fix that by first checking for the roles, then finding where they are (transfer), and if nowhere, then seizing them.  

DHCP Client - NT Authority/network service - Depends - AFD and TCP/IPSEC

Distributed Transaction Coordinator - Local System - Depends DFS, MUP, SAM/RPC, Server, Workstation

DNS Client - NT Authority/network service  - Depends TCPIP/ipsec

License Logging - NT Authority/network service - Depends: none

Performance Logs and Alerts - Network Authority\Network Service Depends: none.  That one never stays started.

remote Procedure Call (RPC) Locator - That one is manual on the reference system and not started.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Peter1985Author Commented:
Thanks for those.

Yes, there are other DC's in the domain.  Are there any knowledge base entries for this?
Larry Struckmeyer MVPCommented:
Here is a link that describes the sequence.  First see if the SBS has them or has lost one or more, then see if the other(s) are holding them.  btw, this is one of the reasons we discourage multiple DC's in an SBS domain.
Peter1985Author Commented:
The SBS server has all roles.

The event log shows shutdown was due to license logging service.  I can only start the service as LocalSystem.  It says access denied for NT Authority/network service.
Larry Struckmeyer MVPCommented:
I suspect you will need to uncover the reason it won't start.  As I said this is not the best place for complicated issues.  Perhaps:

But I would call MS Customer Support Services. (CSS)
Peter1985Author Commented:
Thanks for all your help.  It helped get a lot of the services running but unfortunately I ended up having to rebuild the server.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.