SQL 2008 not discovered in SCOM
Hi,
I have come across a new issue, SCOM 2007 R2 agent has been installed on a SQL 2008 server and installation is sucessful and no errors in eventlog of both agent and management server. But in the monitoring console under datatbase state in SQL server group
the server is not listed. and also the server is not categorized as 2008/2005 under computers in SQL folder (in monitoring pane) it is left blank space.
Note: No overrides has been applied
Any help on this is much appreciated.
Thanks, Sarav
Thanks, Sarav
May 26th, 2011 5:27pm
What SQL management pack do you use? Do you have the latest version?
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2011 5:47pm
I have found couple of discovery failure logs:
The process started at
3:53: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 "DiscoverSQL2005RSDiscovery.vbs" {4CC14CC2-E918-1733-726A-32631502C25B} {BBFEB11D-BEA3-86ED-FED1-1BB2962C2387}
Xxxxxx.xxx.xx.xx Xxxxxx.xxx.xx.xx XXXXXX
Working Directory:
C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 2\1008\
One or more workflows were affected by this.
Workflow name: Microsoft.SQLServer.2005.ReportingServicesDiscoveryRule.Server
Instance name: Xxxxxx.xxx.xx.xx
Instance ID: {BBFEB11D-BEA3-86ED-FED1-1BB2962C2387}
Management group: SCOM_1_TST
For more information, see Help and
Support
Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type:
Warning
Event Source:
Health Service Modules
Event Category:
None
Event ID:
21405
Date:
5/26/2011
Time:
3:53:01 PM
User:
N/A
Computer:
XXXXXX
Description:
The process started at
3:53: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 "DiscoverSQL2005DBEngineDiscovery.vbs" {E71360F6-C12E-8326-4539-FBC9D78862F5} {BBFEB11D-BEA3-86ED-FED1-1BB2962C2387}
Xxxxxx.xxx.xx.xx Xxxxxx.xxx.xx.xx XXXXXX "Exclude:SCANMAIL"
Working Directory:
C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 2\1004\
One or more workflows were affected by this.
Workflow name: Microsoft.SQLServer.2005.DBEngineDiscoveryRule.Server
Instance name: Xxxxxx.xxx.xx.xx
Instance ID: {BBFEB11D-BEA3-86ED-FED1-1BB2962C2387}
Management group: SCOM_1_TST
For more information, see Help and
Support
Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type:
Warning
Event Source:
Health Service Modules
Event Category:
None
Event ID:
21405
Date:
5/26/2011
Time:
3:53:01 PM
User:
N/A
Computer:
XXXXXX
Description:
The process started at
3:53: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 "DiscoverSQL2005ASDiscovery.vbs" {AAD43FAE-0F82-0499-51E1-B30B1344AF93} {BBFEB11D-BEA3-86ED-FED1-1BB2962C2387}
Xxxxxx.xxx.xx.xx Xxxxxx.xxx.xx.xx XXXXXX
Working Directory:
C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 2\1012\
One or more workflows were affected by this.
Workflow name: Microsoft.SQLServer.2005.AnalysisServicesDiscoveryRule.Server
Instance name: Xxxxxx.xxx.xx.xx
Instance ID: {BBFEB11D-BEA3-86ED-FED1-1BB2962C2387}
Management group: SCOM_1_TST
For more information, see Help and
Support
Center at http://go.microsoft.com/fwlink/events.asp.
But I have executed the script manually and it shown a message as "Starting RS discovery" but no change in the console.
Thanks, SaravThanks, Sarav
May 26th, 2011 6:07pm
Yes! 6.1.314.36 version. We have sql 2005 and 2008 mp`s
The server is not showing up in Discovered inventory in monitoirng console when targetted to SQL components.
Thanks, Sarav
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2011 6:20pm
Hi,
Check this: http://thoughtsonopsmgr.blogspot.com/2011/02/eventid-21405-process-started-at-x.html
May 27th, 2011 2:33am
Also make sure you check and define runas accounts as per the management pack guide.Bob Cornelissen - BICTT (My BICTT Blog)
Free Windows Admin Tool Kit Click here and download it now
May 27th, 2011 2:42am
I did compared this server with other SQL server that were discovered sucessfully and the DEP option is set same for both the server`s.
The local system account is having the SA privileges as like the other SQL boxes.. Yet to figure out the problem..
Thanks, SaravThanks, Sarav
May 27th, 2011 11:03am
Try running the script manually - it won't be conclusive because you cannot be the default action account - but you may see the errors then.Microsoft Corporation
Free Windows Admin Tool Kit Click here and download it now
May 27th, 2011 11:59am
I execute the script manually thorough command prompt and also directly (right click - open) it did not give me any errors!
==========Command output:=============
C:\Program Files\System Center Operations Manager 2007\Health Service State\Moni
toring Host Temporary Files 20\2734>"C:\WINDOWS\system32\cscript.exe" /nologo "D
iscoverSQL2005DBEngineDiscovery.vbs" {E71360F6-C12E-8326-4539-FBC9D78862F5} {BBF
EB11D-BEA3-86ED-FED1-1BB2962C2387} hostname.xxxx.xxx.xxx hostname.xxxx.xxx
.tst hostname "Exclude:SCANMAIL"
C:\Program Files\System Center Operations Manager 2007\Health Service State\Moni
toring Host Temporary Files 20\2734>
Thanks, Sarav
May 27th, 2011 12:22pm
You executed the SQL 2005 discovery script but the thread title and your original post refer to SQL 2008. Have you tried running the DiscoverSQL2008DBEngineDiscovery.vbs script already? Are there any errors
related to it in the event log?
Jens
Free Windows Admin Tool Kit Click here and download it now
May 27th, 2011 12:52pm
Sorry for the confusion. The subject has to be changed as 2005 sql..
I executed the script and got the same error in the eventlogsThanks, Sarav
May 27th, 2011 1:38pm