Click on the Category button to get more articles regarding that product.
Our Education/Migration Lab is the place where we consider every Crash as Bonus and source for learning and finally reproduce crashes before they happen at customers.
Last massive we Seen was with Server 2008 RTM and Exchange Server on it. We are unsure if it was disabling IPV6 by Registry, Handling, or Manipulation Certificate Stores (wrong Trusted Root Certificates). Mainly this bug happens with Exchange or SharePoint and thus IIS Webserver where you handle San/Wildcard or self-signed Certificates.
However > that happens:
ERROR:
-
Server 2008 stuck at “applying computer settings”
-
All Services are Down
-
Your main services like Exchange / SharePoint and VMWARE Tools are not working
-
You can PING the Server. You can PING from within the Server.
-
You can’t access \c$ from External
-
You can’t access a SHARE from within the Server
If this already happened
-
Reboot in Safe Mode
-
Open mmc
-
Add Services
-
Disabled all Services which you Don’t need like (sample > backup/Vmware/VSS/Agents just leave the main Services from Windows)
-
Reboot The Server normal
-
Check the HOTFIX from Microsoft
-
Re-install VMware Tools
https://support.microsoft.com/en-us/kb/2379016 (Hotfix Server 2008)
|
How to find a Service that LOCKS others because it’s stuck |
|
This issue can be caused by a service deadlock in Windows. To confirm, run this command from a command prompt window: sc querylock You can find more info very well done here: If the output contains IsLocked: TRUE, then the service control manager is in a locked state due to a failed service start. |
When you start a computer that is running Windows Vista Service Pack 2 (SP2) or Windows Server 2008 Service Pack (SP2), the computer stops responding and appears to hang at the “Applying User Settings” or “Applying Computer Settings” stage of the logon process.
You may experience that the “network connections” folder is empty. Additionally, the following services may not start at startup.
Note these services are set to the “Automatic” start up type.
-
Print Spooler
-
Terminal Services
-
Server service
-
Remote Registry
-
Windows Management Instrumentation (WMI)
-
Distributed Transaction Coordinator
-
Any services that are related to applications
-
Note: This issue typically occurs after you install a server certificate and then configure Secure Sockets Layer (SSL) on the computer. For example, you install a SSL server certificate in Internet Information Services (IIS) 7.0 and then enable HTTPS on your website to use the certificate.
CAUSE
This issue occurs because of a deadlock in the Service Control Manager database.
The Service Control Manager tries to start the HTTP.sys service and then puts a lock in place in the Service Control Manager database. Then, HTTP.sys makes a call that requires Cryptographic Services during startup. Then, a request is sent to start Cryptographic Services. However, a lock is already in place in the Service Control Manager database. Therefore, a deadlock occurs.
|
|
|
Note The following method can be used in Windows Safe Mode when you are not able to log on successfully to install the hotfix or fixit. To work around the issue without installing the hotfix, create a DependOnService registry key to modify the behavior of HTTP.sys. This makes HTTP.sys depend on crytosvc service to be started first. To do this, follow these steps:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP
|
, type regedit in the Start Search box, and then press ENTER.
