Applies to: SQL Server 2019, SQL Server 2017, SQL Server 2016, SQL Server 2014
Symptoms
Assume that you create a pull subscription to a merge publication. After enabling the synchronization with Windows Synchronization Manager, there's no subscription listed in the Sync Center (mobsync.exe) of the subscriber.
Workaround
Note: This workaround applies only to SQL Servers with a single instance.
Important: Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration.
Here's how to work around this issue:
-
In the search box on the taskbar, type regedit, then select Registry Editor (Desktop app) from the results to open Registry Editor in Windows 10.
-
Locate and select the registry subkey:
HKLM\Software\Microsoft\Windows\CurrentVersion\SyncMgr\Handlers\{FFAADE58-9A14-45F3-A497-E969A64F09C7}. -
Rename the subkey name depending on the SQL Server version as follows:
SQL Server Version Registry Handler Value SQL Server 2014 D6133761-E626-4DF7-90F6-7DDD8FCCB926SQL Server 2016 E828F4BF-6E5C-4549-A3BA-CF53F6A60819SQL Server 2017 C96C286D-DFC0-4CF0-9CF8-7D582094D263SQL Server 2019 B1544C19-71BD-417C-8DE2-430A0CDCEA06
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors (upstream author metadata: aartig13). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
