Go Back   TechArena Community > Technical Support > Computer Help > Windows Server > Server Update Service
Become a Member!
Forgot your username/password?
Register Tags Active Topics RSS Search Mark Forums Read SiteMap

Tags: , ,

Sponsored Links



WSUS 3.0 stopped working after server reboot

Server Update Service


Reply
 
Thread Tools Search this Thread
  #1  
Old 26-06-2008
MMJII
 
Posts: n/a
WSUS 3.0 stopped working after server reboot

Hello All,
I upgraded my 2K3 WSUS from 2.0 to 3.0 the upgrade went flawlessly, The new
wsus website displayed in the browser with client information. I had to
reboot the server and now when I try to open the wsus site I get file or
directory not found HTTP error 404.
I then updated WSUS with WSUS 3.0 SP1 and after the update the WSUS website
worked again, but after a reboot I get the same "file or directory not found
HTTP error 404." and the site does not display. Does anyone have any ideas
as to why this is occurring?
Thanks in advance for any thoughts.
MMJII


Reply With Quote
  #2  
Old 26-06-2008
MMJII
 
Posts: n/a
Re: WSUS 3.0 stopped working after server reboot

B.T.W. this an SBS 2K3 server
Thanks
"MMJII" <MMJII@microsoft.com> wrote in message
news:%23nYtZ2w1IHA.3920@TK2MSFTNGP02.phx.gbl...
> Hello All,
> I upgraded my 2K3 WSUS from 2.0 to 3.0 the upgrade went flawlessly, The

new
> wsus website displayed in the browser with client information. I had to
> reboot the server and now when I try to open the wsus site I get file or
> directory not found HTTP error 404.
> I then updated WSUS with WSUS 3.0 SP1 and after the update the WSUS

website
> worked again, but after a reboot I get the same "file or directory not

found
> HTTP error 404." and the site does not display. Does anyone have any ideas
> as to why this is occurring?
> Thanks in advance for any thoughts.
> MMJII
>
>



Reply With Quote
  #3  
Old 26-06-2008
Winfried Sonntag [MVP]
 
Posts: n/a
Re: WSUS 3.0 stopped working after server reboot

MMJII schrieb:

> I upgraded my 2K3 WSUS from 2.0 to 3.0 the upgrade went flawlessly, The new
> wsus website displayed in the browser with client information. I had to
> reboot the server and now when I try to open the wsus site I get file or
> directory not found HTTP error 404.


In WSUS 3.0 you have a MMC for administration. Pls read the Operation
Guide for more information:
http://www.microsoft.com/downloads/d...displaylang=en

Winfried
--
http://www.microsoft.com/germany/win...s/default.mspx
http://www.wsuswiki.com/Home
Reply With Quote
  #4  
Old 27-06-2008
MMJII
 
Posts: n/a
Re: WSUS 3.0 stopped working after server reboot

Thanks for the info.
I found the MMC but when I use it it starts off "adding snap-in to I get the
error msg that an erroro occurred trying to connect to WSUS server.
Clicked reset sever node but it didi noting.
The is the erroro copied to clipbord
Thanks for any thoughts

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.ExecuteCodeWithGuaranteedClea
nup(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(Str
ing serverName, Boolean useSecureConnection, Int32 portNumber)
at
Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateSer
ver(PersistedServerSettings settings)
at
Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToSer
ver()
at
Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTo
ols()


"Winfried Sonntag [MVP]" <Winfried.Sonntag@gmx.de> wrote in message
news:bemtvrs2xctq$.dlg@ID-163725.user.individual.de...
> MMJII schrieb:
>
> > I upgraded my 2K3 WSUS from 2.0 to 3.0 the upgrade went flawlessly, The

new
> > wsus website displayed in the browser with client information. I had to
> > reboot the server and now when I try to open the wsus site I get file

or
> > directory not found HTTP error 404.

>
> In WSUS 3.0 you have a MMC for administration. Pls read the Operation
> Guide for more information:
>

http://www.microsoft.com/downloads/d...displaylang=en
>
> Winfried
> --
>

http://www.microsoft.com/germany/win...s/default.mspx
> http://www.wsuswiki.com/Home



Reply With Quote
  #5  
Old 27-06-2008
Winfried Sonntag [MVP]
 
Posts: n/a
Re: WSUS 3.0 stopped working after server reboot

MMJII schrieb:

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


Do have check that all the above services are running?

> 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\.


Do you have try the solution?

Winfried
--
http://www.microsoft.com/germany/win...s/default.mspx
http://www.wsuswiki.com/Home
Reply With Quote
  #6  
Old 01-07-2008
MMJII
 
Posts: n/a
Re: WSUS 3.0 stopped working after server reboot

Winfried
The services (IIS, Update services, and SQL) are running.
I deleted the wsus file under %appdata%\Microsoft\MMC\.and the Update
services admin opens, but when I try to connect to the server i get an error
stating " Cannot connect to AJ01 The server may be using another port or
different SSL setting. I used port 8530 (default) other ports did not work
either.
I get these errors in the App event log but the services they reference
(Self-update, Reporting Web Service, API Remoting Web Service,Client Web
Service, SimpleAuth Web Service, and DSS Authentication Web Service) I
cannot find in the service admin window.
Any ideas are appreciated.
Thanks
MMJII

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Clients
Event ID: 13042
Date: 7/1/2008
Time: 6:17:34 AM
User: N/A
Computer: AJ01
Description:
Self-update is not working.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12002
Date: 7/1/2008
Time: 6:17:34 AM
User: N/A
Computer: AJ01
Description:
The Reporting Web Service is not working.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12012
Date: 7/1/2008
Time: 6:17:34 AM
User: N/A
Computer: AJ01
Description:
The API Remoting Web Service is not working.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12012
Date: 7/1/2008
Time: 6:17:34 AM
User: N/A
Computer: AJ01
Description:
The API Remoting Web Service is not working.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12022
Date: 7/1/2008
Time: 6:17:34 AM
User: N/A
Computer: AJ01
Description:
The Client Web Service is not working.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12042
Date: 7/1/2008
Time: 6:17:34 AM
User: N/A
Computer: AJ01
Description:
The SimpleAuth Web Service is not working.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12052
Date: 7/1/2008
Time: 6:17:34 AM
User: N/A
Computer: AJ01
Description:
The DSS Authentication Web Service is not working.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.



"Winfried Sonntag [MVP]" <Winfried.Sonntag@gmx.de> wrote in message
news:dujlcs2mvsmw.dlg@ID-163725.user.individual.de...
> MMJII schrieb:
>
> > 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.

>
> Do have check that all the above services are running?
>
> > 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\.

>
> Do you have try the solution?
>
> Winfried
> --
>

http://www.microsoft.com/germany/win...s/default.mspx
> http://www.wsuswiki.com/Home



Reply With Quote
  #7  
Old 01-07-2008
Winfried Sonntag [MVP]
 
Posts: n/a
Re: WSUS 3.0 stopped working after server reboot

MMJII schrieb:

> The services (IIS, Update services, and SQL) are running.
> I deleted the wsus file under %appdata%\Microsoft\MMC\.and the Update
> services admin opens, but when I try to connect to the server i get an error
> stating " Cannot connect to AJ01 The server may be using another port or
> different SSL setting. I used port 8530 (default) other ports did not work
> either.
> I get these errors in the App event log but the services they reference
> (Self-update, Reporting Web Service, API Remoting Web Service,Client Web
> Service, SimpleAuth Web Service, and DSS Authentication Web Service) I
> cannot find in the service admin window.
> Any ideas are appreciated.


Wow, many errors. OK, have a look in Internet Information Service for
the web-services and control the rights and settings with this
document:
Appendix C: IIS Settings for Web Services:
http://technet2.microsoft.com/Window...38a7a1033.mspx
Appendix D: Permissions on WSUS Directories and Registry Keys:
http://technet2.microsoft.com/Window...d338c1033.mspx

Winfried
--
http://www.microsoft.com/germany/win...s/default.mspx
http://www.wsuswiki.com/Home
Reply With Quote
  #8  
Old 02-07-2008
MMJII
 
Posts: n/a
Re: WSUS 3.0 stopped working after server reboot

Thank you
I will attempt tomorrow 7 get back to you

"Winfried Sonntag [MVP]" <Winfried.Sonntag@gmx.de> wrote in message
news:3dk3c4to5hlj.dlg@ID-163725.user.individual.de...
> MMJII schrieb:
>
> > The services (IIS, Update services, and SQL) are running.
> > I deleted the wsus file under %appdata%\Microsoft\MMC\.and the Update
> > services admin opens, but when I try to connect to the server i get an

error
> > stating " Cannot connect to AJ01 The server may be using another port or
> > different SSL setting. I used port 8530 (default) other ports did not

work
> > either.
> > I get these errors in the App event log but the services they reference
> > (Self-update, Reporting Web Service, API Remoting Web Service,Client Web
> > Service, SimpleAuth Web Service, and DSS Authentication Web Service) I
> > cannot find in the service admin window.
> > Any ideas are appreciated.

>
> Wow, many errors. OK, have a look in Internet Information Service for
> the web-services and control the rights and settings with this
> document:
> Appendix C: IIS Settings for Web Services:
>

http://technet2.microsoft.com/Window...38a7a1033.mspx
> Appendix D: Permissions on WSUS Directories and Registry Keys:
>

http://technet2.microsoft.com/Window...d338c1033.mspx
>
> Winfried
> --
>

http://www.microsoft.com/germany/win...s/default.mspx
> http://www.wsuswiki.com/Home



Reply With Quote
  #9  
Old 02-07-2008
Lawrence Garvin
 
Posts: n/a
Re: WSUS 3.0 stopped working after server reboot

"Winfried Sonntag [MVP]" <Winfried.Sonntag@gmx.de> wrote in message
news:3dk3c4to5hlj.dlg@ID-163725.user.individual.de...
> MMJII schrieb:
>
>> The services (IIS, Update services, and SQL) are running.
>> I deleted the wsus file under %appdata%\Microsoft\MMC\.and the Update
>> services admin opens, but when I try to connect to the server i get an
>> error
>> stating " Cannot connect to AJ01 The server may be using another port or
>> different SSL setting. I used port 8530 (default) other ports did not
>> work
>> either.
>> I get these errors in the App event log but the services they reference
>> (Self-update, Reporting Web Service, API Remoting Web Service,Client Web
>> Service, SimpleAuth Web Service, and DSS Authentication Web Service) I
>> cannot find in the service admin window.
>> Any ideas are appreciated.

>
> Wow, many errors.


This collection of error is a classic symptom that the port number of the
WSUS server has been changed manually after installation.

The Health Monitoring is looking for these services on a virtual server they
no longer exist at.

--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Reply With Quote
  #10  
Old 02-07-2008
Winfried Sonntag [MVP]
 
Posts: n/a
Re: WSUS 3.0 stopped working after server reboot

Lawrence Garvin schrieb:

> This collection of error is a classic symptom that the port number of the
> WSUS server has been changed manually after installation.


Do you think so, or you know? ;)

Winfried
--
http://www.microsoft.com/germany/win...s/default.mspx
http://www.wsuswiki.com/Home
Reply With Quote
  #11  
Old 04-07-2008
MMJII
 
Posts: n/a
Re: WSUS 3.0 stopped working after server reboot

How would I begin to resolve this, I let the default port number stand when
installing.
"Lawrence Garvin" <onsite@postalias.news> wrote in message
news:E6F79C5C-65C0-44EF-B7A4-1752851760E2@microsoft.com...
> "Winfried Sonntag [MVP]" <Winfried.Sonntag@gmx.de> wrote in message
> news:3dk3c4to5hlj.dlg@ID-163725.user.individual.de...
> > MMJII schrieb:
> >
> >> The services (IIS, Update services, and SQL) are running.
> >> I deleted the wsus file under %appdata%\Microsoft\MMC\.and the Update
> >> services admin opens, but when I try to connect to the server i get an
> >> error
> >> stating " Cannot connect to AJ01 The server may be using another port

or
> >> different SSL setting. I used port 8530 (default) other ports did not
> >> work
> >> either.
> >> I get these errors in the App event log but the services they reference
> >> (Self-update, Reporting Web Service, API Remoting Web Service,Client

Web
> >> Service, SimpleAuth Web Service, and DSS Authentication Web Service) I
> >> cannot find in the service admin window.
> >> Any ideas are appreciated.

> >
> > Wow, many errors.

>
> This collection of error is a classic symptom that the port number of the
> WSUS server has been changed manually after installation.
>
> The Health Monitoring is looking for these services on a virtual server

they
> no longer exist at.
>
> --
> Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
> Senior Data Architect, APQC, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2008)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My Websites: http://www.onsitechsolutions.com;
> http://wsusinfo.onsitechsolutions.com
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>



Reply With Quote
  #12  
Old 04-07-2008
MMJII
 
Posts: n/a
Re: WSUS 3.0 stopped working after server reboot

Thanks for all the ideas, I just un installed & re installed & all is well
again many Thanks
"MMJII" <MMJII@microsoft.com> wrote in message
news:ubyM3hT3IHA.1428@TK2MSFTNGP06.phx.gbl...
> How would I begin to resolve this, I let the default port number stand

when
> installing.
> "Lawrence Garvin" <onsite@postalias.news> wrote in message
> news:E6F79C5C-65C0-44EF-B7A4-1752851760E2@microsoft.com...
> > "Winfried Sonntag [MVP]" <Winfried.Sonntag@gmx.de> wrote in message
> > news:3dk3c4to5hlj.dlg@ID-163725.user.individual.de...
> > > MMJII schrieb:
> > >
> > >> The services (IIS, Update services, and SQL) are running.
> > >> I deleted the wsus file under %appdata%\Microsoft\MMC\.and the

Update
> > >> services admin opens, but when I try to connect to the server i get

an
> > >> error
> > >> stating " Cannot connect to AJ01 The server may be using another port

> or
> > >> different SSL setting. I used port 8530 (default) other ports did not
> > >> work
> > >> either.
> > >> I get these errors in the App event log but the services they

reference
> > >> (Self-update, Reporting Web Service, API Remoting Web Service,Client

> Web
> > >> Service, SimpleAuth Web Service, and DSS Authentication Web Service)

I
> > >> cannot find in the service admin window.
> > >> Any ideas are appreciated.
> > >
> > > Wow, many errors.

> >
> > This collection of error is a classic symptom that the port number of

the
> > WSUS server has been changed manually after installation.
> >
> > The Health Monitoring is looking for these services on a virtual server

> they
> > no longer exist at.
> >
> > --
> > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
> > Senior Data Architect, APQC, Houston, Texas
> > Microsoft MVP - Software Distribution (2005-2008)
> >
> > MS WSUS Website: http://www.microsoft.com/wsus
> > My Websites: http://www.onsitechsolutions.com;
> > http://wsusinfo.onsitechsolutions.com
> > My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
> >

>
>



Reply With Quote
Reply

  TechArena Community > Technical Support > Computer Help > Windows Server > Server Update Service


Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "WSUS 3.0 stopped working after server reboot"
Thread Thread Starter Forum Replies Last Post
Error Microsoft (C) Register Server stopped working Kwee Windows Software 5 06-06-2009 09:52 PM
WSUS 2.0 Server Replica - Downstream Server of WSUS 3.0 Server? Notworking.. tbird2340 Server Update Service 4 15-10-2008 08:15 PM
WSUS MMC is working, Synchronization is working, but WSUS fails to download updates and Self Update is not working Bruce Sanderson Server Update Service 2 04-07-2008 09:02 AM
Microsoft (C) Register Server has stopped working Peter Afonin Vista Help 7 27-10-2007 02:26 AM
Register Server has stopped working Dan Vista Setup and Install 4 27-10-2007 02:14 AM


All times are GMT +5.5. The time now is 11:20 AM.