Long-winded, but I want to provide a complete background before asking
a specific question...
My indirect sync setup has worked fine for several years until about 6
weeks ago. It's pretty basic -- two hubs with replica farms
communicate over a full-time VPN. Both hubs have full read-write
access to each other's dropbox -- confirmed by creating, editing, and
deleting text files in each other's dropbox. The managed replicas are
NOT in shared folders, and are invisible to the other hub.
I can open Windows Explorer and type the UNC of the dropbox, and
navigate directly to the appropriate dropbox.
The sync's now fail every time. On the history at one hub (DELOUP),
they appear as "Synchronization failure: Direct. No suitable
synchronizer". A snippet from the synchronizer.log follows:
Time = 2008-03-28 09:14:38 AM
Log Type = Read message
Result = Success
Synchronizer = FS
Dropbox = \\DELOUP\DROPBOX
Sender Synchronizer = {8B1430F9-9BAD-4A1F-B14E-B42FBDF37520}
Exchange ID = {27F3CD1D-59D4-4CF4-B56D-F9DF4AE6BC01}
Message Type = 8
Time = 2008-03-28 09:14:38 AM
Log Type = Start exchange
Replica = C:\ReplicaFarm\AdmanBE-EDFarm032.mdb
Exchange ID = {27F3CD1D-59D4-4CF4-B56D-F9DF4AE6BC01}
Initiated Locally = No
Exchange Type = 4
Sender Synchronizer = {8B1430F9-9BAD-4A1F-B14E-B42FBDF37520}
Sender ReplicaID = {B64C1179-F2A9-4320-9149-CC42B4BDEF31}
Synchronizer = FS
Time = 2008-03-28 09:14:39 AM
Log Type = Write message
Result = Failure
Reason = Invalid destination path
Replica = C:\ReplicaFarm\AdmanBE-EDFarm032.mdb
Synchronizer = FS
Dropbox = \\KECHIKA\dropbox
Destination Synchronizer = {8B1430F9-9BAD-4A1F-B14E-B42FBDF37520}
Exchange ID = {27F3CD1D-59D4-4CF4-B56D-F9DF4AE6BC01}
Message Type = 8
Time = 2008-03-28 09:14:39 AM
Log Type = Close exchange
Replica = C:\ReplicaFarm\AdmanBE-EDFarm032.mdb
Exchange ID = {27F3CD1D-59D4-4CF4-B56D-F9DF4AE6BC01}
Result = Failure
Time = 2008-03-28 09:14:39 AM
Log Type = Cancel exchange
Replica = C:\ReplicaFarm\AdmanBE-EDFarm032.mdb
Exchange ID = {27F3CD1D-59D4-4CF4-B56D-F9DF4AE6BC01}
Reason = Invalid destination path
Time = 2008-03-28 09:14:39 AM
Log Type = Process message error
Reason = Invalid destination path
Sender Synchronizer = {D271B200-BDD1-11D7-B466-000475E78E1A}
Exchange ID = {27F3CD1D-59D4-4CF4-B56D-F9DF4AE6BC01}
Destination Synchronizer = {8B1430F9-9BAD-4A1F-B14E-B42FBDF37520}
Message Type = 8
Time = 2008-03-28 09:14:39 AM
Log Type = Write message
Result = Failure
Reason = Invalid destination path
Replica =
Synchronizer = FS
Dropbox = \\KECHIKA\dropbox
Destination Synchronizer = {8B1430F9-9BAD-4A1F-B14E-B42FBDF37520}
Exchange ID = {27F3CD1D-59D4-4CF4-B56D-F9DF4AE6BC01}
Message Type = 3
On the other hub (KECHIKA), the sync's fail in a different mode --
they show as "in progress" in the RM history. Furthermore, when I
check the partner's Dropbox after initiating a sync, I would expect to
find a .MSG file, but none are present.
Here is a snippet of KECHIKA's synchronizer log file:
Time = 2008-03-28 07:15:10 AM
Log Type = Start exchange
Replica = D:\apps\AccessOnTheWeb\Farm\admanbe-WDFarm005.mdb
Exchange ID = {27F3CD1D-59D4-4CF4-B56D-F9DF4AE6BC01}
Initiated Locally = Yes
Exchange Type = 4
Destination Synchronizer = {D271B200-BDD1-11D7-B466-000475E78E1A}
Destination ReplicaID = {74659921-52E7-11DB-B467-000475E78E1A}
Synchronizer = YOUPICK
Time = 2008-03-28 07:15:10 AM
Log Type = Trying Trans****t for exchange
Synchronizer = DIRECT
Time = 2008-03-28 07:15:10 AM
Log Type = Start exchange
Replica = D:\apps\AccessOnTheWeb\Farm\admanbe-WDFarm005.mdb
Exchange ID = {27F3CD1D-59D4-4CF4-B56D-F9DF4AE6BC01}
Initiated Locally = Yes
Exchange Type = 4
Destination Synchronizer = {D271B200-BDD1-11D7-B466-000475E78E1A}
Destination ReplicaID = {74659921-52E7-11DB-B467-000475E78E1A}
Synchronizer = YOUPICK
Time = 2008-03-28 07:15:10 AM
Log Type = Trying Trans****t for exchange
Synchronizer = FS
Time = 2008-03-28 07:15:10 AM
Log Type = Sending message
Replica = D:\apps\AccessOnTheWeb\Farm\admanbe-WDFarm005.mdb
Destination Synchronizer = {D271B200-BDD1-11D7-B466-000475E78E1A}
Message Type = 8
Time = 2008-03-28 07:15:27 AM
Log Type = Write message
Result = Success
Replica = D:\apps\AccessOnTheWeb\Farm\admanbe-WDFarm005.mdb
Synchronizer = FS
Dropbox = \\DELOUP\DROPBOX
Destination Synchronizer = {D271B200-BDD1-11D7-B466-000475E78E1A}
Exchange ID = {27F3CD1D-59D4-4CF4-B56D-F9DF4AE6BC01}
Message Type = 8
This log seems to indicate that the .msg file has been created
successfully, yet it does not appear in the dropbox.
So it appears to me that the two hubs cannot exchange information via
each other's dropbox, yet I can manually create and edit textfiles in
the same folders.
Our company has recently undergone a merger with two other
organizations, and new IT people are involved. I used to be aware of
router configurations, but that process is now a "black box" handled
by faceless people somewhere else.
Now to the question -- is it possible that the router over which the
VPN is running has been configured to block certain programs (ie, the
Jet synchronizer) from creating/sending files to the dropboxes? The
local IT guy suspects that one of the "new guys" did indeed make some
router configuration changes, but I don't know who or what... I have
exhausted all my other possibilities about what's causing the failure,
and I need to take some hard information to the IT department
Thanks for reading.
|
