Delete Replication History "Jesse" <nospam[ at ]nospam.com> 6/6/2007 7:28:34 PM Several months ago while testing daylight savings, the date and time on server was set ahead to November to test daylight savings. A scheduled replication ocurred and shows up in the history of each replica with a November date. The hourly scheduled replication now fails to happen and I believe this is because it sees a "November date as the most recent and does not run. Is there a way to clear the "November" date so that the scheduled replications will once again work?

Re: Delete Replication History "David W. Fenton" <XXXusenet[ at ]dfenton.com.invalid> 6/6/2007 11:18:38 PM "Jesse" <nospam[ at ]nospam.com> wrote in news:#JubvFHqHHA.3264[ at ]TK2MSFTNGP04.phx.gbl: [Quoted Text] > Several months ago while testing daylight savings, the date and > time on server was set ahead to November to test daylight savings. > A scheduled replication ocurred and shows up in the history of > each replica with a November date. The hourly scheduled > replication now fails to happen and I believe this is because it > sees a "November date as the most recent and does not run. Is > there a way to clear the "November" date so that the scheduled > replications will once again work? I don't know that there is, but I'm not sure why that should matter. Have you tried recreating the schedule? I fear, though, that you're going to have to rebuild your replica set, or use something other than a scheduled synch to make your synchs happen on schedule. It's very easy to write a VBScript using the TSI Synchronizer that will run a synch, and you could schedule that synch to run with the Windows scheduler. You could to that until the November date passes, and if the regular synch resumes then, you can kill the scheduled VBScript. If not, then you'll have to rebuild your replica set (unless the VBScript synch is sufficient!). A sample VBScript is appended after my .sig. It requires that the TSI Synchronizer (in this case, the Jet 4 version, i.e., Synch40) be registered for it to work. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/ Dim tsiSynch Set tsiSynch = CreateObject("Synch40.Synchronizer") tsiSynch.Running = True tsiSynch.UID = [username] ' if necessary tsiSynch.Password = [password] ' if necessary tsiSynch.DatabaseName = [path to first replica] tsiSynch.SynchDirect [path to second replica] tsiSynch.Running = False Set tsiSynch = Nothing

Re: Delete Replication History Yvonne Anderson <yvonnemichele[ at ]noos.fr> 6/12/2007 10:41:38 AM What it is this group, and why is it appearing on my computer? Yvonne Michele Anderson yvonnemichele[ at ]noos.fr On 7/06/07 1:18, in article Xns9947C4702CA5Ef99a49ed1d0c49c5bbb2[ at ]127.0.0.1, "David W. Fenton" <XXXusenet[ at ]dfenton.com.invalid> wrote: [Quoted Text] > "Jesse" <nospam[ at ]nospam.com> wrote in > news:#JubvFHqHHA.3264[ at ]TK2MSFTNGP04.phx.gbl: > >> Several months ago while testing daylight savings, the date and >> time on server was set ahead to November to test daylight savings. >> A scheduled replication ocurred and shows up in the history of >> each replica with a November date. The hourly scheduled >> replication now fails to happen and I believe this is because it >> sees a "November date as the most recent and does not run. Is >> there a way to clear the "November" date so that the scheduled >> replications will once again work? > > I don't know that there is, but I'm not sure why that should matter. > > Have you tried recreating the schedule? > > I fear, though, that you're going to have to rebuild your replica > set, or use something other than a scheduled synch to make your > synchs happen on schedule. It's very easy to write a VBScript using > the TSI Synchronizer that will run a synch, and you could schedule > that synch to run with the Windows scheduler. You could to that > until the November date passes, and if the regular synch resumes > then, you can kill the scheduled VBScript. If not, then you'll have > to rebuild your replica set (unless the VBScript synch is > sufficient!). > > A sample VBScript is appended after my .sig. It requires that the > TSI Synchronizer (in this case, the Jet 4 version, i.e., Synch40) be > registered for it to work.