|
|
You're in the
sql server clients
group:SQL Native Client
sql server clients:
I'm currently playing with SQL Server 2005. I deployed the server on a
W2K-Server. It works fine. I have deployed two clients on computers running XP-Pro, using SQLNCLI.MSI. No problem. I have done the same deployment on a computer running W2K using the same SQLNCLI.MSI. That computer is unable to connect to the database. The error shown is: Connection failed: SQLState: '08001' SQL Server Error: 2 [Microsoft][SQL NativeClient]Named Pipes Provider: could not open a connection to SQL Server [2]. Connection failed: SQL State: 'HYT00' SQL Server Error: 0 [Microsoft][SQL NativeClient]Login timeout expired Connection failed: SQLState: '08001' SQL Server Error: 2 [Microsoft][SQL NativeClient]An error has occured while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be cause by the fact that under the default settings SQL Server does not allow remote connections. Since 2 out of 3 computers are able to connect, obvioulsy the server is correctly configured to accept remote connections. For all 3 client computers, the connection test is done by creating an ODBC datasource, selecting "SQL Native Client" as driver, entering correct parameters to reach the server and then testing the connection with the ODBC wizard. What can make the W2K computer be unable to connect to the server ? I also installed the complete client utilies to test furter. Running SQL Configuration Manager, I was able to check fr the protocols, specifically named pipes and I verifyed that the pipe name was correct. I don't see anything wrong and yet the computer can't connect to the server. Any idea ? -- Francois PIETTE http://www.overbyte.be
[quoted text, click to view]
> I understand that only a Win2K client cannot connect to SQL 2005 after you > installed SQL native client. You encounter error message "login timeout > expired". 2 WinXP machine works fine. If I'm off-base, please let me know. You correctly sumarized the situation. [quoted text, click to view] > Since named pipes is based on netbios, you may want to temoporarily disable > any firewall on the client to test. There is no firewall. I can also add that the same computer is using an MSDE (SQL7) database. [quoted text, click to view] > Also, on SQL server side, please first run "SQL Server Surface Area > Configuration" tool to enable remote connections, then open "SQL Server > Configuration Manager" to make sure TCPIP protocol is enabled, and check > the port it uses. Please check the SQL error log and make sure both named > pipes and TCPIP is really enabled on the server. > C:\Program Files\Microsoft SQL Server\MSSQL.x\MSSQL\LOG\errorlog I will check, but since two XP computers are connected correctly, I guess everything is OK at server side. Checked. Named pipes and tCP/IP are activated. TCP/IP use port 1433. [quoted text, click to view] > On Win2k mahcine, first use configuration manager to make sure both TCPIP > and named pipes are enabled. They are both enabled. I also tryed changing the order of protocols. No success. [quoted text, click to view] > Then you may try the following steps: > > 1. Ping <server name> <port> to make sure it is open and can be accessed > from client. For example: > > ping sqlserver 1433 > > 2. Try to use TCP to by using the following command: > > sqlcmd tcp:<servername>,<port> > > For example: > > sqlcmd tcp:sqlserver,1433 > > 3. Try to use Named pipe to connect to command. For example: > > sqlcmd -S np:\\ComputerA\pipe\sql\query > > > sqlcmd -S np:\\ComputerA\pipe\MSSQL$<instancename>\sql\query --named > instance Will try and let you know the results. -- Francois PIETTE http://www.overbyte.be
Using your information, I was able to solve the problem.
The problem was the pipe name for the instance. Thanks for your good support. -- Francois PIETTE http://www.overbyte.be "Peter Yang [MSFT]" <petery@online.microsoft.com> a écrit dans le message de news:jeX70weZHHA.2368@TK2MSFTNGHUB02.phx.gbl... [quoted text, click to view] > Hello Francois, > > Sorry I posted the reply to another thread from you here. > > I understand that only a Win2K client cannot connect to SQL 2005 after you > installed SQL native client. You encounter error message "login timeout > expired". 2 WinXP machine works fine. If I'm off-base, please let me know. > > Since named pipes is based on netbios, you may want to temoporarily disable > any firewall on the client to test. > > Also, on SQL server side, please first run "SQL Server Surface Area > Configuration" tool to enable remote connections, then open "SQL Server > Configuration Manager" to make sure TCPIP protocol is enabled, and check > the port it uses. Please check the SQL error log and make sure both named > pipes and TCPIP is really enabled on the server. > > C:\Program Files\Microsoft SQL Server\MSSQL.x\MSSQL\LOG\errorlog > > On Win2k mahcine, first use configuration manager to make sure both TCPIP > and named pipes are enabled. Then you may try the following steps: > > 1. Ping <server name> <port> to make sure it is open and can be accessed > from client. For example: > > ping sqlserver 1433 > > 2. Try to use TCP to by using the following command: > > sqlcmd tcp:<servername>,<port> > > For example: > > sqlcmd tcp:sqlserver,1433 > > 3. Try to use Named pipe to connect to command. For example: > > sqlcmd -S np:\\ComputerA\pipe\sql\query > > > sqlcmd -S np:\\ComputerA\pipe\MSSQL$<instancename>\sql\query --named > instance > > If you have any update, please feel free to let me know. Thank you. > > Thanks & Regards, > > Peter Yang > MCSE2000/2003, MCSA, MCDBA > Microsoft Online Community Support > ================================================== > Get notification to my posts through email? Please refer to > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > ications > <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>. > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > where an initial response from the community or a Microsoft Support > Engineer within 1 business day is acceptable. Please note that each follow > up response may take approximately 2 business days as the support > professional working with you may need further investigation to reach the > most efficient resolution. The offering is not appropriate for situations > that require urgent, real-time or phone-based interactions or complex > project analysis and dump analysis issues. Issues of this nature are best > handled working with a dedicated Microsoft Support Engineer by contacting > Microsoft Customer Support Services (CSS) at > <http://msdn.microsoft.com/subscriptions/support/default.aspx>. > ================================================== > This posting is provided "AS IS" with no warranties, and confers no rights. >
Hello Francois,
If you'd like to connect to server by using SQL native client, you may need to install sql client tool which include configuration manager. Actually configuration manager use WMI API to connect to WMI provider to get sql native client related information. If you don't want to use configuration manager, you may need to develop your own code/script to do this job: #WMI Provider for Configuration Management http://msdn2.microsoft.com/en-us/library/ms180499.aspx http://blogs.msdn.com/sql_protocols/archive/2005/10/19/482840.aspx If you have any feedback or wishes on this feature, I encourage you submit via the link below and our product team would like to hear your voice: http://lab.msdn.microsoft.com/productfeedback/default.aspx Please let me know if you have any further feedback or comments. Thanks & Regards, Peter Yang MCSE2000/2003, MCSA, MCDBA Microsoft Online Community Support ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at <http://msdn.microsoft.com/subscriptions/support/default.aspx>. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Hello Francois,
Sorry I posted the reply to another thread from you here. I understand that only a Win2K client cannot connect to SQL 2005 after you installed SQL native client. You encounter error message "login timeout expired". 2 WinXP machine works fine. If I'm off-base, please let me know. Since named pipes is based on netbios, you may want to temoporarily disable any firewall on the client to test. Also, on SQL server side, please first run "SQL Server Surface Area Configuration" tool to enable remote connections, then open "SQL Server Configuration Manager" to make sure TCPIP protocol is enabled, and check the port it uses. Please check the SQL error log and make sure both named pipes and TCPIP is really enabled on the server. C:\Program Files\Microsoft SQL Server\MSSQL.x\MSSQL\LOG\errorlog On Win2k mahcine, first use configuration manager to make sure both TCPIP and named pipes are enabled. Then you may try the following steps: 1. Ping <server name> <port> to make sure it is open and can be accessed from client. For example: ping sqlserver 1433 2. Try to use TCP to by using the following command: sqlcmd tcp:<servername>,<port> For example: sqlcmd tcp:sqlserver,1433 3. Try to use Named pipe to connect to command. For example: sqlcmd -S np:\\ComputerA\pipe\sql\query sqlcmd -S np:\\ComputerA\pipe\MSSQL$<instancename>\sql\query --named instance If you have any update, please feel free to let me know. Thank you. Thanks & Regards, Peter Yang MCSE2000/2003, MCSA, MCDBA Microsoft Online Community Support ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at <http://msdn.microsoft.com/subscriptions/support/default.aspx>. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Don't see what you're looking for? Try a search.
|
March 2003
May 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |