 | |
SQLCMD on SQL cluster
microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools
 |
| | Thread Tools | Display Modes |
#41
 
| |||
| |||
|
Re: SQLCMD on SQL cluster -
12-04-2008
, 07:26 PM
|
No luck - change the script to: SQLCMD -S colldb1.datatel.daemen.edu -U datatel -P Hub8/TPO -i c:\IMMUNIZATION\Immune_Dump.sql -o c:\IMMUNIZATION\DEM_DUMP.TXT -h -1 -Y 57 and I get the same error message. "Erland Sommarskog" wrote: Brian Wilkins (bwilkins (AT) daemen (DOT) edu) writes: I developed a SQLCMD batch file that I run on a sql 2005 server . On the single server copy of 2005 it works fine. SQLCMD -U loginame -P ourpassword -i c:\IMMUNIZATION\Immune_Dump.sql -o c:\IMMUNIZATION\DEM_DUMP.TXT -h -1 -Y 57 When I transferred it to a 2 server cluster of sql server 2005 I get the following error. HResult 0x2, Level 16, State 1 Named Pipes Provider: Could not open a connection to SQL Server [2]. Sqlcmd: Error: Microsoft SQL Native Client : 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.. Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired. I went through many of the steps for this error and they all seem to be already set (ie tcp, named pipes etc...) - no luck I guess you need to specify the server name with the -S option. This is particularly obvious, if you run SQLCMD on one node in the cluster, and SQL Server is right now running on the second. But even if you run SQLCMD on the active node, I believe you need to specify the server, as the server name is not the same as the machine name. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx |
#42
| |||
| |||
|
|
No luck - change the script to: SQLCMD -S colldb1.datatel.daemen.edu -U datatel -P Hub8/TPO -i c:\IMMUNIZATION\Immune_Dump.sql -o c:\IMMUNIZATION\DEM_DUMP.TXT -h -1 -Y 57 and I get the same error message. "Erland Sommarskog" wrote: Brian Wilkins (bwilkins (AT) daemen (DOT) edu) writes: I developed a SQLCMD batch file that I run on a sql 2005 server . On the single server copy of 2005 it works fine. SQLCMD -U loginame -P ourpassword -i c:\IMMUNIZATION\Immune_Dump.sql -o c:\IMMUNIZATION\DEM_DUMP.TXT -h -1 -Y 57 When I transferred it to a 2 server cluster of sql server 2005 I get the following error. HResult 0x2, Level 16, State 1 Named Pipes Provider: Could not open a connection to SQL Server [2]. Sqlcmd: Error: Microsoft SQL Native Client : 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.. Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired. I went through many of the steps for this error and they all seem to be already set (ie tcp, named pipes etc...) - no luck I guess you need to specify the server name with the -S option. This is particularly obvious, if you run SQLCMD on one node in the cluster, and SQL Server is right now running on the second. But even if you run SQLCMD on the active node, I believe you need to specify the server, as the server name is not the same as the machine name. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx |
#43
| |||
| |||
|
|
No luck - change the script to: SQLCMD -S colldb1.datatel.daemen.edu -U datatel -P Hub8/TPO -i c:\IMMUNIZATION\Immune_Dump.sql -o c:\IMMUNIZATION\DEM_DUMP.TXT -h -1 -Y 57 and I get the same error message. "Erland Sommarskog" wrote: Brian Wilkins (bwilkins (AT) daemen (DOT) edu) writes: I developed a SQLCMD batch file that I run on a sql 2005 server . On the single server copy of 2005 it works fine. SQLCMD -U loginame -P ourpassword -i c:\IMMUNIZATION\Immune_Dump.sql -o c:\IMMUNIZATION\DEM_DUMP.TXT -h -1 -Y 57 When I transferred it to a 2 server cluster of sql server 2005 I get the following error. HResult 0x2, Level 16, State 1 Named Pipes Provider: Could not open a connection to SQL Server [2]. Sqlcmd: Error: Microsoft SQL Native Client : 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.. Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired. I went through many of the steps for this error and they all seem to be already set (ie tcp, named pipes etc...) - no luck I guess you need to specify the server name with the -S option. This is particularly obvious, if you run SQLCMD on one node in the cluster, and SQL Server is right now running on the second. But even if you run SQLCMD on the active node, I believe you need to specify the server, as the server name is not the same as the machine name. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx |
#44
| |||
| |||
|
|
No luck - change the script to: SQLCMD -S colldb1.datatel.daemen.edu -U datatel -P Hub8/TPO -i c:\IMMUNIZATION\Immune_Dump.sql -o c:\IMMUNIZATION\DEM_DUMP.TXT -h -1 -Y 57 and I get the same error message. "Erland Sommarskog" wrote: Brian Wilkins (bwilkins (AT) daemen (DOT) edu) writes: I developed a SQLCMD batch file that I run on a sql 2005 server . On the single server copy of 2005 it works fine. SQLCMD -U loginame -P ourpassword -i c:\IMMUNIZATION\Immune_Dump.sql -o c:\IMMUNIZATION\DEM_DUMP.TXT -h -1 -Y 57 When I transferred it to a 2 server cluster of sql server 2005 I get the following error. HResult 0x2, Level 16, State 1 Named Pipes Provider: Could not open a connection to SQL Server [2]. Sqlcmd: Error: Microsoft SQL Native Client : 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.. Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired. I went through many of the steps for this error and they all seem to be already set (ie tcp, named pipes etc...) - no luck I guess you need to specify the server name with the -S option. This is particularly obvious, if you run SQLCMD on one node in the cluster, and SQL Server is right now running on the second. But even if you run SQLCMD on the active node, I believe you need to specify the server, as the server name is not the same as the machine name. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx |
#45
| |||
| |||
|
|
No luck - change the script to: SQLCMD -S colldb1.datatel.daemen.edu -U datatel -P Hub8/TPO -i c:\IMMUNIZATION\Immune_Dump.sql -o c:\IMMUNIZATION\DEM_DUMP.TXT -h -1 -Y 57 and I get the same error message. "Erland Sommarskog" wrote: Brian Wilkins (bwilkins (AT) daemen (DOT) edu) writes: I developed a SQLCMD batch file that I run on a sql 2005 server . On the single server copy of 2005 it works fine. SQLCMD -U loginame -P ourpassword -i c:\IMMUNIZATION\Immune_Dump.sql -o c:\IMMUNIZATION\DEM_DUMP.TXT -h -1 -Y 57 When I transferred it to a 2 server cluster of sql server 2005 I get the following error. HResult 0x2, Level 16, State 1 Named Pipes Provider: Could not open a connection to SQL Server [2]. Sqlcmd: Error: Microsoft SQL Native Client : 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.. Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired. I went through many of the steps for this error and they all seem to be already set (ie tcp, named pipes etc...) - no luck I guess you need to specify the server name with the -S option. This is particularly obvious, if you run SQLCMD on one node in the cluster, and SQL Server is right now running on the second. But even if you run SQLCMD on the active node, I believe you need to specify the server, as the server name is not the same as the machine name. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx |
#46
| |||
| |||
|
|
No luck - change the script to: SQLCMD -S colldb1.datatel.daemen.edu -U datatel -P Hub8/TPO -i c:\IMMUNIZATION\Immune_Dump.sql -o c:\IMMUNIZATION\DEM_DUMP.TXT -h -1 -Y 57 and I get the same error message. "Erland Sommarskog" wrote: Brian Wilkins (bwilkins (AT) daemen (DOT) edu) writes: I developed a SQLCMD batch file that I run on a sql 2005 server . On the single server copy of 2005 it works fine. SQLCMD -U loginame -P ourpassword -i c:\IMMUNIZATION\Immune_Dump.sql -o c:\IMMUNIZATION\DEM_DUMP.TXT -h -1 -Y 57 When I transferred it to a 2 server cluster of sql server 2005 I get the following error. HResult 0x2, Level 16, State 1 Named Pipes Provider: Could not open a connection to SQL Server [2]. Sqlcmd: Error: Microsoft SQL Native Client : 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.. Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired. I went through many of the steps for this error and they all seem to be already set (ie tcp, named pipes etc...) - no luck I guess you need to specify the server name with the -S option. This is particularly obvious, if you run SQLCMD on one node in the cluster, and SQL Server is right now running on the second. But even if you run SQLCMD on the active node, I believe you need to specify the server, as the server name is not the same as the machine name. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.