Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Unexpected eof encountered in bcp data file...msmerge_genhistory90.bcp
1 view
Skip to first unread message
jim.s...@honeywell.com
Oct 3, 2008, 11:17:02 PM10/3/08
to
Creating a new merge replication on SQL 2005 and the snapshot fails.
When I run the bcp command from the command prompt it returns the
unexpected EOF. The source file is msmerge_genhistory90.bcp and the
destination is the msmerge_genhistory table on the subscriber. The
BCP file does exist in the specified folder. I cannot see the table
on the subscriber, but a select on that table does return zero rows.
When I run the bcp command from the command prompt it returns the
unexpected EOF. The source file is msmerge_genhistory90.bcp and the
destination is the msmerge_genhistory table on the subscriber. The
BCP file does exist in the specified folder. I cannot see the table
on the subscriber, but a select on that table does return zero rows.
Blind Squirrel
Oct 4, 2008, 10:02:13 AM10/4/08
to
Paul Ibison
Oct 6, 2008, 4:59:04 AM10/6/08
to
Jim,
how big is the bcp file?
Also, is there a difference between the collations on the publisher and
subscriber?
Rgds,
Paul Ibison (www.replicationanswers.com)
how big is the bcp file?
Also, is there a difference between the collations on the publisher and
subscriber?
Rgds,
Paul Ibison (www.replicationanswers.com)
Paul Ibison
Oct 6, 2008, 11:45:02 AM10/6/08
to
Jim @ Honeywell Security
Oct 6, 2008, 2:06:56 PM10/6/08
to
On Oct 6, 1:59 am, Paul Ibison <Paul.Ibi...@ReplicationAnswers.Com.
Collations are the same on both servers "SQL_LATIN_GENERAL_CPI_CI_AS"
The bcp file is 8kb.
Thanks for the assistance Paul.
Jim @ Honeywell Security
Oct 7, 2008, 6:23:37 PM10/7/08
to
On Oct 6, 11:06 am, "Jim @ Honeywell Security"
SQL servers were RTM. Updated to SP2 on all servers. Problem did not
reoccur.
0 new messages