Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, May 17, 2016 12:42 PM
This has happened to me on three different WSUS servers one server being the upstream server the others downstream replicas. All of the servers are running Windows 2012, I have install the WSUS service, IIS and am using the WID database. The installation run normally, I run post configuration, and synchronize with the upstream server, before I leave for the day client computers and servers are reporting to the new down stream server and everything appears to be running well.
On three occasions I have come back into work and found that the WSUS server is not working on one of the servers and when I try to connect to the server I recieve the error "Cannot connect to <Servername>. Please make sure the Post-Installation task is completed successfully in that server. If it was, please verify if the server is using another port or different Secure Socket Layer (SSL) setting.
I have not implemented SSL on these servers yet HTTP is still on port 80 and WSUS is on 8530.
All replies (7)
Monday, May 23, 2016 3:16 AM ✅Answered
Hi ricksherny,
Check if this method could work:
1. In cmd, cd “c:\Program Files\Update Services\Tools”
2. Enter command wsusutil.exe usecustomwebsite true
3.Enter command wsusutil.exe checkhealth
4. Then check event log, if you can see event 10000
Best Regards,
Anne
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Tuesday, May 17, 2016 1:13 PM
Fixed this, the <windir>Microsoft.net\framework64 folder did not have the network service account added. I added the account and gave it full control and I was able to connect.
4 hours later I was again not able to connect to the WSUS for this one server. I tried resetting the node, but it would not restart. I restarted the WSUS, IIS and Update services and tried again, but the WSUS application would not start. The server has been restarted and that brings the service back, but I don't want to have to reboot the server every few hours. Any ideas?
Wednesday, May 18, 2016 7:31 AM
Hi ricksherny,
1. Please compare the configurations on the problematic downstream server with other downstream servers, check if all settings are the same;
2. Check if you are running any third-party application on the problematic server, if yes, then turn off it and check the result; also run anti-virus scan and check the result;
3. Check if the server has installed any update recently, especially kb3159706, if yes, uninstall the KB and check the result.
Best Regards,
Anne
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Wednesday, May 18, 2016 8:00 AM
We had the same problem.
Lots of: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database 'SUSDB'. [CLIENT: <named pipe>]
Now removed kb3159706 and WSUS is working again.
Wednesday, May 18, 2016 12:58 PM
Hi ricksherny,
1. Please compare the configurations on the problematic downstream server with other downstream servers, check if all settings are the same;
2. Check if you are running any third-party application on the problematic server, if yes, then turn off it and check the result; also run anti-virus scan and check the result;
3. Check if the server has installed any update recently, especially kb3159706, if yes, uninstall the KB and check the result.
Best Regards,
Anne
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Thank you for responding! When I came in this morning the 1 WSUS server was again not responding and would not reset. I rebooted the server and I was then able to reset the server and WSUS was again responding.
1 - I compared the downstream servers configuration with the others and they are the same, I also verified that Network Service had full control of the asp.net folder and windows\temp folder all of the servers are configured the same.
2 - No other apps are running on this Server, this is actually a new server (30 days old). Anti Virus is updated and no viruses found
3 - I checked the installed updates and kb3159706 was not found.
Digging a little more this might be a IIS issue. It looks like after 4 hours of running normally WSUS started reporting 12012 12032 12022 12042 12052 12072 and 13042. I will have to look into those unless someone knows a quick fix for them. :)
Thursday, September 27, 2018 7:59 PM
All I found was that if I click the browse button on the wizard and specify the same path than what was already there then the post-Installation ran and completed.
Thursday, June 4, 2020 10:46 AM
All,
It worked for me!
Thanks a lot.
OEFF