June 19, 2009 at 12:22 am
I'm trying to dump a Sql Server 2005 table's contents into an Excel sheet But got this error
NULL
Starting copy...
SQLSTATE=HY000,NativeError=0
Error=[Microsoft][SQL Native Client] unable to resolve column level collations
SQLState=01000,NativeError=5701
WArning=[Microsoft][SQL Native Client]Changed database context to 'cashflowguardian'
NULL
BCP copy out failed
NULL
Does anyone have idea ?
June 19, 2009 at 2:39 am
Hello,
This might be an issue with SQL Server. Take a look at the following link:-
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=274313
Regards,
John Marsh
www.sql.lu
SQL Server Luxembourg User Group
June 19, 2009 at 2:47 am
thx:-)
August 6, 2009 at 10:11 am
I ran into a similar error.
NULL
Starting copy...
SQLState = 01000, NativeError = 0
Warning = [Microsoft][SQL Native Client][SQL Server]Aug 6 2009 12:10PM
SQLState = S1000, NativeError = 0
Error = [Microsoft][SQL Native Client]Unable to resolve column level collations
NULL
BCP copy out failed
NULL
Turns out I had a print statement in my stored procedure that was causing the bcp to crash. When I removed the "print" the bcp worked fine.
August 10, 2010 at 4:16 am
I had the same problem.
Deleting the "PRINT" from the store procedure I was running with BCP,
solved the problem.
Thank very much!
askcoffman (8/6/2009)
I ran into a similar error.NULL
Starting copy...
SQLState = 01000, NativeError = 0
Warning = [Microsoft][SQL Native Client][SQL Server]Aug 6 2009 12:10PM
SQLState = S1000, NativeError = 0
Error = [Microsoft][SQL Native Client]Unable to resolve column level collations
NULL
BCP copy out failed
NULL
Turns out I had a print statement in my stored procedure that was causing the bcp to crash. When I removed the "print" the bcp worked fine.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply