> "Dani" <dani[ at ]vetcontrol.com> wrote in
> news:ef9g7q$90c$1[ at ]emma.aioe.org:
>
> > I have several replica sets with 10 replicas each one in a single
> > machine working since 1999.
> >
> > Two weeks ago I got this error:
> >
> > "3677 Failure to execute the HTTP request to start the internet
> > synchronizer or the internet server.
> > Use Replication Manager to configure internet synchronizer on the
> > internet server."
> >
> > I have restored a backup of the system, even I have config another
> > machine, AND I STILL GOT THIS ERROR.
> >
> > But this error appears sometimes, not always, most times but not
> > always.
> >
> > I have a Firewall and updated norton Antivir.
>
> This sounds like the likely culprit. Have you turned off the
> Firewall to see if that fixes it?
>
> > I'm triying config it with another web server but, I don't know if
> > replicacion works with anything different to IIS or PWS.
> >
> > Anyone knows with other WEB SERVER could I use?
> >
> > I'm woking with Windows NT 4 SP6, Internet Explorer 4 and Windows
> > NT 4.0 Option Pack using IIS FTP and WEB services.
> >
> > I don't have all hotfix instaled, because I don't know if it could
> > be dangerous for replicaction.
> > Is there any essential hotfix for replicaction?
>
> There is the replication security hotfix:
>
>
http://support.microsoft.com/kb/320805>
> You should probably go through the Jet 4.0 FAQ to make sure it's not
> covered there:
>
>
http://support.microsoft.com/?id=282977>
> and, of course, the two Jet 4.0 White Papers, the first on Jet, the
> second on Internet Replication, both available for review here:
>
>
http://support.microsoft.com/?id=190766>
> As to the IIS question, I'm not aware that Internet replication can
> work with any server other than IIS, but the documentation seems to
> hint at the possibility, though offering no instructions for how to
> do it except with IIS.
>
> I wouldn't ever use Internet replication because of the fact that
> all the documentation is oriented for IIS, and I don't consider IIS
> usable in a production environment (i.e., never Internet-facing).
>
> I still think the likely reason is that your Firewall or AV is now
> blocking your web server from loading the synchronizer. You'd
> certainly want it to block such things in general, as there are lots
> of exploits out there that attempt to run executables via HTTP in
> order to compromise your web server. The key is figuring out how to
> allow it to run the synchronizer.
>
> --
> David W. Fenton
http://www.dfenton.com/> usenet at dfenton dot com
http://www.dfenton.com/DFA/