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
SQL Server Analysis service (MSOLAP) service fails to come online with "invalid context of address" error
The SQL Server Analysis service (MSOLAP) may fail to come online and an "invalid context of address" error may be logged in the Event Viewer.
This issue occurs if there are multiple IP addresses mapped to a single virtual server in a DNS server. In a SQL Server service group, the Lanman resource comes online in the specified virtual server name context. The OLAP resource inherits the virtual server context and communicates with the DNS server to resolve the corresponding virtual IP address. If there are multiple IP addresses mapped to a single virtual server, the DNS server may provide any of these IP addresses. If the resolved IP address is different from the one that was specified during the service group configuration, the resource faults and the service group fails to come online.
Workaround: Set the value of the DNSOption attribute of the Lanman agent to PurgeDuplicate. Doing so removes the duplicate DNS entries from the DNS servers.