After you install Microsoft Windows XP Service Pack 2 on a computer that is configured as a distributor, if you try to synchronize data from a subscriber that is configured on a remote
computer, you may notice that the changes that are made in the subscriber
database are not updated to the publisher database. This problem occurs when both the
following are true:
- The publication and the subscription of the replication are
configured for queued updating.
- Message Queuing (also known as MSMQ) is used to queue the
transactions at the remote subscriber.
This problem may also
occur after you install Windows XP SP2 on computers that are configured as a publisher or a subscriber.
This problem occurs because Windows Firewall is blocking the Message Queuing service.
Typically, messages that correspond to the changes in the remote subscriber are posted to a queue that is local to the remote subscriber. The messages are then transmitted by the Message Queuing service to a queue that is local to the computer that is configured as the distributor.
By default, when you install Microsoft Windows XP Service Pack 2, Windows Firewall is turned on. Because Windows Firewall is blocking the Message Queuing service, the messages that correspond to the changes in the remote subscriber will not be transmitted.
To work around this problem, you must add the Message Queuing
service as an exception in the Windows Firewall configuration on the computer
that is running Windows XP SP2. To do this, follow these steps:
- Click Start, and then click Run.
- In the Run dialog box, type Firewall.cpl, and then click OK.
- In the Windows Firewall dialog box, click
the Exceptions tab.
- On the Exceptions tab, click Add Program.
- In the Add a Program dialog box, click the
Browse button, and then locate the Mqsvc.exe file. By default, the file is stored in the following folder:
- Double-click the Mqsvc.exe file.
- In the Add a Program dialog box, click
Programs and Services, click to select the Mqsvc option, and then click OK.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Change in SQL Server 2000 for queued updating subscriptions that use