WSUS error 0x80004005

I'm running SBS 2003 and had upgraded wsus 2 to WSUS 3.
Trying to access WSUS at the moment I get a server application error.
Tried to uninstall and reinstall WSUS 3 but the installation fails and I
find the above error in the setup log.
Have tried to reinstall WSUS 2, but installation fails because of WSUS 3.

I have recentlly had problems with Sharepoint & the bundled SBS SQL, so I
recently uninstalled shate point and SQL and windows internal database. then
reinstalled all from scratch.

Could this explain my WSUS problem? and if so, any suggestions as to how I
cure it?

Thanks

"Neil" <> wrote in message
news:A58DF11F-89A5-44FA-A2B6-...
> I'm running SBS 2003 and had upgraded wsus 2 to WSUS 3.

Let's first talk about the methodology you used to upgrade WSUS2 to WSUS3 on
SBS2003,
and how you installed WSUS2 originally (the WSUS2 release on SBS2003SP1, or
the R2 Technologies WSUS2)

> I have recentlly had problems with Sharepoint & the bundled SBS SQL, so I
> recently uninstalled shate point and SQL and windows internal database.
> then
> reinstalled all from scratch.

Which may well have a lot to do with your WSUS no longer working!

> Could this explain my WSUS problem? and if so, any suggestions as to how I
> cure it?

Well, first, we need to inventory everything you've done, and the *exact*
order you did it, starting with the installation of WSUS =2=.

From there, we can get a reasonable 'inventory' of the current state of the
machine and what it might take to restore full functionality.



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

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

The original WSUS 2 was the R2 technologies installation which did work ok, I
then downloaded the WSUS 3 upgrade from the MS download site.

A developer has written me a custom application which is SQL based, but
would not work with the SBS embeded SQL so SQL express 2008 was installed.

I then developed a problem with SQL & Sharepoint 2, so share point And
windows database etc was uninstalled and reinstalled and now work OK, and
have also had to do a repair install on SQL express too

Both installations of SQL now appear to be working ok.

Thanks




Lawrence Garvin [MVP]" wrote:

> "Neil" <> wrote in message
> news:A58DF11F-89A5-44FA-A2B6-...
> > I'm running SBS 2003 and had upgraded wsus 2 to WSUS 3.
>
> Let's first talk about the methodology you used to upgrade WSUS2 to WSUS3 on
> SBS2003,
> and how you installed WSUS2 originally (the WSUS2 release on SBS2003SP1, or
> the R2 Technologies WSUS2)
>
> > I have recentlly had problems with Sharepoint & the bundled SBS SQL, so I
> > recently uninstalled shate point and SQL and windows internal database.
> > then
> > reinstalled all from scratch.
>
> Which may well have a lot to do with your WSUS no longer working!
>
> > Could this explain my WSUS problem? and if so, any suggestions as to how I
> > cure it?
>
> Well, first, we need to inventory everything you've done, and the *exact*
> order you did it, starting with the installation of WSUS =2=.
>
> From there, we can get a reasonable 'inventory' of the current state of the
> machine and what it might take to restore full functionality.
>
>
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> 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
>
>

Further to my original posts, here is an update to the situation.
If i go to update services in Server Management I get a 'Server Application
Unavailable' error.

After checking WSUS log file I find a problem trying to access SUSDB.
I used SQL management studio to check SUSDB was available, but I cannot
connect to MICROSOFT##SSEE.
I presume this is because I had re-installed the SQL & Sharepoint components.

however, I can connect to '\\.\pipe\mssql$microsoft##ssee\sql\query'

does this help?



"Neil" wrote:

> The original WSUS 2 was the R2 technologies installation which did work ok, I
> then downloaded the WSUS 3 upgrade from the MS download site.
>
> A developer has written me a custom application which is SQL based, but
> would not work with the SBS embeded SQL so SQL express 2008 was installed.
>
> I then developed a problem with SQL & Sharepoint 2, so share point And
> windows database etc was uninstalled and reinstalled and now work OK, and
> have also had to do a repair install on SQL express too
>
> Both installations of SQL now appear to be working ok.
>
> Thanks
>
>
>
>
> Lawrence Garvin [MVP]" wrote:
>
> > "Neil" <> wrote in message
> > news:A58DF11F-89A5-44FA-A2B6-...
> > > I'm running SBS 2003 and had upgraded wsus 2 to WSUS 3.
> >
> > Let's first talk about the methodology you used to upgrade WSUS2 to WSUS3 on
> > SBS2003,
> > and how you installed WSUS2 originally (the WSUS2 release on SBS2003SP1, or
> > the R2 Technologies WSUS2)
> >
> > > I have recentlly had problems with Sharepoint & the bundled SBS SQL, so I
> > > recently uninstalled shate point and SQL and windows internal database.
> > > then
> > > reinstalled all from scratch.
> >
> > Which may well have a lot to do with your WSUS no longer working!
> >
> > > Could this explain my WSUS problem? and if so, any suggestions as to how I
> > > cure it?
> >
> > Well, first, we need to inventory everything you've done, and the *exact*
> > order you did it, starting with the installation of WSUS =2=.
> >
> > From there, we can get a reasonable 'inventory' of the current state of the
> > machine and what it might take to restore full functionality.
> >
> >
> >
> > --
> > Lawrence Garvin, M.S., MCITP:EA, MCDBA
> > Principal/CTO, Onsite Technology Solutions, Houston, Texas
> > Microsoft MVP - Software Distribution (2005-2009)
> >
> > 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
> >
> >

"Neil" <> wrote in message
news1A5D4EC-F9B5-412B-8888-...

>> Well, first, we need to inventory everything you've done, and the *exact*
>> order you did it, starting with the installation of WSUS =2=.
>>
>> From there, we can get a reasonable 'inventory' of the current state of
>> the
>> machine and what it might take to restore full functionality.

> The original WSUS 2 was the R2 technologies installation which did work
> ok, I
> then downloaded the WSUS 3 upgrade from the MS download site.

I need significantly more detail than this.

It's useful to know that you originally had the R2 technologies version of
WSUS2SP1 installed, but it's even more critical to know what you did after
that to get to the point where you are now.


> I then developed a problem with SQL & Sharepoint 2, so share point And
> windows database etc was uninstalled and reinstalled and now work OK, and
> have also had to do a repair install on SQL express too

It might be helpful to know what this problem was that you developed....
perhaps it affected WSUS also, since it seems to have affected almost
everything else on the system.


> Both installations of SQL now appear to be working ok.

"Both"? That's good.. but by my count, you've got four installations of SQL
Server on that machine currently. (Maybe five, depending on how you got from
the R2 WSUS2 to WSUS3.)

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

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

"Neil" <> wrote in message
news:2BF7AC0F-8365-44FC-99C8-...
> Further to my original posts, here is an update to the situation.
> If i go to update services in Server Management I get a 'Server
> Application
> Unavailable' error.

And so you should.


> After checking WSUS log file I find a problem trying to access SUSDB.

Not entirely surprising, either, based on what you've posted so far.

> I used SQL management studio to check SUSDB was available, but I cannot
> connect to MICROSOFT##SSEE.

Correct.

> I presume this is because I had re-installed the SQL & Sharepoint
> components.

Nope.

> however, I can connect to '\\.\pipe\mssql$microsoft##ssee\sql\query'

So.. you *CAN* connect to the Windows Internal Database <???>


> does this help?

Not really.... except it tells me that the WSUS v3 Windows Internal Database
is installed and running.

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

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