Cluster Server 8.0 Implementation Guide for Microsoft SQL Server - Windows
- Section I. Introducing Veritas InfoScale solutions for application high availability
- Understanding the InfoScale solutions for application high availability
- About the VCS agents for SQL Server
- How VCS monitors storage components
- How application availability is achieved in a physical environment
- How is application availability achieved in a VMware virtual environment
- Managing storage and installing the VCS agents
- Installing SQL Server
- Understanding the InfoScale solutions for application high availability
- Section II. Configuring SQL Server in a physical environment
- Overview
- Configuring the VCS cluster
- Configuring the SQL Server service group
- Configuring a SQL Server service group using the wizard
- Making SQL Server user-defined databases highly available
- Verifying the service group configuration
- Administering a SQL Server service group
- Configuring an MSDTC service group
- Configuring the standalone SQL Server
- Configuring an Active/Active cluster
- Configuring a disaster recovery setup
- Section III. Configuring SQL Server in a VMware environment
- Configuring application monitoring using the Veritas High Availability solution
- Administering application monitoring
- Administering application monitoring using the Veritas High Availability tab
- Administering application availability using Veritas High Availability dashboard
- Understanding the dashboard work area
- Section IV. Appendixes
- Appendix A. Troubleshooting
- Error and warning messages from VCS agent for SQL Server
- Troubleshooting application monitoring configuration issues
- Troubleshooting Veritas High Availability view issues
- Appendix B. Using the virtual MMC viewer
- Appendix A. Troubleshooting
Messages from the VCS agent for SQL Server Database Engine
The VCS agent for SQL Server Database Engine returns the following messages when it encounters potential or actual issues with the SQL Server service group.
Table: VCS agent for SQL Server database error messages
Message | Description |
---|---|
Failed to initialize the SQLServer agent. | The agent failed to initialize the SQLServer agent for SQL Server SQLServerVersion. |
Failed to open the SCM handle. Error = Error code. | The agent fails to get a handle to the Service Control Manager (SCM). This could occur if the specified SCM database does not exist or the requested access is denied. Solution: Verify that SCM can be run on the host. See the associated Windows error code for more information. |
Failed to open the service service name. Error = Error code. | The agent failed to open the service from the SCM. Solution: Check whether the service is present in the SCM. |
Failed to query the status of the service service name. Error = Error code. | The agent failed to query the state of the service. Solution: Check whether the service is present in the SCM. |
The service service name is not in stopped state. | The agent is trying to start the service. But the service is in an invalid state. Solution: Check the state of the service. |
Failed to set the virtual computer name in the environment of the service service name. Error = Error code. | This is a VCS internal error. Solution: Contact Veritas Technical Support. |
Failed to start the service service name. Error = Error code. | The agent failed to start the service. Solution: Verify if you can start the service from the Windows Services console. If the service starts successfully, stop the service. If the service does not start, see the associated Windows error code for more information. |
The service service name did not start within the specified time limit. | The agent failed to start the service within the time limit as specified in the SQLOnlineTimeout attribute. Solution: If the system is slow, you can modify the SQLOnlineTimeout attribute value to accommodate the time that the service takes to start. |
Failed to wait for the service service name to start. Error = Error code. | This is a VCS internal error. Solution: Contact Veritas Technical Support. |
Sql script failed. Enable DBG1 Logging for the Script output. | The SQL script failed to monitor the SQL Server instance. See the script output for more information. |
Failed to start the Sql script. (User = user name, Domain = domain name) Error = Error code. | The agent failed to execute the script for detail monitoring. See the associated Windows error code for more information. |
Sql script has failed. Error : Error code. | The SQL script for detail monitoring failed. See the associated Windows error code for more information. |
Error occurred while getting the process exit code. Error : Error code. | This is a VCS internal error. Solution: Contact Veritas Technical Support. |
WaitForSingleObject () failed. Error : Error code | This is a VCS internal error. Solution: Contact Veritas Technical Support. |
Failed to convert the argument list. Error = Error code. | This is a VCS internal error. Solution: Contact Veritas Technical Support. |
Failed to convert the password attribute to UNICODE. Error = Error code. | This is a VCS internal error. Solution: Contact Veritas Technical Support. |
Configuration mismatch: Detail monitoring is configured, but user credentials are not provided. | When configuring detail monitoring for the VCS agent for SQL Server, authentication is required for regardless of the monitoring option (database list or SQL script). Solution: Provide the appropriate user credentials to perform detail monitoring. |
Configuration mismatch: Detail monitoring is configured,but neither a list of databases to be monitored nor a SQL monitor script is provided. | When configuring the VCS agent for SQL Server, if you specify that detail monitoring should be performed, you also need to specify the method to be used. Solution: Select either the database list-based or the SQL script-based monitoring option, and provide the appropriate user credentials. |