Thursday, 31 August 2017

WSUS Server Console Error: Connection Error "An error occurred trying to connect the WSUS server"

Or, 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\.

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

Or, WSUS on Server 2012 R2 - Error: Connection Error "An error occurred trying to connect the WSUS server"

Error Screenshot:








Descriptions: If you have noticed that WSUS server console is being crashed automatically after sometime and matching the error and event ID details as referred in this article, you are at the right place to get it fixed.

I was encountered with this problem and what I noticed is, after every reboot of the server wsus console was working fine for some time (may be 30 minutes to 1 hr), after that the console was getting crashed automatically and none of the client machines were able to receive any update from WSUS server.

I tried lot many things line, rebuilding database idex, re-installing WSUS server role on the same server with existing contents, wsus clean-up etc... But nothing worked.
When I checked the Application event details, I found below event ID and associated details regarding this issue.

Error Event ID (Application): 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 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\.















Reason: There could be many but in my case it was “WsusPool” IIS pool which was creating this problem. Yeah, when I checked WSUS IIS pool status, it was in stopped state. When I started this pool manually, the console started working fine.

Why this application pool was getting stooped automatically? The answer is, it was because of memory limitation on this specific IIS pool. You may be having enough memory available on the server but if there is any restriction or less memory available for the IIS pool, it would create problem.










Solution: Remove the restriction of memory limit from the WSUS app pool.

Steps:
Open IIS Manager > Go to Application Pool > Select the WsusPool > Click on Recycling from the Actions pane










Remove the check mark from “Private memory usage (in KB)” > Click Next



















Leave the Check mark enabled on “Regular time interval” > Click Finish




















Now Right Click on the “WsusPool” > Click Start















Try opening the WSUS console now, it should work...

Cheers, please write me back if you have any query or feedback.

No comments:

Post a Comment