Re: WSUS RTM breaks SBS 2003 SP1 reporting

Hi Stuart,

I've had the same problem as well. Would I be right in thinking that when
you installed the release candidate of WSUS, you used an existing database
(ie SBS Monitoring) instead of a separate one ? (As per the suggestions on
smallbizserver.net)

If that is the case, the uninstallation seems to take the whole database
with it.
(It doesn't seem to make any difference whether you specify to leave the
database during the uninstallation or not.)

I fixed the problem, by reparing monitoring using the instuctions here
http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?&query=sbs+monitoring&lang=en&cr=US&guid=&sloc=en-us&dg=microsoft.public.windows.server.sbs&p=1&tid=dd22f0d0-5fad-45fd-9a5f-b05af31db5ba

Unfortunately, you do appear to lose your old data, but that's the penalty
we've paid for using a RC instead of the finished version :)

When you come to install WSUS again, you'll probably find that you don't
have the option of adding the WSUS data to an existing database. I don't know
if this a tweek by Microsoft between the RC and final version, or whether
there is still something wrong with the monitoring, although my seems to be
OK now.

(I've only just finished sorting out the problem, so I'm waiting for
monitoring data to be collected before I can be sure it's OK)

Hope this helps

"Stuart Renes" wrote:

> Oops... meant to say "ISA 2004 SP1" of course...
>
> "Stuart Renes" <srenes@xxxxxxxxxxx> wrote in message
> news:O3tx3RobFHA.3400@xxxxxxxxxxxxxxxxxxxxxxx
> > Hi All,
> >
> > I just upgraded my SBS 2003 to SP1, re-added ISA 2005 SP1 (I had added it
> > prior to SBS SP1). Everything was working perfectly...until I removed SUS
> > and replaced it with the RTM release of WSUS.
> >
> > WSUS (using port 8530) works great but it seems to have broken all SBS
> > reporting. I was wondering if reinstalling SBS 2003 SP1 would help as I
> > noticed from the logs that it seems to check for the presence of WSUS.
> >
> > All I receive in my email report now is
> > HTTP 400 - Bad Request
> > Internet Explorer
> >
> > Anyone else out there seen this issue?
> >
> > Best Regards,
> >
> > Stuart [MVP - MOM]
> >
> >
>
>
>
.

Relevant Pages

  • Re: moving WUS to another partition
    ... using any SQL Server/MSDE database) just to detach the database. ... I understand that you used wsusutil to move the WSUS ... Microsoft Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS and WSS 3.0 broken
    ... I'd recommend calling CSS and letting them walk you through the restore procedure. ... If you don't have data at risk, you could just reinstall companyweb and WSUS. ... 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. ... >> restore it in order to get WSS working again. ...
    (microsoft.public.windows.server.sbs)
  • WSUS 3.0 upgrade failed
    ... The Parent server and one of the downstream servers upgraded just ... install had failed and that it made a backup of the database. ... uninstall the WSUS 2.0. ...
    (microsoft.public.windowsupdate)
  • Re: WSUS Errors after System state restored
    ... You didn't mention what version of WSUS you are running but my first thought is to download v3 SP1 and run the installer. ... It should uninstall the old version, stopping the appropriate services and removing the database, and you can get a nice upgrade from there as well. ... recover sufficiently and the server went off whilst running. ... see Help and Support Center at ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS RTM breaks SBS 2003 SP1 reporting
    ... I didn't install the RC of WSUS on my SBS server. ... > you installed the release candidate of WSUS, you used an existing database ...
    (microsoft.public.windows.server.sbs)