Connectivity issues
- 2008195 - Issues to consider when changing the default value of network packet size for SQL server connections
- 945627 - You may encounter connectivity issues when you connect an application to SQL Server 2008 CTP
- 307197 - SQL Server cannot bind to the TCP/IP port on which SQL Server is listening when the TCP\IP port is used by another application
- 307864 - Error message when you connect to an instance of SQL Server: "Cannot open user default database"
- 318432 - BUG: Cannot Connect to a Clustered Named Instance Through a Firewall
- 888228 - You receive a "SQL Server does not exist or access denied" error message when you try to connect to a SQL Server named instance in a cluster by using TCP/IP sockets
- 929152 - You cannot connect to a local instance of SQL Server on a Windows XP-based computer or on a Windows 2000-based computer when you use "localhost" in the pipe name
- 942003 - Error message on a Windows Vista-based computer when you try to connect to Microsoft SQL Server Management Studio by using a VPN connection: "The user is not associated with a trusted SQL Server Connection"
- 942861 - Error message when an application connects to SQL Server on a server that is running Windows Server 2003: "General Network error," "Communication link failure," or "A transport-level error"
- 944390 - Error message when you connect to a named instance of SQL Server on a client computer that is running Windows Vista or Windows Server 2008: "Specified SQL server not found" or "Error Locating Server/Instance Specified"
- 2000373 - You may not be able to make a remote connection to SQL Server from a CLR trigger
- 2006769 - "Communication link failure" error message is reported for SSIS packages on SQL servers configured to use encryption and a large network packet size
|
|
