SBS 2008 - How to rebuild the reporting database

Question

I'd like to start using the inbuilt reporting facilities in SBS2008.  But when I start up the console and click on "Reports", although I am taken to the SBS2008 console's reports screen, a couple of seconds later, the following error message
is displayed:
"There was an error while loading data for this page".
When I click "Close" to close the error message, I'm left looking at the console's reports screen but with nothing shown.  The top pane simply says:
"There are no reports to display".
So, I then click on "Add a new report" in the right-hand pane.  Nothing happens for a couple of minutes - not even an hour glass.  Eventaully, a window opens up, headed "New Report Properties".  So, I had a go at creating
a new report, e.g.:
- Report Name = Test123
- Content = Summary
- E-Mail Options = I entered my email address
- Schedule = I set it to daily at 9pm
When I clicked "Ok", after a couple more minutes of thinking, it came back with:
"The report properties cannot be saved. Reopen the Report Properties dialog, and then try again."
I don't know how to tackle this issue.  I administer the network here but don't know SQL Server - and we don't have any SQL Server applications of our own - just the inbult ones like WSUS.
If there is a problem with the actual reporting database, I'd be happy to rebuild it, or even reinstall SQL.   But I don't know how.   My main concern is that WSUS is running beautifully and I don't want to go anywhere near anything that might
break it.  I would rather have no reports than lose WSUS.
Could someone point me to some step-by-step instructions aimed at someone who knows Windows Server (to an extent) and SBS2008 - but has no knowledge of SQL Server?

Answer 1

I worked through the article but hit problems.  Any thoughts would be gratefully received.
Here's what happened:
1. I checked that SQL Server 2005 is installed and that Windows SBS Manager is installed and started
2. I looked for "SQLServer (SBSMONITORING)" in the list of services but it is completely missing
I then followed the section headed "If necessary, create a new SBSMonitoring database".  This takes one to another article:
http://blogs.technet.com/b/sbs/archive/2011/08/22/how-to-recreate-the-sbsmonitoring-database.aspx.
I followed the instructions, which included downloading Create-SBSMonitoringDb.ps1 and running it in an administrative Power Shell.  When I ran it, I got a load of errors.
=============================================================
PS C:\windows\temp> .\Create-SBSMonitoringDb.ps1
Stop-Service : Cannot find any service with service name 'MSSQL$SBSMONITORING'.
At C:\windows\temp\Create-SBSMonitoringDb.ps1:28 char:13
+ Stop-Service <<<<  'MSSQL$SBSMONITORING'
    + CategoryInfo          : ObjectNotFound: (MSSQL$SBSMONITORING:String) [Stop-Service], ServiceCommandException
    + FullyQualifiedErrorId : NoServiceFoundForGivenName,Microsoft.PowerShell.Commands.StopServiceCommand
Get-ItemProperty : Cannot find path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\SBSMONITORING\Setup\' because it does not exist.
At C:\windows\temp\Create-SBSMonitoringDb.ps1:35 char:23
+     $key=get-itemproperty <<<<  "HKLM:\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\SBSMONITORING\Setup\"
    + CategoryInfo          : ObjectNotFound: (HKLM:\SOFTWARE\...NITORING\Setup\:String) [Get-ItemProperty], ItemNotFo
   undException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetItemPropertyCommand
Start-Service : Cannot find any service with service name 'MSSQL$SBSMONITORING'.
At C:\windows\temp\Create-SBSMonitoringDb.ps1:54 char:14
+ Start-Service <<<<  'MSSQL$SBSMONITORING'
    + CategoryInfo          : ObjectNotFound: (MSSQL$SBSMONITORING:String) [Start-Service], ServiceCommandException
    + FullyQualifiedErrorId : NoServiceFoundForGivenName,Microsoft.PowerShell.Commands.StartServiceCommand
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote
connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not  allow
remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote
connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
WARNING: Waiting for service 'Windows SBS Manager (DataCollectorSvc)' to finish starting...
WARNING: Waiting for service 'Windows SBS Manager (DataCollectorSvc)' to finish starting...
WARNING: Waiting for service 'Windows SBS Manager (DataCollectorSvc)' to finish starting...
WARNING: Waiting for service 'Windows SBS Manager (DataCollectorSvc)' to finish starting...
WARNING: Waiting for service 'Windows SBS Manager (DataCollectorSvc)' to finish starting...
WARNING: Waiting for service 'Windows SBS Manager (DataCollectorSvc)' to finish starting...
WARNING: Waiting for service 'Windows SBS Manager (DataCollectorSvc)' to finish starting...
WARNING: Waiting for service 'Windows SBS Manager (DataCollectorSvc)' to finish starting...
WARNING: Waiting for service 'Windows SBS Manager (DataCollectorSvc)' to finish starting...
<Ctrl-C>
=================================================================
If you have read this far and understand the above, what should I do next?