Jet indirect/internet replication requries the Jet synchronizer....

by Michael S. Kaplan, published on 2005/08/11 03:30 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2005/08/11/450249.aspx

Approximately 1.5 lives ago (or two to three versions of Office ago -- pick your own preferred meaurement method), I was something of a guru when it came to Jet replication -- for Jet 3.0x, 3.5x, and 4.0.

I was doing a lot of consulting for companies that amounted to salvaging data from replica sets with problems, training, helping people set stuff up right, and so on. All very quick, small jobs. I even wrote a whole bunch of tools -- for the fixing, for the training, for the long-term maintenance. And those tools were designed to call undocumented, exported functions from the Jet DLLs. I asked for and received permission to release some of these tools provided I did not charge for them (which was fine, I was not going to charge anyway).

That is all background. :-)

One of the most important of these tools was the TSI Synchronizer, a programmatic replacement for Microsoft's Replication Manager (which has a user interface that many people found to be less than intuitive).

Now note what I said here -- it is a replacement for Replication Manager, and nothing else. It is not a replacement for the Jet Synchronizer, of the Jet Internet Synchronizer. You must have those items to do indirect an/or internet synchronizations. If you don't have them, you may find yourself unable to perform sync operations in any case where you need that synchronizer process running on your machine.

Now the Jet Synchronizer (which is packaged with the Microsoft Replication Manager), is not available currently, for reasons that I have not yet been able to completely fathom. It is a different set of people in a different group in a different division of Microsoft, and I am in no way offended that they do not check with me prior to making decisions. :-)

But out in the newsgroups a bunch of people are reportedly claiming that the TSI Synchronizer is a replacement for the Jet Synchronizer, rather than a wrapper around it. Hopefully they can be pointed here so that they do not keep trying to make those claims....

# Richard on 12 Aug 2005 6:49 AM:

You were mentioned, complimentarily, on Joel's blog.

# Michael S. Kaplan on 12 Aug 2005 5:47 PM:

Hi Richard --

Yep, saw that (cf: http://blogs.msdn.com/michkap/archive/2005/08/10/449909.aspx#450307 and discussion).

# Adri on 17 Sep 2005 6:56 AM:

I had a look at TSI Synchronizer, it's great!
I have a problem with the Synchronizer. Is it possible to load it as a service on Windows XP/Windows 2000? I have tried FireDaemon Lite, but when I run the Replication Manager it gives an error "A system error has occured or your swap file has reached its limit" Are there parameters that must be specified?

TIA

# Michael S. Kaplan on 17 Sep 2005 9:57 AM:

Hi Adri -- Running either the TSI Synchronizer or the Jet Synchronizer as a service is untested, unsupported, and not recommended....
Please consider a donation to keep this archive running, maintained and free of advertising.
Donate €20 or more to receive an offline copy of the whole archive including all images.

go to newer or older post, or back to index or month or day