4.0.0 HP PolyServe Software for Microsoft SQL Server Administration Guide (T5392-96056, March 2010)

10 Troubleshooting
This chapter describes the following issues:
• Install/uninstall issues:
• SQL Server 2005 installation takes too long
• Installations via a Microsoft Terminal Services client
• Installer reports a failure
• Uninstall problems
• Connection issues:
• DNS misconfiguration causes Virtual SQL Server connection to fail
• Connection error with Windows authentication
• Windows authentication fails with SQL Server replication
• Client receives error when connecting via an alias
• Cannot authenticate on local machine with virtual hostname
• Error when creating a Virtual SQL Server
• An attempt to virtualize a SQL Server instance fails with the error “A member could not be added
to or removed from the local group because the member does not exist”
• Cannot access a Virtual SQL instance from the active node
• SQL Server 2005 instance does not start
• Virtualized SSAS service does not start and reports an invalid request address
• Error when creating a distributor for replication
Install/uninstall issues
SQL Server 2005 installation takes too long
Under certain circumstances, the SQL Server 2005 Setup program can take a long time to complete.
This is a known Microsoft issue. Microsoft has developed a hotfix that corrects this problem.
See the following Microsoft Knowledge Base article for more information about the problem and its
resolution. You will need to contact Microsoft to obtain the hotfix described in the article.
http://support.microsoft.com/kb/910070
If you choose to implement the workaround specified in the Microsoft article, do not use Method 1,
which disables TCP/IP. Matrix Server requires TCP/IP to function.
Installations via a Microsoft Terminal Services client
You must use an administrative console when installing SQL Server and Service Packs over a Microsoft
Terminal Services Client connection. Otherwise, the Terminal Services Client will run in application
mode, which causes the installation to fail. No information will be written to the SQL logs. To invoke
an administrative console, do the following:
HP PolyServe Software for Microsoft SQL Server administration guide 113