Article ID: 184132 - Last Review: November 1, 2006 - Revision: 1.3

The Value Entered Does Not Match with the Specified Type

This article was previously published under Q184132

On This Page

Expand all | Collapse all

SYMPTOMS

When you try to add a Custom Date using the year 00 on the Custom tab of the properties sheet for a Microsoft Office document, you receive the following error message:
The value entered does not match with the specified type. The value will be stored as text.

RESOLUTION

Windows NT 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734  (http://support.microsoft.com/kb/152734/EN-US/ ) How to Obtain the Latest Windows NT 4.0 Service Pack

The English version of this post-SP3 hotfix has been posted to the following Internet locations.

http://www.microsoft.com/ntserver/nts/downloads/archive/NT4y2kpostSP3/default.asp (http://www.microsoft.com/ntserver/nts/downloads/archive/NT4y2kpostSP3/default.asp)
ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP3/y2k2-fix/ (ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP3/y2k2-fix/)

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

MORE INFORMATION

For more information on what is fixed in Y2K2-fix, please see the following articles in the Microsoft Knowledge Base:

175093  (http://support.microsoft.com/kb/175093/EN-US/ ) User Manager Does Not Recognize February 2000 As a Leap Year
183123  (http://support.microsoft.com/kb/183123/EN-US/ ) Find Files Displays Garbled Date if Year is 2000 or Greater
183125  (http://support.microsoft.com/kb/183125/EN-US/ ) Shell Doc Property Dialog Custom Date Incorrect after Year 2000
186669  (http://support.microsoft.com/kb/186669/EN-US/ ) FPNW Logout.exe Incorrectly Reports Year After Jan. 1, 2000
191768  (http://support.microsoft.com/kb/191768/EN-US/ ) Date of Print Job May Be Displayed Incorrectly in Print Queue
193056  (http://support.microsoft.com/kb/193056/EN-US/ ) Problems in Date/Time after Choosing February 29 in a Leap Year
193434  (http://support.microsoft.com/kb/193434/EN-US/ ) Migration Changes NetWare Accounts Expiration Date
194726  (http://support.microsoft.com/kb/194726/EN-US/ ) FPNW Client Does Not Get Correct Time or Date After Y2K
207799  (http://support.microsoft.com/kb/207799/EN-US/ ) IBM PS/1 will not Boot on or After January 1, 2000
216916  (http://support.microsoft.com/kb/216916/EN-US/ ) NTBACKUP Writes Incorrect Year to Log File
For information on the Y2K2-fix for Windows NT 4.0, Terminal Server Edition, please see the following article in the Microsoft Knowledge Base:
196548  (http://support.microsoft.com/kb/196548/EN-US/ ) Y2K Update for Windows NT 4.0, Terminal Server Edition

APPLIES TO
  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition
Keywords: 
kbbug kbfix kbqfe KB184132
 

Article Translations