Hi, I am getting Error: Connection Error in two of the WSUS servers. Normally a couple of restarts usaully gets me the console from the server, or by connecting to the WSUS server from other WSUS Update Service consoles. But for the last two/three days I am not able to do that. I checked the Application logs in the server after a reboot of the server. After about 10 min's of a restart, the servers come up with the following Even ID.

13042: Self-update is not working.

12002: The Reporting Web Service is not working.

12012: The API Remoting Web Service is not working.

12032: The Server Synchronization Web Service is not working.

12022: The Client Web Service is not working.

12042: The SimpleAuth Web Service is not working.

12052: The DSS Authentication Web Service is not working.

12072: The WSUS content directory is not accessible.
System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)

Any idea how I can go back to not having all these errors and hopefully connect to the console?

Shahidul

Hi

We are working on a new WSUS server with more power to replace our old WSUS server. I thought it would be an easy task to do, because I could just look on the old one that is still running and working fine.

Both servers are Running Windows Server 2012 R2 and nothing else. Just like my old server I want it to run on port 443 with SSL certificate. I have stopped the Default Web Site leaving me with only the WSUS Administration website with bindings on port 80 and 443. My users are not domain joined and many of the are connecting from external locations. Because if that WSUS configuration is made in registry and not with GPO, but again this setup work fine with my old WSUS server.

I get this error:

Result CODE: 0x0 0x80244019 - Same as HTTP status 404  The server cannot find the requested URI (Uniform Resource Identifier).

My test computers does not register in WSUS, unless I use plan http (80). I guess I have some kind of issue on my IIS, but how do I troubleshoot this issue?

I have no problem connecting to https://wsus2.domain.com/ClientWebService/client.asmx from my test client.

Thomas | MCP | http://www.techwork.dk

Hi,

I have WSUS on Win2K12 with patch applied and ESD mime type fixed. I'm able to install win 10 to win 10 1511 upgrades, but i'm not getting upgrade on Win7/8 computers. I can see in testing group that computer needs it, but in state I can see this:

"(Unable to Find Resource:) ReportingEvent.Client.181; Parameters: Windows 7 and 8.1 upgrade to Windows 10 Enterprise, version 1511, 10586 - en-us, Volume"

Strange is that "$WINDOWS.~BT" folder exists on that machine and previous event in WSUS console is "Download succeeded."

I'm await if download is OK, logged in user will get upgrade window where he can initiate upgrade process.

Thanks

Hi,

i would like to ask and know, if its possible to decline or uninstall an single KB within an Windows 10 cumulative update? Maybe one KB makes some trouble and has to be uninstalled for an productive environment, then the current action is to uninstall the whole cumu-patch?

Thanks in advance

Regards

I have a WSUS server in my company, and he has a problem. It takes days to get updates for the first time, after picking up for the first time he performs the updates normally, but getting there takes a long time, does anyone have any tips of how to solve this problem? Below the result of the WindowsUpdate.log file submission

Note that it presents a first error saying: WARNING: Cab file does not contain correct inner CAB file. And after several other erros.

2016-05-23 14:31:52:617  852 238 Agent *************
2016-05-23 14:31:52:617  852 238 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2016-05-23 14:31:52:632  852 238 Agent *********
2016-05-23 14:31:52:632  852 238 Agent   * Online = Yes; Ignore download priority = No
2016-05-23 14:31:52:632  852 238 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2016-05-23 14:31:52:632  852 238 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2016-05-23 14:31:52:632  852 238 Agent   * Search Scope = {Machine}
2016-05-23 14:31:52:632  852 238 Setup Checking for agent SelfUpdate
2016-05-23 14:31:52:632  852 238 Setup Client version: Core: 7.6.7600.320  Aux: 7.6.7600.320
2016-05-23 14:31:52:664  852 238 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2016-05-23 14:31:52:788  852 238 Misc  Microsoft signed: NA
2016-05-23 14:31:52:788  852 238 Misc WARNING: Cab does not contain correct inner CAB file.
2016-05-23 14:31:52:788  852 238 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2016-05-23 14:31:52:804  852 238 Misc  Microsoft signed: NA
2016-05-23 14:31:52:804  852 238 Setup Wuident for the managed service is valid but not quorum-signed. Skipping selfupdate.
2016-05-23 14:31:52:804  852 238 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
2016-05-23 14:31:52:804  852 238 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
2016-05-23 14:32:23:605  852 238 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
2016-05-23 14:32:23:621  852 238 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.1.204:8530/ClientWebService/client.asmx
2016-05-23 14:48:33:974  852 238 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2016-05-23 14:48:33:974  852 238 PT WARNING: SOAP Fault: 0x00012c
2016-05-23 14:48:33:974  852 238 PT WARNING:     faultstring:Fault occurred
2016-05-23 14:48:33:974  852 238 PT WARNING:     ErrorCode:CookieExpired(6)
2016-05-23 14:48:33:974  852 238 PT WARNING:     Message:(null)
2016-05-23 14:48:33:974  852 238 PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2016-05-23 14:48:33:974  852 238 PT WARNING:     ID:a47c5231-5e15-4273-93a8-2059fc95c9e9
2016-05-23 14:48:33:974  852 238 PT WARNING: Cached cookie has expired or new PID is available
2016-05-23 14:48:33:974  852 238 PT Initializing simple targeting cookie, clientId = 25e67204-1fda-4621-a50f-cb7a6a3e4d05, target group = PAGE, DNS name = teste-wsus.page.local
2016-05-23 14:48:33:974  852 238 PT   Server URL = http://192.168.1.204:8530/SimpleAuthWebService/SimpleAuth.asmx
2016-05-23 15:20:47:366  852 238 PT WARNING: Exceeded max server round trips: 0x80244010
2016-05-23 15:20:47:382  852 238 PT WARNING: Sync of Drivers failed (Software succeeded): 0x80244010
2016-05-23 15:27:07:937  852 238 PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
2016-05-23 15:27:07:937  852 238 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.1.204:8530/ClientWebService/client.asmx

Hello All,

Is it completely safe to install widows security and critical updates while applications are running ?
I know that most updates require a reboot to finish the installation so you don't know

if everything is ok until you reboot the system, but is there any chance

that the updates will cause the system or some applications to crash even before reboot ?

Normally we don't install any updates without downtime but the customer

doesn't want a long downtime in case of one particular server so he wants us to install the updates while the application is running.

I was advised against it by some colleagues but I don't know specifically why it should be a problem.

Thanks in advance !

hi , i've wsus 3.0 sp2 installed on a windows 2012 server , 

when i do client diagnostic the result is 

WSUS Client Diagnostics Tool

Checking Machine State
        Checking for admin rights to run tool . . . . . . . . . PASS
        Automatic Updates Service is running. . . . . . . . . . PASS
        Background Intelligent Transfer Service is not running. PASS

GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002

Impossibile trovare il file specificato.

 the windowsupdate.log contain that information

2016-05-2414:42:52:1857641eee0AUFeatured notifications is disabled.
2016-05-2414:42:52:1857641eee0AUSetting AU scheduled install time to 2016-05-28 01:00:00
2016-05-2414:42:52:1857641eee0AUSuccessfully wrote event for AU health state:0
2016-05-2414:42:52:18576422f5cReportREPORT EVENT: {8BB5429D-04F5-4EFC-9A3A-8801B40C6A80}2016-05-24 14:42:47:203+02001202102{00000000-0000-0000-0000-000000000000} 00AutomaticUpdatesSuccessContent InstallReboot completed.
2016-05-2414:42:52:1857641eee0AUSuccessfully wrote event for AU health state:0
2016-05-2414:48:52:22576422f5cPTWARNING: Cached cookie has expired or new PID is available
2016-05-2414:48:52:22576422f5cPTInitializing simple targeting cookie, clientId = 8bd76c8b-8ae7-4c34-b673-3de6c257ace9, target group = , DNS name = pc-ced.cci.locale
2016-05-2414:48:52:22576422f5cPT Server URL = http://SERVER2012:8530/SimpleAuthWebService/SimpleAuth.asmx
2016-05-2414:48:54:58176422f5cPTWARNING: GetCookie failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200
2016-05-2414:48:54:58176422f5cPTWARNING: PTError: 0x80244008
2016-05-2414:48:54:58176422f5cPTWARNING: GetCookie_WithRecovery failed : 0x80244008
2016-05-2414:48:54:58176422f5cPTWARNING: RefreshCookie failed: 0x80244008
2016-05-2414:48:54:58176422f5cPTWARNING: RefreshPTState failed: 0x80244008
2016-05-2414:48:54:58176422f5cPTWARNING: PTError: 0x80244008
2016-05-2414:48:54:58176422f5cReportWARNING: Reporter failed to upload events with hr = 80244008.
2016-05-2414:49:39:8437642288cAUTriggering AU detection through DetectNow API
2016-05-2414:49:39:8437642288cAUTriggering Online detection (interactive)
2016-05-2414:49:39:84376422ce8AU#############
2016-05-2414:49:39:84376422ce8AU## START ##  AU: Search for updates
2016-05-2414:49:39:84376422ce8AU#########
2016-05-2414:49:39:84376422ce8AU<<## SUBMITTED ## AU: Search for updates [CallId = {F10BC73B-FDC5-486C-8E23-39F489583B4D}]
2016-05-2414:49:39:84376422f5cAgent*************
2016-05-2414:49:39:84376422f5cAgent** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2016-05-2414:49:39:84376422f5cAgent*********
2016-05-2414:49:39:84376422f5cAgent * Online = Yes; Ignore download priority = No
2016-05-2414:49:39:84376422f5cAgent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2016-05-2414:49:39:84376422f5cAgent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2016-05-2414:49:39:84376422f5cAgent * Search Scope = {Machine}
2016-05-2414:49:39:84376422f5cSetupChecking for agent SelfUpdate
2016-05-2414:49:39:84376422f5cSetupClient version: Core: 7.6.7601.19161  Aux: 7.6.7601.19161
2016-05-2414:49:39:89076422f5cMiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2016-05-2414:49:39:89076422f5cMiscMicrosoft signed: NA
2016-05-2414:49:39:89076422f5cMiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPAC56.tmp with dwProvFlags 0x00000080:
2016-05-2414:49:39:89076422f5cMiscMicrosoft signed: NA
2016-05-2414:49:39:92176422f5cMiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2016-05-2414:49:39:93776422f5cMiscMicrosoft signed: NA
2016-05-2414:49:39:95276422f5cSetupDetermining whether a new setup handler needs to be downloaded
2016-05-2414:49:39:95276422f5cSetupSelfUpdate handler is not found.  It will be downloaded
2016-05-2414:49:39:95276422f5cSetupEvaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
2016-05-2414:49:39:95276422f5cSetupSetup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
2016-05-2414:49:39:95276422f5cSetupEvaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2016-05-2414:49:39:96876422f5cSetupSetup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
2016-05-2414:49:39:96876422f5cSetupEvaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2016-05-2414:49:39:98476422f5cSetupSetup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
2016-05-2414:49:39:98476422f5cSetupSelfUpdate check completed.  SelfUpdate is NOT required.
2016-05-2414:49:40:81076422f5cPT+++++++++++  PT: Synchronizing server updates  +++++++++++
2016-05-2414:49:40:81076422f5cPT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://SERVER2012:8530/ClientWebService/client.asmx
2016-05-2414:49:40:81076422f5cPTWARNING: Cached cookie has expired or new PID is available
2016-05-2414:49:40:81076422f5cPTInitializing simple targeting cookie, clientId = 8bd76c8b-8ae7-4c34-b673-3de6c257ace9, target group = , DNS name = pc-ced.cci.locale
2016-05-2414:49:40:81076422f5cPT Server URL = http://SERVER2012:8530/SimpleAuthWebService/SimpleAuth.asmx
2016-05-2414:49:40:84276422f5cPTWARNING: GetCookie failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200
2016-05-2414:49:40:84276422f5cPTWARNING: PTError: 0x80244008
2016-05-2414:49:40:84276422f5cPTWARNING: GetCookie_WithRecovery failed : 0x80244008
2016-05-2414:49:40:84276422f5cPTWARNING: RefreshCookie failed: 0x80244008
2016-05-2414:49:40:84276422f5cPTWARNING: RefreshPTState failed: 0x80244008
2016-05-2414:49:40:84276422f5cPTWARNING: Sync of Updates: 0x80244008
2016-05-2414:49:40:84276422f5cPTWARNING: SyncServerUpdatesInternal failed: 0x80244008
2016-05-2414:49:40:84276422f5cAgent * WARNING: Failed to synchronize, error = 0x80244008
2016-05-2414:49:40:84276422f5cAgent * WARNING: Exit code = 0x80244008
2016-05-2414:49:40:84276422f5cAgent*********
2016-05-2414:49:40:84276422f5cAgent**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2016-05-2414:49:40:84276422f5cAgent*************
2016-05-2414:49:40:84276422f5cAgentWARNING: WU client failed Searching for update with error 0x80244008
2016-05-2414:49:40:8427641eee0AU>>##  RESUMED  ## AU: Search for updates [CallId = {F10BC73B-FDC5-486C-8E23-39F489583B4D}]
2016-05-2414:49:40:8427641eee0AU # WARNING: Search callback failed, result = 0x80244008
2016-05-2414:49:40:8427641eee0AU # WARNING: Failed to find updates with error code 80244008
2016-05-2414:49:40:8427641eee0AU#########
2016-05-2414:49:40:8427641eee0AU##  END  ##  AU: Search for updates [CallId = {F10BC73B-FDC5-486C-8E23-39F489583B4D}]
2016-05-2414:49:40:8427641eee0AU#############
2016-05-2414:49:40:8427641eee0AUSuccessfully wrote event for AU health state:0
2016-05-2414:49:40:8427641eee0AUAU setting next detection timeout to 2016-05-24 17:49:40
2016-05-2414:49:40:8427641eee0AUSetting AU scheduled install time to 2016-05-28 01:00:00
2016-05-2414:49:40:8427641eee0AUSuccessfully wrote event for AU health state:0
2016-05-2414:49:40:8427641eee0AUSuccessfully wrote event for AU health state:0
2016-05-2414:49:45:84976422f5cReportREPORT EVENT: {568DFF8E-314A-4D13-A14E-1356B36FDFDC}2016-05-24 14:49:40:842+02001148101{00000000-0000-0000-0000-000000000000} 080244008 AutomaticUpdatesFailureSoftware SynchronizationWindows Update Client failed to detect with error 0x80244008.
2016-05-2414:49:45:84976422f5cReportCWERReporter::HandleEvents - WER report upload completed with status 0x8
2016-05-2414:49:45:84976422f5cReportWER Report sent: 7.6.7601.19161 0x80244008(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdates {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0

Goodmorning,

We had some storage issues where the WSUS server (on Server 2012R2) is located. Now, If I try to open WSUS console, it directly displays  "Error: Database error", and (the wellknown) "reset server node" button.
In the eventvwr, the following error is displayed;
Event 824 MSSQL$MICROSOFT##WID
SQL Server detected a logical consistency-based I/O error. [..] Complete a full database consistency check (DBCC CheckDB) (on susdb.mdf).
I have already discovered how I connect to the SusDB.MDF (through SQL Management Studio) and tried to start DBCC, but it failed after some time.

I also tried to run the wsusdbmaintenance sql script, but it also failed with "opening a connection to SQL server [2]". So it looks like the WID has some internal problems.

Is there somehow a possibility to re-create the WID and SUSDB without reinstalling WSUS again? Or are there any other solutions to fix the problem?

Thanks in advance

I am having issues with patching some newly created Windows Server 2012 R2 servers.

Windows Server 2012 Update rollup 2919355 is not cumulative despite the description

https://support.microsoft.com/en-gb/kb/2919355

It states "This update is a cumulative update that includes the security updates and the non-security updates for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 that were released before March 2014. In addition to previous updates, it includes features such as improved Internet Explorer 11 compatibility for enterprise applications, usability improvements, extended mobile device management, and improved hardware support. "

I have this update applied, but it does not contains the fixes in Windows Server 2012 R2 update rollup: November 2013

https://support.microsoft.com/en-gb/kb/2887595

the specific fix it does not contain is https://support.microsoft.com/en-gb/kb/2896636"You cannot use certain third-party devices to send a document to a shared folder in Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2"

If this is the case as I believe, then the only way to fully patch Server 2012 R2, is to manually apply every single Rollup ever released. Because WSUS has marked the previous rollups as "Superseded".

also the article at https://blogs.technet.microsoft.com/chad/2015/01/21/current-windows-server-2012-r2-windows-8-8-1-update-rollups/  seems to say you just need to put on :-

April 2014 – http://support2.microsoft.com/kb/2919355 

November 2014 – http://support2.microsoft.com/kb/3000850

and December 2014 – http://support2.microsoft.com/kb/3013769

Am I correct?  can anyone else verify if this as the case? 

Is there some other cumulative rollup we should be applying instead ?

Is there any formal way of providing customer feedback to the WSUS Team?  UserVoice? Microsoft Connect? Secret Twitter Handle? Some shared email box? Draw a chalk X on the mailbox outside Building 23 and then stick a note under the bus bench outside Building 12?  Whatever it is, let us know and we'll use it.

I'm a Microsoft MVP and a Gold Microsoft Partner, and I'm coming up empty. Is it possible that there is no feedback channel for the WSUS team? There are a lot of things that cause pain and frustration for customers that only seem to make sense if the product team really is unaware of the impact. Rather than complain here or on Twitter, we'd love to help make the pain points go away.

Thanks for your help!

Nash

Nash Pherson, Senior Systems Consultant
Now Micro - My Blog Posts
If you found a bug or want the product to work differently, share your feedback.
<-- If this post was helpful, please click the up arrow or propose as answer.

Our WSUS server (Windows Server 2012 R2) hanged when it was installing updates on itself. I rebooted it in a harsh way, it started normally and finished installing the updates. However, now I can't start the WSUS management console due to a connection error. The WSUS server service itself doesn't start as well.

The Application server contains multiple events 18456, source MSSQL$MICROSOFT##WID, message "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database 'SUSDB'. [CLIENT: <named pipe>]" If I try to connect to the server using SQL Server Management Studio, it displays the following error: 

"Cannot connect to \\.\pipe\MICROSOFT##WID\tsql\query. Login failed for user 'MY-LOGIN'. (Microsoft SQL Server, Error: 18456)"

The Application even log contains the same event mentioned above, only the message is different: "Login failed for user 'MY-LOGIN'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT:<named pipe>]".

If I restart the Windows Internal Database service, it starts normally and doesn't throw any errors in the Application log. Among other things, it successfully mounts the SUSDB database. No other errors (including DCOM errors) can be found in the log.

Seems that security setting on the WID engine are damaged. Any ideas how to fix them? Besides reinstalling the server, of course? :)

Evgeniy Lotosh // MCSE: Server infrastructure, MCSE: Messaging

I’m still having problems with this.

KB3148812 had been installed and WSUS stopped working, clients were unable to check for updates. Did some research and uninstalled it.

Later installed 3159706 via Windows Update – no restart notification displayed but WSUS was still not starting (saw a ‘Reset server node’ message which did not work). Rebooted, Server Manager flagged WSUS Service as not started on restart, but a refresh showed it was started. Ran WSUS, but saw same message.

Copied error and followed recommendation to delete wsus file at %appdata%\Microsoft\MMC\. WSUS now starts, but the server was not listed. Chose to connect to the server but an error message about SQL not running was displayed (port is correct: 8530). All SQL services seem to be running.

Any suggestions, please?

Thanks

--

Here's the error from the console:

**********************************************************************

The WSUS administration console was unable to connect to the WSUS Server via the remote API.

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,

Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.

System.IO.IOException -- The handshake failed due to an unexpected packet format.

Source
System

Stack Trace:
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
** this exception was nested inside of the following exception **

System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.

Source
Microsoft.UpdateServices.Administration

Stack Trace:
   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
   at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()

**********************************************************************

We have a default install of WSUS 6.3.9600.16384 we have been unable to put into production because IIS Worker Processes are consuming 90(+)% of the (4) CPU's which causes the WSUS management console to crash. The install is on a newly built Windows 2012 R2 Datacenter server with no other server Roles or Features installed. When the WSUS role was added, it added the additional required roles and features as needed, we added nothing extra.

In IIS, when the role was installed it shows 2 sites, the Default Web Site bindings on port 80 and the WSUS Administration site bindings on ports 8530 & 8531. 2,900 Machines are hitting the new server and showing up in WSUS console. We are also able to sync and pull down updates without issue.

What is occurring is that IIS Worker Processes will consume all of the CPU resources causing the WSUS management to freeze and crash. Once the management console crashes, we found that we can do an "iisreset" and once the reset has completed WSUS begins functioning without issue until the IIS Worker Processes peg the CPU's again. (Which most times only takes a few minutes after IIS has been reset.) We have done multiple new builds/WSUS installs as described above and each time we have the same issue with the IIS Worker Process pegging the CPU's.

When this occurs we see the following error in the event logs:

The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console.

The IIS worker process that is causing this is the WSUSPool (process id: 7052)

Does anyone have a solution or work around to fix this issue?

Additional Note: Previously we were using WSUS 3.0 on Windows Server 2008 for several years and never encountered this issue.

Greetings

I am installing my WSUS in windows server 2012 R2 fully updated and SQL 2014 Standard edition fully updated also. hardware specs in dual processor and 16 GB of ram. it handle only wsus no other role installed in this server, and by the freshly installed both windows and sql. after enabling wsus role in the server I got the famous update which is KB3159706 so it crash my wsus for I searched the internet and I found I need to do so manual step to it so I did the post installation and it is successfully done and also I enabled the Http activation and I am not using SSL so I only took the ownership of the file but I didn't edit it. it worked fine for few hours but then it crashed suddenly and iisreset command was solving the issue but for few hours and then it crash again, by the way I did reindexing for the database and it didn't solve the problem. the only thing that solve the problem is to uninstall the KB 3159706 update. but my question is there a way to install the update and make WSUS working correctly did anybody figure out how to do so.

thanks in advance

Hossam

Hi, after a recent update I WSUS would not display in its usual fashion. I have an option to copy the error to the clipboard and the following is displayed:

Can anyone please advise me to what the problem might be, and how to resolve the issue?

WINDOWS 7 WORKSTATIONS / SETUP FOR A WEEK NOW / SHOW AS "NOT REPORTED YET.: IN WSUS.....?????  lOGFILE SHOWS.....

Hi, I still have problems with my WSUS server running on Windows Server 2012 R2.

KB3148812 broke my WSUS, like everyone, so I waited for KB3159706 to be released.

After installing KB3159706 and doing the manual steps, my WSUS seemed to work fine at first sight, but in fact it's not...

Without doing anything particular, the WSUS seems to crash randomly 2/3 times per day : when it happens I can't connect to the WSUS console, and the clients can't reach the WSUS server to get updates, that's really annoying...

The only thing I can do is reboot the Windows Server to get the WSUS back, but you understand that I can't do that every 4 hours...