In this instance, I don't think a console repair will work, as I don't think the console is broken. The reports stopped a week ago as well, and reports are not console driven. I suspect there is a SQL issue causing both problems. The console is trying to pull data and SQL is croaking and the error us bubbling up.

the sbs 2008 is using WSUS to update its patches.
The server has a default sharepoint service running and using symantec backup exec for sbs to backup. If you talk about SQL, these are related database on SQL.

SBS also uses SQL behind the scenes for the monitoring and reporting component, so a SQL related failure, particularly one related to updating the "Windows Internal Database" can cause reporting to fail, and if it throws an error that the console doesn't know how to interpret, the console itself will throw unusual errors and potentially crash.

So I stand by my initial suggestions in the order they should be tried.

Somewhat re-iterating what you've already seen here, but here's a step-by-step.

The problem usually results from a SQL database being added to the built-in instance. You should be able to add an instance, but you have to use a separate database and a different port to avoid interfering with the monitoring and reporting database.

Written by Glen Knight (demazter) as part of a series of how-to articles.
Introduction
One of the biggest consumers of disk space with Small Business Server 2008(SBS) is Windows Server Update Services, more affectionately known as WSUS.
For t…

This course is ideal for IT System Administrators working with VMware vSphere and its associated products in their company infrastructure. This course teaches you how to install and maintain this virtualization technology to store data, prevent vuln…

In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB.
How Percona can help
Percona can help you determine if Percona Server for MongoDB is the right solution for …