Database design elements timeStamp bug

hi! There was a requirement to test the application behaviour in certain date. So we down the Domino server, changed the Windows 2000 datetime and started the server.

After the test, we repeated the same steps to the current datetime.

However I notice that ever since we modified the server datetime, every startup of the server will show “Time is too far in the future” console message. I checked the forum and found its of no harm. However, its annoying.

But what concerns me is the timestamp at the database design elements. During the ‘timechange’ period, I modified few agents. So now they bear the modified timestamp of 24/02/2006 (which i set for the testing).

I tried to cut and paste the agent, however the timestamps remain. And when I tried to Sign database again, to my shock this time ALL elements bear the timestamp of 24/02/2006!!!

I read that we can use a new replica or new copy to workaround with this type of issues. But i tried and the same timestamp remains. But if I copy the agent to DB at OTHER server, the pasted agent now holds the correct timestamp.

So i suspect Notes keep a ‘latest timestamp’ somewhere in each database. Is there anyway to remove this?

I’m pretty sure that the server time is okay as I tried an agent that prints “Now” (issue from server console), it showed correct datetime.

Subject: Database design elements timeStamp bug

Notes really does not like being lied to .

The date-time stamp of design elements, as well as documents, is crtitical when doing replication. Thus, setting your clock forward on a live saver / database is a Bad Idea. After you are done, Notes will detect that it’s running “in the past” and try to prevent problems that might corrupt replicas of the database.

e.g. If you had replicated your changes while in the future, after you come back to now, the replica’s date would be ahead of your server dates, and Notes would “think” they were more recent, and would move them back.

If you have to do this for testing a specific date, the safest way is to clone the whole system, test on that copy, then delete it.

Subject: RE: Database design elements timeStamp bug

so is there any workaround?? I know its no harm in the development server, but I just don’t like it to have wrong timestamp

Subject: RE: Database design elements timeStamp bug

I have an issue similar than this. I have a LOCAL copy of the database and I made changes to the computer date for testing. In the mean time I did changes to some design elements. After that, I returned the Computer date to the correct one, but now all the elements that I modify in this database have the wrong (5/20/2005) date. If I create a new form, the date is wrong too!!! However, when I create a new document, it gets the proper date.

How I can fix this?

I check this forum, but I don’t see a solution. I delete the cache.ndk but that didn’t work.

Any other suggestion?

Subject: SOLUTION : Database design elements timeStamp bug

Ok … we found a solution … Make a replica of your original database and the problem go away …