Article ID: 253518
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 3.51
This article was previously published under Q253518
SYMPTOMS
Under certain circumstances, files that are accessed on a Windows NT 3.51-based server from a Microsoft Windows 2000-based client may have their file date changed to the year 1619, 1601, or another value.
CAUSE
The problem is caused by OLE, which sets the file's time stamp to 0xffffffff (-1) for all file time properties. This special -1 file time is supported by Windows 2000 and Microsoft Windows NT 4.0, but not by Windows NT 3.51.
RESOLUTION
A post-Service Pack 5 (SP5) hotfix is available for Windows NT 3.51.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English-language version of this fix should have the following file attributes or later:
Date Size File name Platform
-------------------------------------------------
2/3/00 327,312 bytes Ntfs.sys Intel
1/17/00 810,576 bytes Ntoskrnl.exe Intel
Additional query words: date
Keywords: kbhotfixserver kbqfe kbenv kbprb KB253518
