What SR #?  Feel free to email me that directly if you prefer...

I don't see any tickets open with Dev over this issue.....I too would be curious about the "next update" claim.

Now I have seen some agent errors when returning from sleep state that auto-correct, cause by the fact the agent tries before the networking comes back fully.  If you are seeing continual errors throughout the day, that would be something new to me.

If see you posted earlier here....

https://community.microfocus.com/collaboration/zenworks/esm/f/endpoint/510304/antimalware-cloud-services/1888615#1888615

I still can't help wonder if you are having issues between the PC and the local listener.   Internal Communications can be blocked via FW or other items.  

SR was 01914191

So it was indeed the one item I noted where "Exit 3" is causing the error.  The 'Fix' will be to mark that as debug info so it does not flow up.

It is flagged for the next release in U3, but that is a LONG way off.

Does the Error happen if both Windows and the AV Client are set to English?  As I recall your Devices are set to a Language for which the AV agent is localized but for which ZCM is not.  

Does it happen repeatedly, or perhaps just during install?  Clearly, if it happens daily on all your devices, it could trouble your users greatly and you may be able to request some test file to prevent it, while if it happens just once you can likely tell your users to ignore it.

Also verify there is no functionality lost beyond the error.

Hi Craig, 

customer is getting this errors daily on every workstation , which has ZAV enabled. I can test setting the UI to English, but we need fix for this error, English UI is not acceptable.

Craig can I get the fix ?

Edited ....

Fix is NOT in FTF 995

Where is this FTF? I checked under the SLD site, and it says that 995 has been superseded. It appears that 997 is now the version but I cannot locate that. Any assistance would be great. 

Apply the Log4J Server side patches and you will get 997.

Is not fixed even in FTF997, getting still ZavListener errors.

Any news on a fix? 

I have the same problems on a clean install and latest version just with a different error number:

No, I have opened SR for it, last message I got was at January 7 "Is still pending development." ...

No, I have opened SR for it, last message I got was at January 7 "Is still pending development." ...

This is flagged for 20.3, which is about to enter Beta.

This occurs when the OEM ZAV is set to a language supported by the OEM Anti-Malware Agent but not supported by ZENworks.  Beyond the error generated by the unexpected condition (which makes tracking other issues hard), there is not any functional impact.

Yes Craig, but it generates thousends of error messages daily, which renders monitoring useless, Every device is in error state. I was hopping to get fix much quicker.