List of known issues when you install SQL Server 2005 on Windows Server 2008

When you install SQL Server 2005 on a computer that is running Windows Server 2008, you experience one or more of the following problems.

Problem 1

You 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 2

After you install a SQL Server 2005 failover cluster, you cannot find SQL Server cluster resources in Failover Cluster Manager.

Problem 3

After you install SQL Server 2005, the full-text search service cannot start.

Problem 4

When you install SQL Server 2005 on a Read-Only Domain Controller (RODC), you receive the following error message:

Problem 5

When you install SQL Server 2005 on a Windows Server 2008 failover cluster, you receive the following error message:

Cause of Problem 2

In 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 3

This 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 4

On 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 5

The cause of this problem is the same as the cause of Problem 3.

Workaround for Problem 1

To work around this problem, follow these steps:

1. 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:
   http://msdn2.microsoft.com/en-us/library/ms191260.aspx (http://msdn2.microsoft.com/en-us/library/ms191260.aspx)
   For more information about how to create a connection string by using the named pipe protocol, visit the following MSDN Web site:
   http://msdn2.microsoft.com/en-us/library/ms189307.aspx (http://msdn2.microsoft.com/en-us/library/ms189307.aspx)
2. 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.
   For more information about Windows Firewall with Advanced Security, visit the following Microsoft Web site:
   http://technet.microsoft.com/en-us/windowsvista/aa937624.aspx (http://technet.microsoft.com/en-us/windowsvista/aa937624.aspx)

Workaround for Problem 2

For 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 3

To work around this problem, install SQL Server 2005 SP2.

Workaround for Problem 5

You can safely ignore this error message. After you install SQL Server 2005, you must install SQL Server 2005 SP2.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about how to install and how to configure SQL Server 2005 Reporting Services on Windows Server 2008, click the following article number to view the article in the Microsoft Knowledge Base: For more information about a problem that occurs when you install or uninstall Microsoft SQL Server 2005 or SQL Server 2005 with Service Pack 2 on a Windows Server 2008-based computer, click the following article number to view the article in the Microsoft Knowledge Base: