Windows Server 2016 - Server service broken
I have a Windows Server, where the server service (aka svchost.exe -k smbsvcs) will not start. At first, the error I received was:
Windows could not start the Server service on Local Computer
Error 1075: The dependency service does not exist or has been marked for deletion
After some Googling, I found a solution to the above error by going into the registry and deleting the DependOnService string within the LanmanServer key. While that did resolve the above error, I now have a new error when I try to start the Server service:
Windows could not start the Server service on Local Computer
Error 2: The system could not find the file specified
Obviously, the C:\Windows\System32\svchos
Also, as a related issue, I am seeing the following error repeated in Event Viewer:
Log Name: Application
Source: Perfnet
EventID: 2004
Message: Unable to openthe Server service performance object. The first four bytes (DWORD) of the Data section contains the status code
-Robert
Windows could not start the Server service on Local Computer
Error 1075: The dependency service does not exist or has been marked for deletion
After some Googling, I found a solution to the above error by going into the registry and deleting the DependOnService string within the LanmanServer key. While that did resolve the above error, I now have a new error when I try to start the Server service:
Windows could not start the Server service on Local Computer
Error 2: The system could not find the file specified
Obviously, the C:\Windows\System32\svchos
Also, as a related issue, I am seeing the following error repeated in Event Viewer:
Log Name: Application
Source: Perfnet
EventID: 2004
Message: Unable to openthe Server service performance object. The first four bytes (DWORD) of the Data section contains the status code
-Robert
McKnife
Severe internal problems can be solved by doing an inplace-upgrade. I would recommend this unless the server is a domain controller.
ASKER
@McKnife - I don't see that as a viable option at this point. Any other suggestions?
Why not? An inplace upgrade is done quickly, depending on the server, 30-90 minutes. Or are you hoping to repair it without any downtime?
Another option is this command on an elevated command prompt:
Another option is this command on an elevated command prompt:
Dism /Online /Cleanup-Image /RestoreHealth ASKER
@McKnife - We are not licensed for Windows Server 2019. Also, I am hoping to repair without downtime since it's a production server. The server does not have outside internet access, however, I can mount the MS W2016 ISO as an alternative and point the DISM to that instead.
You misunderstood. An inplace-upgrade, when used to repair, means "upgrading" to the same version you already have. You mount the setup ISO and start setup from within your running windows. System files are re-written, programs and settings are kept.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.