dreamkass
Posts: 2
Score: 0 Joined: 11/18/2008 Status: offline
|
Looks like it happened to me too, here's my setup in a lab environment. 3 x W2K8 as DC's 1 x W2K8 as a SCCM Site - WSUS: Custom Site port 8530
- WDS
- SQL Server 2005: SCCM & WSUS DB's
- IIS7 + WebDAV extension: default site port 80
- SCCM Roles: DP, MP, SLP, FSP, RP, SUP
I had sync my SUP yesterday 2 times correctly then today I installed the SCCM Client on the SCCM Site server... on reboot the WSUSservice and WsusCertServer services were gone, checked IIS no more WSUS Site? After the SCCM Client installation i had a bunch of WMI ID 63 errors and SCCM installation success (just before the reboot) On reboot, services started then I got this: MsiInstaller Warning 1004: Detection of product '{2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}', feature 'WSUSApiFeature', component '{067AEA00-5C0B-444C-8961-313ACF4C3C75}' failed. The resource '' does not exist. MsiInstaller Warning 1001: Detection of product '{2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}', feature 'WSUSApiFeature' failed during request for component '{8691403E-727C-4E5E-BA2D-0608341F1BBF}' MsiInstaller Error 11706: Product: Microsoft Windows Server Update Services 3.0 SP1 -- Error 1706. An installation package for the product Microsoft Windows Server Update Services 3.0 SP1 cannot be found. Try the installation again using a valid copy of the installation package 'WUSSetup.msi'. Product: Microsoft Windows Server Update Services 3.0 SP1 -- Configuration failed. Windows Installer reconfigured the product. Product Name: Microsoft Windows Server Update Services 3.0 SP1. Product Version: 3.1.6001.65. Product Language: 0. Reconfiguration success or error status: 1603. 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 ::1:8530 Source System Stack Trace: at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP) 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()
|