Anonymous_User Absent Member.
Absent Member.
3124 views

Incorrect modified and created file dates

We are running NW 6.0 SP5 and client 4.91 SP2. We also have Symantec v10.0.1
running on the workstation (no antivirus running on the server). I disabled
the antivirus on the workstation but the problem still exists.

There seems to be a couple issues with the modified and created dates for
files that reside on our NSS volumes.

Issue #1
For a lot of our older files that have not been accessed for a while, the
created and modified dates are flipped in such a way that the modifed date
is older than the created date. Not exactly sure, but there is a good chance
that the the modified date shows the original creation date, and the
creation date actually shows the last modified date. As expected, if I
modify and save the file, the modified date is now updated correctly, and
the creation date stays the same.

There are two problems with this.
1) What caused the modified date and the creation date to be flipped in the
first place (maybe an upgrade or conversion to NSS ??).
2) Once the files are modified, the modified date is correct but the
creation date is still not correct (and never will be)

We often run reports to show files older than a certain date or not modified
for a certain amount of time. For these old files that have the date flip
problem, the reports are not accurate.

Issue #2
We are using MS Project 2003 and if I open a Project file and then exit
without modifying or saving the file, the last modified date is still
changed. This does not seem to happen with other Microsoft Office 2003
applications.


Neither of these issues exists on the local drive, just on the NSS volume. I
have searched and read various things about NSS volumes, session stamping
and extended attributes which seem to be related to this, but have not found
any suggestions or resolutions to this problem. Does anyone know it there
are patches, fixes, registry edits etc. that might resolve this problem or
is it something that we have to live with on NSS volumes? Thanks in
advance.


Labels (1)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Incorrect modified and created file dates

Brian Clarke wrote:
> We are running NW 6.0 SP5 and client 4.91 SP2. We also have Symantec v10.0.1
> running on the workstation (no antivirus running on the server). I disabled
> the antivirus on the workstation but the problem still exists.
>
> There seems to be a couple issues with the modified and created dates for
> files that reside on our NSS volumes.
>
> Issue #1
> For a lot of our older files that have not been accessed for a while, the
> created and modified dates are flipped in such a way that the modifed date
> is older than the created date. Not exactly sure, but there is a good chance
> that the the modified date shows the original creation date, and the
> creation date actually shows the last modified date. As expected, if I
> modify and save the file, the modified date is now updated correctly, and
> the creation date stays the same.
>
> There are two problems with this.
> 1) What caused the modified date and the creation date to be flipped in the
> first place (maybe an upgrade or conversion to NSS ??).
> 2) Once the files are modified, the modified date is correct but the
> creation date is still not correct (and never will be)


Set the Date on your PC to 1999. Create a File and Copy it to the
server. The Creation Date of that file will be 1999, despite it being
2006. Most likely something along this line happened at some point in
time. In fact, I have seen places that have processes in place to
back-date PCs time to get around "Expired" software or perhaps even to
deal with Y2K issues.


> We often run reports to show files older than a certain date or not modified
> for a certain amount of time. For these old files that have the date flip
> problem, the reports are not accurate.
>
> Issue #2
> We are using MS Project 2003 and if I open a Project file and then exit
> without modifying or saving the file, the last modified date is still
> changed. This does not seem to happen with other Microsoft Office 2003
> applications.


This must be something in the code for Project. I do not have it handy.
I could be possible there is something in the MS Code written especially
for local NTFS partitions to prevent the time from updating. Far far
from a solution, but you could provide some users with a "Visio Viewer"
to use for viewing these documents.




--
Craig Wilson
Novell Product Support Forum Sysop
Master CNE, MCSE 2003, CCN
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Incorrect modified and created file dates

As a side note, I've used the FileDate Changer from Nirsoft to assist in
troubleshooting issues like these...
http://nirsoft.net/

--
Tony Pedretti
TransUnion Corporation


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Incorrect modified and created file dates

Hello,

> Issue #2
> We are using MS Project 2003 and if I open a Project file and then exit
> without modifying or saving the file, the last modified date is still
> changed. This does not seem to happen with other Microsoft Office 2003
> applications.


I've run into a similar (and possibly related) issue on OES Linux. The
last modified date, in my case, is _not_ changed by Microsoft Office
applications at all while talking to an NCP volume (standard-issue
reiserfs exported via "ncpcon create volume", not NSS). With apparently
any other application, the last modified date is updated correctly. Even
for Office files, the last modified is updated correctly locally and on
Samba shares. It's just the combination of Office plus NCP volume that
isn't working.

Are we having a known, client-related timestamp problem here? System
information: Novell Client for Windows 4.91 SP2, Build No. 4.91.2.20051209
on XP SP2, OES SP2 on Linux, patches up to date as per "rug pin
--entire-channel oes".

Grateful for any ideas.

Cheers,
Florian

--
Mag.(FH) Florian G. Haas
Systemingenieur
Kapsch BusinessCom AG, Wienerbergstrasse 53, A-1121 Wien


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.