"Terry Robinson"<Terry.Robinson[ at ]State.CO.US> wrote in
news:a814922abe1b4c4b967c274b9c7e0885[ at ]ureader.com:
[Quoted Text] > We have a replicated Access 2002 database with about 80 users
> which uses Internet Synchronization set up using Replication
> Manager. The database ONLY contains data tables and their
> relationships (no queries, forms etc). The master database in on
> a server, the replicas may be on LAN, WAN or VPN via dial-up or
> satellite (some of our users are in remote locations with no high
> speed connection).
All that sounds perfectly proper -- no red flags raised by any of
it.
> We have several computers which report "Invalid http address" when
> they attempt to synchronize. Experiments have shown that
> reinstalling Windows (XP Pro) will fix the problem for a while but
> it shows up again when ArcView mapping software is installed. In
> at least two cases, new laptops with just factory installed
> software have also shown the problem. The only clue we have is
> that permissions to the server may be at fault. Has anyone else
> seen this, or (better yet) discovered a solution?
Have you searched this newsgroup for "Invalid http address" on
Google Groups? I get lots of articles. I would zero in on the
answers from Michael Kaplan first, since he likely offered the best
explanation/solution for this problem.
I have no personal experience because I won't use Internet
replication because of the dependency on IIS.
From the little I read ther,e it looks like a replica farm at each
site is the long-term solution, and fixing the problem requires
shipping a new replica out to replace the ones that have developed
this problem. Not good. On replica farms:
http://trigeminal.com/usenet/usenet006.asp?1033
Remember, the minimum size for a replica farm is just two replicas.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
|