SQL Server Snapshot Replication error 22018 RRS feed

  • Question

  • I am trying to get snapshot replication between two MSSQL servers to work but am receiving errors. Any help will be much appreciated!

    My setup: Publisher/Distributor: SQL 2008 R2 Subscriber: SQL 2016

    I am just trying it with a simple test table named Cars containing:

    Car_ID   Car_Name
    1   Hummer
    2   Porsche
    3   Tesla
    4   Bently
    5   Lotus Elise
    6   Mini

    In the Replication Monitor I get the following errors:

    Error messages: The process could not bulk copy into table '"dbo"."Cars"'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20037) Get help: http://help/MSSQL_REPL20037 metadata query failed Invalid character value for cast specification (Source: MSSQLServer, Error number: 22018) Get help: http://help/22018 Unspecified error

    Thursday, August 11, 2016 6:30 PM


All replies

  • Refer the link

    Please click Mark As Answer if my post helped.

    Friday, August 12, 2016 8:25 AM
  • Hi NStewart_PMAP,

    I’m writing to follow up with you on this post. Was the issue resolved? If you issue has resolved, I’d like to mark this issue as "Answered". Please also feel free to unmark the issue, with any new findings or concerns you may have.

    If you have any other questions, please let me know.

    Friday, August 26, 2016 1:49 AM
  • I had exactly the same problem replicating from SQL Server 2008 R2 to SQL Server 2016.

    It seems that it is a specific problem with replication from 2008 R2 to 2016. The same replication setup works fine from SQL Server 2012 to SQL Server 2016.
    Another workaround I found is to set the compatibility level of the subscriber database to 120 (instead of 130)

    I guess that there is a problem with native client 10 and the way it gathers the meta data of the destination table.



    • Proposed as answer by Prasenjit Gupta Wednesday, January 31, 2018 6:44 PM
    Thursday, April 20, 2017 3:25 PM
  • Fixed my issue Wolfgang.  Thanks!
    Tuesday, September 18, 2018 9:30 PM
  • After 14 hours trying to find the problem and prayer, I was directed to this!

    Thank you!

    Monday, April 22, 2019 5:06 AM