Run as account does not Exist.
Hi,
I am getting the following error for Run As account .
The action account is been added and has the sys admin rights, but still i am getting alerts as
Run as account does not Exist.
Appreciate any help.
Thanks
January 24th, 2011 7:14am
Can you give us a bit more
Is this on the SQL MP and are they the SQL runas accounts that are giving out?Paul Keely
Free Windows Admin Tool Kit Click here and download it now
January 24th, 2011 9:49am
Hi Paul,
The error is as below:
Run As Account does not exist on the target system or does not have enough permissions.
I see the following in the description:
Managegement Group: xxx Script: GetSQL2005DBFreeSpace.vbs : Cannot login to database [yyy.com][MSSQLSERVER:master]
January 24th, 2011 10:09am
Hi Paul,
Yes this is on SQL MP and they are SQL runas accounts.
Free Windows Admin Tool Kit Click here and download it now
January 24th, 2011 10:57am
Ok and can I ask you have you configured a specif account for SQL monitoring and if you have do you have it distributed to the SQL servers in Question?
http://blogs.technet.com/b/kevinholman/archive/2010/09/08/configuring-run-as-accounts-and-profiles-in-r2-a-sql-management-pack-example.aspx
or for the basics
http://technet.microsoft.com/en-us/library/bb735423.aspx
Paul Keely
January 24th, 2011 11:01am
Hi
Can you just check that the databases that are being referenced by this alert aren't set to auto-close. I have seen this alert fire when the database is unavailable (the user can't login) simply because the database is "closed".
Cheers
GrahamView OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
January 24th, 2011 1:25pm
hi Paul,
As i have mentioned in the Alert description above, we are getting same descritpion for SQL 2005 and SQL 2008 DB with only difference in the yr displayed.
So Could it be some error with the script?
Please suggest
January 25th, 2011 10:31am
Hi Graham,
As i have mentioned in the Alert description above, we are getting same descritpion for SQL 2005 and SQL 2008 DB with only difference in the yr displayed.
So Could it be some error with the script?
Please suggest
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2011 10:31am
the error is pretty self explainatory imho. The account can't login to the master db. Have you tried to connect to this manually with this account? Even though it's sa it could still have an explicit deny.Rob Korving
http://jama00.wordpress.com/
January 25th, 2011 10:56am
If it is the SA account, it should always return with "access denied" - the SA account is nearly always disabled and replaced with a honeypot account in a locked down SQL environment.Microsoft Corporation
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2011 11:13am