Article ID: 264063
This article was previously published under Q264063
Calling VBScript-based date or time related functions from Microsoft Active Server Pages (ASP) on non-English (US) localizations of Microsoft Windows 2000, may return unexpected results when a user logs in interactively at the Internet Information Services (IIS) server.
VBScript, the default scripting language used by ASP, formats date and time values based on the settings specified by the interactive user. When there is no user logged in interactively (at the console), the system defaults that were specified during setup are used. However, when a user logs in interactively, that user's locale (regional) settings are used for all VBScript date and time formatting on the server. NOTE: This problem is the result of a design implementation in VBScript. Although IIS 5.0 is listed in the "Applies To" section, the problem will manifest in any service/application that attempts to use VBScript Date/Time formatting functions when a user is not logged in interactively (ie. IIS4, IIS3, W, H, etc.).
To work around this behavior, you can use any of following workarounds:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Because the presence of an interactive user can affect the Locale ID, and thus the formatting of date, time, and currency values, Microsoft recommends that you explicitly set the Locale ID by using the Session.LCID property in the Global.asa for your Web application.
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/246011/EN-US/ )Troubleshooting Windows 2000 MultiLanguage Version
Article ID: 264063 - Last Review: October 18, 2012 - Revision: 3.0