MS Office 2000 Office Documents show modified date 1/1/1985

[pcrtech]

Multiple users are having the issue where Word and Excel documents are saved and they show a modified date of 1/1/1985 the O/S is windows xp. This does not happen on Windows 98 workstations. The Office Suite used is Microsoft Office 2000 SR1

-Although Microsoft Office file is modified present day on the users pc - it shows a date of 1/1/1985. Created date and accessed date is accurate.
-This happens on the user's network drive, not their c drive
-when I modify their files on their network drive from my PC, file shows correct modified date
-when I modify document on my c drive shows correct modified date as well
-This does not happen on windows 98 PCs
-when you do save as - does not prompt to over-write same file even though they have the same name
-ran spybot and ad-aware with same results
-ran antivirus scan with no virus detection
-ran MS Office 2000 updates with no difference
-logged in as a different user- problem still occured
-Browsed the network noticed multiple users with known XP PCs had saved files with the modified date of 1/1/1985

I could probably list by date created within windows explorer, but I have multiple users asking me the same question. I appreciate your replies in advance.

 

[bcastner]

Open a new notepad session, to be called fix_time.cmd
Copy/paste the below, and save it as fix_time.cmd. Add it to your logon script, or drag&drop to the All Users, Startup folder:

@echo off
@cmd /c net stop w32time
@start/wait cmd /c w32tm /unregister
@start/wait cmd /c w32tm /register
@start /wait cmd /c net start w32time

 

[linney]

I noticed one poster talk about seeing this with NAV and NetWare involved.

http://groups.google.com/groups?sourceid=navclient&ie=UTF-8&oe=UTF-8&q=modified+date+1/1/1985

http://www.google.com/search?sourceid=navclient&ie=UTF-8&oe=UTF-8&q=modified+date+1/1/1985

 

[bcastner]

What I am concerned about is that the CMOS battery is essentially dead, and the BIOS reverts to a primal date/time as they are experiencing.

If the system Date/Time as shown on the taskbar is also 1-1-1985 after the "fix" above to force a time syncronization, then replacing the cmos battery on the motherboard of the computer is recommended strongly.

 

[pcrtech]

bcastner - thank you for your immediate reply. unfortunately the cmos battery is not the issue (I should have included this in my notes). Just as linney stated this seems to be a Novell issue. Well, it so happens that the pc I was testing this on needed to be rebuilt - what I found was that our new pc image (just created by our network engineer) seems to have addressed the issue. He himself is not aware of what fixed the problem - but we both dedeuced that it was probably the novell client update (from 4.83 to 4.9sp1). I went ahead and updated the client on a known problem pc. The client update did not address the issue either, but a brand new re-image does. Which makes our users happy. At this point I don't have an answer but the problem is fixed. As I have a little more time to delve into this topic I will go ahead and add to this thread.

 

[bcastner]

pcrtech,

When you have the chance, could you provide more detail on your solution? It still strikes me as a CMOS battery issue, but your workaround is both daunting and impressive. I have a ton of older Novell sites, and the notion of having to do a re-image is scary.