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

Article translations Article translations
Article ID: 936302 - View products that this article applies to.
Important SQL Server 2005 requires Microsoft SQL Server 2005 Service Pack 2 (SP2) to run on Windows Server 2008 and Vista SP1. You must first install the full release version of SQL Server 2005 before you can apply 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
For more information about how to install SQL Server Express SP2, see the SQL Server 2005 Express Edition SP2 Readme. Earlier versions of SQL Server, including all editions of SQL Server 2000, Microsoft SQL Server 2000 Desktop Engine (MSDE 2000), SQL Server 7.0, and SQL Server 6.5, are not supported on Windows Server 2008 or on Windows Vista. For more information about SQL Server 2005 on Windows Server 2008 or on Windows Vista , visit the following Microsoft Web site:
http://www.microsoft.com/sql/howtobuy/windowsvistasupport.mspx
Expand all | Collapse all

On This Page

SYMPTOMS

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:
Failure creating local group SQLServer2005SQLBrowserUser$RAYRODC

Problem 5

When you install SQL Server 2005 on a Windows Server 2008 failover cluster, you receive the following error message:
All resources did not come online and therefore you will need to manually set the cluster restart option.

Problem 6

Consider 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 
In this scenario, you receive the following error message:
TITLE: Microsoft SQL Server 2005 Setup

-------------------------------------------------------

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

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:
http://technet2.microsoft.com/windowsserver2008/en/library/ce82863f-9303-444f-9bb3-ecaf649bd3dd1033.mspx?mfr=true

Cause of Problem 5

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

Cause of Problem 6

There 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

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

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 2008

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.

Workaround for Problem 6

At 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.

STATUS

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

REFERENCES

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:
938245 How to install and how to configure SQL Server 2005 Reporting Services on a computer that is running Windows Server 2008
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:
929150 Error message when you install or uninstall Microsoft SQL Server 2005 or SQL Server 2005 with Service Pack 2 on a Windows Vista-based or Windows Server 2008-based computer

Properties

Article ID: 936302 - Last Review: November 11, 2011 - Revision: 7.0
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
  • Microsoft SQL Server 2005 Express Edition
  • Microsoft SQL Server 2005 Express Edition with Advanced Services
Keywords: 
kbsqlsetup kbexpertiseadvanced kbtshoot kbprb KB936302

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com