Synchronizer stops unexpectedly "brandonz via AccessMonster.com" <u9878[ at ]uwe> 11.07.2006 06:48:30 I am using access2000 repman & indirect synchronization. Everything works fine for few days. But now the syhchronizer at one site stops unexpectedly. If I manually start it, it just stops & leaves a "faulting application MSTRAN40.exe" event. If I unmanage the current database, the synchronizer can start & keep running. I notice this database has a replica at remote PC, and the dropbox at remote PC can't be accessed sometimes. It could be the main problem that cause the synchronizer to die. I suppose the dead requests in the replica set cause the synchronizer to have error. Does anyone have same experence before? Is there any way to clear out those queued but never finished synchonization requests associated with a replica set? -- Message posted via http://www.accessmonster.com

Re: Synchronizer stops unexpectedly "David W. Fenton" <XXXusenet[ at ]dfenton.com.invalid> 11.07.2006 23:22:18 "brandonz via AccessMonster.com" <u9878[ at ]uwe> wrote in news:63130387ca3c7[ at ]uwe: [Quoted Text] > I am using access2000 repman & indirect synchronization. > Everything works fine for few days. But now the syhchronizer at > one site stops unexpectedly. If I manually start it, it just stops > & leaves a "faulting application MSTRAN40.exe" event. > If I unmanage the current database, the synchronizer can start & > keep running. I notice this database has a replica at remote PC, > and the dropbox at remote PC can't be accessed sometimes. It could > be the main problem that cause the synchronizer to die. I suppose > the dead requests in the replica set cause the synchronizer to > have error. Does anyone have same experence before? Is there any > way to clear out those queued but never finished synchonization > requests associated with a replica set? Empty the dropboxes on both ends. That's the only place it matters. You can't clear out the history list except by setting the replica expiration period to something small, then letting it pass and setting it back to something reasonable. But that can cause lots of *other* potential problems and perhaps leave your replica set hosed, so I'd never do it. Don't worry about the incomplete synchs. What hasn't completed synchronizing will be re-attempted the next time a synch is initiated. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/

Re: Synchronizer stops unexpectedly "brandonz via AccessMonster.com" <u9878[ at ]uwe> 12.07.2006 04:50:28 Thanks David. I cleared all mdb & msg files at both dropbox. But I am still not sure why synchronizer stop when there is a connection problem(Or may be other problem). In indirect synchronization, the synchronizer suppose will wait & try untill the connection is back. Do you ever encounter such error before? I got this problem last time with STI synchronizer 3.5 in another environment using indirect synchronization. I solved that problem by upgrading to Repman 2000. Now, Repman 2000 gave me the same error. haha. -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/Forums.aspx/access-replication/200607/1

Re: Synchronizer stops unexpectedly "David W. Fenton" <XXXusenet[ at ]dfenton.com.invalid> 12.07.2006 22:57:06 "brandonz via AccessMonster.com" <u9878[ at ]uwe> wrote in news:631e8e906a578[ at ]uwe: [Quoted Text] > I cleared all mdb & msg files at both dropbox. > But I am still not sure why synchronizer stop when there is a > connection problem(Or may be other problem). . . . There are dozens of possible reasons, most of them outside of Jet/Replication. > . . . In indirect synchronization, the > synchronizer suppose will wait & try untill the connection is > back. Do you ever encounter such error before? . . . Yes, it's pretty common. > . . . I got this problem last time with > STI synchronizer 3.5 in another environment using indirect > synchronization. I solved that problem by upgrading to Repman > 2000. Now, Repman 2000 gave me the same error. haha. It's normal for synchs to not complete. You just clean up and start over again, and they often complete then. I don't know why. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/

Re: Synchronizer stops unexpectedly "brandonz via AccessMonster.com" <u9878[ at ]uwe> 13.07.2006 01:33:10 [Quoted Text] >It's normal for synchs to not complete. You just clean up and start >over again, and they often complete then. I don't know why. Sorry David, I did not explain clearly. The thing troubles me is not incomplete sync job. Althrough some history sync jobs never finish, a later completed job would sync database well. The problem is now, the syncronizer just exit immediately after it start up. So, the indirect syncronization is totally unusable. I have to use direct synchronization instead. I have Event ID:1000 for application error. It says "faulting module msjet40. dll ...faulting application MSTR40.EXE ..." -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/Forums.aspx/access-replication/200607/1

Re: Synchronizer stops unexpectedly "David W. Fenton" <XXXusenet[ at ]dfenton.com.invalid> 13.07.2006 23:33:50 "brandonz via AccessMonster.com" <u9878[ at ]uwe> wrote in news:632968313ffbb[ at ]uwe: [Quoted Text] >>It's normal for synchs to not complete. You just clean up and >>start over again, and they often complete then. I don't know why. > > Sorry David, I did not explain clearly. The thing troubles me is > not incomplete sync job. > Althrough some history sync jobs never finish, a later completed > job would sync database well. > > The problem is now, the syncronizer just exit immediately after it > start up. So, the indirect syncronization is totally unusable. I > have to use direct synchronization instead. > > I have Event ID:1000 for application error. It says "faulting > module msjet40. dll ...faulting application MSTR40.EXE ..." You'll have to take that up with Microsoft. Is this happening on all machines or just on one or two? -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/

Re: Synchronizer stops unexpectedly "brandonz via AccessMonster.com" <u9878[ at ]uwe> 17.07.2006 02:21:11 some machines only. I may raise it to microsoft. David W. Fenton wrote: [Quoted Text] >>>It's normal for synchs to not complete. You just clean up and >>>start over again, and they often complete then. I don't know why. >[quoted text clipped - 10 lines] >> I have Event ID:1000 for application error. It says "faulting >> module msjet40. dll ...faulting application MSTR40.EXE ..." > >You'll have to take that up with Microsoft. > >Is this happening on all machines or just on one or two? > -- Message posted via http://www.accessmonster.com