none
Error 55012 when running the snapshot. RRS feed

  • Question

  • I'm trying to set up a snapshot replication. When i run the job creating a snapshot I get an error:

    Message
    2019-10-30 13:01:59.57 Microsoft (R) SQL Server Snapshot Agent
    2019-10-30 13:01:59.57 [Assembly Version = 15.0.0.0, File Version = 15.0.1900.25]
    2019-10-30 13:01:59.57 Copyright (c) 2016 Microsoft Corporation.
    2019-10-30 13:01:59.57 The timestamps prepended to the output lines are expressed in terms of UTC time.
    2019-10-30 13:01:59.57 User-specified agent parameter values:
    2019-10-30 13:01:59.57 --------------------------------------
    2019-10-30 13:01:59.57 -Publisher DB100
    2019-10-30 13:01:59.57 -PublisherDB REF3_DB
    2019-10-30 13:01:59.57 -Publication REF3_PDR4
    2019-10-30 13:01:59.57 -Distributor DB100
    2019-10-30 13:01:59.57 -DistributorSecurityMode 1
    2019-10-30 13:01:59.57 -XJOBID 0xA694274CD89FAF418C8B059F22C01B85
    2019-10-30 13:01:59.57 --------------------------------------
    2019-10-30 13:01:59.57 Connecting to Distributor 'DB100'
    2019-10-30 13:01:59.62 Parameter values obtained from agent profile:
    2019-10-30 13:01:59.62 ---------------------------------------------
    2019-10-30 13:01:59.62 -BcpBatchSize 100000
    2019-10-30 13:01:59.62 -HistoryVerboseLevel 2
    2019-10-30 13:01:59.62 -LoginTimeout 15
    2019-10-30 13:01:59.62 -QueryTimeout 1800
    2019-10-30 13:01:59.62 ---------------------------------------------
    2019-10-30 13:01:59.62 Validating Publisher
    2019-10-30 13:01:59.62 Connecting to Publisher 'DB100'
    2019-10-30 13:01:59.64 Publisher database compatibility level is set to 150.
    2019-10-30 13:01:59.64 Retrieving publication and article information from the publisher database 'DB100.REF3_DB'
    2019-10-30 13:01:59.64 [0%] Locking published tables while generating the snapshot
    2019-10-30 13:01:59.65 [0%] The replication agent had encountered an exception.
    2019-10-30 13:01:59.65 Source: Replication
    2019-10-30 13:01:59.65 Exception Type: Microsoft.SqlServer.Replication.ReplicationAgentException
    2019-10-30 13:01:59.65 Exception Message: An unspecified error had occurred in the native SQL Server connection component.
    2019-10-30 13:01:59.65 Message Code: 55012
    2019-10-30 13:01:59.65

    There seems to be no help whith this issue… please can anyone help me. 

    Wednesday, October 30, 2019 2:23 PM

All replies

  • Hi Magnus,

    Are you configuring replication in SQL2019 as a publisher? Also did you track the snapshot agent execution using extended events (probably you can user ERROR Report a well as Attention report + sp_statement starting and sp_Statement_completed events)?

    regards!

    Wednesday, October 30, 2019 6:02 PM
  • I'm configuring the server as both Publisher and distributor. 

    I get the following error from the eventviewer when i run: Microsoft OLE DB Driver for SQL Server: Unable to load msoledbsqlr.rll due to either missing file or version mismatch. The application cannot continue.

    How do i resolve the mismatch?

    Thursday, October 31, 2019 6:46 AM
  • Hi Magnus Leindahl,

    According to your message, you are using SQL server 2019. SQL Server 2019 RC is preview software. It is not publicly supported for operations. Customers who are in the SQL Early Adopter Program, may have support to run SQL Server 2019 RC by special agreement, in consultation with Microsoft.  Please refer to SQL Server 2019 preview release notes. I suggest you use SQL server 2017 to create a snapshot replication.

    >> Microsoft OLE DB Driver for SQL Server: Unable to load msoledbsqlr.rll due to either missing file or version mismatch. The application cannot continue.
    How do i resolve the mismatch?

    If SQL server is 64 bit, your OLE DB Driver is also need 64 bit. If 32 bit, they also need to be  same. You can check your version and then download the match version from here. Please refer to Installing OLE DB Driver for SQL Server.

    Best regards,
    Cathy 

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to  MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Thursday, October 31, 2019 7:47 AM
  • Thanks for the answers, Gonzalo and Cathy. It's nice to see that people want to help! I'll go for the SQL Server 2017 for now.

    I will wait for the Full version of 2019.

    /Magnus

    Thursday, October 31, 2019 11:38 AM
  • Thanks for the answers, Gonzalo and Cathy. It's nice to see that people want to help! I'll go for the SQL Server 2017 for now.

    I will wait for the Full version of 2019.

    /Magnus

    Hi Magnus,

    Thank you for your reply. Using SQL server 2017 is a good choice. In order to close this thread, please kindly mark useful replies as answers. By doing so, it will benefit all community members who are having this similar issue.  Your contribution is highly appreciated. 

    In addition, if you have another questions, please feel free to ask.
    Best regards,
    Cathy 


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to  MSDN Support, feel free to contact MSDNFSF@microsoft.com



    Friday, November 1, 2019 5:31 AM