The information in this article applies to:
SYMPTOMSSMS_SITE_SYSTEM_STATUS_SUMMARIZER may generate an "Access violation" error message and cause the SMS_EXECUTIVE service to shut down. When this occurs, a Crash.log file is created that reports the failure. CAUSEThis behavior occurs because the Network Abstraction Layer (NAL) component in Systems Management Server (SMS) contains an error code that is not properly handled. RESOLUTIONA supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next SQL Server service pack
that contains this fix. http://www.microsoft.com/support/supportnet/overview/overview.aspCAUTION: Do not apply this hotfix if you have previously applied the Client Hotfix Bundle described in the following Microsoft Knowledge Base article (this hotfix is included in the bundle and reinstallation can cause client and/or site system problems): Q246527 SMS: Systems Management Server 2.0 Service Pack 1 Client Hotfix BundleThe English-language version of this software update should have the following file attributes or later when you are using the released version of SMS 2.0: NOTE: Due to file dependencies, the most recent software update or feature that contains the above files may also contain additional files.
The English-language version of this software update should have the following file attributes or later when you are using SMS 2.0 SP1: NOTE: Due to file dependencies, the most recent software update or feature that contains the above files may also contain additional files.
To install the hotfix, perform the following steps on the SMS site server:
STATUSMicrosoft has confirmed this to be a problem in Systems Management Server version 2.0. MORE INFORMATION
The SMS_EXECUTIVE service stops a short time after starting, and Site Component Manager restarts it on its next cycle. You can end up with multiple Crash.log files.
The last entry recorded in the Sitestat.log file (with NAL logging level = 0x7) when the problem occurs is:
Additional query words: prodsms
Keywords : kbSMS200 kbSMS200bug kbSMS200fix |
Last Reviewed: January 31, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |