In the year 2036

HCL Domino Domino Forum
1

Due to a problem of time Sychronization, the server clock was set to the year 2036.

When it was discovered, this is was reset to the correct date and time, however inr the databse properties of the mail files, we have this in the modifed date.

And on the server, I will always get meesage saying that time is too far in the future Such as the following:

09/07/2004 06:33:25 PM Database Fixup: Started
09/07/2004 06:33:25 PM Performing consistency check on mail\skira.nsf…

09/07/2004 06:33:26 PM Router: Transferred 1 messages to BTMSERVER/BTM/CITRA via Notes
09/07/2004 06:33:37 PM Folder NT0000015A in database d:\Lotus\Domino\Data\mail\skira.nsf has been purged due to corruption: C
09/07/2004 06:33:37 PM Folder NT0000017A in database d:\Lotus\Domino\Data\mail\skira.nsf has been purged due to corruption: C
09/07/2004 06:33:38 PM Completed consistency check on mail\skira.nsf

09/07/2004 06:33:39 PM Unable to fixup database d:\Lotus\Domino\Data\mail\skira.nsf: Special database object cannot be located
09/07/2004 06:33:39 PM Database Fixup: Shutdown
09/07/2004 06:33:42 PM Router: Transferred 1 messages to [$Retry mail.CITRATUBINDO.CO.ID] (host mail.CITRATUBINDO.CO.ID) via SMTP
09/07/2004 06:33:52 PM Router: Transferred 2 messages to [$Retry mail.CITRATUBINDO.CO.ID] (host mail.CITRATUBINDO.CO.ID) via SMTP
09/07/2004 06:33:53 PM Router: Transferred 1 messages to [$Retry mail.CITRATUBINDO.CO.ID] (host mail.CITRATUBINDO.CO.ID) via SMTP

load compact mail\skira.nsf
09/07/2004 06:34:32 PM Performing consistency check on mail\skira.nsf…

09/07/2004 06:34:37 PM Completed consistency check on mail\skira.nsf

09/07/2004 06:34:37 PM Database (d:\Lotus\Domino\Data\mail\skira.nsf) time is too far in the future.
09/07/2004 06:34:37 PM Compacting mail\skira.nsf (S KIRA)
09/07/2004 06:34:44 PM Router: No messages transferred to POP.COM (host POP.COM) via SMTP: Remote system no longer responding
09/07/2004 06:35:00 PM Compacted mail\skira.nsf, 3072K bytes recovered (1%)
09/07/2004 06:35:00 PM Database compactor process shutdown

Is there a way to “correct” this?

Thanks

2

Subject: In the year 2036 …

Try making a copy (not a replica) of the database and then replacing the mail db on the server with the copy.

Since all your changes are being made with the correct new time now, the one made with the time at 2036 remains the last modified in the existing replica.

3

Subject: RE: In the year 2036 …

Try making a copy (not a replica) of the database and then replacing the mail db on the server with the copy.

                  Good Suggestion.

                  I would try that on my mail file.

                 If this works, any suggestion on doing it for the other mail files (on my local server, and on server loacted elswhere?)
4

Subject: In the year 2036 …

If you made a small change to the mail file template (like adding a sort on subject line in the Inbox folder?) would that cause a database modification at the next time the Design task runs? You may could try something like that which would automatically touch all mail files.

5

Subject: RE: In the year 2036 …

Thanks

I did precise that on my own mail file. That does not change the date a bit.

In fact the screen capture is done after the make changes to my template.

6

Subject: RE: In the year 2036 …

please try fixup and compact task on the server for all the mail files that should probably fix this

Thanks

Venki

7

Subject: RE: In the year 2036 …

Nup – it does not work.

8

Subject: RE: In the year 2036 …

Does your DB show a change date if you delete a document?

9

Subject: RE: In the year 2036 …

I have been deleting SPAM from may daily.

Hence, the answer to your question is that the Modified Year remain as 2036