none
Transactional Replication - Snapshot Agent can not start when using remote distributor RRS feed

  • Question

  • Hi everyone,

    i created a transactional replication (SQL Server 2019) with two different servers.

    there are in different domain.

    Server 1 should only be the Publisher.
    Server 2 should be the Distributor and the Subscriber.

    In server2.  I configured the distributor and added server1's ip and server name as publisher


    In server1. I finished New Publication settings. Main steps as follows:

    using server2 ip as distributor.

    using SQL Server Agent  in Agent Security settings


    but i can't start Snapshot Agent and Log Reader Agent..

    errors:

    why?

    Wednesday, July 1, 2020 12:34 PM

Answers

  • Hi huisky,

    It is likely the replication agent process account does not have the required permissions and/or you are trying to replicate across untrusted domains.

    Replication across non-trusted domains or workgroups can be done using Windows Authentication by configuring pass-through authentication.

    Create a local Windows account on both the Publisher and Subscriber that has the same username and password. Use this account for the replication agent process account and have the connections to the publisher, distributor, and/or subscriber impersonate this account. Ensure the account has the permissions required in Replication Agent Security Model.

    Please refer below links which may be helpful:

    Replication between two different domains

    Is replication possible on two different domains?

    Best regards,

    Melissa

    -------------------------------------------

    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, July 2, 2020 6:31 AM

All replies

  • Is your Distribution database is up and working good ? Are you able to connect to Publisher server from Distribution server using SSMS ?
    • Edited by DBA_Atul Wednesday, July 1, 2020 12:59 PM .
    Wednesday, July 1, 2020 12:58 PM
  • I am sure they able to connect with each other
    Wednesday, July 1, 2020 1:14 PM
  • Hi huisky,

    I created one transactional replicaition using similar situation with you but could not reproduce the same error.

    According to the error message in View Snapshot Agent Status, it looks like a connection issue.

    Please follow below steps to troubleshoot on both servers and check whether it works:

    1. Validate the server name and instance name, and make sure the service is running.
    2. TCP/IP is enabled in SSCM and have the correct IP address and port.
    3. Make sure SQL Browser service is running on the server.
    4. If firewall is enabled on the server, you need to put sqlbrowser.exe and/or UDP port 1434 into exception.

    Please refer below links for more details:

    Troubleshoot connecting to the SQL Server Database Engine

    A network-related or instance-specific error occurred while establishing a connection to SQL Server

    Best regards,

    Melissa

    -------------------------------------------

    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, July 2, 2020 2:29 AM
  • This looks like a name resolution error. Your snapshot agent is unable to find your Distributor/Publisher. From your distributor verify you can connect to your publisher.
    Thursday, July 2, 2020 3:31 AM
    Moderator
  • 1.the computer name is also the sqlserver instance name, sqlserver service is running ok

    2.the firewall is closed, they can connect with each other using ip

    3.SQL Browser service is running

    in publisher server

    in distributor server

    mark: two machine are in different domain..


    • Edited by huisky Thursday, July 2, 2020 6:29 AM
    Thursday, July 2, 2020 5:28 AM
  • This looks like a name resolution error. Your snapshot agent is unable to find your Distributor/Publisher. From your distributor verify you can connect to your publisher.

    distributor can connect to publisher using ip..

    Is it should be connect with each other using instance name? but they are in public network,it is imposible

    Thursday, July 2, 2020 5:33 AM
  • Hi huisky,

    It is likely the replication agent process account does not have the required permissions and/or you are trying to replicate across untrusted domains.

    Replication across non-trusted domains or workgroups can be done using Windows Authentication by configuring pass-through authentication.

    Create a local Windows account on both the Publisher and Subscriber that has the same username and password. Use this account for the replication agent process account and have the connections to the publisher, distributor, and/or subscriber impersonate this account. Ensure the account has the permissions required in Replication Agent Security Model.

    Please refer below links which may be helpful:

    Replication between two different domains

    Is replication possible on two different domains?

    Best regards,

    Melissa

    -------------------------------------------

    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, July 2, 2020 6:31 AM
  • Hi huisky,

    Could you please provide any update? Thanks.

    Best regards,

    Melissa

    -------------------------------------------

    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, July 3, 2020 7:07 AM
  • Hi huisky,

    Could you please provide any update? Thanks.

    Best regards,

    Melissa

    -------------------------------------------

    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

          I have a new problem when configuring pass-through authentication:

           https://social.technet.microsoft.com/Forums/zh-CN/c71c2ecd-2b79-4d7d-a5b3-c72ef2f157cf/can-not-join-the-domain-controller?forum=winserverDS

    Saturday, July 4, 2020 1:58 AM
  • Hi huisky,

    Good to hear that you have fixed the pass-through authentication issue.

    If you still face some issues with replication, please update here with more details.

    In order to close this thread, please kindly mark helpful replies or your own reply as answers. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.

    Best regards,

    Melissa

    -------------------------------------------

    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

    Monday, July 6, 2020 1:16 AM