asked on

WSUS on server 2012 r2 keeps crashing

Hello All,

I am having a mind boggling issue with a fresh WSUS server on a dedicated server just for the role. Server operating system is 2012 R2 and it is fully patched. I am getting a series of errors as WSUS crashes.

Event 7032-------------------------------------------------------------------------------------------------------------------------
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 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 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.

System.Net.Sockets.SocketException -- An existing connection was forcibly closed by the remote host

Source
System

Stack Trace:
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
** this exception was nested inside of the following exception **
---------------------------------------------------------------------------------------------------------------------------------
Then under system log I recieve this error
Event 5002----

Application pool 'WsusPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

----------------------------------------
Event 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)

----------

If I restart the server the WSUS role functions for a short duration then crashes again. I have attempted to reinstall at least 3 separate times. I am installing the role from the server manager pane.

Don S.

Seems like a permissions issue in the folders for content and/or wsus database. See this article: http://technet.microsoft.com/en-us/library/cc708545(v=ws.10).aspx

Rbraswell

ASKER

The permissions appear to be spot on based on the article. I am going to remove WSUS again and install it on another drive. let us see if this remedies the issue.

Rbraswell

ASKER

I ran a WSUS diagnostic by solar winds and ran into 2 errors client side.

# Solarwinds® Diagnostic Tool for the WSUS Agent
# 9/24/2014
Machine state
User rights: User has administrator rights
Update service status: Running
Background Intelligent Transfer service status: Running
OS Version: Windows 7 Enterprise Service Pack 1
Windows update agent version: 7.6.7600.320 (WU Agent is OK)
Windows Update Agent configuration settings
Automatic Update: Enabled
Options: Automatically download and notify of installation
Use WSUS Server: Enabled
Windows Update Server: http://hulk:8530
Windows Update Status Server: http://hulk:8530
WSUS URLs are identical: Identical
WSUS URL is valid: Valid URL
WSUS Server Connectivity
clientwebservice/client.asmx: OK
simpleauthwebservice/simpleauth.asmx: OK
content: Error: NotFound (Omitting required port suffix on URL to access WSUS installed to port 8530 or resource is unreachable)
selfupdate/iuident.cab: OK
iuident.cab: Error: NotFound (Omitting required port suffix on URL to access WSUS installed to port 8530 or resource is unreachable)

Don S.

What port did you install wsus to? Is there anything else using iis on the server?

ASKER CERTIFIED SOLUTION

Rbraswell

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Rbraswell

ASKER

Because it was the solution to my issue.

OlafE

This issue seems to happen especially on a fresh installed WSUS server, which has to handle a multitude of updates.
A solution I found for this is to increase some ressources for the WsusPool in Internet Information Server:
In IIS right click WsusPool and select Advanced Settings.
Increase the values for Queue Length in General Section (I increased from 1000 to 3000, more is possible).
Increase the Private Memory Limit under Recycling (defaulting to 1843200 KB) to 7843200 KB (If your server has enough memory.)