Article ID: 839278 - View products that this article applies to.
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:
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:
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/830839/ )Change in SQL Server 2000 for queued updating subscriptions that use Message Queuing
Article ID: 839278 - Last Review: May 13, 2005 - Revision: 2.4
Contact us for more help