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 MSDTC
The VCS agent for MSDTC returns the following messages when it encounters potential or actual issues with the MSDTC service group.
Table: Error and warning messages about MSDTC
Message | Description |
---|---|
Lanman attribute has not been configured. | No value specified for the LanmanResName attribute. Solution: Specify a valid value for the LanmanResName attribute. |
MountResName attribute has not been configured. | No value specified for MountResName attribute. Solution: Specify a valid value for the MountResName attribute. |
LogPath attribute has not been configured. | No value specified for LogPath attribute. Solution: Specify a valid value for the MountResName attribute. |
Failed to open the SCM handle. Error = Error code. | The agent fails to get a handle to the Windows Service Control Manager (SCM). This situation 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 MSDTC service. Error = Error code. | The agent failed to open the MSDTC service from the Service Control Manager (SCM). Solution: Check whether the service is present in the Service Control Manager. |
Failed to start the MSDTC service. Error = Error code. | The agent failed to start the MSDTC service. See the associated Windows error code for more information. |
The MSDTC log path is 'path name'. Configured one is 'path name'. | The specified path for the MSDTC logs is different from the actual path. Solution: Specify the correct MSDTC log path. |
The MSDTC service is not in the RUNNING state. Offline might be unsuccessful. | The MSDTC service might be in PAUSE, PAUSE PENDING, or START PENDING state. Solution: Resume the service and then attempt to stop it. |
Failed to stop the MSDTC service. Error = Error code. | The MSDTC service cannot be stopped. See the associated Windows error code for more information. |
Failed to wait for the MSDTC service to stop. Error = Error code. | The agent cannot stop the service within the specified time limit of 20 seconds. See the associated Windows error code for more information. |