A Microsoft platform for building enterprise-level data integration and data transformations solutions.
I am using one windows local account(with the same name) for connecting publisher, distributor and subscriber.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
A Microsoft tool designed to automate database migration to SQL Server from Access, DB2, MySQL, Oracle, and SAP ASE.
I am using one windows local account(with the same name) for connecting publisher, distributor and subscriber.
Hi Seeya,
May I check with you, how do I use SQL Server Authentication instead of Windows Authentication as both databases are connected to different domains and active directory controller remotely?
Do you have any step by step guide for setting snapshot data replication using SQL Server Authentication instead of using Windows Authentication(impersonate account)?
Thanks.
Hi @Cindy See ,
Please verify that your agent accounts have the necessary permissions listed in the section Permissions That Are Required by Agents in Replication Agent Security Model.
https://learn.microsoft.com/en-us/sql/relational-databases/replication/security/replication-agent-security-model?redirectedfrom=MSDN&view=sql-server-ver16
Best regards,
Seeya
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi Erland and Seeya,
I encountered this error at the last status message "The process could not connect to Distributor hostname." when I clicked on the view synchronization status of the pull subscription.
Please advise.
Thanks.
From Cindy
Hi @Cindy See ,
the system will show that it cannot connect to the subscriber.
Is there a specific error reported?
In order to be able to solve the problem more effectively, we would like you to provide some details.
Best regards,
Seeya