Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 860
  • Last Modified:

How can I reinstall WSUS 3.0

I installed ISA 2000 on a Windows 2003 machine which has already WSUS3.0 installed. I then decided to remove ISA for some reason. After ISA got uninstalled and system rebooted, WSUS service doesn't work. When I start the console, it syas it can not connect to the WSUS server. I hope it's all about starting some services which ISA had stoped during uninstallation. However, I'd be happy if I can reinstall WSUS3.0 without intacting data files.
0
behterami
Asked:
behterami
  • 3
  • 2
1 Solution
 
Kamran ArshadIT AssociateCommented:
Hi,

What are the errors in the eventlogs?
0
 
behteramiAuthor Commented:
I get 4 warnings in the Application section of Event Viewer when I try to start WSUS3.0 console. These 4 warning messages are indeed 2 which has been repeated. The first is from ASP.NET 2 and the seconf is from Windows Update Service. I attache both messages for your consideration. Thanks is advance.
Event Type:	Warning
Event Source:	ASP.NET 2.0.50727.0
Event Category:	Web Event 
Event ID:	1309
Date:		3/04/2009
Time:		8:56:09 AM
User:		N/A
Computer:	CRUX
Description:
Event code: 3001 
Event message: The request has been aborted. 
Event time: 3/04/2009 8:56:09 AM 
Event time (UTC): 2/04/2009 9:56:09 PM 
Event ID: c4efa62a9adc4562927b886e59a89747 
Event sequence: 185 
Event occurrence: 44 
Event detail code: 0 
 
Application information: 
    Application domain: /LM/W3SVC/1/ROOT/SimpleAuthWebService-1-128831817935937500 
    Trust level: Full 
    Application Virtual Path: /SimpleAuthWebService 
    Application Path: c:\Program Files\Update Services\WebServices\SimpleAuthWebService\ 
    Machine name: CRUX 
 
Process information: 
    Process ID: 4040 
    Process name: w3wp.exe 
    Account name: NT AUTHORITY\NETWORK SERVICE 
 
Exception information: 
    Exception type: HttpException 
    Exception message: Request timed out. 
 
Request information: 
    Request URL: http://crux/SimpleAuthWebService/SimpleAuth.asmx 
    Request path: /SimpleAuthWebService/SimpleAuth.asmx 
    User host address: 192.168.168.143 
    User:  
    Is authenticated: False 
    Authentication Type:  
    Thread account name: NT AUTHORITY\NETWORK SERVICE 
 
Thread information: 
    Thread ID: 12 
    Thread account name: NT AUTHORITY\NETWORK SERVICE 
    Is impersonating: False 
    Stack trace: 
 
 
Custom event details: 
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 
 
 
**************************
**************************
Event Type:	Warning
Event Source:	Windows Server Update Services
Event Category:	None
Event ID:	7032
Date:		3/04/2009
Time:		8:57:16 AM
User:		N/A
Computer:	CRUX
Description:
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.get_ServerTools()
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Open in new window

0
 
behteramiAuthor Commented:
Thanks for the links. They didn't help. I will reinstall OS.
0
 
behteramiAuthor Commented:
I removed the registry keys pertaining to SQL instances and used the Windows Uninstaller to remove Microsoft Internal Database. Then I reinstalled WSUS 3 SP1 and it worked.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now