locked
Reg-WSUS issue RRS feed

  • Question

  • 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 -- No connection could be made because the target machine actively refused it 192.168.22.207:8530

    Source
    System

    Stack Trace:
       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, Int32 timeout, Exception& exception)
    ** this exception was nested inside of the following exception **


    System.Net.WebException -- Unable to connect to the remote server

    Source
    Microsoft.UpdateServices.Administration

    Stack Trace:
       at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
       at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()
       at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer()
       at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
       at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
       at Microsoft.UpdateServices.UI.SnapIn.Common.ExtensionSnapInManager.OnInitialize()
    Friday, July 18, 2014 11:57 AM

All replies

  • You have tried what it suggest, 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 ?
    Friday, July 18, 2014 12:09 PM
  • System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 192.168.22.207:8530

    The logical conclusion is that there's no WSUS server at 192.168.22.207:8530, or the machine has been configured to block connections from the client being used.

    You should check the IIS logs and see if IIS received the connection request, and what error code was actually returned (e.g. 404, 401.1, 401.2, 401.3, 403.x).

    Also... whenever I see people trying to access WSUS using IP Addresses (instead of hostnames), I *always* ask this question: Why are you not using a hostname???


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Monday, July 21, 2014 2:22 AM