Transactional Replication

  • Recently stood up a 2022 Enterprise server. Have 8 publications with subscriptions on a SQL 2019 server for reporting purposes.

    7 of the publications work as expected, the 8th does the snapshot, but fails when populating the subscriber. It fails on the same table/file every time and moves on to the next file if I drop the other from the publication. The failure is an invalid EOF.

    The replication worked fine on the previous server and as I mentioned earlier, the other publications work well.

    The files are being written to a local SSD. The server has 600GB of RAM, and plenty of cores.

    Any thoughts

    Thanks

    Kirk

  • Is SSRS giving you an error message? If so, screenshot please. Try updating the DataSource on ssrs for the failed report.

    • This reply was modified 3 weeks, 3 days ago by Tav29.
  • Strange. All subscribers same version? Same collation?

  • Everything is exactly the same. Driving me crazy

  • Not sure if my email replies are getting posted to this thread or not.

    SSRS is unaware of any issues.

    One thing I left out, my apologies. All the publications and subscriptions were created from a script generated on a 2019 server then executed on the 2022 box.

    LI've also created a subscription on the publication server and it failed with the same error.

  • So I killed off all replication and brought it all back. Same thing again. All publications seem to be working except the same one. This is crazy.

  • Finally got it working. It appears the script that I had to build out the subscriptions had a flaw in it. Had to reconfigure them by hand. Thanks all

  • What was the flaw in teh script?

    Also, FTI, SSRS is SQL Server Reporting Services to most people. Replication is just replication.

  • The only difference I'm seeing thus far is the @schema_option in the call to sp_addarticle. The original script has 0x00000000080350DF whereas the new script has 0x000000000803509F.

  • That's interesting. Strange that it would be different? I assume you did all this yourself on SSMS, so no version difference there.

  • This was removed by the editor as SPAM

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

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