SBS 2011 Hangs on "Applying Computer Settings"
My office experienced a power loss. On reboot of the server, the load up sequence hangs at "applying user settings" I have powered down and started in safe mode with networking, but couldn't find the culprit. I have rebooted the router and the modem, to try and see if it is a DNS/DHCP issue hanging the server, to no avail. I don't know what the next step would be, so I'd appreciate any help.
SBS 2011 Standard
SBS 2011 Standard
ASKER
first, i'm using standard, not sbs 2011 essentials. so the sbs is dns and dhcp, right? im still getting hung at applying computer settings
Any chance IPv6 is disabled? That will cause this to happen.
ASKER
i checked it. it's not disabled.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
where could i find it? how do i access the logs?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks. i'll try again in the morning. i appreciate your help
Sorry, can't imagine where I saw Essentials in your question. Brain must have inserted it in some mysterious way. Robwill has you on the right track...
Any update on this as I am experiencing the exact same problem?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As well as the above, consider this Microsoft article:
http://support.microsoft.c
http://support.microsoft.c
The problems described in the symptoms section occur because of a lock on the Service Control Manager (SCM) database. As a result of the lock, none of the services can access the SCM database to initialize their service start requests. To verify that a Windows computer is affected by the problem discussed in this article, run the following command from the command Prompt:
sc querylock
The output below would indicate that the SCM database is locked:
QueryServiceLockstatus - Success
IsLocked : True
LockOwner : .\NT Service Control Manager
LockDuration : 1090 (seconds since acquired)
Let me fix it myself
you can modify the behavior of HTTP.SYS to depend on another service being started first. To do this, perform the following steps:
Open Registry Editor
Navigate to HKLM\SYSTEM\CurrentControlSet\Servic es\HTTP and create the following Multi-string value: DependOnService
Double click the new DependOnService entry
Type CRYPTSVC in the Value Data field and click OK.
Reboot the server
NOTE: Please ensure that you make a backup of the registry / affected keys before making any changes to your system.
Power outs are strange things in that many times nothing bad happens, and other times it is a real bear.
You can also run a repair from the installation media, and if your last known good backup is actually good, you can restore the system state or the OS from backup.