Creation date of Word and Excel files is 01/01/1985

[Jim Boettger]

NW4.11 patched to sp9a, WIndows 2000 Pro, SP2, CLient 4.83 with PT1 applied.
Saving a newly created Word or Excel document gives a creation date of
01/01/1985.

Saved a file to local C drive no problem. Saved a file to a Win2k server
share no problem.

Any thoughts would be appreciated.

Thanks
Jim Boettger

[Alan Adams]

Which version of MS Office. Have seen that reported before (and IIRC
it was with Office XP); just curious whether yours is consistent with
that or happens even on a different version of Word/Excel.

Alan Adams, MCNE

[Jim Boettger]

O2K. Have a call open with support but since 4.11 is not a supported
product any longer they are hesitant to help. We did try a couple of things
but nothing worked. I will be setting up a 6.0 SBS to test to see I get the
same behavior. The tech tried to recreate it on a 5.1 server and he said he
did not have a problem.

Cheers,
Jim

"Alan Adams" <add...@withheld.com> wrote in message
news:vftrauk6pv94s4qvs...@4ax.com...

[Jim Boettger]

Installed the SBS 6.0 machine and similar problems. When using the DOS Dir
command the creation shows 01/01/85. Using NDIR /DA shows the correct
dates. Using Windows Explorer, shows last accessed as 01/01/85 but creation
date is correct.

Will be doing somemore research on Monday.

Cheers.
Jim

"Jim Boettger" <jboe...@mhmlaw.com> wrote in message
news:xGDr8.4692$vf1....@prv-forum2.provo.novell.com...

[Alan Adams]

> Using NDIR /DA shows the correct dates.

Say what? You mean that "Last Update", "Accessed" and
"Created/Copied" as shown by NDIR all show the correct non-1985 dates,
yet the workstation where you saved the file shows 1985 when using
Windows to display the same information?

I presume that means if you went to some other workstation, the
correct date for the same files would show even though Windows. (i.e.
There is no problem with the directory entry information actually on
the NetWare server; only the Windows workstation's view of that
information where the file was actually saved / renamed.)

I searched the newsgroup here for all the references to "1985", and
there was one poster who claimed they were updating from a previous
client to 4.80.SP3 "due to a problem during our transition from McAfee
to Norton AntiVirus CE 7.61 (all files saved to a NW5.1 server have
the date 1-1-1985)". Are either of those involved in your particular
case? If so, does removing them change anything? (Not saying that's
the issue necessarily; just whether its a factor required for
duplication.)

I've briefly been able to try with Windows XP Professional & Office XP
and Windows 2000 Professional SP2 and Office 2000 SR-1. No amount of
saving, saving as, renaming etc. ever showed me the issue. FWIW, I
had either no virus scanner or McAfee VirusScan 5.21 installed on the
workstations I was at.

Hmmm, since it's just the one workstation's view that seems to be
messed up, and you're against a NetWare 4.11 server, perhaps I should
test with file caching turned off (since I think that's what would be
the effective result in your configuration).

Alan Adams, MCNE

[Jim Boettger]

Alan, NAV CE 7.61 is definitely in the mix. Geez wouldn't that be a hoot
if AV was causing this.
Will be doing some more testing tomorrow. Two different machines, CPQ IPAQ
1.0 PIII and a Presario 1700, both exhibit the same issue
and both have NAV CE installed. Will try disabling AV first and then
removing the AV client.

Thanks for your input.

Jim Boettger

"Alan Adams" <add...@withheld.com> wrote in message

news:mvi1bu81e7as8d0b9...@4ax.com...

[Jim Boettger]

Alan, bingo. It's NAV.
http://search.symantec.com/custom/us/techsupp/enterprise/kb/query.html?col=k
b+us&qp=url%3A%2Fent-security.nsf%2F552ba2f7636bedf088256818006f78bf&qp=url%
3Aus-sarc&qp=url%3Aus-ts&qp=url%3Aus-lu&lk=1&rf=0&nh=10&prod=Norton+AntiViru
s&ver=7.6+Corporate+Edition&miniver=nav_76_ce&src=ent&base=http%3A%2F%2Fwww.
symantec.com%2Ftechsupp%2Fenterprise%2Fproducts%2Fnav%2Fnav_76_ce%2F&qt=1985

Thanks for your help.

Jim

"Jim Boettger" <jboe...@mhmlaw.com> wrote in message

news:r15s8.5060$vf1....@prv-forum2.provo.novell.com...

[Alan Adams]

I'm suspicious because Symantec is saying that 7.61 (the one you're
reporting you already have) has the fix/workaround to this issue
included? Or are you saying that you have 7.61, but not the "NAVCE
7.61 Build 34a" or later version that has the resolution implemented?

I'm looking at the "Norton AntiVirus Corporate Edition 7.61 inline
Release Notes" document in the results of the search you posted:

> NAVCE 7.61 Build 34a
>
> AutoProtect resets file modified date on Netware or Unix server
>
> Symptom: When you save or rename a file on a server, realtime
> scanning on the client causes the file modified date to change.
> On a Netware server, the modified date changes to 1/1/1985. On
> a UNIX server, the date changes to 01/01/1970.
>
> Resolution: After a file is scanned, the new file times are
> compared against the old file times. If the times are not equal,
> then the original file times are put back.

Alan Adams, MCNE

[Jim Boettger]

Alan, I did not have build 34a of the NAV client installed. Downloaded it
today, installed it and the world is right again.

Thanks for your help.

Jim

"Alan Adams" <add...@withheld.com> wrote in message

news:m1i3buc4qpre9lgm9...@4ax.com...

[Alan Adams]

Cool. Thanks for the post back.

Alan Adams, MCNE