Event ID 28005 in SCOM. SQL issue I think.

Posted on 2012-08-17
Medium Priority
Last Modified: 2012-08-21
We are having SCOM issues and I believe its related to the error below I am seeing on the SCOM server. We have SCOM and SQL installed on the same box. A contractor set it up and he is long gone. I can't get any of the subscriptions to stay in an enabled state so no email alerts are going out. When I enable the subscription it disables itself after a few minutes. Here is the error I am getting:

Log Name:      Application
Source:        MSSQLSERVER
Date:          8/17/2012 2:02:34 PM
Event ID:      28005
Task Category: Server
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Scomserver.domain.com

An exception occurred while enqueueing a message in the target queue. Error: 15404, State: 11. Could not obtain information about Windows NT group/user 'Domain\a-contractor', error code 0x534.

I am getting hundreds of these in the application log on the SCOM server. Now I don't know jack about 2008 SQL or SQL any version for that matter. When I look at some of the database properties in SQL Studio Manager, I see the database owner is the a-contractor account which has been deleted. One database in particular is the OperationsManager database.

I right click the OperationsManager database in SQL, select Properties and then select General on the left pane. In the right pane, under Database, the Owner is the contractor account that we deleted. Question is how to change that to be another account and could this configuration be causing the error above?

I am also seeing this error within SCOM under Active Alerts.

An alert subscription with the internal name "{0}" has been disabled because there is an issue with its configuration.  Refer to the product knowledge for more information on how to troubleshoot this issue.

            You can get the subscription's name as it's shown in the operations console by running the following command from the Operations Manager command shell:

            Get-NotificationSubscription | where-object{$_.Name -eq "{0}"}

I am guessing this is why my subscriptions keep getting disabled after I enable them. I don't know what its talking about when it says Internal Name "{0}"??

When I run the above Get command in the OpsManager shell, it comes back with nothing.
Question by:osiexchange
LVL 14

Assisted Solution

Daniel_PL earned 1000 total points
ID: 38307554

Try with changing SCOM database owner. Please find steps described in following article:


The error is not in this case but there is procedure to change database owner which applies here.
LVL 20

Accepted Solution

Marten Rune earned 1000 total points
ID: 38310930

This is your scenario exactly!

They recommend SA as DBOwner of the database. I must say I agree. Given that the SQL Server Service is run with a proper lowrights domain account (could be local to, but I prefere domain, so I can grant access to folders on the network for SQL).

Regards Marten

Author Closing Comment

ID: 38317410
Fixed issue.

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

     When we have to pass multiple rows of data to SQL Server, the developers either have to send one row at a time or come up with other workarounds to meet requirements like using XML to pass data, which is complex and tedious to use. There is a …
In this article I will describe the Backup & Restore method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
Screencast - Getting to Know the Pipeline
With just a little bit of  SQL and VBA, many doors open to cool things like synchronize a list box to display data relevant to other information on a form.  If you have never written code or looked at an SQL statement before, no problem! ...  give i…

807 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question