SBS 2008 Console May Take Too Long to Display Alerts and Security Statuses, Display Not Available, or Crash

re: SBS 2008 Console May Take Too Long to Display Alerts and Security Statuses, Display Not Available, or Crash

itk.jason — Wed, 29 Jul 2009 23:56:31 GMT

I have applied the fix successfully. But the sbs console still crashes when i run a daily summary report. Any other suggestions ?

re: SBS 2008 Console May Take Too Long to Display Alerts and Security Statuses, Display Not Available, or Crash

jason@itk — Wed, 29 Jul 2009 23:35:36 GMT

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 ?

re: SBS 2008 Console May Take Too Long to Display Alerts and Security Statuses, Display Not Available, or Crash

Ink cartridges — Tue, 28 Jul 2009 15:04:24 GMT

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.

re: SBS 2008 Console May Take Too Long to Display Alerts and Security Statuses, Display Not Available, or Crash

David — Fri, 24 Jul 2009 21:44:19 GMT

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.

re: SBS 2008 Console May Take Too Long to Display Alerts and Security Statuses, Display Not Available, or Crash

SBS Bloggers — Tue, 21 Jul 2009 23:45:37 GMT

Hello David,

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:

USE SBSMonitoring

EXECUTE [SBSMonitoring].[dbo].[CleanupDatabase]

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.

Thanks,

Justin

re: SBS 2008 Console May Take Too Long to Display Alerts and Security Statuses, Display Not Available, or Crash

David — Fri, 17 Jul 2009 19:04:21 GMT

Hello

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.

Thank you

re: SBS 2008 Console May Take Too Long to Display Alerts and Security Statuses, Display Not Available, or Crash

AAS — Thu, 16 Jul 2009 18:25:47 GMT

After redownloading it and running the instructions it worked. Thanks.

re: SBS 2008 Console May Take Too Long to Display Alerts and Security Statuses, Display Not Available, or Crash

David — Thu, 16 Jul 2009 16:42:13 GMT

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 ?

Thank you

re: SBS 2008 Console May Take Too Long to Display Alerts and Security Statuses, Display Not Available, or Crash

SBS Bloggers — Wed, 15 Jul 2009 21:47:37 GMT

AAS,

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.

Thanks,

Justin

re: SBS 2008 Console May Take Too Long to Display Alerts and Security Statuses, Display Not Available, or Crash

AAS — Wed, 15 Jul 2009 18:57:35 GMT

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?