MP SQL Server 2014 Discovery error - Microsoft.SQLServer.2014.DBEngineD iscoveryRule.Server

Hi,

I have a problem with the MP SQL Server 2014. I imported the MP Discovery, but I'm failing to discover the SCOM database.
On the server where the BD SCOM exist, two error appear in the Event Viewer: 
ID 4201 - Critical
DiscoverSQL2014DBEngineDiscovery.vbs: The query 'select * from SqlService where SQLServiceType =' 1 '' did not return any valid instances. Please check to see if this is a valid WMI Query .. Invalid class

ID 21405 error - Warning
The process started at 3:41:01 PM failed to create System.Discovery.Data, no errors detected in the output. The process exited with 0.
Command executed: "C: \ Windows \ system32 \ cscript.exe" / nologo "DiscoverSQL2014DBEngineDiscovery.vbs" {1C3DCFB6-8C6D-C131-EE37-22D9A478DAE0} {7F26FF79-1EF0-4BB4-9673-E08C44568A0E} xxxx.xxxx.xxx. xxxx.xxxx.xxx.xx xx xxxxxx "Exclude"
Working Directory: C: \ Program Files \ Microsoft Monitoring Agent \ Agent \ Health Service State \ Monitoring Host Temporary Files 2 \ 1414 \

One or more workflows Were affected by this.

Workflow name: Microsoft.SQLServer.2014.DBEngineDiscoveryRule.Server
Instance name: server1.local
Instance ID: {7A26AF79-LL67-3451-9673-E08C44568ASD}
Management group: SCOMMG

I hava a SCOM 2012 R2 in a Windows Server 2012 R2, and have SCOM BD in SQL Server 2014. The two servers are fully updated.
I installed the latest version of MP SQL Server 2014, version 6.6.0.

Can anyone help me with this issue?

Thank you,
Rui

 
August 24th, 2015 11:15am

It looks like you might have WMI issues with the server.

If you open WBEMTest and run the query

select * from SqlService where SQLServiceType =' 1 '

What is the result?

The WMI fix is:

http://blogs.technet.com/b/momteam/archive/2014/05/12/kb-event-4001-in-the-operations-manager-log-during-sql-server-2012-monitoring.aspx

http://www.opsman.co.za/scom-issue-discovering-sql-instances-databases/

Regards

Graham

Free Windows Admin Tool Kit Click here and download it now
August 24th, 2015 5:32pm

Thank you Graham. Work great!

I run the command "mofcomp sqlmgmproviderxpsp2up.mof" in the directory "C:\Program Files (x86)\Microsoft SQL Server\120\Shared" similarly to the link you share: http://www.opsman.co.za/scom-issue-discovering-sql-instances-databases/

Now SCOM is monitoring SQL DB, but the following error appear in the event viewer.

Error ID: 4201 

"DiscoverSQL2014DBEngineDiscovery.vbs : Access denied while reading registry value [\\Server1.local\HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQLServer\Parameters\(Default)]."

Any suggestion?

Thank you,

Rui

August 25th, 2015 5:54am

Have you configured the Run As Accounts? The following is for SQL 2005 \ 2008 \ 2012 but it works the same for SQL 2014 other than they have their own Profiles (the SQL 2014 MP is a pain as it breaks the way the SQL MPs have worked in the past):

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

SQL 2014 MP class structure:

http://blogs.technet.com/b/manageabilityguys/archive/2015/08/14/dynamic-sql-computer-group-with-health-service-watcher-objects.aspx

Cheers

Graham

Free Windows Admin Tool Kit Click here and download it now
August 25th, 2015 5:58am

Yes, i have configured Run As account. With an account that have all the necessary permissions.
August 25th, 2015 12:15pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics