Systems Management Server Event Log Codes 350 Through 400

The information in this article applies to:

• Microsoft Systems Management Server versions 1.0, 1.1, and 1.2

This article details Systems Management Server event log codes 350 through 400.

Event Log Codes 350 - 400

Code Description ---- -----------

350 New site installation initiated for site X.

351 Could not create send request to install site X.

352 Could not create Site Reconfiguration Minijob for site X.

353 Site reconfiguration for site X initiated.

354 Local site reconfiguration initiated.

355 Remote site reconfiguration job for site X failed due to problems

       creating the minijob.

       to SQL Server .

358 Received an ACTUAL site control file from site X.

359 Preinstall job for site X has failed.

360 Site Install Job for site X has failed.

361 Site reconfig job for site X has failed.

362 Creation of Minijob to parent site from site is failing.

363 Sites table is empty. Cannot do any processing.

364 Forwarding site control file(s) to parent site X.

365 Cannot post site control files to parent site X.

366 Cannot identify this site. No site code is in registry.

367 Attempt to add site X to the Sites table in the database failed.

368 Attempt to add domain X for Site Y to Domains table in database has

       failed.

370 X is not setup correctly.

371 Unable to create MAC volume X on server Y with path Z.

372 There is not enough free disk space on share A, server B. Available

       diskspace is C MBytes, the package requires D bytes.

       copy the package.

       the description generated by the setup script is Z.

       or failed CRC check. Have the administrator resend the package to
       correct this problem.

377 Site X is attempting to produce an illegal site hierarchy.

378 Failed to install SMS_BOOTSTRAP service at the secondary site.

       Possible causes are the service account doesn't have the proper
       rights, the install drive doesn't exist or the server platform is
       incorrect.

       that is not empty. Either delete the directory by hand or choose a
       different directory and redo the secondary site install.

       the alert was Y.

       (BOOTSTRP.PK1) and/or the site control package (BOOTSTRP.PK2) have
       disappeared from that site's installation directory, where they had
       been previously stored. Installation or upgrade cannot continue. If
       this was an upgrade, SMS_BOOTSTRAP has triggered a restart of the
       secondary site, attempting to restart the previous version of SMS.
       If this succeeds, it should be possible to retry the upgrade using
       SMS Setup to upgrade the primary site again.

       (BOOTSTRP.PK1) is invalid, failing internal consistency checks.
       Installation or upgrade cannot continue. If this was an upgrade,
       SMS_BOOTSTRAP has triggered a restart of the secondary site,
       attempting to restart the previous version of SMS. If this

       it should be possible to retry the upgrade using SMS Setup to
       upgrade the primary site again. Possible causes are: a transmission
       error during sending.

       package (BOOTSTRP.PK2) is invalid, failing internal consistency
       checks. Installation or upgrade cannot continue. If this was an
       upgrade, SMS_BOOTSTRAP has triggered a restart of the secondary
       site, attempting to restart the previous version of SMS. If this
       succeeds, it should be possible to retry the upgrade using SMS

       to upgrade the primary site again. Possible causes are: a
       transmission error during sending.

       insufficient disk space to decompress the main site package
       (BOOTSTRP.PK1) or the site control package (BOOTSTRP.PK2).
       Installation or upgrade cannot continue. If this was an upgrade,
       SMS_BOOTSTRAP has triggered a restart of the secondary site,
       attempting to restart the previous version of SMS. If this
       succeeds, it should be possible to retry the upgrade using SMS

       to upgrade the primary site again. Possible causes are: low disk
       space on the secondary site server.

       has failed during decompression. Installation or upgrade cannot
       continue. If this was an upgrade, the secondary site may now

       a mixture of files from the previous and new versions and should be
       considered unstable. SMS_BOOTSTRAP has triggered a restart of the
       secondary site, attempting to start the "mixed" version of SMS. If
       this succeeds, it should be possible to retry the upgrade using SMS
       Setup to upgrade the primary site again.

       package has failed during decompression. Installation or upgrade
       cannot continue. If this is an upgrade, SMS_BOOTSTRAP has triggered
       a restart of the secondary site, attempting to start the new

       of SMS using the old site control file. If this succeeds, it should
       be possible to retry the upgrade using SMS Setup to upgrade the
       primary site again.

       decompressed, the main site package did not included a master

       map (SYSTEM.MAP). This file should have been in the install
       directory. Installation or upgrade cannot continue. If this is an
       upgrade, SMS_BOOTSTRAP has triggered a restart of the secondary
       site, attempting to start the new version of SMS without the system
       map. If this succeeds, it should be possible to retry the upgrade
       using SMS Setup to upgrade the primary site again.

       for more than 48 hours at the secondary site without the site
       successfully starting. Installation or upgrade will not continue.
       If this was an upgrade, SMS_BOOTSTRAP has triggered a restart of

       secondary site, attempting to restart the previous version of SMS.
       If this succeeds, it should be possible to retry the upgrade using
       SMS Setup to upgrade the primary site again.

390 Cannot enumerate user groups for domain (X). If this is a NetWare

       domain, this may be due to the Gateway Service for NetWare not
       running on the SMS site server. Possible NT error: (Y)

       However none of the package servers are able to support Macintosh
       packages. Please make sure Service for Macintosh is running on at
       least one of the package servers.

       successful secondary site install. Please select an NTFS drive and
       retry the secondary site install.

       MBytes, the drive with most free space only has Y MBytes free.