Your next step is the right one: this is typically caused by something modifying UEM's zip files. Although UEM profile archives can be extracted by any standard ZIP tool, UEM won't accept files that have been created or modified by such tools. That [FATAL] Error reading archive message is logged when the profile archive is not a "UEM zip". Are there any [DEBUG] Reader::OAVA: ... messages immediately preceding that FATAL error?
There is a hidden feature that prevents the export of a particular profile archive if the corresponding import failed:
It's hidden for the reason that I highlighted, but let me know if you'd like to try it, and I can send you the ADMX template for that particular setting. But, just to be very clear: that would at best be a stopgap measure; it's important to find the root cause for this.
Could you send me the admx files with this hidden feature so i can try it please.
Besides this we are still monitoring our antivirus, i hope we will have found the root cause very soon.
Thanks in advance.
I've attached the ADMX template with which you can enable this hidden Prevent export for failed import setting.
I do want to stress again (also for others who might find this post later on) that this really intended for transient import failures. If a profile archive is corrupted, it will need to be manually reset or restored for import and export to work properly again (as the policy setting's help text also indicates.)
Hi ElroyS ,
Did you manage to identify what caused corruption to your flex files? I had the same issue today for a user. I can see the error in the log files;
- 2019-07-22 09:05:50.786 [DEBUG] Reader::OAVA: Couldn't open archive
2019-07-22 09:05:50.786 [FATAL] Error reading archive
But have no idea what application could have caused the issue with the archive files. The issue is for all flex files for 1 user only.