BCP command fails on SQL 2008

Question

BCP command fails on SQL 2008

Shree-903371

SSCommitted

Points: 1930
More actions
July 8, 2010 at 2:16 pm

#387309

In one my code, I have used BCP(Bulk Copy Command) to get data from text file. I have used that code to create report using Crystal Reports. It was working fine on SQL server 2005.
We have moved the development server to SQL Server 2008, then also it runs fine my system but when I publish it on server for testing, its failing.
We thought it was admin issue and the server needs rights on the folder from which we get the data. But after granting access to the server also the it fails.
Does anybody have any suggestions on it or did anybody faced this situation?
Thank you in advance.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

sturner SSC-Insane Points: 22411 More actions · Answer 1

What error code or error message are you getting? I could be failing for a dozen different reasons. Most likely connectivity or login credential issue if nothing else has changed.

The probability of survival is inversely proportional to the angle of arrival.

Shree-903371 SSCommitted Points: 1930 More actions · Answer 2

Its givving Query Engine Error. Its running fine on my system. Just when i publish it on the server its failing.

Lowell SSC Guru Points: 323518 More actions · Answer 3

Shree-903371 (7/9/2010)
Its givving Query Engine Error. Its running fine on my system. Just when i publish it on the server its failing.

http://aspadvice.com/blogs/rjdudley/archive/2005/05/13/2589.aspx

his first reason is my first guess...either the db you are connected to is the wrong one(ie master by mistake) or the table has schema differences.

Friday, May 13, 2005 5:03 PM by rjdudley
"Query Engine Error" With Crystal Reports .NET
There are two main reasons this error is thrown when using the PUSH (dataset) method of getting data to a Crystal Report.
1) The schema of the datatable differs from what the report was designed from. This can be either a different field name, or a missing field, or in a different order. The easiest way to debug this is to bind the dataset to a datagrid, and compare the resulting schema to the XSD you used to design the report. Compare data types, column names, etc.
2) The name of the data table is incorrect. When you designed your report from an XSD, the report saved the name of the data table(s) that were in your dataset. When you filled your dataset, you probably forgot to specify the name of the data table. If you're using a DataAdapter, your command should be:
MyAdapter.Fill(MyDataSet, "MyTableName")

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!