psiess
New Member
- Messages
- 1
- Reaction score
- 0
- Points
- 1
Our Config Manager configuration has 1 primary and 5 secondary servers. We had a problem with the primary server database and had to restore from a backup that was about 10 hours old. I followed the post-move instructions from your article about moving the database (https://www.prajwaldesai.com/move-sccm-database-to-another-drive/) and did the alter database Trustworth and changedbowner steps. After that, I was able to connect to the primary server using the console and everything looked ok.
However, since the restore, I cannot get SQL replication to work consistently. If I run the Replication Link Analyzer, syncing on that link will start and work for one cycle. After that, the primary will continue to send updates but the secondary stops sending updates and the link status goes to failed.
I'm stuck. I feel like forcing each secondary to initialize SQL replication might solve the problem but I can't find a way to do that.
However, since the restore, I cannot get SQL replication to work consistently. If I run the Replication Link Analyzer, syncing on that link will start and work for one cycle. After that, the primary will continue to send updates but the secondary stops sending updates and the link status goes to failed.
I'm stuck. I feel like forcing each secondary to initialize SQL replication might solve the problem but I can't find a way to do that.
