This article includes some errors that may occur.
- I am unable to install SystemWeaver as a Windows service.
- The service has been started, but it stops unexpectedly.
- I am unable to access the Server Monitor Service Status Tool.
- I am unable to install the Server Monitor Service.
- I am unable to start the Server Monitor Service.
I am unable to install SystemWeaver as a Windows service.
Error message
Access is denied.
Resolution
To avoid the problem, use the Run as administrator option in Windows when you do the installation.
The service has been started, but it stops unexpectedly.
Error message
"Error 1067 The process terminated unexpectedly."
Resolution
This message can appear if the services do not have write access to the directories where the log files are created. SystemWeaver services are normally set to log on as "Local System". Check file locations and access rights to assure the Local System has all the necessary rights.
I am unable to access the Server Monitor Service Status Tool.
Error message
An error has occurred.
There was no endpoint listening at http://localhost:xxxx/ServerMonitor that could accept the message.
Resolution
Check to make sure that the SystemWeaver Server Monitor Service is running under Services. It must be running to be able to access the Status Tool.
I am unable to install the Server Monitor Service.
Error message
The type initializer for '' threw an exception. This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
Resolution
The error is an indication that FipsAlgorithmPolicy is enabled on the server. FIPS stands for “Federal Information Processing Standards.” It's a set of government standards that define how certain things are used in the government. Disabling it will resolve the problem.
I am unable to start the Server Monitor Service.
Error message
The SystemWeaver Server Monitor 2 service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other service or programs.
Resolution
Check to see if you have a special character in any of the paths in the swServerMonitorService.settings file. Special characters must be expressed using character entity references.
Example:
<exe>D:\SystemWeaver\Server & notificationServer\swDBServer.exe</exe>
must be written as:
<exe>D:\SystemWeaver\Server & notificationServer\swDBServer.exe</exe>