SBS2K3 Server Monitoring error

I have a server running SBS 2003 SP2.

I activated server monitoring about 6 months ago and it ran pretty well up until about one month ago when it failed. I tried re-running the Monitoring Configuration Wizard and it now failes.

The error message is "An error occurred while running the wizard". The
Configuring Data Store, Data Collection and Alert Threshold are all
checked at completion but Configuring Reports fails. if I do not check Receive a
daily performance report in e-mail, Configuring Reports completes
successfully. Checking to Elect to receive usage reports will also cause
Configuring Reports to fail. Specifing in an internal or external email
address has the same result, it fails.

Here's the error log:

Event Type:      Error
Event Source:  ServerStatusReports
Event Category:      None
Event ID:      1
Date:            9/23/2010
Time:            3:34:29 PM
User:            N/A
Computer:      (server name hare)
Description:
Server Status Report:
      URL:            http://localhost/monitoring/perf.aspx?reportMode=0
      Error Message:      Cannot open database requested in login 'SBSMonitoring'. Login fails.

Login failed for user '(domain name)\Administrator'.
      Stack Trace:         at usage.globalFn.connectDataSource(Boolean pingFirst)
   at usage.frmPerf.renderReportWorker()
   at usage.frmPerf.renderReport()

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Greg MasonOwnerAsked:
Who is Participating?
 
Rob WilliamsConnect With a Mentor Commented:
There was a recent similar question where it was suggested some of the web sites may have been updated to .NET 2.0 and if that wasn't the case reinstalling monitoring was suggested:
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_22765670.html
0
 
Greg MasonOwnerAuthor Commented:
Tried it. No joy.

Client doesn't want to spring for paid monitoring, Is there anything else that might work?
0
 
Rob WilliamsConnect With a Mentor Commented:
You could try re-installing the monitoring components as per:
http://msdn.itags.org/microsoft-sbs/36137/
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
Greg MasonOwnerAuthor Commented:
That didn't work either, although I am loath to re-install SQL since it will effect production and probably just make things worse..

We told the client the entire O/S will need to be re-installed from scratch to fix the issue. No one on the Microsoft support blog site has even addressed the question (typical) for a week! The only response I got was from here!
0
 
Greg MasonOwnerAuthor Commented:
Good effort and might have solved the issue in some circumstances. Just not this one.
0
 
Rob WilliamsCommented:
Thanks gem555. Sorry I was not able to help. I am surprised others did not "jump in", although that may indicate it is a unique problem.
Cheers!
--Rob
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.