Discovery of MSSQL Database Instances

[syddent]

I am new to discovery. Below looks like a credential issue, but I am wondering if I do not have the right problem.

I have run discovery in my environment. I find the host machine and the software that is running on that host machine. I find MSSQL Server running on the machine. However discovery does not find the instances on the MSSQL Server.

The following message shows up in the ECC queue

<?xml version="1.0" encoding="UTF-8"?><results probe_time="13108" result_code="0"><result><error>Authentication failure with the local MID server service credential.</error><error>Failed to access target system.   Please check credentials and firewall settings on the target system to ensure accessibility: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))</error></result><parameters>

If this is a credential issue, does someone have a hint on what needs to be present besides a Username and password?

Thanks

Sydney Dent

[paul971]

I'm seeing the version, port, etc in my response from the discovery but it is not being inserted to ServiceNow. It's like we received the data ServiceNow thinks it is mapping/updating but it is not actually inserting the data to the MSSQL record (we've debugged and viewed the xml to confirm). Simply not being parsed by ServiceNow though it is being discovered.. 😕 confusing

Any thoughts?

ctomasi jeremyeperdue johnandersen mark.stanger

Developer Community Architects

[Chuck Tomasi]

Any errors in the discovery log?

[paul971]

hey chuck,

no errors, no warnings.

i had to deactivate an OOB Business Rule that restricted write access to anyone, unless a member of a group that had been removed or null and then it seemed to work fine. Business Rule is : Restrict Write Access to Cmdb_ci_appl

Now its doing the same with printers. Discovery is finding it but SN is not inserting the data found on the oid (model, serial, etc) so i'm trying to figure out why

thanks ctomasi

[jeremy_perdue]

Random thought here... Is probe caching still on on your instance?

Did you get a solution on this?

Best Regards,

Jeremy Perdue, ServiceNow Consultant | Contender Solutions

[bharath10]

Hello Doug,

what if we are not doing DB Discovery/not set dedicated credentials for DB discovery.

can we get DB's running in environment, from regular discovery.(servers discovery & software install/running on it).

i can see we have DB instance(in application navigator) but there are many db instance records (with different class of DB)with blank name, not having version info, & detail of on which host/server its running.... even i can see db instance record with same name.  could you help me to understand it better.

Thanks in advance.

Bharat