The "archiveType unknown" error may appear in the Events Log during patch application attempts for FileZilla. This article outlines steps to troubleshoot and resolve this issue.
Error Context
This error occurs when a patch policy encounters issues related to downloading, extracting, or applying updates. Possible causes include:
- Firewall restrictions blocking patch downloads.
- Inadequate permissions to create temporary folders.
- Software conflicts with security or monitoring tools like Netskope.
Steps to Resolution
Step 1: Ensure Allowlisting Rules Are Configured
Ensure that Automox services and domains are properly allowlisted. Refer to the Agent Firewall Allowlisting Rules for detailed instructions.
Step 2: Verify Temporary Folder Access
Ensure that the Automox agent can create a temp folder:
- Windows: C:\ProgramData\amagent\
- macOS: /Library/Application Support/Automox/
If access is restricted, adjust permissions accordingly.
Step 3: Check for Security Software Conflicts
Some users reported success by disabling Netskope. If you use similar monitoring or security tools, consider temporarily disabling them or adding Automox processes to an allowlist.
Step 4: Review Logs for Additional Clues
Examine Automox agent logs to identify specific issues during patch application. Locate the logs in:
- Windows: C:\ProgramData\amagent\
- macOS/Linux: /var/log/automox/
Search for entries related to FileZilla or archiveType unknown.
Additional Notes
- If these steps do not resolve the issue, collect logs and device details, and contact Automox support.
- Include information such as the affected patch policy, error screenshots, and software versions in your support ticket.