The monitoring and reporting data store was not installed and configured properly

  • Article

Applies To: Windows Small Business Server 2011 Standard

Problem   The monitoring and reporting database is not installed and configured properly.

Features affected   Multiple features that are associated with the network health of Windows SBS 2011 Standard are not functional. This includes the following tasks, which may not run:

  • Email alerts regarding computers in the domain (normally occurs multiple times per day).

  • Updates to computers that should be managed by Windows Server Update Services (WSUS) (occurs multiple times per day).

  • Updates to the anti-spam Safe Senders list and Safe Recipients list for users’ mailboxes (occurs daily).

  • Updates to the SBS Users policy security filter with the information from the Active Domain (occurs multiple times per day).

  • Deleting spam in the badmail directory, when it exceeds a certain size (occurs weekly).

  • Check that the domain network is functioning correctly (occurs nightly).

  • Check for root or leaf certificates that are about to expire (occurs daily).

  • Database cleanup of records that are older than 90 days (occurs nightly).

  • Upload of SQM data (occurs daily).

  • Verify domain licensing (occurs daily).

  • Generation of monitoring reports may not occur and may not be emailed.

Resolution    Due to the number of complex product interactions and dependent tasks related to the failure in installing and configuring the monitoring and reporting data store, manual steps to recover from this failure cannot be provided at this time.

To recover from this error, perform the following steps:

  1. Restore the source domain from a backup, as described in the guide that applies to your source domain.

  2. After you restore the source domain, reinstall Windows SBS 2011 Standard as described in the guide that applies to your migration.

You can also contact Microsoft Product Support to receive support in isolating the source of the failure so that you can correct it before restarting the migration process.