Why are Discovery jobs not completing?

[Dave Hoglund]

They seem to still be processing the HorizontalDiscoveryProbe - Pattern Launcher: MSSql DB On Windows
I noticed in the payload, there is a "credAffinity" which is pointing to 1 MID Server, but not the MID Server used for this discovery.    Should I delete that credential affinity from the other MID?

Also, I see the HorizontalDiscoveryProbe - Pattern Launcher: Windows OS - Servers  seems to show the "Probe processing time" is quite long.

[kaushal_snow]

@Dave Hoglund ,

The presence of a credAffinity pointing to a MID Server not associated with this discovery suggests a potential misconfiguration in credential assignments, which could lead to authentication failures or delays in probe execution. To address this, it's advisable to review and adjust the credential assignments to ensure that the correct MID Server is utilized for the respective discovery tasks...

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.

[vignesh parthib]

Hi @Dave Hoglund ,

Based on your issue, First validate your credential configured for particular class, Discovery > Credentials > run credential test with same MID Server which is causing problem and verify Discovery log

 "Probe processing time" is quite long - Some time related credential failure also

Then Try same step using Actual working MID Server and verify log  to determine exact cause of issue

Thanks,
Vignesh
"If this solution resolves your issue, kindly mark it as correct."

[srinija_itom]

Hi @Dave Hoglund , 

Can you try running quick discovery on single windows server? Are you still observing the slowness in the discovery. 

Possible Root Causes

Target systems respond slowly to WMI queries

If the MID is in a different subnet or region

MID overloaded or too many concurrent discoveries

Regards, 

Srinija

[Harish Bainsla]

Hi @Dave Hoglund please check credentials and run a quick discovery to that IP 

A long probe processing time can be due to many reason like

• Network latency
• MID Server performance 
• Large number of processes
• Credential issues 

if my answer helps you mark helpful and accept solution