Discovery takes long time to complete on Windows Servers

[amolpunekotwal]

Hello Experts,

We have some windows servers where discovery takes 7-8 hrs to complete. Only error I see in the pattern logs are about SQL Server Cluster commands failing as below. Interestingly if we run discovery from different mid server with same ip it gets completed within 5 minutes.  What could be difference between these 2 mids? Network path? Any configuration setting which we needs to validate?

Also even if we some command does not work why it takes so much time declare it failure? As i see most of the commands has 300 seconds timeout value.

We are unable to find out the root cause of this. Please let us know if anyone has experienced the same issue and shed some light.

2024-02-29 23:28:45: Executing WMI query on host: removed original ip with namespace: root/Microsoft/SqlServer and query: SELECT Name FROM __NAMESPACE

2024-02-29 23:28:47: Error during execution of Windows command: executeQuery -Namespace root/Microsoft/SqlServer -Query "SELECT Name FROM __NAMESPACE" due to com.snc.automation_common.integration.exceptions.InvalidCommandException: executeQuery : Could not get query SELECT Name FROM __NAMESPACE on namespace=root/Microsoft/SqlServer. Original Exception: Invalid namespace

At line:1 char:5

+ & { executeQuery -Namespace root/Microsoft/SqlServer -Query "SELECT N ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException

+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,executeQuery

2024-02-29 23:28:47: Execution time: 2899 ms

Thanks & Regards,
Amol Kotwal

[Sandeep _]

Hi @amolpunekotwal ,

I hope this article helps you: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0816039

If I could help you with your Query then, please hit the Thumb Icon and mark as Correct !!
Sandeep

[amolpunekotwal]

Thank you @Sandeep _ for you prompt response, however we are getting error within Windows Server-OS pattern itself within collect MSSQL info section. Also I checked the suggested MSSQL DB pattern which has the updated steps as you mentioned.

Thanks & Regards,
Amol Kotwal

[Mateus Oliveira]

I have the same issue and yet could not find a solution for it. Were you able to work it around somehow?

[Mvakazi]

Hi @amolpunekotwal 

Did you ever get a solution to this issue. I have a similar issue.

Regards,

Mvakazi