DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 948139 - Last Review: February 8, 2008 - Revision: 1.0

SYMPTOMS

Consider the following scenario. You have a Windows Server 2003-based computer that has Windows Server Update Services (WSUS) 3.0 Service Pack 1 (SP1) installed. You upgrade the computer to Windows Server 2008. In this scenario, WSUS-related Web services may stop working.

When you try to access the WSUS administrator console, you receive the following error message:

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 server. Please contact your network administrator if the problem persists.

Click Reset Server Node to connect the server again.
Additionally, when you click Copy Error to Clipboard, you receive the following error information:
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\.

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

Source
System

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.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.TlsStream.CallProcessAuthentication(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
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.PooledStream.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.

Source
Microsoft.UpdateServices.Administration

Stack Trace:
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.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpandFromLoad(SyncStatus status)
When you check the Internet Information Services (IIS) logs on the WSUS server, you see that HTTP requests failed and that they generated an HTTP 405 error. The log line resembles the following:
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status time-taken
2008-02-07 19:48:09 fe80::2ddc:2f84:4cfe:6bf3%10 POST /ApiRemoting30/WebService.asmx - 80 <username> fe80::2ddc:2f84:4cfe:6bf3%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.1433) 405 0 1 0
Note The following path is the default location for the IIS log files:
%SystemDrive%\Inetpub\Logs\Logfiles\w3svc1

CAUSE

This problem occurs because the handler mappings for the Default Web site in IIS 7.0 do not contain the mapping for the .asmx file name extension when you upgrade Windows Server 2003 to Windows Server 2008. This behavior occurs even though Microsoft ASP.NET is installed in IIS 7.0.

In Windows Server 2008, WSUS 3.0 SP1 Setup does not add script mappings for the WSUS virtual directory. Instead, WSUS 3.0 SP1 relies on script mappings on the Default Web site. Sometimes, when you upgrade Windows Server 2003 to Windows Server 2008, there may be no .asmx script mappings on the Default Web site. Therefore, WSUS-related Web services may stop working.

WORKAROUND

To work around this problem, uninstall the ASP.NET role service in IIS, and then use Service Manager to reinstall the service. To do this, follow these steps:
  1. Click Start, click Administrative Tools, and then click Server Manager.
  2. Expand Roles, and then click Web Server (IIS).
  3. In the Role Services section, click Remove Role Services.
  4. Disable the ASP.NET check box, and then click Next.
  5. Click Remove.
  6. Wait for the removal process to finish, and then click Close.
  7. In the same Role Services section, click Add Role Services.
  8. Enable the ASP.NET check box, and then click Next.
  9. Click Install.
  10. Wait for the installation process to finish, and then click Close.

MORE INFORMATION

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
948014  (http://support.microsoft.com/kb/948014/ ) Description of the Windows Server Update Services 3.0 Service Pack 1 package

APPLIES TO
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
  • Windows Web Server 2008
  • Windows Server 2008 for Itanium-Based Systems
  • Microsoft Software Update Services 1.0
Keywords: 
kberrmsg kbtshoot kbprb kbexpertiseinter KB948139
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support