2.1 General Error Messages
The policy_name could not be enforced because it contains invalid keys
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Critical
Possible Cause:
Some other application might have locked the settings that are defined in the policy they cannot be written to GConf.
Action:
Ask the user to login again to the managed device.
The policy_name could not be enforced because few keys defined in the policy could not be cleared appropriately before enforcement
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Critical
Possible Cause:
Some other application might have locked the settings that are defined in the policy. They could not be removed from GConf.
Action:
Ask the user to log in again to the managed device.
The policy_name could not be enforced because the format of the policy data was invalid
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Critical
Possible Cause:
The policy details were corrupted while retrieving or applying it.
Action:
Perform the following:
-
To refresh the policy details, run the following command from the command line:
/opt/novell/zenworks/bin/rug refresh
-
If the policy is not enforced, stop zmd by running the following command from the command line:
/etc/init.d/novell-zmd stop
-
Remove the policy cache files from /var/opt/novell/zenworks/cache/zmd/PolicyManager/policies.xml.
-
Start zmd by running the following command from the command line:
/etc/init.d/novell-zmd start
-
Ask the user to log in again to the managed device.
The policy_name could not be enforced because the user specified was invalid
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Critical
Possible Cause:
The user's login entry for device does not exist in the /etc/passwd file.
Action:
Make sure that the user's entry exists in the /etc/passwd file.
Possible Cause:
An internal error occurred while applying the policy.
Action:
Perform the following:
-
Restart zmd by running the following command from the command line:
/etc/init.d/novell-zmd restart
-
Ask the user to log in again to the managed device.
The policy_name could not be enforced because the username has not been specified in the policy
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Critical
Possible Cause:
An internal error occurred while applying the policy.
Action:
Perform the following:
-
Restart zmd by running the following command from the command line:
/etc/init.d/novell-zmd restart
-
Ask the user to login again to the managed device.
The GConfEnforcer could not find any settings to read from the device
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Critical
Possible Cause:
The default schema files of GConf are corrupted or not valid.
Action:
Ensure that the default schema files of GConf are valid.
Possible Cause:
You might not have configured any specific GConf values for the user.
The GConfEnforcer could not read the requested settings from the device for the specified user
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Critical
Possible Cause:
The user's entry does not exist in the /etc/passwd file.
Action:
Make sure that the user's entry exists in the /etc/passwd file.
The settings made by the policy_name enforcers could not be cleared completely. Settings made by policies of this type might still be in effect on the device
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Critical
Possible Cause:
Some other application might have locked the settings that are defined in the policy, so cannot be removed from GConf.
Action:
Perform the following:
-
Ask the user to log in again to the managed device.
-
Clear the policy enforcement again on the managed device.
The policy_name could not be enforced because there was an error in setting or unsetting the values into the configuration source
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Critical
Possible Cause:
The home directory of a user who has logged in to the managed device does not exist in the /etc/passwd file.
Action:
Ensure that a valid home directory is specified for a user on the managed device in the /etc/passwd.
Possible Cause:
Root has insufficient rights to access the home directory of a user on the managed device.
Action:
Ensure that root has sufficient rights to access the home directory.
Possible Cause:
Some other application might have locked the settings that are defined in the policy, so they cannot be written to GConf.
Action:
Ask the user to log in again to the managed device.
The read settings operation could not be performed by the enforcer GConf Enforcer because there was an error in reading from the configuration source
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Critical
Possible Cause:
The home directory of a user whose settings are being retrieved from the managed device does not exist in the /etc/passwd file.
Action:
Ensure that a valid home directory is specified for a user on the managed device in /etc/passwd file.
Possible Cause:
The user does not have sufficient rights to access the directory from the ZENworks Management Daemon.
Action:
Ensure that the user has sufficient rights to access the ZENworks Management Daemon.
Possible Cause:
Some other application might have locked the settings that are defined in the policy, so they cannot be written to GConf.
Action:
Retry importing the settings.
The enforcement of policy_name was unsuccessful and the application is not installed/compatible. The version of name of the application should be >= minimum required version
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Critical
Possible Cause:
The application (Firefox*, Epiphany*, or EvolutionTM) is not installed or the specified version is earlier than the minimum supported version.
Action:
Upgrade the application to the minimum required version and try enforcing the policy again.
The enforcement of name of the policy was unsuccessful and the operating system distribution is not compatible. The distribution should be >= distribution required version. Only some keys might be enforced
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Critical
Possible Cause:
The distribution or version of the operating system is not compatible with the policy you are trying to enforce.
Action:
Associate the policy to a device with the required distribution and version of the operating system.
The policy_name will not be enforced because the name of the application is not installed
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Critical
Possible Cause:
The policy might be associated to a device that does not have the application installed.
Action:
Install the required application.
The policy_name will not be enforced because the operating system is not required distribution version or higher
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Critical
Possible Cause:
The Novell Linux Desktop policy or the SUSE Linux Enterprise Desktop policy is associated to a device that does not have Novell Linux Desktop or SUSE Linux Enterprise Desktop operating system respectively.
Action:
Associate the Novell Linux Desktop policy only to devices having Novell Linux Desktop operating system installed, and the SUSE Linux Enterprise Desktop policy only to the devices having the SUS Linux Enterprise Desktop operating system installed.
The policy_name was requested to be enforced, however, it is already executing, therefore, we will not start it again.
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Important
Explanation:
If two or more users are logging into the device at the same time, the policy enforcement might not have finished for the first user before it started for the other user. The specified policy is not enforced for users other than the first user.
Possible Cause:
Two or more users have logged in to the device at the same time.
Action:
The users after the first user should login again for the policies to take effect.
Possible Cause:
One of the policies is taking a long time.
Action:
For Text File and Remote Execute policies, review any scripts/programs specified in the policy to see if they could take excessive time. Correct those situations to reduce the amount of time and try enforcing the policy again. For GConf-based policies, do not include any settings in the policy that are not relevant to you. If the policy data is correct, then restart ZMD and enforce the policy again.
Possible Cause:
The time interval for enforcing the policy is too small compared to the amount of time it takes to enforce the policy.
Action:
Increase the time interval.
-
In the ZENworks Control Center, click .
-
Click any Remote Execute or Text File policy for which you want to increase the time interval.
-
On the page, click in section.
-
In the dialog box, increase the time interval you have specified in , option.
Rescheduling the enforcement of name of the policy for 2 minutes later, because its type is not re-entrant and another policy of this type is already executing.
Source:
ZENworks Linux Management; Policy Handlers
Severity:
Important
Possible Cause:
A read settings request was made to the managed device while a user was trying to login.
Action:
Ask the user to login again to the managed device.
Possible Cause:
There is an internal error.
Action:
Restart ZMD and ask the user to login again to the managed device.
The enforcer executable, enforcer_name, could not be located
Source:
ZENworks Linux Management; Policy Handlers
Explanation:
The Policy Manger logs the error message in the ZENworks Control Center when you log into a managed device that does not have the GConf binaries installed.
Possible Cause:
The ZENworks Agent is installed with the -x option on the managed device that does not have GConf binaries installed.
Possible Cause:
The ZENworks Agent installation is corrupted.
Action:
If the error message is displayed when a GConf based policy is assigned, do one of the following:
-
To apply the GConf based policy, reinstall the ZENworks Agent without -x option.
-
Remove the assignment between the policy and the device that does not have the Gconf binaries installed.
Action:
If the error message is displayed when a GConf based policy is not assigned, ignore the message and acknowledge it in ZENworks Control Center.