Share via

Transactional Replication

Cindy See 206 Reputation points
2022-12-09T02:00:06.553+00:00

Publication, distribution and Subscription are created successfully with no errors.
I encountered errors during runtime of the push subscription job, the system will show that it cannot connect to the subscriber. If I create a pull subscription job during runtime, the system said that it cannot connect to the distributor. May I know what could be the issue? Should I use other kind of authentication method to setup the replication instead of using Windows authentication?

Background information
I created only 1 window local account named as snapshot account on each server. (publisher and distributor on same server) and subscriber(running on virtual machine on another server remotely).
I did not create 3 accounts instead such as log account,distribution account, snapshot account
These two servers are connected to different domains remotely.

SQL Server Integration Services
SQL Server Migration Assistant
SQL Server Migration Assistant

A Microsoft tool designed to automate database migration to SQL Server from Access, DB2, MySQL, Oracle, and SAP ASE.

SQL Server | Other

8 answers

Sort by: Most helpful
  1. jose de jesus 141 Reputation points
    2022-12-15T11:11:48.607+00:00

    This is the UNC for the shared folder where replication files are store . Make sure that the account running replication jobs has access to this folder.
    You can test it by accessing the share from the distribution server host


  2. Cindy See 206 Reputation points
    2022-12-15T10:45:01.833+00:00

    Hi,
    I encountered another error "The process could not read file'\hostname\repldata\unc\tt1_2pre' due to OS error 53" appears in sessions of the distribution agent area under distributor to subscriber history tab of the pull subscription.
    Any advice?


  3. Cindy See 206 Reputation points
    2022-12-14T04:36:26.757+00:00

    Hi all,
    I managed to resolve this error "The process could not connect to Distributor hostname" by creating alias at the sql configuration manager.

    Now I have another error, "The job failed. The Job was invoked by User XXX. The last step to run was step 1 (Run agent.)." when I clicked on the view synchronization status of the pull subscription.

    Question 1) When I selected a snapshot replication, can I create a pull subscription?
    Question 2) May I check SQL Server Agent should be started by which account?
    Question 3) What could be the possible causes of this error?

    Thanks.


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.