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 and Justin Crosby]
Under certain conditions, the Windows SBS Console may show one or several of the following symptoms:
If you are seeing one or multiple symptoms like the ones described above, the following steps should help improve the overall performance of the Windows SBS console and prevent them from happening. There is always the chance that you might be experiencing an issue that is unrelated to this post but does present itself with similar symptoms, if that is the case, then the following steps might not provide relief.
This command can take up to 10 minutes depending upon the speed of the hardware. Once complete results should improve immediately.
For more information about monitoring your Windows SBS 2008 server, read Monitoring and Reporting in Windows SBS 2008.
Updated 7/17/2009: Included command to immediately begin clean-up.
upon running the cmd i get the following error:
Sqlcmd: Error: Syntax error at line 300 near command ''' in file 'c:\updateSBSMonitoring.sql'
I have followed the procedure provided in this blog and receive the following error:
"Sqlcmd: Error: Syntax error at line 300 near command ''' in file c:\updateSBSMonitoring.sql"
What am i doing wrong?
Please re-download the file. The file has less than 50 lines. If yours is reporting 300+, the file must have become corrupted during download.
Whilst this appears to have resolved the "Not Available" problem we were experiencing I have noticed that the sbsmonitoring_log database has grown 1Gb overnight.
Will this be reduced during maintenance or is it something I will need to address ?
After redownloading it and running the instructions it worked. Thanks.
Could you please tell me how often the SBS Monitoring database is supposed to run it's cleanup job ? I applied your sql file 3 days ago, and my database still has 90 days of events logged.
Does the cleanup job also get logged in the event viewer ? That way I can see when it was last run.
The cleanup job should run nightly. Depending on the server hardware your job may be timing out before it has time to complete. The cleanup job was designed to only have to clean up a few days (usually 1) worth of data. When we make the change we are cleaning up 60 days worth of data, which can take a lot longer. In your case I reccomend you run the cleanup job manually.
Download and edit the updated script so that it only contains:
Then rerun the main steps 2 and 3 (backup and then run script). This will manually launch the cleanup, and can take 5-15 minutes to run.
Note: we updated the script to manually launch the cleanup, but it appears that you have the previous version, so make sure you download the newest copy.
Thank you Justin. The cleanup job is working fine now, as is my console.
Having run the updated SQL I found my sbsmonitoring_log file increased by 2Gb in size. I'm not sure if this is consistent with your findings.
The author does a great job of arranging this vast body of knowledge into one blog. I do agree w/the other reviewers on that point.
I have applied this fix successfully, and when I generate a summary report the console still crashes. Is there any other suggestions that you could have me try ?
I have applied the fix successfully. But the sbs console still crashes when i run a daily summary report. Any other suggestions ?
Hey I ran this script on a 3.9GB sbsmonitoring database and it created a 20GB LDF file and consumed the remaining space on the drive and brought it down.
Panoptik: The script is provided "As is". If you read posts about the script you will know that it can potentially grow a hysterical sized log file. When that does happen and the database becomes unrecoverable please follow this guide instead: