MSSQL Discovery Troubleshooting Help

[tgoodhew]

We are working on rolling out Discovery. I'm working with our MSSQL admin to get the permissions setup so the powershell probe will work. I have everything set to use Windows Integrated Security...at least I think I do.

When we run the probe against the MSSQL server we get the below error message. We haven't been able to figure out the cause. Is this a permissions issue in MSSQL or something else?

I've been trying to review the probes and understand how the connection to MSSQL is made, but I haven't bee successful in this case. Still lost.

Error:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)

[rkmullis]

I ran into the same issue when we first rolled out Discovery. This may help:

- Make sure you're using the MID server (domain / domain admin) credentials

- Set the following config.xml parameter accordingly:

This parameter becomes obsolete in Calgary: https://wiki.servicenow.com/index.php?title=PowerShell_for_Discovery

[tgoodhew]

no joy on that.

I am using the MID server creds in the domain\ID format. The ID does have local admin on the Windows box (all the windows probes work fine).
I do have the properties set "true" for mid.proxy.password, mid.powershell.use_credentials (should not need this is true is the default).

I did try your suggestion of explcitly setting mid.powershell.use_mssqlauth to false.

Does it make a difference if the server is a cluster instead of a stand alone?

[rkmullis]

What do the SQL logs say on the server(s) in question?

[tgoodhew]

Good question on the MSSQL logs.

I'll get with the DBA to find out.

On a side note, I opened an Incident in HI for this issue. The first question they asked me was if this was a clustered SQL instance or stand alone. It is clustered.

They indicated Dev is aware of an issue with Discovery not properly detecting MSSQL instances and a fix might come out for Calgary or in Dublin.

I'm checking with out DBA to see if we have any stand alone instances to test against to rule in/out the Cluster issue.