Error codes for GravityZone Patch Management
The GravityZone Control Center displays relevant error messages after Patch Management tasks fail on endpoints.
Here are listed the most common error codes and messages related to Linux and macOS endpoints.
Linux error codes
The endpoint received a policy with invalid data. [13] | |
|---|---|
Description | This error occurs when the GravityZone policy contains valid parameters and fields, but they are listing incorrect data. |
Solution | Check the policy settings and make sure that they are applied to the target endpoint. Check your settings and make sure the target endpoint is supported, according to the requirements listed here. |
The endpoint agent is not ready. [21] | |
|---|---|
Description | This error occurs when the Patch Management module failed to initialize on the endpoint due to internal issues. Patch Management also cannot initialize on unsupported Linux distributions. |
Solution | Make sure that the target endpoint is able to receive the policy. Check your settings and make sure the target endpoint is supported, according to the requirements listed here. |
The endpoint received a policy with invalid parameters. [87] | |
|---|---|
Description | This error occurs when the GravityZone policy contains invalid parameters such as different type expected, missing fields, unknown patch type, and invalid patch identifiers. |
Solution | Check your settings and make sure the target endpoint is supported, according to the requirements listed here. |
The endpoint agent could not access the Patch Management module. [126] | |
|---|---|
Description | This error occurs when Bitdefender Endpoint Security Tools for Linux was unable to access the Patch Management module to handle the Patch Scan and Patch Install task settings. |
Solution | Check your settings and make sure the target endpoint is supported, according to the requirements listed here. |
Patch Install task stopped due to internal issues. [995] | |
|---|---|
Description | This error occurs in the following circumstances:
The automatic patch installation handles this error through a scheduler and any errors would only be visible in the debug logs. |
Solution | Check your settings and make sure the target endpoint is supported, according to the requirements listed here. |
Patch Scan task is already running. [1247] | |
|---|---|
Description | This error occurs when you trigger in GravityZone a manual patch scan while another scan task (manual or scheduled) is running. |
Solution | Please wait until the current task is completed. |
The endpoint received a deprecated policy. [1150] | |
|---|---|
Description | This error occurs when the endpoint receives a policy with deprecated settings for Patch Scan and Patch Install tasks. |
Solution | Check the policy settings and make sure that they are applied to the target endpoint. Check your settings and make sure the target endpoint is supported, according to the requirements listed here. |
Task failed! The target company must have a valid license key for Patch Management. [7056] | |
|---|---|
Description | This error occurs when a Patch Scan and Patch Install task has been manually executed by the user or automatically by GravityZone through a maintenance window and the company does not have a license with Patch Management. |
Solution | Make sure you apply the policy to a different company or provide the target company with a license that includes Patch Management. |
Policy name or action not supported. [2147942450] | |
|---|---|
Description | This error occurs when the GravityZone policy name is not listed in the endpoint configuration files or when the action provided is different from install. |
Solution | Make sure that the policy is applied to the target endpoint. Check your settings and make sure the target endpoint is supported, according to the requirements listed here. |
macOS error codes
Task failed! The endpoint received a policy with invalid data. [1] | |
|---|---|
Description | This error occurs when the GravityZone policy contains valid parameters and fields, but they are listing incorrect data. |
Solution | Check the policy settings and make sure that they are applied to the target endpoint. Check your settings and make sure the target endpoint is supported, according to the requirements listed here. |
Task failed! An internal error has occurred. Run the task again on this endpoint. If the issue persists, contact your system administrator. [2] | |
|---|---|
Description | This is a generic error message that may indicate a temporary internal issue with the GravityZone platform or the endpoint. |
Solution | Try to run the task again on the affected endpoint. If the issue persists, contact your system administrator. |
Task failed! Bitdefender requires Full Disk Access on the target endpoint. [3] | |
|---|---|
Description | This error occurs when Bitdefender Endpoint Security Tools components do not have Full Disk Access permissions on the target macOS endpoint. |
Solution | You as an admin or the local user must allow Full Disk Access for Bitdefender Endpoint Security Tools components. For details, refer to Full Disk Access is not granted for Bitdefender Endpoint Security Tools in macOS. If you use a mobile device management solution like Jamf Pro, you can allow Full Disk Access in the configuration profile. For details, refer to Configuring Jamf Pro to deploy BEST on macOS Big Sur 11.0 or later. |
Task failed! The endpoint received a policy with invalid parameters. [160] | |
|---|---|
Description | This error occurs when the GravityZone policy contains invalid parameters such as different type expected, missing fields, unknown patch type, and invalid patch identifiers. |
Solution | Check your settings and make sure the target endpoint is supported, according to the requirements listed here. |
Task failed! The target company must have a valid license key for Patch Management. [7056] | |
|---|---|
Description | This error occurs when a Patch Scan and Patch Install task has been manually executed by the user or automatically by GravityZone through a maintenance window and the company does not have a license with Patch Management. |
Solution | Make sure you apply the policy to a different company or provide the target company with a license that includes Patch Management. |