I just set the frequency of the monitor to 12 minutes instead of 5. Hopefully it will calm down, it happens to seemingly random instances at all sorts of times. It even happens to instances where the load is almost nothing.

Interesting.

I don’t know why local system wouldn’t work, if LS has SA – so I don’t think you will get anywhere with run-as here.

I’d guess offhand that it was a SQL DMO issue… with multiple SQL DMO scripts occasionally running at the same time… but  that’s a guess.  Almost need a verbose SQL error log and see if we can determine what else was happening at the same time.

What version of SQL MP you running?

6.0.6569.0

What is the agent action account running as?

System

Does the agent action account have SA priv of SQL?

Yes. Even tried giving System db_datareader to the Master database despite it being a sysadmin.

If not – have you set and used a SQL run-as account in the SQL monitoring profile and associated it with this system, and does that domain account have local admin on the SQL server, and SA priv to SQL?

Haven’t tried not using System. I’m avoiding managing run as accounts as much as possible. I’m not really sure how I could do it here with the way we are politically divided. I suppose I could do a GoToMeeting and have them input the credentials since they don’t have the rights in OpsMgr and I don’t want to know their passwords. I think they would rather me use system anyway since there is no domain (service) account with sysadmin rights on all of their SQL servers. We’ve got 14 groups responsible for different geographic areas in the state and very few of the groups have any SQL knowledge. I needed to send screenshots to show them how to verify System had db_datareader access to the Master database. OpsMgr is always blamed first so I want to make sure I’ve exhausted my options as the OpsMgr administrator. I could go on with my story but it doesn’t really help this issue.

I’ve got 1 SQL instance that I have rights to manage that has the alert every once in a while, I can try anything on it.

What version of SQL MP you running?

What is the agent action account running as?

Does the agent action account have SA priv of SQL?

If not – have you set and used a SQL run-as account in the SQL monitoring profile and associated it with this system, and does that domain account have local admin on the SQL server, and SA priv to SQL?

Getting a bunch of these. I verified the account has the rights. Is anyone else seeing this? It looks like I’m going to have to disable the rule and recreate it to ignore the GetSQL2005BlockingSPIDs.vbs script errors but I’m not a big fan of that. The repeat count isn’t very high so it isn’t happening every execution interval. Everything else about the SQL instances are healthy. Suggestions?

Regards,

Christopher Summers

==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/

==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/

==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/

==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/

==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/