Snapshot Replication

  • Hi Guys,

    I am in the middle of an upgrade to SQL server 2012 from 2005, however we want to keep one of our server on SQL 2005 as it has a Database published as a Snapshot replication.

    My Question is are we able to do a Push of the Published database into one of our SQL 2012 server ? A pull of the data as a Subscriber works from the SQL 2012 server, however doing a push to the same subscriber SQL 2012 server from the 2005 server does not work.

    Main message Error: 14151, Severity: 18, State: 1.

    I have tried to set the agents with the same Domain account but still got the same error, so just wondering if the version is the issue here.

    Thanks

  • I believe there is an issue with your Log Reader Agent (you probably already know this) - it could be because something is blocking it on the publisher so check there...

    Have you tried to re-initialize the 2012 subscription?

    ______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience

  • MyDoggieJessie (3/12/2014)


    I believe there is an issue with your Log Reader Agent (you probably already know this) - it could be because something is blocking it on the publisher so check there...

    Have you tried to re-initialize the 2012 subscription?

    Thanks for the reply, yes i have re-initialize the 2012 subscription, we have tried all sorts with this, but i found a blog which said this that the alias could be the issue as they are not the same. The Blog seems to suggest you cannot push from a 32bit to a 64bit platform unless you create identical alias in both 32bit and 64bit “SQL Native Client 10.0 Configuration” panes, however the issue now is that i am not able to test this as my install only has a SQL Native for 32bit.

    http://blogs.msdn.com/b/repltalk/archive/2010/04/26/distribution-agent-fails-with-error-locating-server-instance-specified-xffffffff.aspx

Viewing 3 posts - 1 through 2 (of 2 total)

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