Cluster Server 8.0 Bundled Agents Reference Guide - Windows
- Introducing VCS bundled agents
- Storage agents
- Network agents
- FileShare agents
- Services and applications agents
- VCS infrastructure and support agents
- VCS hardware replication agent for NetApp
- Troubleshooting bundled agents
ServiceMonitor agent error messages
No value specified for the ServiceorScriptName attribute.
Recommended Action: Verify the ServiceorScriptName attribute defined in the configuration file is assigned a value.
The agent failed to obtain the SID for the specified user.
Recommended Action: Verify that the domain controller is accessible, or the specified user exists. See the error code if the problem persists.
No value specified for the Password attribute.
Recommended Action: Verify the Password attribute defined in the configuration file is assigned a value and contains alphabets only.
The agent failed to decrypt the specified password.
Recommended Action: Verify that the password is encrypted using the VCS Encrypt utility (described in the Cluster Server Administrator's Guide).
The agent failed to convert the password attribute. This is a VCS internal error.
Recommended Action: Offline and online the service group. Contact Veritas Technical Support if the problem persists.
The agent failed to obtain the SCM handle. This occurs if the SCM database does not exist, or if the SCM manager denies the requested access.
Recommended Action: Verify that SCM can be run on the host.
The resource definition in the configuration file contains an invalid, or incorrect service name.
Recommended Action: Verify that the ServiceOrScriptName defined in the configuration file is the same as the display name used by SCM. Also verify that the specified service is supported by the SCM version on the host and that the specified service was opened successfully.
The agent failed to determine the status of the service. This is a VCS internal error.
Recommended Action: Verify that the attribute ServiceOrScriptName defined in the configuration file is the same as the display name used by SCM. Otherwise, offline and online the service group. Contact Veritas Technical Support if the problem persists.
The agent failed to offline the service because the service is not in STARTED state.
Recommended Action: Verify the state of the service and re-issue the online command.
The agent failed to obtain the information about the user in whose context, the specified service will run.
Recommended Action: Verify that the user exists, or the domain controller is accessible. See the error code if the problem persists.
The agent failed to obtain the SID for the specified user.
Recommended Action: Verify that the domain controller is accessible, or the specified user exists. See the error code if the problem persists.
The user information specified in the UserAccount information is different from the user information, in whose context the service will run.
Recommended Action: Stop the service and modify the user information. Re-issue the online command.
The agent failed to launch the script to monitor the service.
Recommended Action: Verify that the script is accessible. See the Windows error code if the problem persists.
The agent failed to receive a response from the monitor script.
Recommended Action: Review the configuration definition of the attribute MonitorProgTimeout. Increase its value if required.
The agent failed to terminate the script specified in the MonitorService attribute.
Recommended Action: Stop the agent. See the Windows error code, if the problem persists.
The agent failed to get a response from the script that monitors a specified service.
Recommended Action: Verify that the exit codes returned by the script conform to VCS standards. See the Windows error code for further information. Contact Veritas Technical Support if the problem persists.
The agent failed to enable the privilege required to kill a process. See the Windows error code for further information.
The resource definition in the configuration file contains an invalid or incorrect service name.
Recommended Action: Verify that the attribute ServiceOrScriptName defined in the configuration file is the same as the display name used by SCM. Also verify that the specified service is supported by the SCM version on the host.