This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 408226 (SQLBUDT)
When you try to upgrade a named instance of Microsoft SQL Server 2000 to Microsoft SQL Server 2005 on a computer that is running the 64-bit version of the Intel Itanium-based operating system, you may receive the following error message:
UpgradeAdvisor returned -1 . Error message:An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Shared Memory Provider, error: 36 - The Shared Memory dll used to connect to SQL Server 2000 was not found) . Net SqlClient Data Provider at Microsoft.SqlServer.BestPracticesAnalyzer.Upgrade.BPAUAAnalyzer. ValidateSQL() at Microsoft.SqlServer.BestPracticesAnalyzer.Upgrade.BPAUAAnalyzer. ValidateParameters() at Microsoft.SqlServer.BestPracticesAnalyzer.Upgrade.BPAUAAnalyzer. Execute() at Microsoft.SqlServer.UpgradeAdvisor.AnalyzerEngine.RunAnalyzer(Object analyzerInfo)
This problem occurs if all the following conditions are true on the computer:
At least one instance of SQL Server 2005 is installed.
A 64-bit named instance of SQL Server 2000 is installed.
A default instance of SQL Server 2000 Analysis Server is installed.
Note This problem may also occur when you upgrade the named instance of SQL Server 2000 if a named instance of SQL Server 2005 Analysis Services (SSAS) is also installed and these named instances have the same name. However, we do not support the scenario in which a named instance of SSAS and a named instance of SQL Server 2000 are installed when the instances are different versions and have the same name.
This problem occurs because the SQL Server 2005 Upgrade Advisor cannot connect to the named instance of SQL Server 2000.
The SQL Server 2005 Upgrade Advisor uses information that the SQL Server Browser service returns when the SQL Server 2005 Upgrade Advisor tries to connect to an instance of SQL Server 2000. However, the SQL Server Browser service cannot return the correct information about the connection request. Therefore, the connection fails.
To work around this problem, use one of the following methods:
Use SQL Server 2000 SQL Server Resolution Protocol (SSRP) instead of the SQL Server Browser service to handle the connection request. To do this, follow these steps:
Open the SQL Server Configuration Manager.
In the left pane, click SQL Server 2005 Services.
Right-click SQL Server Browser, and then click Properties. The SQL Server Browser Properties dialog box appears.
Click the Advanced tab, and then set the Active property to No.
After you complete these steps, you can upgrade the instances of SQL Server 2000 and SQL Server 2000 Analysis Server. After the upgrade is complete, re-enable SQL Server Browser service. To do this, set the Active property to Yes, and then restart the SQL Server Browser service.
Upgrade the named instance of SQL Server 2000 to SQL Server 2005 before you create a named instance of SQL Server 2005 Analysis Server that has the same name.
Note Make sure that the named instance of SQL Server 2000 has at least one remote protocol enabled. For example, make sure that TCP/IP is enabled or that Named Pipes is enabled.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.