dbTalk Databases Forums  

BCP.EXE fails in 90 where it succeeded in 80

microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools


Discuss BCP.EXE fails in 90 where it succeeded in 80 in the microsoft.public.sqlserver.tools forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Thomas W. Brown
 
Posts: n/a

Default BCP.EXE fails in 90 where it succeeded in 80 - 06-12-2008 , 12:19 PM






I'm trying to BCP out a temporary table (this is actually occuring in an
application and with the connection still open that "owns" the temporary
table, the application launches BCP.EXE to move the data to the file system).

The command line is of the form:
bcp "##temptablename...." out "c:\path\tempfilename.bin" -n -S server -q
-a 65535 -T

In the 8.0 version of the utility there is no problem, the BCP out operation
succeeds. But in the 9.0 version I get a series of errors:

SQLState = 28000, NativeError = 18456
Error = [Microsoft][SQL Native Client][SQL Server]Login failed for user
'username'.
SQLState = IM006, NativeError = 0
Error = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
SQLState = 42000, NativeError = 4060
Error = [Microsoft][SQL Native Client][SQL Server]Cannot open database
"##temptablename..." requested by the login. The login failed.
SQLState = IM006, NativeError = 0
Error = [Microsoft][SQL Native Client]Packet size change not supported by
server, default used

That last error goes away if I take out the "-a 65535" command line option
(although the documentation shows this still as a valid option).

Any and all help on this issue would be most appreciated!

-- TB

Reply With Quote
  #2  
Old   
Thomas W. Brown
 
Posts: n/a

Default RE: BCP.EXE fails in 90 where it succeeded in 80 - 06-12-2008 , 01:22 PM






Hmmm... it seems that explicitly specifying "tempdb" makes BCP v9.0 work...

bcp "tempdb.##temptablename..." out "output file path" -n -S server -q -a
65535 -T

None of the other errors show up. Clarification on what is happening here
would be appreciated.

-- TB

"Thomas W. Brown" wrote:

Quote:
I'm trying to BCP out a temporary table (this is actually occuring in an
application and with the connection still open that "owns" the temporary
table, the application launches BCP.EXE to move the data to the file system).

The command line is of the form:
bcp "##temptablename...." out "c:\path\tempfilename.bin" -n -S server -q
-a 65535 -T

In the 8.0 version of the utility there is no problem, the BCP out operation
succeeds. But in the 9.0 version I get a series of errors:

SQLState = 28000, NativeError = 18456
Error = [Microsoft][SQL Native Client][SQL Server]Login failed for user
'username'.
SQLState = IM006, NativeError = 0
Error = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
SQLState = 42000, NativeError = 4060
Error = [Microsoft][SQL Native Client][SQL Server]Cannot open database
"##temptablename..." requested by the login. The login failed.
SQLState = IM006, NativeError = 0
Error = [Microsoft][SQL Native Client]Packet size change not supported by
server, default used

That last error goes away if I take out the "-a 65535" command line option
(although the documentation shows this still as a valid option).

Any and all help on this issue would be most appreciated!

-- TB


Reply With Quote
  #3  
Old   
Thomas W. Brown
 
Posts: n/a

Default RE: BCP.EXE fails in 90 where it succeeded in 80 - 06-12-2008 , 01:22 PM



Hmmm... it seems that explicitly specifying "tempdb" makes BCP v9.0 work...

bcp "tempdb.##temptablename..." out "output file path" -n -S server -q -a
65535 -T

None of the other errors show up. Clarification on what is happening here
would be appreciated.

-- TB

"Thomas W. Brown" wrote:

Quote:
I'm trying to BCP out a temporary table (this is actually occuring in an
application and with the connection still open that "owns" the temporary
table, the application launches BCP.EXE to move the data to the file system).

The command line is of the form:
bcp "##temptablename...." out "c:\path\tempfilename.bin" -n -S server -q
-a 65535 -T

In the 8.0 version of the utility there is no problem, the BCP out operation
succeeds. But in the 9.0 version I get a series of errors:

SQLState = 28000, NativeError = 18456
Error = [Microsoft][SQL Native Client][SQL Server]Login failed for user
'username'.
SQLState = IM006, NativeError = 0
Error = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
SQLState = 42000, NativeError = 4060
Error = [Microsoft][SQL Native Client][SQL Server]Cannot open database
"##temptablename..." requested by the login. The login failed.
SQLState = IM006, NativeError = 0
Error = [Microsoft][SQL Native Client]Packet size change not supported by
server, default used

That last error goes away if I take out the "-a 65535" command line option
(although the documentation shows this still as a valid option).

Any and all help on this issue would be most appreciated!

-- TB


Reply With Quote
  #4  
Old   
Thomas W. Brown
 
Posts: n/a

Default RE: BCP.EXE fails in 90 where it succeeded in 80 - 06-12-2008 , 01:22 PM



Hmmm... it seems that explicitly specifying "tempdb" makes BCP v9.0 work...

bcp "tempdb.##temptablename..." out "output file path" -n -S server -q -a
65535 -T

None of the other errors show up. Clarification on what is happening here
would be appreciated.

-- TB

"Thomas W. Brown" wrote:

Quote:
I'm trying to BCP out a temporary table (this is actually occuring in an
application and with the connection still open that "owns" the temporary
table, the application launches BCP.EXE to move the data to the file system).

The command line is of the form:
bcp "##temptablename...." out "c:\path\tempfilename.bin" -n -S server -q
-a 65535 -T

In the 8.0 version of the utility there is no problem, the BCP out operation
succeeds. But in the 9.0 version I get a series of errors:

SQLState = 28000, NativeError = 18456
Error = [Microsoft][SQL Native Client][SQL Server]Login failed for user
'username'.
SQLState = IM006, NativeError = 0
Error = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
SQLState = 42000, NativeError = 4060
Error = [Microsoft][SQL Native Client][SQL Server]Cannot open database
"##temptablename..." requested by the login. The login failed.
SQLState = IM006, NativeError = 0
Error = [Microsoft][SQL Native Client]Packet size change not supported by
server, default used

That last error goes away if I take out the "-a 65535" command line option
(although the documentation shows this still as a valid option).

Any and all help on this issue would be most appreciated!

-- TB


Reply With Quote
  #5  
Old   
Thomas W. Brown
 
Posts: n/a

Default RE: BCP.EXE fails in 90 where it succeeded in 80 - 06-12-2008 , 01:22 PM



Hmmm... it seems that explicitly specifying "tempdb" makes BCP v9.0 work...

bcp "tempdb.##temptablename..." out "output file path" -n -S server -q -a
65535 -T

None of the other errors show up. Clarification on what is happening here
would be appreciated.

-- TB

"Thomas W. Brown" wrote:

Quote:
I'm trying to BCP out a temporary table (this is actually occuring in an
application and with the connection still open that "owns" the temporary
table, the application launches BCP.EXE to move the data to the file system).

The command line is of the form:
bcp "##temptablename...." out "c:\path\tempfilename.bin" -n -S server -q
-a 65535 -T

In the 8.0 version of the utility there is no problem, the BCP out operation
succeeds. But in the 9.0 version I get a series of errors:

SQLState = 28000, NativeError = 18456
Error = [Microsoft][SQL Native Client][SQL Server]Login failed for user
'username'.
SQLState = IM006, NativeError = 0
Error = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
SQLState = 42000, NativeError = 4060
Error = [Microsoft][SQL Native Client][SQL Server]Cannot open database
"##temptablename..." requested by the login. The login failed.
SQLState = IM006, NativeError = 0
Error = [Microsoft][SQL Native Client]Packet size change not supported by
server, default used

That last error goes away if I take out the "-a 65535" command line option
(although the documentation shows this still as a valid option).

Any and all help on this issue would be most appreciated!

-- TB


Reply With Quote
  #6  
Old   
Thomas W. Brown
 
Posts: n/a

Default RE: BCP.EXE fails in 90 where it succeeded in 80 - 06-12-2008 , 01:22 PM



Hmmm... it seems that explicitly specifying "tempdb" makes BCP v9.0 work...

bcp "tempdb.##temptablename..." out "output file path" -n -S server -q -a
65535 -T

None of the other errors show up. Clarification on what is happening here
would be appreciated.

-- TB

"Thomas W. Brown" wrote:

Quote:
I'm trying to BCP out a temporary table (this is actually occuring in an
application and with the connection still open that "owns" the temporary
table, the application launches BCP.EXE to move the data to the file system).

The command line is of the form:
bcp "##temptablename...." out "c:\path\tempfilename.bin" -n -S server -q
-a 65535 -T

In the 8.0 version of the utility there is no problem, the BCP out operation
succeeds. But in the 9.0 version I get a series of errors:

SQLState = 28000, NativeError = 18456
Error = [Microsoft][SQL Native Client][SQL Server]Login failed for user
'username'.
SQLState = IM006, NativeError = 0
Error = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
SQLState = 42000, NativeError = 4060
Error = [Microsoft][SQL Native Client][SQL Server]Cannot open database
"##temptablename..." requested by the login. The login failed.
SQLState = IM006, NativeError = 0
Error = [Microsoft][SQL Native Client]Packet size change not supported by
server, default used

That last error goes away if I take out the "-a 65535" command line option
(although the documentation shows this still as a valid option).

Any and all help on this issue would be most appreciated!

-- TB


Reply With Quote
  #7  
Old   
Thomas W. Brown
 
Posts: n/a

Default RE: BCP.EXE fails in 90 where it succeeded in 80 - 06-12-2008 , 01:22 PM



Hmmm... it seems that explicitly specifying "tempdb" makes BCP v9.0 work...

bcp "tempdb.##temptablename..." out "output file path" -n -S server -q -a
65535 -T

None of the other errors show up. Clarification on what is happening here
would be appreciated.

-- TB

"Thomas W. Brown" wrote:

Quote:
I'm trying to BCP out a temporary table (this is actually occuring in an
application and with the connection still open that "owns" the temporary
table, the application launches BCP.EXE to move the data to the file system).

The command line is of the form:
bcp "##temptablename...." out "c:\path\tempfilename.bin" -n -S server -q
-a 65535 -T

In the 8.0 version of the utility there is no problem, the BCP out operation
succeeds. But in the 9.0 version I get a series of errors:

SQLState = 28000, NativeError = 18456
Error = [Microsoft][SQL Native Client][SQL Server]Login failed for user
'username'.
SQLState = IM006, NativeError = 0
Error = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
SQLState = 42000, NativeError = 4060
Error = [Microsoft][SQL Native Client][SQL Server]Cannot open database
"##temptablename..." requested by the login. The login failed.
SQLState = IM006, NativeError = 0
Error = [Microsoft][SQL Native Client]Packet size change not supported by
server, default used

That last error goes away if I take out the "-a 65535" command line option
(although the documentation shows this still as a valid option).

Any and all help on this issue would be most appreciated!

-- TB


Reply With Quote
  #8  
Old   
Thomas W. Brown
 
Posts: n/a

Default RE: BCP.EXE fails in 90 where it succeeded in 80 - 06-12-2008 , 01:22 PM



Hmmm... it seems that explicitly specifying "tempdb" makes BCP v9.0 work...

bcp "tempdb.##temptablename..." out "output file path" -n -S server -q -a
65535 -T

None of the other errors show up. Clarification on what is happening here
would be appreciated.

-- TB

"Thomas W. Brown" wrote:

Quote:
I'm trying to BCP out a temporary table (this is actually occuring in an
application and with the connection still open that "owns" the temporary
table, the application launches BCP.EXE to move the data to the file system).

The command line is of the form:
bcp "##temptablename...." out "c:\path\tempfilename.bin" -n -S server -q
-a 65535 -T

In the 8.0 version of the utility there is no problem, the BCP out operation
succeeds. But in the 9.0 version I get a series of errors:

SQLState = 28000, NativeError = 18456
Error = [Microsoft][SQL Native Client][SQL Server]Login failed for user
'username'.
SQLState = IM006, NativeError = 0
Error = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
SQLState = 42000, NativeError = 4060
Error = [Microsoft][SQL Native Client][SQL Server]Cannot open database
"##temptablename..." requested by the login. The login failed.
SQLState = IM006, NativeError = 0
Error = [Microsoft][SQL Native Client]Packet size change not supported by
server, default used

That last error goes away if I take out the "-a 65535" command line option
(although the documentation shows this still as a valid option).

Any and all help on this issue would be most appreciated!

-- TB


Reply With Quote
  #9  
Old   
Thomas W. Brown
 
Posts: n/a

Default RE: BCP.EXE fails in 90 where it succeeded in 80 - 06-12-2008 , 01:22 PM



Hmmm... it seems that explicitly specifying "tempdb" makes BCP v9.0 work...

bcp "tempdb.##temptablename..." out "output file path" -n -S server -q -a
65535 -T

None of the other errors show up. Clarification on what is happening here
would be appreciated.

-- TB

"Thomas W. Brown" wrote:

Quote:
I'm trying to BCP out a temporary table (this is actually occuring in an
application and with the connection still open that "owns" the temporary
table, the application launches BCP.EXE to move the data to the file system).

The command line is of the form:
bcp "##temptablename...." out "c:\path\tempfilename.bin" -n -S server -q
-a 65535 -T

In the 8.0 version of the utility there is no problem, the BCP out operation
succeeds. But in the 9.0 version I get a series of errors:

SQLState = 28000, NativeError = 18456
Error = [Microsoft][SQL Native Client][SQL Server]Login failed for user
'username'.
SQLState = IM006, NativeError = 0
Error = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
SQLState = 42000, NativeError = 4060
Error = [Microsoft][SQL Native Client][SQL Server]Cannot open database
"##temptablename..." requested by the login. The login failed.
SQLState = IM006, NativeError = 0
Error = [Microsoft][SQL Native Client]Packet size change not supported by
server, default used

That last error goes away if I take out the "-a 65535" command line option
(although the documentation shows this still as a valid option).

Any and all help on this issue would be most appreciated!

-- TB


Reply With Quote
  #10  
Old   
Thomas W. Brown
 
Posts: n/a

Default RE: BCP.EXE fails in 90 where it succeeded in 80 - 06-12-2008 , 01:22 PM



Hmmm... it seems that explicitly specifying "tempdb" makes BCP v9.0 work...

bcp "tempdb.##temptablename..." out "output file path" -n -S server -q -a
65535 -T

None of the other errors show up. Clarification on what is happening here
would be appreciated.

-- TB

"Thomas W. Brown" wrote:

Quote:
I'm trying to BCP out a temporary table (this is actually occuring in an
application and with the connection still open that "owns" the temporary
table, the application launches BCP.EXE to move the data to the file system).

The command line is of the form:
bcp "##temptablename...." out "c:\path\tempfilename.bin" -n -S server -q
-a 65535 -T

In the 8.0 version of the utility there is no problem, the BCP out operation
succeeds. But in the 9.0 version I get a series of errors:

SQLState = 28000, NativeError = 18456
Error = [Microsoft][SQL Native Client][SQL Server]Login failed for user
'username'.
SQLState = IM006, NativeError = 0
Error = [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
SQLState = 42000, NativeError = 4060
Error = [Microsoft][SQL Native Client][SQL Server]Cannot open database
"##temptablename..." requested by the login. The login failed.
SQLState = IM006, NativeError = 0
Error = [Microsoft][SQL Native Client]Packet size change not supported by
server, default used

That last error goes away if I take out the "-a 65535" command line option
(although the documentation shows this still as a valid option).

Any and all help on this issue would be most appreciated!

-- TB


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.