Re: WSUS and WSS 3.0 broken

I'm not sure if there's a recommended order for doing this. I'd read the documentation first, and then if you don't find specific guidance, I would uninstall both, then reinstall companyweb, then reinstall WSUS.

How to remove and how to install the Windows Small Business Server 2003 SharePoint Services 2.0 companyweb Web site
http://support.microsoft.com/kb/829114

Is this R2? If so, just uninstall WSUS, then reinstall from the R2 CD. Otherwise, do the reinstall this way:

Installing Windows Server Update Services 3.0 on Windows Small Business Server 2003
http://technet.microsoft.com/en-us/library/cc708091.aspx


"Hugh" <Hugh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:B6D56962-D8DF-4A83-92D0-A4E0B805C461@xxxxxxxxxxxxxxxx
Dave,

I do not have data in the companyweb so I would consider going the reinstall
route for companyweb and WSS. I would appreciate your assistance with this.

Also, I do not have shadow copy enabled on any of the hard drive.

Thanks for the help.
--
Hugh


"Dave Nickason [SBS MVP]" wrote:

I'm assuming you have data in your companyweb site that you don't want to
lose. In that case, I'd recommend calling CSS (Microsoft support) and
letting them walk you through the restore procedure.

If you don't have data at risk, you could just reinstall companyweb and
WSUS. Please post back if you need help going that route.

By the way, you might be able to get those database files back from shadow
copies if they're enabled on the drive where the database was installed.

"Hugh" <Hugh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1F289A62-C152-40DA-9091-9CF42BB90B6F@xxxxxxxxxxxxxxxx
> Nick,
>
> Unfortunately the documentation just gave me the command line string > but
> did
> not provide the files and paths to the uninstalled db.
>
> I appreciate your input and will post the solution when I find one.
>
> Regards.
> -- > Hugh
>
>
> "Dave Nickason [SBS MVP]" wrote:
>
>> Sorry, I don't know the path offhand. My own server has a custom WSUS
>> install to its own drive, and it was upgraded from WSUS 2, so I can't >> say
>> for sure where they belong. Can you tell from the document that
>> recommended
>> deleting the database?
>>
>> "Hugh" <Hugh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:7A7AE7B7-5C01-44EE-A59F-EDE2BBE80519@xxxxxxxxxxxxxxxx
>> > Dave,
>> >
>> > Thanks for the prompt reply. I run a full daily backup but am unsure >> > as
>> > to
>> > the correct path that I need to restore to. I did not want to >> > restore
>> > the
>> > incorrect files.
>> >
>> > Any ideas as to what the correct path might be?
>> >
>> > Thanks again for your assistance.
>> > -- >> > Hugh
>> >
>> >
>> > "Dave Nickason [SBS MVP]" wrote:
>> >
>> >> Can you restore a backup of that database? That database is shared >> >> by
>> >> things other than WSUS, which I believe is what you're running into
>> >> here -
>> >> WSS uses that database in addition to WSUS, so you're going to have >> >> to
>> >> restore it in order to get WSS working again.
>> >>
>> >>
>> >> "Hugh" <Hugh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> news:513C1BE1-BA8C-450E-9F81-FEAD8AB52325@xxxxxxxxxxxxxxxx
>> >> > In trying to troubleshoot WSUS 3.0, I saw a post that directed me >> >> > to
>> >> > remove
>> >> > the Windows Internal Database and reinstall WSUS. Now my WSS 3.0 >> >> > and
>> >> > WSUS
>> >> > applications are broken. I have tried reinstalling both WSS and >> >> > WSUS
>> >> > but I
>> >> > get a message that "failed to start the database service
>> >> > MSSQL$Microsoft##SSEE".
>> >> >
>> >> > Also, my event log is a sea of red - Windows Server Update >> >> > Services
>> >> > Event
>> >> > 421: Connection to database failed. Reason=SQL Server does not >> >> > exist
>> >> > or
>> >> > access denied...:
>> >> >
>> >> > Any suggestions or assistance as how to fix these applications is
>> >> > greatly
>> >> > appreciated.
>> >> >
>> >> > -- >> >> > Hugh
>> >>
>> >>
>>
>>



.

Relevant Pages

  • Re: WSUS and WSS 3.0 broken
    ... You might want to look at the WSUS release notes - I'm pretty sure ... Add/Remove, then reinstall? ... SBS monitoring & reporting now works as does WSS 2.0. ... you might be able to get those database files ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS and WSS 3.0 broken
    ... Does it matter if I reinstall WSUS before WSS? ... copies if they're enabled on the drive where the database was installed. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS and WSS 3.0 broken
    ... I do not have data in the companyweb so I would consider going the reinstall ... you might be able to get those database files back from shadow ... install to its own drive, and it was upgraded from WSUS 2, so I can't say ... WSS uses that database in addition to WSUS, so you're going to have to ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS and WSS 3.0 broken
    ... You don't need to reinstall WSUS, but then you'll need to come up with an alternative method of patching your workstations. ... SBS monitoring & reporting now works as does WSS 2.0. ... >> uninstall both, then reinstall companyweb, then reinstall WSUS. ...
    (microsoft.public.windows.server.sbs)
  • Re: Sharepoint Restore
    ... How should I reinstall the companywebsite? ... Should I use the continue setup on my SBS server and uninstall the intranet ... reinstall my server and now I have trouble to restore my companyweb site. ... new content database and then try the restore operation again. ...
    (microsoft.public.windows.server.sbs)