RE: SUS to WSUS gone astray...


Hello,

Thanks for your post and Russ's input.

Based on resarch of the error message, this is caused by a corrupted SUSDB
database. If you are using SBS 2003 Premium edition with SQL server
installed, please first please try:

- Stopping SQL Server Services
- Backing up WSUS Databases
- Started SQL Server Services
- When restarted the services, please check if the issue persists.

If the issue persists, I suggest we follow the steps below to reinstall the
SBS 2003 R2. During uninstallation, please keep the update files.

To uninstall the SBS 2003 R2:

1. In Add/remove programs, select Remove to remove Windows Small business
server R2.

2. Delete all files under the folder: C:\WSUS

3. Delete all files the folder: C:\Program Files\Update Services

4. Delete the WSUS related Virtual directories under the Default web site
in IIS admin.

- UpdateServices virtual directory
- ClientWebService virtual directory
- SelfUpdate virtual directory

5. Confirm that IIS and other buildCin websites were still functioning.

6. Check and confirm the GPOs for WSUS ware gone.

- Small Business Server Update Services Client Computers Policy
- Small Business Server Update Services Server Computers Policy
- Small Business Server Update Services Common Settings Policy

7. Check and confirm the Task schedulers were removed.

- Update Services configuration task
- Update Services synchronization task
- Update Services auto approval task

To reinstall the SBS R2:

1. Run from the Cd\WSUS_20\wsussetup.exe

2. Uncheck the Launch Website & selected Finish.

3. Run the SBS2003 R2 setup by launching setup.exe file

4. In the autorun page, please select Install Windows Small business
Server 2003 R2 to install the SBS R2.

After the SBS R2 reinstalled successfully, please verify to see if the
Update Services in SBS server management console works properly.


Related information:

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

Installing Microsoft Windows Server Update Services 3.0 on Windows Small
Business Server 2003
http://www.microsoft.com/downloads/details.aspx?familyid=4F8813EE-DEE5-4B9F-
A127-55042F34BA43&displaylang=en

Issues that may occur on a Microsoft Windows Small Business Server
2003-based computer after you remove an MSDE 2000 SP4 instance, a SQL
Server 2000 Desktop Engine (Windows) SP4 instance, or a SQL Server 2000 SP4
instance

http://support.microsoft.com/kb/920899/en-us


Hope this helps.


Best regards,
Robbin Meng(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security

.

Relevant Pages

  • RE: trouble installing companyweb
    ... gone ahead and patched the server before continuing with step 13 of KB884453. ... sbs components that I could, ... install any 3rd-party software before you finish the installation. ... For the failed intranet component ...
    (microsoft.public.windows.server.sbs)
  • RE: Monitoring and Reporting
    ... I understand that you unable to get SBS ... monitoring report after you install Windows server 2003 sp2. ... To successfully install SBS 2003 SP1, ... Downloading and Installing Windows Small Business Server 2003 Service Pack 1 ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 R2 - Please Help
    ... computers be slow after you install the full SBS 2003 R2 components. ... log on slow is probably refer to incorrect DNS ... as the DNS server on the clients rather than the ISP DNS servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Fax Sharepoint Routing
    ... Business Server 2003 and click "Change/Remove", ... If the Fax Services component was original installed by using the SBS ... Install fro the Fax Server component. ... And then we should push the shared fax client application from server to ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... slip stream SBS you would have had it ages ago. ... How did they buy this Server? ... My main reason for slipstreaming the install is because I cannot get the ...
    (microsoft.public.windows.server.sbs)