Intranetware 4.11 problem with "Synthetic Time"

[GaryEllington]

Hello all.

I have a very small 4.11 network with a single server and 5 workstations.

Immediately after the daylight savings time change, the server began displaying the following message every two minutes!

&quot;< date > < time > DS-5.73-12&quot;
&quot;Synthetic Time is being issued on partition APS.&quot;

Very annoying %-(

I have checked every time related SETting I can find, and cannot find anything referencing &quot;Synthetic Time&quot;, or why it would need to be &quot;issued&quot; so frequently.

I have shut down the entire network (downed &amp; powered off the server, after logging out and powering off every workstation). Restarted everything, all the clocks are correct on all machines, but dang server console still issueing &quot;Synthetic Time&quot;.

Any ideas?

 

[yvfwc]

Goto

http://www.support.novell.com/products/nw411/

and check TID#10011024. If that isn't it search for &quot;synthetic time&quot; and there are other TID's on that subject.

Good Luck,

Mark ;-)

 

[andyrne]

Synthetic time is issued when the time is moved back for some reason, and lasts untill the time on the server reaches the point at which it moved back. eg if the time was 10 am and you set the time back to 9 am, the server would issue synthetic time warnings until the time on the server reached 10 am again. Each time an nds object is updated, it has it's time stamp updated. Synthetic time stamps are issued when there are problems with the server time, to stop the time stamps of nds objects being updated incorrectly.

Although I can't remember the exact steps for repairing synthetic time, there is an option in dsrepair that will fix this.

 

[Guest_imported]

You need to load DSREPAIR with the -A switch (LOAD DSREPAIR -A)... Choose Advanced Options | Replica & Partition Operations | Highlight the Replica and press Enter | Repair Time Stamps and Declare a new Epoch

That'll sort it... Job's a good 'un.

Regards
FNB CNE5/4/3

 

[jmartin]

Sure!. You must to declare a new epoch in the server.This is the only way to fix the problem. I had several cases like this and Novell teachs it. Use DSREPAIR module and follow the steps that last visitor say, remember your admin password, and enter it with the ´admin.context_name´ convention.

 

[GaryEllington]

Thanks to everyone for their suggestions...

FatNorthenBiffa, you were dead on with the repair procedure, and jmartin, thanks a LOT for the login tip. I finally figured that out yesterday on my own, but it took awhile. Its comforting to know I would have gotten it anyway here.

PROBLEM IS SOLVED! Yippee! X-)