Support Tip: Error message when deleting the Subscribers object from AdministrationNotifications in Operations Manager

~ Keshav Deo Jain | Support Engineer

FIXHere’s a quick note on an issue I’ve run into a couple times that might help you out if you happen to see it. What happens is that the error message below may appear while deleting the Subscribers object from Administration\Notifications in Microsoft System Center Operations Manager 2007 (OpsMgr 2007), System Center 2012 Operations Manager (OpsMgr 2012) or System Center 2012 R2 Operations Manager (OpsMgr 2012 R2):


The Error Message

The full error message you receive will be similar to the following:

The following information was gathered when the operation was attempted. The information may appear cryptic but provides context for the error. The application will continue to run.

System.InvalidOperationException: The notification subscription was not valid for the update. See inner exception for details.

—> System.ArgumentException: The notification subscription is not valid for insert. See inner exception for details. —> Microsoft.EnterpriseManagement.Common.ManagementPackException: Database error. MPInfra_p_ManagementPackInstall failed with exception:
Database error. MPInfra_p_ManagementPackInstall failed with exception:
Could not allocate space for object 'dbo.DeployedManifest'.'PK_DeployedManifest' in database 'OperationsManager' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
at Microsoft.EnterpriseManagement.Common.Internal.ServiceProxy.HandleFault(String methodName, Message message)
at Microsoft.EnterpriseManagement.Common.Internal.MonitoringNotificationServiceProxy.UpsertNotificationSubscription(String conditionDetectionConfiguration, String dataSourceConfiguration, IList`1 endpoints, String name, String internalName, String displayName, String description, String languageCode, String targetString, String targetManagementPackId, String targetManagementPackVersion, String targetManagementPackPublicKey, String targetManagementPackAlias, Int32 subscriptionType, Boolean enabled, Boolean resetStateOnEnabled, Boolean isUpdate)
at Microsoft.EnterpriseManagement.MonitoringNotificationManagement.UpsertNotificationSubscription

The Fix

Generally this error occurs when there is not enough space available for the OperationsManager database. You can run the following query in SQL Management Studio to verify the free space available for the OperationsManager database:

exec sp_spaceused

This query will give you the database size as well as the amount of free space as shown below:


If you come across this error, usually the easy fix is to simply create additional free space for database. To do this, right-click on the OperationsManager database in SQL Management Studio and choose Properties. In Properties, click Files in the right side pane. From there you can change the DB size.

Alternately, you could also enable the autogrow setting for the database. Note that the OperationsManager database has autogrow disabled by default, which is what we recommend. This is because if the OperationsManager database has a size that is too small and the database is set to autogrow, the autogrow process will use more system resources than during normal operation which can impair system performance. With that said, you can find details about autogrow in the following Knowledge Base article:

315512 Considerations for the "autogrow" and "autoshrink" settings in SQL Server

Keshav Deo Jain | Support Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up:

Configuration Manager Support Team blog: 
Data Protection Manager Team blog: 
Orchestrator Support Team blog: 
Operations Manager Team blog: 
Service Manager Team blog: 
Virtual Machine Manager Team blog:

Microsoft Intune:
WSUS Support Team blog:
The RMS blog:
App-V Team blog:
MED-V Team blog:
Server App-V Team blog:
The Surface Team blog:
The Application Proxy blog:

The Forefront Endpoint Protection blog :
The Forefront Identity Manager blog :
The Forefront TMG blog:
The Forefront UAG blog: