April 7, 2010 at 8:11 am
The error is:[Microsoft][ODBC SQL Server Driver]Unexpected EOF encountered in BCP dat
I have several snapshot replication working properly.
I've read somewhere the issue is probably caused by the table having GUID fields.
Can anyone else shed some light?
April 7, 2010 at 9:53 am
Looks like data from the .bcp file (which contains the actual data) could not be imported correctly. Try re-running your snapshot agent to create a fresh snapshot and check if the distribution agent fails again.
If it fails again, we will have to analyze what kind of data (inside the .bcp) is causing the failure. Most of the times, it will be some data issue. You can try to bcp in data from that file in native mode and specify and error and output file to pinpoint more accurately where it fails (you can create a temp table for importing this data by using the schema definition of the actual article table).
Or, you can keep a profiler running to capture more details about the error.
April 7, 2010 at 11:52 am
Good idea.
I've tried to recreate this snapshot a few times.
I'll try using profiler next.
James
April 7, 2010 at 1:22 pm
Here is what I pulled from profiler:
Could not bulk load. The sorted column 'Version' is not valid. The ORDER hint is ignored.
The data type for 'version' is timestamp (not null).
I was able to change a timestamp setting in the publisher to not change to binary, recreate the snapshot, and it worked.
Thanks for your help.
April 7, 2010 at 1:46 pm
You're welcome, Appollo. By the way, the timestamp columns are replicated as binary data types by SQL Server replication (by default).
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply