Hi! I have installed the SQL MP 6.5.1.0 for SQL2005,SQL2008,SQL2012 and SQL2014. I know that I need to use one SQL RunAsAccount and add that account in the SQL RunAsProfiles to have the correct access to run the SCOM SQL scripts and get the correct monitoring. We have give this SQL RunAsAccount the "Local Administrator" and "sysadmin" rights on all instances through a group. This SQL servers also use UAC, then we tested to add this SQL RunAsAccount directly with sysadmin rights on one SQL servers instances instead through a group. But still the same problem... I haven't test the new SQL MP version 6.5.4.0 yet and I know that there is one fix for "Fixed Timeout error in CPU utilization monitoring scenario"

The SQL RunAsAccount use "More Secure" and we are running the SQL RunAsProfiles target type against a Group with "Windows Computers" for all the SQL servers that we want to run this RunAsAccount against. We have the same problem when we tested to change the target type to "SQL Computers" 

At most of our customer it works fine but at one customer we still get all this SQL monitor related errors:

• Power Shell Script failed to run (timeout 200 sec)

        - scriptname=CPUUsagePercentDataSource.ps1

        - workflow=Microsoft.SQLServer.2008DBEngine.ThreadsCountMonitor

• Operations Manager failed to start a process

       - command=GetSQL2008DBWinServStat.js

       - workflow=Microsoft.SQLServer.2008.Database.ServiceMonitor

• Operations Manager failed to start a process due to lack of Resources

       - command=GetSQL2012DBFreeSpace.vbs

• Operations Manager failed to run a WMI Query

         - workflow=Microsoft.SQLServer.2012.Database.ServiceMonitor

Someone with any idea what's the problem can be?

Hi,

Why not configuring runas account for SQL MP following the blog below:

Configuring Run As Accounts and Profiles in OpsMgr A SQL Management Pack Example

http://blogs.technet.com/b/kevinholman/archive/2010/09/08/configuring-run-as-accounts-and-profiles-in-r2-a-sql-management-pack-example.aspx

Regards,

Yan Li

Thats exactly what I have done and still I get all this script errors. At other customer it works, can it be som Policy problem?

//Mats A

Hi,

>At most of our customer it works fine but at one customer we still get all this SQL monitor related errors

Do you mean only one SQL server havs this error message poped out? If that is the case, then you may check whether the runas account configured has proper permissions on that server. You may add the account to local admin group.

Please also go through the link below:

http://blogs.technet.com/b/kevinholman/archive/2013/10/24/opsmgr-sql-mp-version-6-4-1-0-capabilities-and-configuration.aspx

Regards,

Yan Li