An error occurred trying to connect the wsus server

Windows Server Update Service (WSUS) handles the distribution of updates that are released by Microsoft Updates to computers on a network. It is a Windows service that will manage and deploy the updates, patches, and hotfixes for the Windows server and client operating system. However, some users complained that an error occurred when trying to connect to the WSUS server. This could occur due to several reasons. In this article, you will know how to fix this problem. Following is the exact error message users see.

An error occurred trying to connect the WSUS server. This error can happen for a number of reasons. Check connectivity with the server. Please contact your network administrator if the problem persists.

There are many reasons for this said error and we can resolve this error by using different methods. If an error occurred trying to connect to the WSUS server then use the following prescribed solutions to fix this issue.

1. Delete WSUS files
2. Enhance Storage Space
3. Restart Node in the Console
4. Restart the Service
5. Increase the Private Memory Limit
6. Contact your network administrator

Let’s try to resolve your error by using these methods.

1] Delete WSUS files

WSUS database will grow if you are downloading and deploying patches for the different operating systems and different Microsoft products and if you delete expired WSUS files you will be freeing more space as a result of which your issue will be resolved. Follow the prescribed to delete redundant WSUS files.

1. Write %appdata% in the Search bar (you can find the search bar at the bottom) and click on Open.
2. Go to Microsoft > MMC directory in File Explorer.
3. Right-click on the WSUS file and click on the Delete option in the drop-down list.

After using this method, your said error will be resolved.

2] Enhance Storage Space

WSUS service needs an ample amount of storage space and if the storage space on your computer is insufficient then its administrator console won’t be able to store the data from the server, hence, it will be difficult to retrieve the information from the WSUS server and the service can’t work. To know what’s eating your storage, you should use the following instruction.

• Click on the Start button.
• Here, click on Settings > System.
• Click on Storage.
• Go to the required drive and click on Show more categories.
• Wait for a few seconds, once storage usage is loaded, here you can see which type of files use what amount of disk space.
• If you want to know more storage usage information about a particular type of file, then click on its option.

Once you know the storage space of the hard disk, delete all unnecessary files to free more space and you can also enhance more storage space if required. Hopefully, by adding more storage space your error will be resolved.

3] Restart Node in the Console

Restarting the node in the console will allow your computer to reboot the network and other services running alongside it. Follow the prescribed steps to do the same.

1. Click on the Start icon on your WSUS Server > All Programs
2. Go to Administrative Tools > Microsoft Windows Server Update Service to access the WSUS Administrative Console.
3. Go to the System Health page and then move to the Nodes page.
4. Select the particular PPM Server node, here click on the Restart
   button.

There are optional features such as Redeploy content folder, you can select it and click OK to restart the node. After using this method, your error will be cured.

4] Restart the Service

To fix the said error, you can restart the Internet Information Service. The IIS is required to host a website on your computer and for other network purposes. Follow the steps mentioned below to restart related services.

1. Press the Windows key + S, search for the Control Panel and open it.
2. Click on Programs and then click on the Programs and Features option.
3. In the left pane of the window, click on the Turn Windows features on and off option.
4. Select the Internet Information Service feature, expand select all the options under IIS, untick them, and click on the OK button.

Once the service is stopped, go ahead and restart them. Restarting the service will solve this issue.

5] Increase Private Memory Limit

The Private Memory Limit controls the memory usage of a web application. If you have manually configured this setting, it’s very likely that there is some kind of error in the configuration, as a result of which, you encounter the error code in question.

WSUS connection issue can be resolved by increasing the Private Memory Limit to 4-8 GBs. If you are not certain what to put in the option, you can put ‘0’ there. This will allow the program to decide how much memory it needs. To fix the said error, let’s try to tune our service so that it works fine.

1. Open the IIS Manager using the search bar.
2. Go to the Application Pools in the Connections list.
3. Select WsusPool and select Advance Settings
4. Here, you need to search the parameter named Private Memory Limit(KB), the default value will be here but you need to increase this value.
5. You then have to increase the Private Memory Limit and decrease the Regular Time Interval.
6. Click on OK and restart the pool to apply the new value.

Hopefully, after increasing the Private Memory Limit of WsusPool your said error will be resolved.

6] Contact your network administrator

If nothing worked and you are on a client computer, don’t fret about anything and contact your administrator. They might have made some adjustments on their end and reconfiguring it will resolve the issue for you.

How do I force Windows 10 to update from WSUS?

If you want to deploy Windows Client updates using the server, all you have to do is open the WSUS Administrator Console and then navigate to Update ServicesServer_NameUpdatesAll Windows 10 Upgrades. Right-click on the correct update and then select Approve from the context menu.

Read: Windows Server Update Services (WSUS) Troubleshooting.

An error occurred trying to connect the wsus server

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

General discussion

We using WSUS server for client and Server patching. We facing one error. Find attachment of the same.

An error occurred trying to connect the WSUS Server. This error can happen for a number of reasons. Check connectivity with the server. Please contact your network administrator if the problem persists.

You need to provide some more information.

Such as when did the problem first occur; did it happend after a reboot or newly installed patch?

Are the required services running?

Are you using any dedicated service accounts?

Do you use a dedidcated sql server or windows internal database?

Are you trying to connect to the console from the WSUS server it self?

Any obvious errors in windows event log?

Jesper Vindum, Denmark

Help the forum: Monitor(alert) your threads and vote helpful replies or mark them as answer, if it helps solving your problem.

Are the required services running?

yes required services are running

Are you using any dedicated service accounts?

yes we using dedicated service accounts

Do you use a dedicated sql server or windows internal database?

We using dedicated sql server

Are you trying to connect to the console from the WSUS server it self?

Yes we trying to connect to the console from the WSUS server it self

Any obvious errors in windows event log?

On monday night we approved April month patches on systems after that Server D drive where we saved all patches that drives get almost full, Currently having 7GB Free space. After that only we faced this issue.

Источник

An error occurred trying to connect the wsus server

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

Hello this morning I discovered that I could not connect to the WSUS server. I rebooted the server and it did not fix the issue like it usually does.

The error is: An Error occurred trying to connect the WSUS server. This error can happen for a number of reasons. Check connectivity with the server. Please contact your network administrator if the problem persists.

and I copied the error in my clipboard and it shows this:

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.WebException — The request failed with HTTP status 403: Forbidden.

at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)

at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)

at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)

at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)

at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)

at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpandFromLoad(SyncStatus status)

can anyone please help on what to do next?

I checked all ther services for WSUS server and they are all runnning

Answers

Is there a way you can do that?

Wouldn’t know. I’m not a PKI expert; just a WSUS expert. 🙂

I would imagine it depends on the parameters in which you’ve installed your PKI, the templates used for those certificates, and the conditions imposed upon certificate renewals.

But a relevant (rhetorical!) question is this: How did the server certificate and client certificate end up with differing expiration dates in the first place. (Discussing this question is out-of-scope for this forum, but I think it is something you probably should evaluate as an ongoing consideration to managing this SSL environment.)

Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP — Software Distribution (2005-2011)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
My Blog: http://onsitechsolutions.spaces.live.com

System.Net.WebException — The request failed with HTTP status 403: Forbidden.

Can you connect from the *LOCAL* console on the WSUS server.

This is usually an error caused by a proxy server; either

• Somebody put a proxy server between you and the WSUS server (and didn’t tell you), or
• Somebody reconfigured an existing proxy server that sits between you and the WSUS Server, or
• Somebody reconfigured your computer with regard to that proxy server and now you cannot get through it, or
• Somebody enabled SSL (improperly) on the WSUS server.

The most efficient way to isolate this issue is to review the IIS logs on the WSUS server, and find the SUBCODE of this HTTP 403 error (if it’s coming from the WSUS server), or to review the proxy logs of the intervening proxy server. The subcode will more explicitly identify the exact cause of the issue.

Источник

FIX: An error occured trying to connect the WSUS server by Bas Wijdenes

Table of Contents

WSUS, the basics.

During the weekend I updated all the servers at the customer. I expected everything to have gone well. On Monday morning I came to the office and found out that I had not updated the WSUS server itself.
I then logged onto the server and then received this error message:

Strange, because I used the server yesterday to update…
With a bit of trying and Googling I finally came up with the solution.

Let’s fix “An error occured trying to connect the WSUS server”.

In the steps I assume that you are a system administrator and know how to deal with Command Prompt.
If you don’t, you can always leave a comment.

• Open Command Prompt as administrator.
• Run the following command:
  CD “C:Program FilesUpdate ServicesTools”
• Followed with:
  wsusutil.exe postinstall /servicing
• Restart the WSUS Server.

The problem should now be solved.

Here is also a screenshot, as you can see my Command Prompt is elevated.

Does it work temporarily?

It is also possible that within IIS your WsusPool has stopped.
Open IIS and go to Application Pools.
Right-click on WsusPool and start the Pool.

Summary

Do you also use config manager in your infrastructure? And is my solution only a temporary solution?
Then this Technet may help you further.

The complete error message

An error occured trying to connect the WSUS server. This error can happen for a number of reasons. Check connectivity with the server. Please contact your network administrator if the problem persists.

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%MicrosoftMMC.

Источник

An error occurred trying to connect the wsus server

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

I keep getting this Error:Connection Error message and even if I restart IIS and the WSUS service the reset node button doesn’t work. I have to do a full reboot.

Here is the error I get

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%MicrosoftMMC.

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

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.CheckCompletionBeforeNextReceive(ProtocolToken message, 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.

Stack Trace:
at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()

What do I need to do to fix this? I’ve looked around online and haven’t found a solution that seems to work.

Источник

Server 2012 R2 WSUS Connection Error

I just installed a fresh copy of Server 2012 R2 and installed the WSUS role. Everything seems fine and I can connect my workstations to it, however, after I performed my initial Synchronization my MMC keeps crashing. Even if I try and access it from my desktop or server using the WSUS mmc.

It crashes after you wait a few minutes and it also crashes every time I go to the Updates or Synchronizations. It usually gets to around 50% complete then hangs.

I tried reinstalling the role, I’m about to reinstall the server but that seems over kill since this is a fresh install.

As a side note, this is an Azure A3 VM. Below is error and Event log data.

Log Name: Application

Source: Windows Server Update Services

Date: 6/2/2015 1:08:28 PM

Task Category: None

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.WebException — The operation has timed out

at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)

at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)

at Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse(WebRequest webRequest)

at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, Int32 publicationState)

at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState)

at Microsoft.UpdateServices.Internal.BaseApi.Update.SearchUpdates(UpdateScope searchScope, ExtendedPublicationState publicationState, UpdateServer updateServer)

at Microsoft.UpdateServices.UI.AdminApiAccess.UpdateManager.GetUpdates(ExtendedUpdateScope filter)

at Microsoft.UpdateServices.UI.SnapIn.Pages.SyncResultsListPage.GetSyncInfoRow(WsusSynchronizationInfo syncInfo)

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.

Источник

So I’m having an issue I just cannot fix, I’ve looked at many different forums and still cannot find a fix that works for me.

I have WSUS installed on a Windows Server 2012 r2. The updating of computers is working fine. When I go to «all Updates» on the console I select the dropdowns  Approval: Any Except Declined and Status: Any. This shows loading for a while and then I get,

Error: Connection Error 

«An error occurred trying to connect the WSUS server. This error can happen for a number of reasons. Check connectivity with the servers. Please contact your network administrator if the problem persists.

Click Reset Server Nodes to try to connect to the server again»

Resetting theNode brings back the console, I can access other parts of the console but as soon as I select the options mentioned above this happens again. 

I’ve deleted the «WSUS» file from %appdata%, restarted WSUS services and ISS. This still does not resolve the issues. 

Any help will be greatly appreciated.

Thanks

sqlcmd -I -S \.pipeMICROSOFT##WIDtsqlquery -i C:WsusDBMaintenance.sql

sqlcmd.exe -I -S np:\.pipeMSSQL$MICROSOFT##SSEEsqlquery -i C:WSUSDBMaintenance.sql

wuauclt /detectnow

cd C:Program FilesUpdate ServicesTools
Wsusutil.exe postinstall /servicing

ITSmarttricks Team

This is Mangesh Dhulap the Founder and Editor of IT SMART TRICKS have 6+ years of Industrial Experience. We expect from our visitors to like, share, and comment on our posts.

On a fresh or existing WSUS install, you may notice that the WSUS Administrator MMC applet stops functioning and present the error “Error: Connection Error – An error occurred trying to connect to the WSUS Server.”

I originally experienced this on Windows Server Update Services running on Windows Server 2012 R2 and applied the fix. Recently, I deployed Windows Server Update Services on a new Windows Server 2019 – Server Core install, and experienced this issue during the first synchronization. Before realizing what the issue was, I attempted to re-install WSUS and IIS from scratch numerous times until I came across old notes. One would have thought they would have resolved this issue on a new server operating system.

When the issue occurs, all processes will appear to be running on the server. Looking at the server event log, you’ll notice multiple application errors:

• Event ID: 13042 - Windows Server Update Services
  Description: Self-update is not working.

• Event ID: 12002 - Windows Server Update Services
  Description: The Reporting Web Service is not working.

• Event ID: 12012 - Windows Server Update Services
  Description: The API Remoting Web Service is not working.

• Event ID: 12032 - Windows Server Update Services
  Description: The Server Synchronization Web Service is not working.

• Event ID: 12022 - Windows Server Update Services
  Description: The Client Web Service is not working.

• Event ID: 12042 - Windows Server Update Services
  Description: The SimpleAuth Web Service is not working.

• Event ID: 12052 - Windows Server Update Services
  Description: The DSS Authentication Web Service is not working.

• Event ID: 12072 - Windows Server Update Services
  Description: 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)

You will also see the below error message when attempting to use the WSUS MMC.

The Problem

This issue occurs because the WSUS application pool in IIS “WsusPool” has reached it’s maximum private memory limit and attempts to recycle the memory usage.

Ultimately I believe this causes the IIS worker process to crash since it has run out of memory, and the pending command (whether it’s a synchronization or something else) fails to complete.

Previously, I noticed database corruption on a WSUS SQL Express database when this issue occurred, so I recommend applying the fix on a fresh install of WSUS.

The Fix

To resolve this issue, we need to adjust the max

1. On the server running WSUS and IIS, open the “Internet Information Services (IIS) Manager” inside of the “Windows Administrative Tools” (found in the start menu, or Control Panel).
   
2. On the left hand side under “Connections”, expand the server, and select “Application Pools”.
   
3. On the right hand side under “Application Pools” heading, right-click on “WsusPool” and select “Advanced Settings”.
   
4. In the “Advanced Settings” window, scroll down until you see “Private Memory Limit (KB)”. Either change this to “0” (as shown below) to set no memory limit, or increase the limit to the value you prefer.
   
5. Select “Ok” to close the window.
6. Restart IIS by running “iisreset” from an administrative command prompt, restarting the server, or selecting “Restart” under “Manage Server” when looking at the default pane in IIS when the server is selected.

The issue should now be resolved and your WSUS server should no longer be crashing.

If you are applying this fix on a Server Core install, you’ll need to connect remotely to the IIS instance to apply the fix.