Showing posts with label pipe. Show all posts
Showing posts with label pipe. Show all posts

Sunday, March 11, 2012

Connection from XP SP2 to Windows 2003 R2 with SQL Server 2005 failed

I cannot make named pipe connection with client by ODBC DSA.

Here is information. Refering to http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1.

[1] Client side:

1. What is the connection string in you app or DSN? (please specify) ODBC \\[SERVER_NAME]\pipe\sql\guery

2. If client fails to connect, what is the client error messages? (please specify) Connection failed: SQLState: ’01000’ SQL ServerError: 1326 [Microsoft][ODBC SQL Server Driver][Named Pipes]connectionOpen (Connect()) Connection failed: SQLState: ’08001’ SQL Server Error: 17 [Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.

3. Is the client remote or local to the SQL server machine? [Remote | Local]

4. Can you ping your server? [YES | NO ]

In cmd.exe console, type “ping -a <server_name>”.

5. Can you telnet to your SQL Server? [YES | NO, please specify the error message ]

In cmd.exe console, type “telnet <server name> port, where port can be 135, 445 or sql_server_tcp_port. If your cmd.exe console turns into a complete black screen with a cursor flushing on top left corner, you are connected. Type ctrl+’[‘ to bring up telnet prompt and type “quit” <enter>.

6. What is your client database provider? [SNAC | MDAC | ADO.NET1.0 | ADO.NET2.0| other ODBC (please specify] Or/And, what is your client application? [SQL Management Studio | SQL Profiler | Visual Studio | Other (please specify).

7. Is your client computer in the same domain as the Server computer? (Same domain | Different domains | WorkGroup)

8. What protocol the client enabled? [Shared Memory | TCPIP | Named Pipes].

9. Do you have aliases configured that match the server name portion of your connection string? If so, please check if it is correct. You can use cliconfg.exe (SS 2000) or SQL Server Configuration Manager (SS 2005) to configure the alias. [NO]

10. Do you select force encryption on server and/or client? [NO]

I was able to connect with TCP/IP settings.

[2] Server side:

1. What is the MS SQL version? [SQL Server 2005]

2. What is the SKU of MS SQL? [Enterprise | Standard | Workgroup | Express (or MSDE) | other (please specify)].

3. What is the SQL Server Protocol enabled? [Shared Memory | TCPIP | Named Pipes ]. Use SQL Server Configuration Manager to configure it and check ERRORLOG or event log to confirm.

4. Does the server start successfully? [YES | NO] If not what is the error messages in the SQL server ERRORLOG?

5. If SQL Server is a named instance, is the SQL browser enabled? [YES | NO]

6. What is the account that the SQL Server is running under?[Local System | Network Service | Domain Account]

7. Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider? [YES | NO | not applicable | not enabled]

8. Do you make firewall exception for SQL Browser UDP port 1434? In SQL2000, you still need to make firewall exception for UDP port 1434 in order to support named instance.[YES | NO | not applicable | not enabled]

I could connect locally with named pipes.

Do I have to make some file shares manually?

[2a] Tool Used to Connect

What tool or Application are you using to connect to SQL Server (eg: Visual Studio, SQL Server Management Studio, SQLCmd.exe, OSQL, etc) and especially the version of SQL Server (Express, Workgroup, Standard, Enterprise, Developer)

[3] Platform:

1. What is the OS version? [Windows XPSP2 | Windows 2003 | Windows 2000 | Windows 98 | others (please specify ) ].

1. Server [Windows Server 2003 R2]

2. Client [Windows XP SP2]

2. Do you have third party antivirus, anti-spareware software installed? [Symantec | Norton | other (please specify) ? NO].

[4] Misc:

1. If you have certificate configuration issue: Please use “certutil.exe –v –store my” to dump certificate specific info and post it in your question. [NO]

What happens if you execute
net use \\[server_name]\ipc$
from the client?

Saturday, February 25, 2012

connection error

Hi

I am getting following error while connecting in sql server. i have already disabled firewall, enabled remote connections using pipe and tcp and made sure the sql server and sql browser services are running.

but still the problem persists...can any help me ?

Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi
shing a connection to the server. When connecting to SQL Server 2005, this failu
re may be caused by the fact that under the default settings SQL Server does not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

thanks in advance

Do you have a named instacne or a default one ? how are you connecting, you will have to provide some more information on your situation to make it easier forus to give you the right suggestions.

Jens K. Suessmeyer


http://www.sqlserver2005.de