Tons of niZeroconfService Event errors in Windows Event Log for "Client application bug: DNSServiceResolve"

[ErikL68]

I'm seeing numerous Event Log entries in the Windows Application event log for this error:

Source: niZeroconfService

Event ID: 100

The description for Event ID 100 from source niZeroconfService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Client application bug: DNSServiceResolve(NI\032cDAQ-9188\03201A78561._ni._tcp.local.) active for over two minutes. This places considerable burden on the network.

The specified resource type cannot be found in the image file

As my system uses Ethernet cDAQs, I don't want to "place considerable burden on the network" if I can avoid it.  What can be done to fix this? Is it outside of LabVIEW?

The machine is running an app compiled under LV 2019SP1-x64 on Windows 10 Enterprise v 1809, and uses multiple cDAQ-9188 chassis.

[TeraTech]

I realize this is an old thread but there is very little on this elsewhere. I am having this issue as well. What did you do to fix it? I'm running LV 2017.

[zvacha]

Were you able to figure out what actually caused this? Anything to try to make these errors go away? Thanks!

[TeraTech]

No I have not done any additional research or taken any additional action.  Sorry.

[ErikL68]

I just checked a few machines running my app, and I'm no longer seeing many errors from niZeroconfService. Only One PC, running a few cDAQ-9189s and a few dozen cDAQ-9185s, produced these same errors as well as another error "####: ERROR: client version 0x####### daemon version 0x00000001", where the hashes characters were various (hex) numbers, and a third had nothing but service init/startup/started informational entries in the Event Log.

Fortunately, the errors that do occur are no longer nearly as frequent or often. On the PC seeing the original error, I found 20 occurring at the exact same timestamp only a few minutes after the services completed startup, then they stopped. Two weeks later, the version errors started occurring but stopped the same day, and there were only a handful occurring every 2-1/4 hours and stopping after 4 groups, with no further errors in the three weeks since.

I think I can live with this. Hopefully your case is no worse.