Re: Unable to reinstall SBS Monitoring

On Sep 24, 1:39 pm, "Costas" <cpstechgr...@xxxxxxxxx> wrote:
If you want to uninstall or reinstall SBS 2003 R2 components on a server
that is running WSUS 3.0 you have to uninstall WSUS 3.0 first and then
remove/reinstall the components

http://technet2.microsoft.com/WindowsServerSolutions/SBS/en/library/d...

--
Costas

<bdcpb...@xxxxxxxxxxx> wrote in message

news:1190654556.775384.43100@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



Hello All:

After upgrading WSUS 2.0 to 3.0 my SBS monitoring started misbehaving
and showing "page cannot be displayed" errors.

I proceeded to remove and reinstall SBS Monitoring as outlined below.
However, I keep getting an error in the middle of the setup process. I
have tried this entire procedure at least three times and get the same
error:

"An error occurred while installing Microsoft Data Engine (MSDE).
Rerun Setup, and retry installing Monitoring"

Note that despite the error, MSSQL$SBSMONITORING and SQLAGENT$
SBSMONITORING do appear on the services applet, but as disabled.

Below I'm outlining the instructions used for the reinstallation as
well as the error log found at C:\Program Files\Microsoft SQL Server
\MSSQL$SBSMONITORING\LOG

I appreciate your help. Thanks!

Reinstallations instructions:

1) Uninstall Monitoring using Add/Remove Programs
2) Remove the Microsoft SQL Data Engine (MSDE) component. To do so,
follow these steps:
a) Click "Start", point to "Control Panel", and then click "Add or
Remove Programs".
b) Click "Microsoft SQL Server Desktop Engine (SBSMONITORING)", and
then click "Remove".
c) When you are prompted about whether you want to remove Microsoft
SQL Server Desktop Engine (SBSMONITORING) from your computer, click
"Yes".
d) Start Windows Explorer, and then locate and delete the following
folder:
Program Files\Microsoft SQL Server\MSSQL$SBSMONITORING
e) Use Registry Editor to delete the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\Monitoring
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
\SBSMonitoring
3) Delete the Monitoring virtual directory from IIS.
4) Rename the C:\Inetpub\Monitoring folder
5) Remove the SQLServer Service registry key.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQL
$<INSTANCENAME>
(Nothing found)
6) Remove the SQLServerAgent Service registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SQLAgent
$<INSTANCENAME>
(Nothing found)
7) Reboot
8) Reinstall Monitoring using Add/Remove programs
a) Select maintenance for Server Tools and install for Monitor
b) Confirm selection and proceed with setup

Before the setup completes it displays the following error:
An error occurred while installing Microsoft Data Engine (MSDE). Rerun
Setup, and retry installing Monitoring.

Error Log

2007-09-24 12:04:44.65 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.2 (Build 3790: Service Pack 2)

2007-09-24 12:04:44.65 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-09-24 12:04:44.65 server All rights reserved.
2007-09-24 12:04:44.65 server Server Process ID is 3488.
2007-09-24 12:04:44.65 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$SBSMONITORING\LOG
\ERRORLOG'.
2007-09-24 12:04:44.67 server SQL Server is starting at priority
class 'normal'(2 CPUs detected).
2007-09-24 12:04:44.87 server SQL Server configured for thread mode
processing.
2007-09-24 12:04:44.92 server Using dynamic lock allocation. [500]
Lock Blocks, [1000] Lock Owner Blocks.
2007-09-24 12:04:45.01 spid3 Warning ******************
2007-09-24 12:04:45.01 spid3 SQL Server started in single user
mode. Updates allowed to system catalogs.
2007-09-24 12:04:45.03 spid3 Starting up database 'master'.
2007-09-24 12:04:45.32 server Using 'SSNETLIB.DLL' version
'8.0.766'.
2007-09-24 12:04:45.32 spid5 Starting up database 'model'.
2007-09-24 12:04:45.37 spid3 Server name is 'GEO1\SBSMONITORING'.
2007-09-24 12:04:45.37 spid3 Skipping startup of clean database id
5
2007-09-24 12:04:45.37 spid3 Skipping startup of clean database id
6
2007-09-24 12:04:45.37 spid3 Starting up database 'msdb'.
2007-09-24 12:04:45.68 server SQL server listening on Shared
Memory.
2007-09-24 12:04:45.68 server SQL Server is ready for client
connections
2007-09-24 12:04:45.76 spid5 Clearing tempdb database.
2007-09-24 12:04:47.09 spid5 Starting up database 'tempdb'.
2007-09-24 12:04:47.25 spid3 Recovery complete.
2007-09-24 12:04:47.25 spid3 SQL global counter collection task is
created.
2007-09-24 12:04:47.26 spid3 Warning: override, autoexec
procedures skipped.
2007-09-24 12:04:58.89 spid51 Error: 15457, Severity: 0, State: 1
2007-09-24 12:04:58.89 spid51 Configuration option 'allow updates'
changed from 0 to 1. Run the RECONFIGURE statement to install..
2007-09-24 12:04:59.06 spid51 Error: 15457, Severity: 0, State: 1
2007-09-24 12:04:59.06 spid51 Configuration option 'allow updates'
changed from 1 to 0. Run the RECONFIGURE statement to install..
2007-09-24 12:04:59.70 spid3 SQL Server is terminating due to
'stop' request from Service Control Manager.- Hide quoted text -

- Show quoted text -

Costas...

Thanks for your promt response.

I did follow the directions on that document. More specifically, this
document directed me to:
Migrate from WSUS 2.0 to WSUS 3.0
http://technet2.microsoft.com/windowsserver/en/library/3a8c83c3-4eac-4cc3-86fc-a54e67de9c121033.mspx?mfr=true

I completed the instruction and the WSUS seems to be working fine.

My problem is now related to SBS Monitoring which is giving me an
error during the reinstall.

Am I missing something?

Thanks,

Bruce


.

Relevant Pages

  • Re: Mail Stops Intermittently after WSUS install
    ... According to your description, I understand after you installed the WSUS, ... exchange intermittently stop the services and you need start it manually. ... visit the following Microsoft Web Site: ... including installing WSUS on computers running Windows? ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS & WSUS 3.0
    ... I will provide you with a link to a doc that is used to install the RTM version of WSUS 3, not to be used when installing ona SBS server. ... Either the built-in group Users or the NT Authority\Network Service account should have read permission for the root folder on the drive where the WSUS content directory resides. ...
    (microsoft.public.windows.server.sbs)
  • Re: Mail Stops Intermittently after WSUS install
    ... According to your description, I understand after you installed the WSUS, ... exchange intermittently stop the services and you need start it manually. ... visit the following Microsoft Web Site: ... including installing WSUS on computers running Windows? ...
    (microsoft.public.windows.server.sbs)
  • RE: Using SQL Server 2005 for WSUS Server
    ... SQL Server service is not started. ... The account who install the WSUS server does not has administrative ... Please ensure that the latest SQL Server Service Pack ...
    (microsoft.public.sqlserver.setup)
  • svchost / wuauclt.exe spikes CPU at login
    ... they never complained about slowness until AFTER i put in WSUS ... THe computers that had complaints did get some updates made to their ... the computer needed updates and it was installing them, etc.), but they ...
    (microsoft.public.windowsupdate)
Loading