| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Commercial Internet System 2.0 (Japanese) - Win NT
| Product Summary |
Product: Commercial Internet System
Version: 2.0 |
Category: Compliant#
Operating System: Win NT |
| Language: Japanese |
Release Date: 01 Oct 1998 |
| Operational Range: |
01 Jan 1900 - 31 Dec 2078 |
| Prerequisites: |
None |
| Product Dependencies: |
Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 4.01 or later |
| Clock Dependencies: |
Uses the Operating System date/time routines |
| Last Updated: |
30 Aug 1999 | |
| Product Details |
|
How the product handles dates:
Connection Manager
- The only area where Connection Manger interacts with date related data is in performing counter operations. This is done using seconds from 1970. There are no areas where Connection Manager users input, save, or manipulate dates.
Connection Manager Administration Kit
- Connection Manager Administration Kit uses no date related data.
Connection Point Services
Connection Point Services uses date released data in the following manners:
- The PBA tool date stamps phone book changes and logs them to a log file.
- The latest entry date from the log is presented to the user in a system defined format (mm-dd-yy by default).
- When doing phone book posting, the phone book server does a date comparison of the "live" phone book with the updated newpbk.mdb. It then proceeds to update itself if newpbk.mdb is newer than the live version.
Internet Authentication Service (IAS) and IAS Commercial Edition
There are three areas where IAS interacts with date related data:
- RADIUS attribute based on date and time of day û the attribute data type is specified in RFC to be 32-bit and having no known year 2000 issues.
- Accounting log file names are in yyyymmdd log format. IAS gets the date from the operating system and uses 4-digit years.
- Accounting record logs date in mm/dd/yyyy format. IAS gets the date from the operating system and uses 4-digit years.
Internet Mail, News, and Chat
CDONTS:
CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2 digits to represent the year within the date header information. Date properties exposed by CDONTS are read-only and based on the FILETIME data structure.
Outbound messages are stamped with the current system time using the operating system clock. The date used for the headers are 4 digits with no known year 2000 issues, but the RFC 822 message headers only use the last 2 digits for the year date.
Chat Server:
The Chat Server calculates time based on tick counts for real time collaboration, which do not span across a year period. When dates are kept, the Chat server will store the date using a large integer, which allows the year to be stored with 4 digits.
IMC:
The IMC stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601.
Messages that are of the format RFC 822, that come into the IMC, are handled by IMAIL and the file system (NTFS). RFC 822 messages store date formats with 2-digits representing the year.
Site Server 3.0, Commerce Edition
- For Content Replication, date and time is stored as an 8-byte real value (double), with a positive number representing a date between January 1, 1900 and December 31, 2078.
- For Personalization and Membership, the date and time is stored as an 8-byte field. Four bytes for the number of dates before or after the base date of January 1, 1900, and four bytes for the number of milliseconds after midnight. Dates range from January 1, 1753, to December 31, 9999.
- Commerce Server: the product uses Windows and OLE API and SQL/ADO API to convert entered dates to the display/storage formats. Dates are converted with the full 4-digit year.
- See separately available year 2000 compliance documentation for Site Server 3.0, Commerce Edition.
- SQL Server 6.5 û see separately available year 2000 product guide documentation for SQL Server 6.5.
Two-digit shortcut handling:
Connection Point Services
- Connection Point Services doesn't handle dates with its log files. It stores, retrieves, and displays a date. It stores and displays the year in a 2-digit format (YY) or 4-digit format (YYYY) based on system regional settings. Two-digit years are displayed when system settings call for 4-digit display (YYYY). After year 2029, Connection Point Services uses the 4-digit format.
Internet Authentication Service (IAS) and IAS Commercial Edition
No two-digit short cut handling is used in Internet Authentication Service.
Site Server 3.0, Commerce Edition
- With the Microsoft Management Console, the input of dates is controlled by selecting from a drop-down box that displays dates in a 4-digit year format.
- The Web Admin will not accept a date with a 2-digit year.
- In the Rule Builder, 2-digit shortcuts are allowed when editing rules. The 2-digit shortcut is enabled if the system short date format is set for "yy".
- With the Rule Builder, the conversion is done using various external objects, such as the OLE date time pickers, and components gained either from the operating system or Internet Explorer 4.
- Membership Directory Manager supports dates in 2-digit shortcuts.
- With the Membership Directory Manager the logic is the same as for Internet Explorer 4.0.
- Data entry is available only through a web page, and the product immediately uses the above-mentioned conversions on those entries.
- CommerceûûOLE Automation calls make most of the conversions. The product does have a private DataFunctions object that does the conversion in some cases, but this object also relies on OLE Automation calls.
- Ad SystemûûServer code uses 4-digit only. The Ad Manager code uses the same DataFunctions as Commerce Server 3.0, as well as some native SQL-provided conversion routines ({ts} as an example).
Common date usage errors:
- See comments for Site Server 3.0, Commerce Edition.
- CommerceûûThis component of the product is essentially a Software Development Kit (SDK). Therefore, year 2000 issues that users encounter with other SDK-type products are possible with this product. This product shows examples of using its formatting objects to get the right dates etc., but it doesn't enforce their use.
- Ad SystemûûAlthough not really an SDK, users have the ability to modify the Ad Manager pages in the product, leading to potential year 2000 problems. To avoid problems, users should refrain from modifying pages in the product.
Testing guidelines and recommendations:
- Since most Commerce sites are web-based applications, it is important to verify any interface with the user and the HTML/ASL code written to handle this interaction. Store authors need to verify that the parts they author are compliant. There are places in the sample sites that have date drop-downs that will expire in 3û5 years. To change this, change the HTML.
- In general, avoid testing in a production environment or with non-duplicated production files because side effects with other products are difficult to predict.
Site Server 3 Testing Instructions
Microsoft understands that for various reasons customers may be required to conduct their own year 2000 certification testing. Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Commercial Internet System. It is recommended that testing be done on non-productions systems.
- Post data between systems that have one set to December 31, 1999 and the other set to January 1, 2000, simulating time-zone issues.
- Also, start replication between servers just prior to midnight, December 31, 1999.
- Add members to Membership Groups with expiration date set to right before and after January 1, 2000.
- Import Content Analyst log files that contain information that cross the 1999 to 2000 boundary.
| |
Return to Search Screen
| Legend of Symbols: |
| * |
The product is compliant with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document. |
| # |
The product is compliant with an acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability, or reliability of the product. |
| + |
The product is compliant with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details. |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
If after reviewing this information you have additional questions related to this product, click here.
YEAR 2000 READINESS DISCLOSURE
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://www.microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA.
ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.
|
