SQL Server Q&A

Symptoms
After you repair an instance of Microsoft SQL Server 2008, the Shared Memory protocol for the instance is always enabled. Additionally, the VIA protocol for the instance is always disabled.
You can use several methods to run the repair operation. For example, you can repair an instance by using theAdd or Remove Programs item in Control Panel.
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for SQL Server 2008. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
968382?(http://support.microsoft.com/kb/968382/) How to obtain the latest service pack for SQL Server 2008

Symptoms
Consider the following scenario. On a client computer that is running Windows Vista orWindows Server 2008, you connect to a named instance of Microsoft SQL Server. The named instance is located on a remote server. In this scenario, the connection may fail.
Note This problem occurs when you connect to one of the following versions of SQL Server:Microsoft SQL Server 2000Microsoft SQL Server 2005Microsoft SQL Server 2008If you use Windows Data Access Components (Windows DAC) 6.0 to connect to the named instance, you receive the following error message:

[DBNETLIB]Specified SQL server not found.
[DBNETLIB]ConnectionOpen (Connect()).If you use SQL Native Client to connect to the named instance, you receive the following error message:

[SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
[SQL Native Client]Login timeout expired.This problem occurs when the named instance is a failover cluster instance. Additionally, this problem may occur if the remote server has multiple IP addresses.
Resolution
When you connect to the named instance, the client network library sends a User Datagram Protocol (UDP) request packet to the IP address of the named instance. Then, SQL Server Browser returns a UDP response packet that contains the information about the connection endpoints.
However, in the UDP response packet, the source IP address may not be the IP address to which the UDP request packet was sent. If the named instance is a failover cluster instance, the source IP address is the IP address of the physical computer instead of the virtual IP address of the remote server. If the remote server has multiple IP addresses, the source IP address may be any of the IP addresses that are assigned to the remote server.
In Windows Vista, Windows Firewall does not allow for loose source mapping. Therefore, Windows Firewall drops the UDP response packet.
For more information about loose source mapping, see the “UDP connections” section of the following Microsoft Web site:
http://technet2.microsoft.com/WindowsServer/en/library/3ccb6af5-d960-4a8d-b12b-70692dc47bf41033.mspx?mfr=true(http://technet2.microsoft.com/WindowsServer/en/library/3ccb6af5-d960-4a8d-b12b-70692dc47bf41033.mspx?mfr=true)

Symptoms
On a computer that is running Windows Vista, you install a default instance of Microsoft SQL Server 2005 Service Pack 2 or alater version of SQL Server 2005. On the same computer, you install a named instance of Microsoft SQL Server 2008. For example, you install an instance that is named “SQL2008.”
In this scenario, you may receive an error message that resembles the following when you start the SQL Server 2008 Reporting Services Configuration Manager:

No report servers were found. Details: Invalid namespace
Resolution
This problem occurs if the SQL Server 2008 Reporting Services Configuration Manager points to the SQL Server 2005 Reporting Services instance, and it cannot find the SQL Server 2008 instance.

Symptoms
On a 64-bit computer, you install an instance of the 32-bit (x86-based) version of Microsoft SQL Server 2008. On the same computer, you install an instance of the 64-bit version of SQL Server 2008. Ifyou then uninstall the 64-bit instance, you receive the following error message when you open SQL Server Configuration Manager:

Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager.
Invalid namespace [0x8004100e]This problem also occurs if you uninstall the 32-bit instance, and you then open SQL Server Configuration Manager.
Resolution
This problem occurs because the WMI provider is removed when you uninstall an instance of SQL Server 2008. The 32-bit instance and the 64-bit instance of SQL Server 2008 share the same WMI configuration file. This file is located in the %programfiles(x86)% folder.

Symptoms
When you upgrade an instance of SQL Server to SQL Server 2008, some client-related protocol settings are not automatically applied to the SQL Server 2008 client. For example if you have enabled Secure Socket Layer Encryption (SSL) on a SQL Server 2005 instance either by turning on the Force protocol encryption option in Client Network utility or by using the Properties page of SQL Native Client Configuration in SQL Server configuration manager, the setting is not preserved when you upgrade that instance to SQL Server 2008.
Resolution
This behavior is by design.