<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />
Zappl's two user-initiated features — App Installs and Self Service Updates — display prompts with error codes when encountering issues during initialisation. Users can provide these error codes to administrators for troubleshooting.
Refer to the error table below for explanations and remediation steps for each potential error code.
</aside>
Error Code | Cause | Remediation |
---|---|---|
001 | Zappl certificates could not be downloaded and added to the macOS keychain. | Verify that the Zappl ‣ have been met. Zappl needs to have access to download certificates prior to importing them to the macOS keychain. Specifically, this requires outbound network access using port 443 (HTTPS) to zappl.co . |
002 | One or more Zappl keychain components could not be accessed. | Verify the logged in user has a valid accessible keychain. If the issue persists, reinstall Zappl. |
003 | A duplicate Zappl process has hung and cannot be terminated. | Use the Activity Monitor to kill the duplicate Zappl instance. If the issue persists, restart the computer and try again. |
004 | The current version of macOS is unsupported. | Upgrade the computer to the latest version of macOS, or at least macOS 11 (Big Sur). |
005 | An internet connection could not be detected. | Connect the computer to the internet and verify that the connection is stable. If the issue persists, verify the Zappl ‣ have been met. |
006 | The Zappl server could not be reached. | Verify that the network connection is stable and that the Zappl ‣ have been met. If the issue persists, the service could be experiencing a temporary outage. |
007 | The Zappl server could not be reached whilst attempting to validate the configured license keys. | Verify that the network connection is stable and that the Zappl ‣ have been met. If the issue persists, the service could be experiencing a temporary outage. |
008 | The configured activation token is invalid. | Ensure that the activation token in your Zappl custom preferences configuration profile is valid. If you do not have your activation token, please contact us to obtain this. |
009 | The configured public key is invalid. | Ensure that the public key in your Zappl custom preferences configuration profile is valid. If you do not have your public key, please contact us to obtain this. |
010 | One or more components required by Zappl could not be updated/installed. | Verify that the network connection is stable and that the Zappl ‣ have been met. If the issue persists, the service could be experiencing a temporary outage. |
011 | The Zappl installation directory is corrupt and could not be accessed. | Reinstall Zappl. If the issue persists, please **contact us.** |
Symptom | Explanation | Remediation |
---|---|---|
The Install Zappl.zsh script fails with Error: The Zappl deployment failed because the installer script is inaccessible. Please check the Zappl network requirements and try again. |
||
The script was blocked when attempting to download the Zappl installer components from zappl.co . |
Verify that the network connection is stable and that the Zappl ‣ have been met. Specifically, this requires outbound network access using port 443 (HTTPS) to zappl.co . |
If the issue persists, the service could be experiencing a temporary outage. |
| App installation fails with Error: Not enough disk space available to download and install the *app name* update
| The app installer size is greater than the available disk space on the computer, preventing it from being downloaded. | Free up disk space on the computer. The Zappl log displays how much space is required for the particular update/install, however it is advisable to free up as much space as possible to prevent further installs/updates from failing. |
| App installation fails with Error: *app name* is not compatible with this macOS version
| The installed version of macOS does not meet the macOS requirements for the app. | Review the Zappl log to see the macOS requirement for the app.
If the installed macOS version is too far behind, upgrade the computer to the supported macOS version.
If the app can only be installed on older versions of macOS, limit installs of the app to computers which meet the required macOS criteria. |
| App installation fails with Error: The *app name* installer could not be downloaded.
| Zappl could not download the installer for the app in question. | Verify that full network access is permitted to the software vendor’s public download URLs and try again.
If the issue persists, the vendor may be experiencing a temporary outage. |
| App installation fails with
Error: Could not mount disk image for *app name*
| The disk image containing the software was successfully downloaded, but couldn’t be mounted. | Remove any disk image restrictions. Disk images can be blocked using MDM configuration profiles and other third party security tools. Blocking disk images will cause any apps with .dmg installers to fail, therefore lifting these restrictions will resolve this issue.
If no restrictions are in place, the downloaded disk image may be damaged. In this case, retry the install/update and if the issue persists please contact support. |
| Creating scheduled email reports in the Zappl portal fails with The email address is not associated with an existing Zappl user. Please create a new user and try again
| For extra security, only existing users in the Zappl portal can receive scheduled email reports. If you try to schedule an email report for an email address that is not linked to a user in the Zappl portal, this error will be seen. | Create a new user in the Zappl portal using the desired email address for the scheduled report, then try again. |
<aside> <img src="https://prod-files-secure.s3.us-west-2.amazonaws.com/103d340e-2942-4102-bf59-017fbac37c50/ca136360-be2d-4aee-bcf4-6ce5b80e1c28/zappl.png" alt="https://prod-files-secure.s3.us-west-2.amazonaws.com/103d340e-2942-4102-bf59-017fbac37c50/ca136360-be2d-4aee-bcf4-6ce5b80e1c28/zappl.png" width="40px" />
Navigation
</aside>