Database properties shows **** at modified date

When looking at the last modified date of saved documents or database elements located on the server, the same date keeps appearing over and over, example: 01/02/**** 3:57:43. So far the modified date is in the range of 01/02/**** 3:53:13 to 01/02/**** 5:58:45 (more or less the same). When an agent is run (on the server) creating a text file with the notesdocument.lastmodified date information, only the time prints out to the text file.

Now, when a local replica is created of the same database, and the process is repeated on the client machine, all of the last modified dates are reported correctly to the text file. Not with the 01/02/**** … but with the actual correct last modified date, example 26/06/2003.

So it would seem that the last modified date is only being “displayed” incorrectly when the properties are accessed on the server, not the client machine. Does anyone know how to correct this problem on the server. All the dates on the server are reporting correctly. The @Created date of the document property is correct.

Anyone got any ideas, please help. This is also causing views not to update and do not show updated data until a shift f-9 is performed. ARRRRGGGHHH

Subject: Database properties shows **** at modified date

I used to have this problem too, but only in names.nsf on the server.Search the forum, it has been discussed, I think compacting/fixup will solve the problem.

cheers,

Tom

Subject: RE: Database properties shows **** at modified date

I have searched and searched this forum and the R5 forum. I have only been able to find one post a year ago with no responses.

Comapct and Fixup do not fix this problem.

Any more help would be appreciated.

Subject: RE: Database properties shows **** at modified date

http://www-10.lotus.com/ldd/nd6forum.nsf/55c38d716d632d9b8525689b005ba1c0/a1dcf7c80fadb49e85256cde00692372?OpenDocument

Search for “Database time too far in the future” - I think it’s a similar problem …

cheers,

Tom

Subject: Database properties shows **** at modified date

In my case it also helped creating a local replica. The lastModif dates changed from 8/12/**** to the current date.

After that I created a new replica on the server from the local replica, and the problem was solved on the server too.

Does anybody know what causes the problem?