The casa_atsd service on a Linux server fails to start
Source:
ZENworks 11 ; ZENworks Server
Explanation:
On a Linux server, if you choose to manually start the casa_atsd service that is in the unused state, the service fails to start.
Action:
If the casaatsd.pid file exists within the /var/lib/CASA/authtoken/svc/ directory, delete the file and then restart the service.
Unable to start the ZENworks Services on a Windows Primary Server
Source:
ZENworks 11; ZENworks Server
Explanation:
After you reboot or restart a Windows Primary Server, the ZENworks Services fail to start. If you choose to manually start the services, the following error message is displayed: Error 1609: The service did not start due to a logon failure.
Possible Cause:
A group policy setting, applied on the server, has revoked the log on as a service right for the specified user account.
NOTE:Most of the ZENworks Services run as a privileged user account. This account can be identified based on the following naming convention: __z_x_y__ , where x and y are the last two digits of the IP address of the server, added at the time of installation.
Action 1 (Mandatory):
Configure the applied group policy setting to add the user account to the list of accounts that possess the log on as a service right.
Action 2 (Optional):
If the ZENworks Services do not start after performing Action 1, perform the following steps:
-
Start the Local Security Settings MMC snap-in.
-
Expand , and then click .
-
In the right pane, right-click , and then click .
-
Add the user to the policy, and then click .
-
Close the Local Security Settings MMC snap-in.
Cannot control the size of the directory that contains the failed status messages collected by the server
Source:
ZENworks 11; ZENworks Server
Explanation:
As there is no way to control the size of the directory that contains all failed status messages, when the directory size becomes very large, there is a possibility that servers might crash.
Action:
To allow the cleanup of all the failed status messages collected in the collection\status\failed folder, based on a specified size, the max-failed-folder-size setting needs to be added in the statusstorer.xml file, on the Primary Server. For example, to set the size limit to 15 MB, add the following line in statusstorer.xml file: <Parameter Name="max-failed-folder size">15728640</Parameter>
The statusstorer.xml file can be accessed from the following location:
If the max-failed-folder-size setting is not added, the default size (in bytes) for the failed folder is set as 10MB.
When you set the max-failed-folder-size value to 0, the failed status messages are not stored.
After you make any changes to the configuration file, you need to restart the ZENworks Loader service.