Snapshot Agent Fails to Bulk Copy: Datetime Field Overflow

  •  

    I am attempting to use Merge Replication with a push subscription on two SQL Server 2000 (Standard) servers.  Server A is the publisher and distributor.  Server B is the subscriber.  The process starts up the snapshot agent to produce a copy of the master, but fails when it hits one table.  The agent reports that it:

    The process could not bulk copy out of table '[dbo].[TABLENAMEHERE]'.  

    Double clicking on the error shows that the error is reported as

    Datetime field overflow

    (Source: ODBC SQL Server Driver (ODBC); Error number: 0)

    So I deleted all of the data in the table thinking that perhaps we had a data problem.  Repeating with an empty table, the same error was reported.

    If anyone has some insight into this problem, I would appreciate hearing your ideas.  Thanks!

  • Just Try the following in the posted order

    • - do you have enough free space (and Permissions) in the target drive?
    • - Antivirus Software not scanning/target folder
    • - Try changing snapshot format from native to chararcter mode
    • - Try to re-apply SP3 (check the version of sqlsrv32.dll and odbcbcp.dll on your machine. The version of these two files needs to match which should the sp3 version 2000.81.9031.14.)
    • - have you runned the mdac version check tool to make sure it converge to the same on Publ. and Subs.

     

    hth


    * Noel

  • A few additional important points:

    - Plenty of hard disk space. 

    - Permissions should not be an issue:  The replication was working for a couple months.  Modifications to the database were made (additional tables), and replication then began having problems.

    -  Just applied SP3 yesterday (although it hadn't been applied originally when replication was working properly) and received the error again.  (Haven't yet checked the versions you mention above.)

    - Removed the table on which the snapshot was choking from the replication process, and then an other table was reported as the error.  Removed that one from the replication, and still another was reported as the error--this table was one that had been in place when replication had been working.

    - Antivirus software IS running, but was also running when the replication was running successfully.

    - Haven't checked mdac yet, but the servers are identical from hardware to configuration.

  • and what about changing snapshot to CHARACTER mode instead of native ?

     


    * Noel

  •  

    Just finished checking that.  Same problem.

  •  

    Machine 1:  SQLSRV23.DLL   Version  =  2000.85.1117.0

    Machine 2:  SQLSRV23.DLL   Version  =  2000.85.1117.0

     

  • can you manually bcp that table out?

     


    * Noel

  •  

    Yes.

  • Tried eliminating tables from the replicated list.   First tables with the most columns were not included:  didn't help.  Second tables with foreign keys were not included:  didn't help.  Each time an affected table is removed, another one take's it's place, but always the same error.

    Am wondering if this could somehow be related to max snapshot file size... Like maybe the copy goes until some buffer is filled.  is there such a thing? 

     

  • Charles,

    The more I look to it the more it looks as a diskspace problem.

    you said

    >>Each time an affected table is removed, another one take's it's place, but always the same error. <<

    Are you saying is always:

    Datetime field overflow

    (Source: ODBC SQL Server Driver (ODBC); Error number: 0)

    BTW  You must compare the versions between sqlsrv32.dll and dbcbcp.dll  not just the version of one of them!

    hth


    * Noel

  • I am getting the same error too, after disabling a working replication, moving the physical location of the source databases, and reconfiguring replication.  When I checked the driver versions, I got the following:

    odbcbcp.dll = 2000.85.1025.0

    SQLSVR32.dll = 2000.85.1117.0

    I know these need to match, but what is the best way to "fix" the versions?  I tried renaming the SQLSVR32.dll and rerunning MDAC 2.8 install (per MBS suggestion) but no luck.... 

Viewing 11 posts - 1 through 11 (of 11 total)

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