Thursday, June 30, 2011

SCOM: Run As Account does not exist on the target system or does not have enough permissions [MS SQL server 2008]


Yesterday  my SQL Server Management Pack reporting that it is facing some problem with “run as accounts” it says either “run as accounts does not exists” or they don't have “enough permission” to do some tasks. Both these server have SQL Server 2008 installed.

When SQL 2008 is installed by default, it no longer places BUILTIN\Administrators in the SQL security access list.  The install of SQL 2008 now prompts the installer to give SQL a user account, or Group, to grant SA (SysAdmin) rights to.  If installing on a standalone instance, NT AUTHORITY\SYSTEM (Local System) is still granted SA rights.  If installing on a clustered instance, NT AUTHORITY\SYSTEM (Local System) is granted public rights, but not SA.

Kevin Holman



Kevin Holman wrote an excellent post on this error.. click here

I have only few machine which are running SQL Server 2008, so i plan to give my default agent action account the rights on SA in SQL Server 2008.


Login to problematic SQL Server. Open SQL Management Studio. Got to SECURITY and then expand LOGINS,


Choose the “Default Agent Action Account” right click on it and then choose Properties.


Now click on “Server Role” and then select “SysAdmin” and click on OK..


That’s All :-) .. It should resolve the SQL Server 2008 Run As Problem.

I hope that it helps someone :)


Aman Dhally

Wednesday, June 29, 2011

SCOM: Event ID “2000”

Today I check my SCOM windows event log and saw some error logs with “EVENT ID 2000”. Complaining about that the one of my  SERVER is not a part of SCOM Management Group.

So Lets try to resolve it .
Step 1
My First Step is Login to the server who is generating an alerts. First I removed the SCOM Agent and then I reinstall   again manually.
Step 2
Now in SCOM console to to “Administration” then click on “Pending Management” and you may see the name of the server on which we just installed the SCOM AGENT.
Right click on Server and click on “Approve”

Now wait for 3-4 minutes to update the changes in SCOM and after few minute you will see that server is appeared in SCOM and it is healthy now.
And you will see “EVENT ID 29103” saying that our problematic server is now successfully able to contact with SCOM server.

I hope it may helps someone
Aman Dhally