The official blog for Windows Server Essentials and Small Business Server support and product group communications.
EPS Team Blogs
[Today's post comes to us courtesy of Damian Leibaschoff from Commercial Technical Support]
In SBS 2008 and SBS 2011 standard, we have a service called the Windows SBS Manager that is responsible for a number of tasks around monitoring, alert reporting and maintenance. This service relies on a SQL database running on a SQL express instance called SBSMonitoring. Under certain circumstances, the database may become unusable, when this happens you can experience behaviors like the SBS console crashing, or incorrectly reporting the status of machines. When this happens there might be a need to create a new, blank, database to regain functionality. Since all the information collected is dynamic, by creating a new database you would lose only any custom reports you may have created in the SBS Console, report customizations, and all the archived reports. Furthermore, upon recreating the database, it will need some time to contact all clients and report on their status, this time may vary, since clients may be offline, it is recommended to wait 48hrs before trying to validate the data.
To recreate the databases use these steps:
File C:\windows\temp\create-sbsmonitoringdb.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see "get-help about_signing" for more details. By default we should have the required code execution policy on our SBS servers, this issue is usually related to the way the script was downloaded into the affected server. Open the properties of the download script file from Windows Explorer and click on the Unblock option.
Hooray! I've been waiting for this for a long time. I've copying SMSMonitoring databases from working servers to fix broken ones.
If you get problems with this script, search "Stop-Service DataCollectorSvc" and the next line "Stop-Service 'MSSQL$SBSMONITORING'" and add -force before starting the script