Date of 2050 Causes Access Violations in SMS ServicesLast reviewed: April 24, 1997Article ID: Q151648 |
The information in this article applies to:
SYMPTOMSSMS fails at installation when the SMS_Site_Config_Manager Service tries to start with access violations in Siteins.exe and Preinst.exe. On a previously installed site, the SMS_Executive, SMS_Package_Command_Manager_NT, SMS_Hierarchy_Manager, and SMS_Site_CONFIG_Manager Services cause an access violation when started.
RESOLUTIONChange the system date, either from within Windows NT or in the system's BIOS, back to the appropriate date.
MORE INFORMATIONIf the computer date is set to the year 2050 (or greater), the services will cause access violation exceptions. The addresses are always consistent:
Siteins.exe Exception: access violation (0c00000005), Address: 0x1f328327. Preinst.exe Exception: access violation (0c00000005), Address: 0x1f328327 Smsexec.exe Exception: access violation (0c00000005), Address: 0x1f328327 Pcmwin32.exe Exception: access violation (0c00000005), Address: 0x0040ec87 STATUSMicrosoft has confirmed this to be a problem in Systems Management Server version 1.x. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
|
Additional query words:
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |