To obtain SQL Server 2005 SP2, visit the following Microsoft Web site:
Problem 1You specify a named instance when you install a SQL Server 2005 failover cluster. You have a client computer that is running Windows Vista or Windows Server 2008. However, you cannot connect to the named instance from the client computer.
Problem 2After you install a SQL Server 2005 failover cluster, you cannot find SQL Server cluster resources in Failover Cluster Manager.
Problem 3After you install SQL Server 2005, the full-text search service cannot start.
Problem 4When you install SQL Server 2005 on a Read-Only Domain Controller (RODC), you receive the following error message:
Problem 5When you install SQL Server 2005 on a Windows Server 2008 failover cluster, you receive the following error message:
Problem 6Consider a scenario in which you have an existing SQL Server 2005 clustered instance, and you try to perform any of the following operations by using setup.exe:
- Edition upgrade
- Change server collation
- Rebuild system databases
The setup has encountered an unexpected error while Completing Commit. The error is: The cluster resource cannot be made dependent on the specified resource because it is already dependent.
Cause of Problem 2In the new Windows Server 2008 cluster, all physical disks that can be clustered exist in the Available Storage group until they are used by an application. After you install a SQL Server 2005 failover cluster by using the default disk group, SQL Server cluster resources are located in the Available Storage group. However, the Available Storage group is not visible in Failover Cluster Manager.
Cause of Problem 3This problem occurs because the NTLM Security Support Provider (NTLMSSP) service does not exist on Windows Server 2008. However, the full-text search service depends on the NTLMSSP service.
Cause of Problem 4On a domain controller, the Local Users and Groups tool is not available. Applications that directly run on a domain controller create users or groups in the User object in the Domain class. When you install SQL Server 2005, the SQL Server 2005 Setup program must create additional groups. However, you do not have the write permission on a RODC. Therefore, the SQL Server 2005 Setup program cannot create these groups.
For more information about RODCs, visit the following Microsoft Web site:
Cause of Problem 5The cause of this problem is the same as the cause of Problem 3.
Cause of Problem 6There is a known compatibility issue with SQL 2005 Setup and Windows Server 2008 Failover cluster. Setup tries to add the network name or the shared disk as a dependency to the SQL Server resource, and this fails because the dependency already exists.
Workaround for Problem 1To work around this problem, follow these steps:
- If you use the TCP/IP protocol to connect to the named instance, specify the TCP port number in the connection string.
If you use the named pipe protocol to connect to the named instance, specify the name of pipe in the connection string.
For more information about how to create a connection string by using the TCP/IP protocol, visit the following Microsoft Developer Network (MSDN) Web site:
- On the client computer, use one of the following methods:
- Method 1
In Windows Firewall with Advanced Security, enable incoming traffic to the program that you use to connect to the named instance.
- Method 2
In Windows Firewall with Advanced Security, enable inbound traffic from all possible IP addresses of the SQL Server 2005 failover cluster.
- Method 1
Workaround for Problem 2For information about how to work around Problem 2, click the following article number to view the article in the Microsoft Knowledge Base:
Workaround for Problem 3To work around this problem, install SQL Server 2005 SP2.
Workaround for Problem 5You can safely ignore this error message. After you install SQL Server 2005, you must install SQL Server 2005 SP2.
Workaround for Problem 6At the time of the most recent update to this article, SQL Server 2005 is in extended support phase, and this problem will not be fixed in this release.
However, as a workaround, you can try to remove the SQL servers dependency on network name and shared disk resources.
There is also a slight change in the syntax that is used to invoke the setup. In addition to the other keywords, you now have to provide the virtual IP address on which SQL Server listens.
Use the following example as a guide to rebuild the system databases:
start /wait <CD or DVD Drive>\setup.exe /qn VS=<VSName> IP=XXX.XX.XX.XX,NETWORK_NAME INSTANCENAME=<InstanceName> REINSTALL=SQL_Engine REBUILDDATABASE=1 ADMINPASSWORD=<StrongPassword> SAPWD=<NewStrongPassword> SQLCOLLATION=<NewSystemCollation> SQLACCOUNT=<domain\user> SQLPASSWORD=<DomainUserPassword> AGTACCOUNT=<domain\user> AGTPASSWORD=<DomainUserPassword>changes.