locked
Error in configuring subscription for merge replication RRS feed

  • Question

  • When i try to configure subscription for the merge replication, i get the error message as
    (But subscription get completed successfully). I click the view detail in Replication monitor it display error like this.

    Error messages:
    The process could not connect to Subscriber 'SOFTENGER'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20084)

    Login failed for user 'TESTSOFTENGER\SOFTE$'. (Source: MSSQLServer, Error number: 18456)

    The subscription to publication 'MergeOperation' could not be verified. Ensure that all Merge Agent command line parameters are specified correctly and that the subscription is correctly configured. If the Publisher no longer has information about this subscription, drop and recreate the subscription.  (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201019)


    Regards,
    RM Thirunavukkarasu
    www.thiruna.blog.com
    Thursday, December 17, 2009 4:49 AM

Answers

  • The error 18456 is generic login failure message .“The key to the message is the 'State' which the server will accurately set to reflect the source of the problem.” ,please refer the error logs to find the detailed error message information  .Please refer the following article published by lekss .

    http://sql-articles.com/articles/troubleshooting/troubleshooting-login-failed-error-18456  

    Refer the following links please 

    "http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx" "MSDN article"
    http://sql-articles.com/articles/troubleshooting/troubleshooting-login-failed-error-18456  


    --------------
    Thanks,Suhas V 

    Thursday, December 17, 2009 5:10 AM
  • It looks like your merge agent is unable to logon to your subscriber. Ensure the account TESTSOFTENGER\SOFTE$' is in the dbo role on the subscriber, in the subscription database and if a distribution database exists there, the dbo_role there as well.

    looking for a book on SQL Server replication? http://www.nwsu.com/0974973602.html looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941
    Saturday, December 19, 2009 1:28 PM
    Answerer
  • Permission Issue.Check  if user exist at the subscriber and have proper permission to access the  database.


    Mohd Sufian www.sqlship.wordpress.com Please mark the post as Answered if it helped.
    Monday, December 21, 2009 12:12 PM

All replies

  • The error 18456 is generic login failure message .“The key to the message is the 'State' which the server will accurately set to reflect the source of the problem.” ,please refer the error logs to find the detailed error message information  .Please refer the following article published by lekss .

    http://sql-articles.com/articles/troubleshooting/troubleshooting-login-failed-error-18456  

    Refer the following links please 

    "http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx" "MSDN article"
    http://sql-articles.com/articles/troubleshooting/troubleshooting-login-failed-error-18456  


    --------------
    Thanks,Suhas V 

    Thursday, December 17, 2009 5:10 AM
  • It looks like your merge agent is unable to logon to your subscriber. Ensure the account TESTSOFTENGER\SOFTE$' is in the dbo role on the subscriber, in the subscription database and if a distribution database exists there, the dbo_role there as well.

    looking for a book on SQL Server replication? http://www.nwsu.com/0974973602.html looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941
    Saturday, December 19, 2009 1:28 PM
    Answerer
  • Permission Issue.Check  if user exist at the subscriber and have proper permission to access the  database.


    Mohd Sufian www.sqlship.wordpress.com Please mark the post as Answered if it helped.
    Monday, December 21, 2009 12:12 PM
  • Configure the both servers  sql and agent services (log on) with domain services account and restart the both sql servers services and check, it should work.
    • Proposed as answer by Subhash GGN Thursday, November 13, 2014 7:15 AM
    • Edited by Subhash GGN Thursday, November 13, 2014 7:16 AM edit
    Thursday, November 13, 2014 7:00 AM