Discovery: failure count is 3 and allowable failures is 2

[Johan13]

Hi,

We are getting the following error after an upgrade to Yokohama Patch 7 and to Discovery and Service Mapping patterns version 1.28.0.

 Windows command failure count is 3 and allowable failures is 2. Exiting pattern execution.

It is the Windows server pattern that fails, on section:

• 38.1 "Hyper-V - Virtual Machines",
• step 14; "Get virtual logical disks data from Msvm_LogicalDisk".

Can we adjust the allowable failures in any way? Any other workaround?

BR, /Johan

[Community Alums]

Hi @Johan13, 

This error is expected behavior with the "Windows Server" pattern version 1.28.0 and is not indicative of a critical failure. The pattern logs this message when it does not find any Hyper-V logical disks on the discovered Windows Server. Rather than being an issue, the pattern is designed to exit the "Hyper-V - Virtual Machines" section and continue with the remainder of the discovery process.

Therefore, no adjustment to the allowable failures is necessary, and no workaround is required as the pattern execution is not halted.

Hope this helps!

Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution and helpful so others can benefit as well.

[Johan13]

That's actually not what happens.
As the log says: "Exiting pattern execution" is what actually happens.

There is a problem PRB1843022 fixed in YokohamaP1, this PRB regards snmp, however, very closely related.

[Johan13 · Accepted solution]

Found it and solved it:
We have set the "mid.sa.windows.allowable_failures", set it to -1 to get the same behaviour as before.

See the MID Server properties.
You set this on the mid server, tab Properties.
BR, /Johan

[venkataramac]

Hi @Johan13 ,

The property should be added to Single Mid Server or all the Mid server which will be used for Discovery. 

If yes, How can this will be added to all the Mid Servers.

Thanks