Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Unable to Discover the Version Name of SQL Instance

ameertalha
Kilo Explorer

I see an issue in my Discovery results - version name of the discovered SQL instances isn't getting populated on the database instance CI form.  

When i access the XML payload in the Input record of "MSSql DB On Windows Pattern - Horizontal Discovery Probe", I see the error :

<results probe_time="4406" result_code="0">

<result>

<output>

{ "status" : "FAILED", "log" : "H4sIAAAAAAAAANVXXW/aShB9v9L9DyOekiuKDGkaYqkPFDatpUC4sdOoqiprsQdY1djO7pIERfnv\nHdv440ZuCipQ3Rewd9Y7Z86ZPV4//f0XQCPkC2yACY2BUF50j3IFl9G...........

..., "results" : { } }

</output>

</result>

I see this error on schedules that run on one specific MID Server, so could it be due to SQL Pre-reqs installed incorrectly on that MID Server? Are there any particular configurations that I should verify on the mid server ? Please navigate me in the right direction to troubleshoot this further.

3 REPLIES 3

Manjeet Singh
ServiceNow Employee
ServiceNow Employee

Hi Ameer,



There could be multiple reasons (authetication, setup..etc). Take a look at this for some possible solutions: Do we need to open port 1433 for MS SQL discovery


Thank you Manjeet. On further troubleshooting, I see the following error in the Process Detection Log:



*


2017-09-04 23:07:49: WMI query on host 10.128.108.87 authentication failure. query: Select * From Win32_Process WHERE (ProcessId = 2804) error: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))



2017-09-04 23:07:49: Failed to find process on port. Windows authentication failed on host 10.128.108.87. Verify that credentials have been correctly define. Error: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))


*



This SQL is running on a Win 2012 VM on an ESX Server. Are there any Vcenter specific requirements to discover the sql instances running on them ? Discovery is able to collect info about the ESX Hosts and VMs, but not about the SQL instances running on them. Any thoughts on this ?


Hi Ameer,



Looks like a credentials issue. From the MID Server run this PowerShell. You should get prompted for credentials.



Get-WmiObject -Query "Select * From Win32_Process WHERE (ProcessId = 2804)" -Computer <IP of MSSQL Server> -Credential <DOMAIN>\<username>