3.4.3 MxDB for SQL Server Installation and Administration Guide

Chapter 4: Troubleshooting 72

• If a SQL Server 2005 uninstall fails for any other reason, check the

following article:

http://support.microsoft.com/kb/909967/en-us

Connection Issues

DNS Misconfiguration Causes Connection Failure

The following error can appear when attempting to connect a Virtual SQL

Server running locally on the cluster.

SSPI handshake failed with error code 0x8009030c while establishing

a connection with integrated security; the connection has been

closed. [CLIENT: XXX.XXX.XXX.XXX]

SQL Server connection. [CLIENT: XXX.XXX.XXX.XXX]

The error occurs because the Virtual SQL Server is not properly registered

with DNS or does not register a correct SPN in the domain.

Domain Name Service (DNS) is the backbone of Active Directory (AD)

and the primary name resolution mechanism for Windows. If DNS is not

configured correctly, Windows authentication may fail.

To verify that DNS is correctly configured for the Virtual SQL Server,

ensure that the following tests are successful.

1. Ping the Virtual SQL Server. For example:

C:\>ping vqar13s11

Pinging vqar13s11.ad1.polyserve.com [99.11.13.181] with 32 bytes of

data:

Reply from 99.11.13.181: bytes=32 time<1ms TTL=128

Ping statistics for 99.11.13.181:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

NOTE: If the ping fails, make sure an [A] record is created in DNS for the

hostname.