Article ID: 839278 - Last Review: May 13, 2005 - Revision: 2.4 BUG: The changes in a remote subscriber are not updated to the publisher for a queued updating replication that uses Message Queuing on a computer that is running Windows XP Service Pack 2SYMPTOMSAfter 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:
CAUSEThis 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. WORKAROUNDTo 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:
REFERENCES
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
830839
(http://support.microsoft.com/kb/830839/
)
Change in SQL Server 2000 for queued updating subscriptions that use
Message Queuing
| Article Translations
|
Back to the top
