Check the netlogon service, and make sure it is set to start automatically, and that the service logs on as System (System Account). If the netlogon service is already set for automatic startup with the system account, then check the Event Viewer to see the exact nature of the problem. You can search the Microsoft On-line Knowledgebase (support.microsoft.com) on the specific Event ID number, and there might be an article that can provide you more detailed information about the problem.
A locked services database usually becomes unlocked after a period of time as such that all services needed are loaded up and running. If your server continues to have a locked services database condition after the machine has been running for a significant period of time (say a half-hour) then your server may suffer from a lack of RAM, or perhaps there is failing hardware which is keeping a service from properly loading, thus keeping the database locked. A failing tape drive could certainly be sucha device to cause this problem. Again, check the Event Viewer for more detailed information on the load-up of services. When a service doesn't load up properly, Event Viewer always records the problem. The Event ID numbers coupled with the MS Knowledgebase are powerful troubleshooting tools.
I would need more detailed information about your exact problem/error messages in order to offer more assistance.
Good luck tracking down the problem(s) and solving them.
