Microsoft KB Archive/936302

= List of known issues when you install SQL Server 2005 on Windows Server code name &quot;Longhorn&quot; =

Article ID: 936302

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Workgroup Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems

-





Beta Information
This article discusses a beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this beta product. For information about how to obtain support for a beta release, see the documentation that is included with the beta product files, or check the Web location where you downloaded the release.



This article discusses a scenario in which you run Microsoft SQL Server 2005 on beta software. This article is provided for information only. This article should not be construed as a statement of support. This article contains information about known issues that occur when you run SQL Server 2005 on Windows Server code name &quot;Longhorn&quot; for testing. You should not run SQL Server 2005 on Windows Server &quot;Longhorn&quot; in production because this configuration is not supported.

Important SQL Server 2005 requires Microsoft SQL Server 2005 Service Pack 2 (SP2) to run on Windows Server &quot;Longhorn.&quot; You must install the release version of SQL Server 2005 before you install SQL Server 2005 SP2.

To obtain SQL Server 2005 SP2, visit the following Microsoft Web site:

http://technet.microsoft.com/en-us/sqlserver/bb426877.aspx



SYMPTOMS
When you install SQL Server 2005 on a computer that is running Windows Server &quot;Longhorn,&quot; 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 &quot;Longhorn.&quot; 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:

Failure creating local group SQLServer2005SQLBrowserUser$RAYRODC



Cause of Problem 2
In the new Windows Server &quot;Longhorn&quot; 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 &quot;Longhorn.&quot; 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:

http://technet2.microsoft.com/windowsserver2008/en/library/ce82863f-9303-444f-9bb3-ecaf649bd3dd1033.mspx?mfr=true



Workaround for Problem 1
To 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:

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

 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

</li></ol>

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:

932897 You cannot find SQL Server cluster resources in Failover Cluster Manager after you install a SQL Server 2005 failover cluster on a computer that is running Windows Server &quot;Longhorn&quot;

Workaround for Problem 3
To work around this problem, install SQL Server 2005 SP2.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="references_section">