Client Service Monitoring Errors

Client service monitoring is not enabled after changes to the ServiceMonitorConfig.xml. We can ensure if client service is enabled by checking in the log file for this message:

Info:- AVEVA Work Tasks Services Monitoring. Monitoring is enabled: "".

This message is logged every 10 minutes. This could be due to an invalid syntax in ServiceMonitorConfig.xml. Open the file in XML editor and ensure all syntaxes are proper. Ensure that changes made are not commented.

Client service configuration file changes are not getting reflected. After making changes to ServiceMonitorConfig.xml, ensure the Client service is restarted. After the client service is restarted, it re-caches the configuration changes and all the changes will be considered.

Client service is not able to start a AVEVA Work Tasks service. In some situations, client service may not be able to start a service. It will continue to restart the service and send restart failure emails. One of the reasons could be that the database server is down or is not getting connected to the windows services.

Client service is restarting the remaining AVEVA Work Tasks windows services continuously in regular interval and sending the emails. Ensure that all services are able to connect to the database and the database is up. Other reason could be due to thread hanging behavior of WFEngine. See Workflow Engine for more information.

In Service Monitoring, if the thread hanging or locking behavior is not getting monitored, then there are chances that cached variable value is zero. This can happen, if the database server is down while reading the data from the database. Restart the client service which will read data once again and recreate the cache.