Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/253342

From BetaArchive Wiki

Article ID: 253342

Article Last Modified on 1/27/2007



APPLIES TO

  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 98 Standard Edition
  • Microsoft Windows 95
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows 98 Second Edition



This article was previously published under Q253342

SYMPTOMS

When you use a non-Gregorian calendar, the year may be reported incorrectly. For example:

You Are Using the Japanese Era Calendar

When you use the Japanese era calendar format, the following Hypertext Markup Language (HTML) script sets the year to 3987:

<HTML>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=x-sjis">
<HEAD>
<TITLE>Format function</TITLE>
</HEAD>
<BODY>
<Script Language="VBScript">
Document.write Year("1999/12/17")
</Script>
</BODY>
</HTML>


NOTE: The year is reported correctly as 1999 if you use the Common era calendar.

Your Are Using the Wareki Era Calendar

When you use the Wareki era calendar format with the Japanese version of Microsoft Office 2000 Small Business Customer Manager, the year is reported incorrectly.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this fix.

To resolve this problem immediately, download the fix by clicking the download link later in this article or contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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.

This update is part of the Windows 2000 Critical Update, February 17, 2000 that is available on the Windows Update site. You can also download this critical update (for installation later or on a different computer) from the following Microsoft Web site:

The English version of this fix should have the following file attributes or later:

   Date      Time       Version      Size    File name   
   ------------------------------------------------------
   01/05/00  3:10:50pm  2.40.4514.1  143,632 Asycfilt.dll
   01/05/00  3:10:50pm  2.40.4514.1  614,672 Oleaut32.dll
   01/05/00  3:10:50pm  5.0.4514.1   164,112 Olepro32.dll  
   01/05/00  3:10:50pm  2.40.4514.1   16,896 Stdole2.tlb 
                

NOTE: To view the version, right-click the file in Windows Explorer, click Properties on the menu that appears, and then click the Version tab.


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes


Keywords: kbfix kbprb kbqfe kbui KB253342