troubleshooting Question

Looking for help with a WSUS resinstallation that is failing during post-deployment configuration tasks...

Avatar of Scott Milner
Scott MilnerFlag for United States of America asked on
WSUSMicrosoft IIS Web Server
13 Comments1 Solution1370 ViewsLast Modified:
Hello Experts!

I'm trying to reinstall WSUS on a Server 2012 R2 Standard domain member server.  I'm attempting to use the Windows Internal Database.  I'm installing from Server Manager - Add roles and features.

The initial role installation of WSUS and feature install of WID complete successfully.  However, the post-deployment configuration tasks have consistently failed for the past two days, through numerous uninstalls, reboots, etc.  It seems to have settled in on the following error in the install log:

2017-03-13 17:01:54  CreateDefaultSubscription failed. Exception: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.2.43:8530
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---

ultimately halting the post-deployment configuration with the following message:

2017-03-13 17:01:54  StartServer encountered errors. Exception=Unable to connect to the remote server
2017-03-13 17:01:54  Microsoft.UpdateServices.Administration.CommandException: Failed to start and configure the WSUS service
   at Microsoft.UpdateServices.Administration.PostInstall.Run()
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
Fatal Error: Failed to start and configure the WSUS service


The first error seems (to me, anyway) to point to a problem with IIS.  The 'remote' server that is being called out is actually the WSUS server (192.168.2.43).  There is nothing else running on port 8530 that I'm aware of, although I'm very weak in IIS.

Here are the steps that I tried during the last installation:

1.  Uninstalled the WSUS role and the WID feature.
2.  Manually deleted the C:\Windows\WID folder (there were remnants left over after the uninstall).
3.  Deleted the WSUS Administration site from IIS Manager.
4.  Rebooted.
5.  Installed the WSUS role and WID feature.
6.  Rebooted  (probably not necessary at this step).
7.  Launched Post-deployment configuration tasks from Server Manager.

The tasks failed after a few minutes.  I've attached the log file.


Can anyone offer me any assistance?  I'm honestly considering dumping the whole server and starting over, but the server also runs internal SMTP services and our helpdesk application, so it's a bunch more work than it sounds to stand it back up.  I'd much prefer to fix this WSUS problem than reload everything.

Thanks in advance.

Scott
ASKER CERTIFIED SOLUTION
Dan McFadden
Technical Lead - Active Directory

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 13 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 13 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros