"Run As Account does not exist on the target system or does not have enough permissions"

Hello,

I've read many of the other articles and discussions on this topic, but none seem to really address this particular issue. We are seeing the alert intermittently on several systems.

First, here is a sample of the alert:

Alert: Run As Account does not exist on the target system or does not have enough permissions
Source: MSSQLSERVER
Path: <serverfqdn>
Last modified by: <action account>
Last modified time: 4/6/2014 1:08:22 PM
Alert description: GetSQL2012BlockingSPIDs.vbs : Cannot login to database [<serverfqdn>][MSSQLSERVER:master] 

In almost all of the cases, the db in question is master.  So far, in all of the cases, we've confirmed that NT AUTHORITY\System is a sql sa.  We are not using the SQL Run As Profile, so SQL Run As is defaulting to use our SCOM action account, which is the default Local System.

Even if we do set a Run As account for SQL, distribute it to the servers, and ensure it's a SQL sa, we will still occasionally get the alert.  When we then go to the system in question, open a command prompt as the Run As account, and run the script manually, it works fine.

So I'm fairly confident this is not a permissions issue.  My reading indicates that this could happen if the db becomes closed, but this only applies if the db is not master.  In our case, the db is almost always master.

I'm wondering if anyone out there has experienced a similar issue.  It would be great if we could increase the timeout on the script, but that's not an overrideable parameter.  I certainly don't want to disable the alert, but it's fairly annoying and is generating incidents that we end up having to close as "false alarm" without having a good reason why.

Thanks,

John