Assets/messages.xml
|
<?xml version="1.0" standalone="yes"?>
<dtsHealthCheck xmlns="http://tempuri.org/HealthCheckDataSet.xsd"> <Message> <MessageID>500</MessageID> <Description>This component started.</Description> </Message> <Message> <MessageID>501</MessageID> <Description>This component was signalled to stop by an administrator or the operating system. The component will complete any processing it is doing and stop at a safe point in time. If the component or this computer is very busy, it may take several minutes for the component to stop.</Description> </Message> <Message> <MessageID>502</MessageID> <Description>This component stopped.</Description> </Message> <Message> <MessageID>503</MessageID> <Description>This component was signalled to pause by an administrator. The component will complete any processing it is doing and pause at a safe point in time. If the component or this computer is very busy, it may take several minutes for the component to pause. Once the component has paused, it will not do any more processing until the administrator signals it to resume processing.</Description> </Message> <Message> <MessageID>504</MessageID> <Description>This component was signalled to resume processing by an administrator.</Description> </Message> <Message> <MessageID>505</MessageID> <Description>Server %1 is unreachable or down.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>506</MessageID> <Description>Copied file "%1" to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>507</MessageID> <Description>Moved file "%1" to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>508</MessageID> <Description>Deleted file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>509</MessageID> <Description>Locked file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>510</MessageID> <Description>Unlocked file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>511</MessageID> <Description>Created directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>512</MessageID> <Description>Removed directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>513</MessageID> <Description>Set the current directory for this process to "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>514</MessageID> <Description>Opened a change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>515</MessageID> <Description>Could not open a change notification handle for directory "%1" because the directory is on a remote computer.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>516</MessageID> <Description>Closed the change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>517</MessageID> <Description>Could not open file "%1" for reading.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>518</MessageID> <Description>Could not open file "%1" for reading and writing.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>519</MessageID> <Description>Could not read from file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>520</MessageID> <Description>Could not write to file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>521</MessageID> <Description>Could not copy file "%1" to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>522</MessageID> <Description>Could not move file "%1" to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>523</MessageID> <Description>Could not delete file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>524</MessageID> <Description>Could not lock file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>525</MessageID> <Description>Could not create directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>526</MessageID> <Description>Could not remove directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>527</MessageID> <Description>Could not set the current directory for this process to "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>528</MessageID> <Description>Could not open a change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>529</MessageID> <Description>Could not wait on a change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>530</MessageID> <Description>Could not open file "%1" for reading.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>531</MessageID> <Description>Could not open file "%1" for reading and writing.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>532</MessageID> <Description>Could not read from file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>533</MessageID> <Description>Could not write to file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>534</MessageID> <Description>Could not copy file "%1" to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>535</MessageID> <Description>Could not move file "%1" to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>536</MessageID> <Description>Could not delete file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>537</MessageID> <Description>Could not lock file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>538</MessageID> <Description>Could not create directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>539</MessageID> <Description>Could not remove directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>540</MessageID> <Description>Could not set the current directory for this process to "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>541</MessageID> <Description>Could not open a change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>542</MessageID> <Description>Could not wait on a change notification handle for directory "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>543</MessageID> <Description>Parsed site control file "%1", serial number %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>544</MessageID> <Description>Wrote delta site control file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>545</MessageID> <Description>Could not read site control file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>546</MessageID> <Description>Could not parse site control file "%1", the file contains a syntax error or it is improperly formatted or corrupt.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>547</MessageID> <Description>Could not parse site control file "%1", the file does not contain an end-of-file (EOF) marker.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>548</MessageID> <Description>Site control file "%1" does not contain a "File Definition" item.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>549</MessageID> <Description>Could not write delta site control file "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>550</MessageID> <Description>Parsed installation map "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>551</MessageID> <Description>Could not read installation map "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>552</MessageID> <Description>Could not parse installation map "%1", the file contains a syntax error or it is improperly formatted or corrupt.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>553</MessageID> <Description>Read registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>554</MessageID> <Description>Wrote registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>555</MessageID> <Description>Deleted registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>556</MessageID> <Description>Read registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>557</MessageID> <Description>Wrote registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>558</MessageID> <Description>Deleted registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>559</MessageID> <Description>Opened a change notification handle for registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>560</MessageID> <Description>Closed the change notification handle for registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>561</MessageID> <Description>Could not connect to registry hive %1 on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>562</MessageID> <Description>Could not open registry key "%1" on computer %2 for reading.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>563</MessageID> <Description>Could not create or open registry key "%1" on computer %2 for reading and writing.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>564</MessageID> <Description>Could not read registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>565</MessageID> <Description>Could not write registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>566</MessageID> <Description>Could not delete the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>567</MessageID> <Description>Could not enumerate the subkeys of the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>568</MessageID> <Description>Could not open a change notification handle for registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>569</MessageID> <Description>The registry key "%1" on computer %2 is missing a required subkey or value, or contains one or more values that contain invalid data.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>570</MessageID> <Description>Could not read the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>571</MessageID> <Description>Could not write the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>572</MessageID> <Description>Could not delete the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>573</MessageID> <Description>Could not enumerate the values of the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>574</MessageID> <Description>The registry value "%1" on computer %2 contains invalid data.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>575</MessageID> <Description>Could not connect to registry hive %1 on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>576</MessageID> <Description>Could not open registry key "%1" on computer %2 for reading.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>577</MessageID> <Description>Could not create or open registry key "%1" on computer %2 for reading and writing.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>578</MessageID> <Description>Could not read registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>579</MessageID> <Description>Could not write registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>580</MessageID> <Description>Could not delete the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>581</MessageID> <Description>Could not enumerate the subkeys of the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>582</MessageID> <Description>Could not open a change notification handle for registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>583</MessageID> <Description>The registry key "%1" on computer %2 is missing a required subkey or value, or contains one or more values that contain invalid data.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>584</MessageID> <Description>Could not read the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>585</MessageID> <Description>Could not write the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>586</MessageID> <Description>Could not delete the registry value "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>587</MessageID> <Description>Could not enumerate the values of the registry key "%1" on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>588</MessageID> <Description>The registry value "%1" on computer %2 contains invalid data.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>589</MessageID> <Description>Creating "%1" trigger for "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>590</MessageID> <Description>Dropping trigger "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>591</MessageID> <Description>Creating table "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>592</MessageID> <Description>Dropping table "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>593</MessageID> <Description>Creating index "%1" on table "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>594</MessageID> <Description>Dropping index "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>595</MessageID> <Description>Creating stored procedure "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>596</MessageID> <Description>Dropping stored procedure "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>597</MessageID> <Description>Creating view "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>598</MessageID> <Description>Dropping view "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>599</MessageID> <Description>SQL Login data is incomplete.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>600</MessageID> <Description>Failed to get a SQL Server connection. Either the SQL Server is not running, or all connections have been used.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>601</MessageID> <Description>Failed to execute SQL command: "%1". Check messages from SQL Server.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>602</MessageID> <Description>The following SQL operation has timed out: "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>603</MessageID> <Description>Failed to get new table name.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>604</MessageID> <Description>Failed to create table "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>605</MessageID> <Description>Failed to rename table "%1" to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>606</MessageID> <Description>Failed to add columns to table "%1".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>607</MessageID> <Description>Failed to drop table "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>608</MessageID> <Description>Failed to create index "%1" on table "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>609</MessageID> <Description>Failed to create procedure "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>610</MessageID> <Description>Failed to create view "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>611</MessageID> <Description>Failed to create trigger "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>612</MessageID> <Description>Failed to drop procedure "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>613</MessageID> <Description>Failed to drop view "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>614</MessageID> <Description>Failed to drop trigger "%1".%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>615</MessageID> <Description>Microsoft SQL Server reported SQL error %1, severity %2: %3%12 Please refer to your ConfigMgr Documentation, SQL Server Documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>616</MessageID> <Description>Microsoft SQL Server reported SQL error %1, severity %2: %3%12 Please refer to your ConfigMgr Documentation, SQL Server Documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>617</MessageID> <Description>Microsoft SQL Server reported SQL error %1, severity %2: %3%12 Please refer to your ConfigMgr Documentation, SQL Server Documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>618</MessageID> <Description>Microsoft SQL Server reported SQL message %1, severity %2: %3%12 Please refer to your ConfigMgr Documentation, SQL Server Documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>619</MessageID> <Description>Microsoft SQL Server reported SQL message %1, severity %2: %3%12 Please refer to your ConfigMgr Documentation, SQL Server Documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>620</MessageID> <Description>Microsoft SQL Server reported SQL message %1, severity %2: %3%12 Please refer to your ConfigMgr Documentation, SQL Server Documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>621</MessageID> <Description>Created the "%1" inbox definition. The inbox will exist on the Site Server with the relative path "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>622</MessageID> <Description>Created the "%1" inbox definition. The inbox will exist on the SQL Server with the relative path "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>623</MessageID> <Description>Created the "%1" inbox definition. The inbox will exist on the Client Access Point with the relative path "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>624</MessageID> <Description>Created the "%1" inbox definition. The inbox will exist on the named export "%2" with the relative path "%3".%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>625</MessageID> <Description>Read the existing "%1" inbox definition. The inbox should exist on the Site Server with the relative path "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>626</MessageID> <Description>Read the existing "%1" inbox definition. The inbox should exist on the SQL Server with the relative path "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>627</MessageID> <Description>Read the existing "%1" inbox definition. The inbox should exist on the Client Access Point with the relative path "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>628</MessageID> <Description>Read the existing "%1" inbox definition. The inbox should exist on the named export "%2" with the relative path "%3".%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>629</MessageID> <Description>Deleted the "%1" inbox definition.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>630</MessageID> <Description>Created an inbox rule to copy "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Files will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>631</MessageID> <Description>Created an inbox rule to copy "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Directories will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>632</MessageID> <Description>Created an inbox rule to move "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Files will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>633</MessageID> <Description>Created an inbox rule to move "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Directories will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>634</MessageID> <Description>Created an inbox rule to mirror "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes.%12%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>635</MessageID> <Description>Created an inbox rule to mirror "%1" directories that match the template "%1" from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes.%12%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>636</MessageID> <Description>Read the existing inbox rule to copy "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Files will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>637</MessageID> <Description>Read the existing inbox rule to copy "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Directories will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>638</MessageID> <Description>Read the existing inbox rule to move "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Files will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>639</MessageID> <Description>Read the existing inbox rule to move "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes. Directories will be created in the destination inbox with the template "%5".%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>640</MessageID> <Description>Read the existing inbox rule to mirror "%1" files from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes.%12%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>641</MessageID> <Description>Read the existing inbox rule to mirror "%1" directories from the "%2" inbox to the "%3" inbox with a maximum delay of %4 minutes.%12%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>642</MessageID> <Description>Deleted the inbox rule to copy "%1" files from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>643</MessageID> <Description>Deleted the inbox rule to copy "%1" directories from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>644</MessageID> <Description>Deleted the inbox rule to move "%1" files from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>645</MessageID> <Description>Deleted the inbox rule to move "%1" directories from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>646</MessageID> <Description>Deleted the inbox rule to mirror "%1" files from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>647</MessageID> <Description>Deleted the inbox rule to mirror "%1" directories from the "%2" inbox to the "%3" inbox.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>648</MessageID> <Description>Resolved the "%1" inbox to "%2".%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>649</MessageID> <Description>Waiting for the "%1" inbox to be defined.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>650</MessageID> <Description>Waiting for SMS_INBOX_MANAGER to create the "%1" inbox.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>651</MessageID> <Description>Still waiting for the "%1" inbox to be defined.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>652</MessageID> <Description>Still waiting for SMS_INBOX_MANAGER to create the "%1" inbox.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>653</MessageID> <Description>Still waiting for the "%1" inbox to be defined.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>654</MessageID> <Description>Still waiting for SMS_INBOX_MANAGER to create the "%1" inbox.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>655</MessageID> <Description>Could not connect to the "%1" inbox source on computer %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>656</MessageID> <Description>Could not create the "%1" inbox definition. (Could not insert the inbox definition into the "%2" inbox source on computer %3.)%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>657</MessageID> <Description>Could not create an inbox rule to copy "%1" files from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>658</MessageID> <Description>Could not create an inbox rule to copy "%1" directories from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>659</MessageID> <Description>Could not create an inbox rule to move "%1" files from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>660</MessageID> <Description>Could not create an inbox rule to move "%1" directories from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>661</MessageID> <Description>Could not create an inbox rule to mirror "%1" files from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>662</MessageID> <Description>Could not create an inbox rule to mirror "%1" directories from the "%2" inbox to the "%3" inbox. (Could not insert the inbox rule into the "%4" inbox source on computer %5.)%12%6%7%8%9%10</Description> </Message> <Message> <MessageID>663</MessageID> <Description>Instructed SMS_REPLICATION_MANAGER to replicate file "%1" to the "%2" inbox at site %3. The replication will be scheduled as low priority.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>664</MessageID> <Description>Instructed SMS_REPLICATION_MANAGER to replicate file "%1" to the "%2" inbox at site %3. The replication will be scheduled as normal priority.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>665</MessageID> <Description>Instructed SMS_REPLICATION_MANAGER to replicate file "%1" to the "%2" inbox at site %3. The replication will be scheduled as high priority.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>666</MessageID> <Description>Could not instruct SMS_REPLICATION_MANAGER to replicate file "%1" to the "%2" inbox at site %3.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>667</MessageID> <Description>Could not instruct SMS_REPLICATION_MANAGER to replicate file "%1" to the "%2" inbox at site %3.%12%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>668</MessageID> <Description>The system is low on virtual memory and the component failed a memory allocation. The component will retry the allocation until it succeeds.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>669</MessageID> <Description>The component raised an exception but failed to handle it and will be stopped immediately. Component name: %1 Executable: %2 Process ID: %3 Thread ID: %4 Instruction address: %5 Exception code: %6 Client version: %8 Additional information: %7%12%9%10</Description> </Message> <Message> <MessageID>670</MessageID> <Description>Failed to update the site control file.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>671</MessageID> <Description>Failed to read the site control file.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>672</MessageID> <Description>Failed to read registry.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>673</MessageID> <Description>Failed to copy file %1 to %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>674</MessageID> <Description>Failed to open file %1.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>675</MessageID> <Description>Failed to connect to the inbox source..%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>676</MessageID> <Description>Inbox %1 has not been created.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>677</MessageID> <Description>Required registry value %1 is empty.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>678</MessageID> <Description>Failed to update registry.%12%1%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>679</MessageID> <Description>This component failed to retrieve the list of SMS sites from the site database.%12</Description> </Message> <Message> <MessageID>680</MessageID> <Description>Failed to delete file %1.%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>681</MessageID> <Description>Failed to move file %1 to %2.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>682</MessageID> <Description>The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was signed but the authentication key did not match the recorded key for this client.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>683</MessageID> <Description>The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was not signed and an authentication key was required.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>684</MessageID> <Description>The data file "%1" that was submitted by the client whose SMS unique ID is "%2", was rejected because the file was signed and this client does not require authentication.%12%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>686</MessageID> <Description>Component %1 on %2 is %3.</Description> </Message> <Message> <MessageID>1001</MessageID> <Description>The Active Directory forest designed to store the Configuration Manager health state references has not been extended with the Configuration Manager 2007 schema extensions. The error encountered was %1.</Description> </Message> <Message> <MessageID>1002</MessageID> <Description>The Active Directory (AD) Cache Client failed to search the AD Forest for NAP-related Configuration Manager Health Information. The error encountered was %1.</Description> </Message> <Message> <MessageID>1003</MessageID> <Description>The file cache store in the System Health Validator point failed to initialize properly. The error encountered was %1.</Description> </Message> <Message> <MessageID>1004</MessageID> <Description>The File Cache Store update failed. This will potentially cause the Configuration Manager System Health Validator to not validate the incoming NAP statement of health requests correctly. The error encountered was %1.</Description> </Message> <Message> <MessageID>1005</MessageID> <Description>The File Cache Store could not be persisted to disk properly. This will potentially cause the Configuration Manager System Health Validator to not validate the incoming NAP statement of health requests correctly. The error encountered was %1.</Description> </Message> <Message> <MessageID>1006</MessageID> <Description>The Configuration Manager System Health Validator Registry Settings failed to get loaded properly. This will prevent the Configuration Manager System Health Validator Service from functioning properly. The error encountered was %1.</Description> </Message> <Message> <MessageID>1007</MessageID> <Description>Changes to Configuration Manager System Health Validator Registry Settings failed to get processed properly. This might prevent the Configuration Manager System Health Validator Service from functioning as desired. The error encountered was %1.</Description> </Message> <Message> <MessageID>1008</MessageID> <Description>The Configuration Manager System Health Validator Service failed to initialize properly. The error encountered was %1.</Description> </Message> <Message> <MessageID>1009</MessageID> <Description>The AD Cache Client failed to initialize properly. The error encountered was %1.</Description> </Message> <Message> <MessageID>1013</MessageID> <Description>Site Component Manager detected that this component should be installed on this site system. Site Component Manager will attempt to install the component every %1 minutes until the installation succeeds.</Description> </Message> <Message> <MessageID>1014</MessageID> <Description>Site Component Manager is installing this component on this site system.</Description> </Message> <Message> <MessageID>1015</MessageID> <Description>Site Component Manager successfully installed this component on this site system.</Description> </Message> <Message> <MessageID>1016</MessageID> <Description>Site Component Manager failed to install this component on this site system.</Description> </Message> <Message> <MessageID>1017</MessageID> <Description>Site Component Manager detected that this component should be reinstalled on this site system. Site Component Manager will attempt to install the component every %1 minutes until the installation succeeds.</Description> </Message> <Message> <MessageID>1018</MessageID> <Description>Site Component Manager is reinstalling this component on this site system.</Description> </Message> <Message> <MessageID>1019</MessageID> <Description>Site Component Manager successfully reinstalled this component on this site system.</Description> </Message> <Message> <MessageID>1020</MessageID> <Description>Site Component Manager failed to reinstall this component on this site system.</Description> </Message> <Message> <MessageID>1021</MessageID> <Description>Site Component Manager detected that this component should be deinstalled from this site system. Site Component Manager will attempt to deinstall the component every %1 minutes. Site Component Manager will abort the deinstallation if it fails to succeed after %2 minutes.</Description> </Message> <Message> <MessageID>1022</MessageID> <Description>Site Component Manager is deinstalling this component from this site system.</Description> </Message> <Message> <MessageID>1023</MessageID> <Description>Site Component Manager successfully deinstalled this component from this site system.</Description> </Message> <Message> <MessageID>1024</MessageID> <Description>Site Component Manager failed to deinstall this component from this site system.</Description> </Message> <Message> <MessageID>1025</MessageID> <Description>Site Component Manager failed to deinstall this component from this site system.</Description> </Message> <Message> <MessageID>1026</MessageID> <Description>Site Component Manager is configuring site system "%1" to receive Configuration Manager Server Components.</Description> </Message> <Message> <MessageID>1027</MessageID> <Description>Site Component Manager successfully configured site system "%1" to receive Configuration Manager Server Components. Site Component Manager will now begin installing the components on the site system.</Description> </Message> <Message> <MessageID>1028</MessageID> <Description>Site Component Manager failed to configure site system "%1" to receive Configuration Manager Server Components.</Description> </Message> <Message> <MessageID>1029</MessageID> <Description>Site Component Manager is reconfiguring site system "%1" to receive Configuration Manager Server Components.</Description> </Message> <Message> <MessageID>1030</MessageID> <Description>Site Component Manager successfully reconfigured site system "%1" to receive Configuration Manager Server Components. Site Component Manager will now begin reinstalling the components on the site system.</Description> </Message> <Message> <MessageID>1031</MessageID> <Description>Site Component Manager failed to reconfigure site system "%1" to receive Configuration Manager Server Components.</Description> </Message> <Message> <MessageID>1032</MessageID> <Description>Site Component Manager detected that all Configuration Manager Server Components have been deinstalled from site system "%1". Site Component Manager is removing remaining accounts, files, and registry keys associated with the Configuration Manager Server Components from the site system.</Description> </Message> <Message> <MessageID>1033</MessageID> <Description>Site Component Manager successfully removed all accounts, files, and registry keys associated with the Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>1034</MessageID> <Description>Site Component Manager failed to remove all accounts, files, and registry keys associated with the Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>1035</MessageID> <Description>Site Component Manager failed to remove all accounts, files, and registry keys associated with the Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>1036</MessageID> <Description>Site Component Manager could not access site system "%1" due to an unexpected failure within the network abstraction layer (NAL).%12</Description> </Message> <Message> <MessageID>1037</MessageID> <Description>Site Component Manager could not access site system "%1".%12</Description> </Message> <Message> <MessageID>1038</MessageID> <Description>Site Component Manager detected that site system "%1" is not running the Microsoft Windows Server operating system.%12</Description> </Message> <Message> <MessageID>1039</MessageID> <Description>Site Component Manager detected that the site server does not contain the binary files for the platform (processor architecture) of site system "%1".%12</Description> </Message> <Message> <MessageID>1040</MessageID> <Description>Site Component Manager detected that site system "%1" is based on an Intel x86 or compatible platform (processor architecture).</Description> </Message> <Message> <MessageID>1041</MessageID> <Description>Site Component Manager detected that site system "%1" is based on the Alpha platform (processor architecture).</Description> </Message> <Message> <MessageID>1042</MessageID> <Description>Site Component Manager could not detect which version of the Microsoft Windows Server operating system is running on site system "%1".%12</Description> </Message> <Message> <MessageID>1043</MessageID> <Description>Site Component Manager detected that site system "%1" is running the Microsoft Windows Server operating system version %2, which is not a supported operating system for this version of SMS.</Description> </Message> <Message> <MessageID>1044</MessageID> <Description>Site Component Manager detected that site system "%1" is running the Microsoft Windows Server operating system version %2 service pack %3, which is not a supported operating system for this version of Configuration Manager.</Description> </Message> <Message> <MessageID>1045</MessageID> <Description>Site Component Manager detected that site system "%1" is running the Microsoft Windows Workstation operating system, which is not a supported operating system for this version of SMS.</Description> </Message> <Message> <MessageID>1046</MessageID> <Description>Site Component Manager detected that site system "%1" is running the Microsoft Windows Server operating system version %2.</Description> </Message> <Message> <MessageID>1047</MessageID> <Description>Site Component Manager detected that site system "%1" is running the Microsoft Windows Server operating system version %2 service pack %3.</Description> </Message> <Message> <MessageID>1048</MessageID> <Description>Site Component Manager detected that site system "%1" is currently in use by ConfigMgr site %2.</Description> </Message> <Message> <MessageID>1049</MessageID> <Description>Site Component Manager could not find an NTFS partition on site system "%1" to hold the Configuration Manager Server Components' files.%12</Description> </Message> <Message> <MessageID>1050</MessageID> <Description>Site Component Manager could not create the Configuration Manager Server Components' installation directory "%2" on site system "%1" or set the correct permissions on the directory.%12</Description> </Message> <Message> <MessageID>1051</MessageID> <Description>Site Component Manager created the Configuration Manager Server Components' installation directory "%2" on site system "%1". Site Component Manager selected this partition because it was the NTFS partition with the most free space.</Description> </Message> <Message> <MessageID>1052</MessageID> <Description>Site Component Manager could not create the "%2" account on site system "%1".%12</Description> </Message> <Message> <MessageID>1053</MessageID> <Description>Site Component Manager created the "%2" account on site system "%1". When Site Component Manager installs services on the site system, it will configure them to log in using this account. If the site system is a stand-alone server, the account is a local machine account with full administrative rights. If the site system is a domain controller, the account is a domain account with domain user rights and full administrative rights only to the site system.</Description> </Message> <Message> <MessageID>1054</MessageID> <Description>Site Component Manager could not verify that the "%2" account exists on site system "%1".%12</Description> </Message> <Message> <MessageID>1055</MessageID> <Description>Site Component Manager could not read the Network Connection account data, which is stored in the installation directory on the site server.%12</Description> </Message> <Message> <MessageID>1056</MessageID> <Description>Site Component Manager could not write Network Connection account data to the installation directory "%2" on site system "%1".%12</Description> </Message> <Message> <MessageID>1057</MessageID> <Description>Because site system "%1" might have malfunctioned, as a safety measure Site Component Manager will attempt to reconfigure it to receive Configuration Manager Server Components and reinstall all of the Configuration Manager Server Components on it. This attempt will occur in %2 minutes.</Description> </Message> <Message> <MessageID>1058</MessageID> <Description>Site Component Manager could not remove the "%2" account from site system "%1".%12</Description> </Message> <Message> <MessageID>1059</MessageID> <Description>Site Component Manager removed the "%2" account from site system "%1".</Description> </Message> <Message> <MessageID>1060</MessageID> <Description>Site Component Manager could not remove the Configuration Manager installation directory "%2" on site system "%1".%12</Description> </Message> <Message> <MessageID>1061</MessageID> <Description>Site Component Manager removed the Configuration Manager Server Components' installation directory "%2" on site system "%1".</Description> </Message> <Message> <MessageID>1062</MessageID> <Description>Site Component Manager detected that the service account has changed, and will now reinstall all of the Configuration Manager Server Components that are installed on the site server.</Description> </Message> <Message> <MessageID>1063</MessageID> <Description>Site Component Manager was instructed by Configuration Manager Setup to shut down the site in preparation for a site upgrade, modification, or reset operation. Site Component Manager will now stop all of the Configuration Manager Server Components on all of the site systems, mark all of these components for reinstallation, and then stop itself. Site Component Manager will reinstall all of the components when it is restarted by Configuration Manager Setup at the end of the site upgrade, modification, or reset operation.</Description> </Message> <Message> <MessageID>1064</MessageID> <Description>Site Component Manager is stopping all of the Configuration Manager Server Components on site system "%1".</Description> </Message> <Message> <MessageID>1065</MessageID> <Description>Site Component Manager will not stop any Configuration Manager Server Components on site system "%1" because no Configuration Manager Server Components are installed on the site system.</Description> </Message> <Message> <MessageID>1066</MessageID> <Description>Site Component Manager will now try again to stop all of the Configuration Manager Server Components on site system "%1", as requested by Configuration Manager Setup.</Description> </Message> <Message> <MessageID>1067</MessageID> <Description>Site Component Manager will now cease trying to stop all of the Configuration Manager Server Components on site system "%1", as requested by Configuration Manager Setup. The Configuration Manager Server Components were not properly deinstalled from the site system.</Description> </Message> <Message> <MessageID>1068</MessageID> <Description>Site Component Manager was instructed by Configuration Manager Setup to deinstall the site. Site Component Manager will now deinstall all of the Configuration Manager Server Components from all of the site systems.</Description> </Message> <Message> <MessageID>1069</MessageID> <Description>Site Component Manager is deinstalling all of the Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>1070</MessageID> <Description>Site Component Manager will not deinstall any Configuration Manager Server Components from site system "%1" because no Configuration Manager Server Components are installed on the site system.</Description> </Message> <Message> <MessageID>1071</MessageID> <Description>Site Component Manager will now try again to deinstall all of the Configuration Manager Server Components from site system "%1", as requested by Configuration Manager Setup.</Description> </Message> <Message> <MessageID>1072</MessageID> <Description>Site Component Manager will now cease trying to deinstall all of the Configuration Manager Server Components from site system "%1", as requested by Configuration Manager Setup. The Configuration Manager Server Components were not properly deinstalled from the site system.</Description> </Message> <Message> <MessageID>1073</MessageID> <Description>Site Component Manager could not detect how much disk space was available in the "%1" directory on this site system.%12</Description> </Message> <Message> <MessageID>1074</MessageID> <Description>Site Component Manager cannot install this component on this site system because %1 bytes are required on the drive containing the "%2" directory, but only %3 bytes are available.</Description> </Message> <Message> <MessageID>1075</MessageID> <Description>Site Component Manager detected that %1 bytes are required by this component on the drive containing the "%2" directory, and that %3 bytes are available. Site Component Manager will proceed with the installation of this component.</Description> </Message> <Message> <MessageID>1076</MessageID> <Description>Site Component Manager could not copy file "%1" to "%2".%12 Site Component Manager reports this error when it fails to: 1. Create the destination directory, if it does not already exist. 2. Assign the proper directory permissions to the destination directory. 3. Copy the source file to the destination directory.</Description> </Message> <Message> <MessageID>1077</MessageID> <Description>Site Component Manager could not copy file "%1" to "%2".%12 Site Component Manager reports this error when it fails to: 1. Create the destination directory, if it does not already exist. 2. Copy the source file to the destination directory.</Description> </Message> <Message> <MessageID>1078</MessageID> <Description>Site Component Manager copied file "%1" to "%2".</Description> </Message> <Message> <MessageID>1079</MessageID> <Description>Site Component Manager did not copy file "%1" to "%2", because the source file is not a newer version than the destination file.</Description> </Message> <Message> <MessageID>1080</MessageID> <Description>Site Component Manager detected that the %1 service was installed on site system "%2", but Site Component Manager could not deinstall the service.%12</Description> </Message> <Message> <MessageID>1081</MessageID> <Description>Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3".%12</Description> </Message> <Message> <MessageID>1082</MessageID> <Description>Site Component Manager could not start the %1 service on site system "%2" to install component %4 with the service logging on as account "%3".%12</Description> </Message> <Message> <MessageID>1083</MessageID> <Description>Site Component Manager successfully used the %1 service to run the following program on site system "%2": %3 %4 %5 The program failed for the following reason: %6</Description> </Message> <Message> <MessageID>1084</MessageID> <Description>Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3".%12</Description> </Message> <Message> <MessageID>1085</MessageID> <Description>Site Component Manager could not start the %1 service on site system "%2" with the service logging on as account "%3".%12</Description> </Message> <Message> <MessageID>1086</MessageID> <Description>Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3".%12</Description> </Message> <Message> <MessageID>1087</MessageID> <Description>Site Component Manager could not start the %1 service on site system "%2" with the service logging on as account "%3".%12</Description> </Message> <Message> <MessageID>1088</MessageID> <Description>Site Component Manager installed the %1 service on site system "%2". The service will log on as account "%3".</Description> </Message> <Message> <MessageID>1089</MessageID> <Description>Site Component Manager started the %1 service on site system "%2".</Description> </Message> <Message> <MessageID>1090</MessageID> <Description>Site Component Manager could not stop the %1 service on site system "%2".%12</Description> </Message> <Message> <MessageID>1091</MessageID> <Description>Site Component Manager could not deinstall the %1 service from site system "%2".%12</Description> </Message> <Message> <MessageID>1092</MessageID> <Description>Site Component Manager stopped the %1 service on site system "%2".</Description> </Message> <Message> <MessageID>1093</MessageID> <Description>Site Component Manager deinstalled the %1 service from site system "%2".</Description> </Message> <Message> <MessageID>1094</MessageID> <Description>Site Component Manager installed this component as a thread of the SMS Executive service on this site system.</Description> </Message> <Message> <MessageID>1095</MessageID> <Description>Site Component Manager started this component on this site system.</Description> </Message> <Message> <MessageID>1096</MessageID> <Description>Site Component Manager stopped this component on this site system.</Description> </Message> <Message> <MessageID>1097</MessageID> <Description>Site Component Manager deinstalled this component as a thread of SMS Executive on this site system.</Description> </Message> <Message> <MessageID>1098</MessageID> <Description>Site Component Manager could not start this component on this site system because the SMS Executive service is not running.</Description> </Message> <Message> <MessageID>1099</MessageID> <Description>Site Component Manager signaled this component on this site system to stop, but it did not stop after 60 seconds.</Description> </Message> <Message> <MessageID>1104</MessageID> <Description>SMS Executive detected that this component stopped unexpectedly.%12</Description> </Message> <Message> <MessageID>1105</MessageID> <Description>SMS Executive is next scheduled to start this component on "%1".</Description> </Message> <Message> <MessageID>1106</MessageID> <Description>SMS Executive will never start this component because it is never scheduled to run. If you want SMS Executive to start the component, enable the component in the Configuration Manager Console and adjust its schedule to an appropriate setting.</Description> </Message> <Message> <MessageID>1107</MessageID> <Description>SMS Executive is scheduled to start this component now, but cannot because it is already running.</Description> </Message> <Message> <MessageID>1108</MessageID> <Description>SMS Executive could not start this component because it could not load \"%1\" using the MFC AfxLoadLibrary() function.%12</Description> </Message> <Message> <MessageID>1109</MessageID> <Description>SMS Executive could not start this component because it could not determine the address of the ThreadMain() function exported by \"%1\" using the Win32 GetProcAddress() function.%12</Description> </Message> <Message> <MessageID>1200</MessageID> <Description>In the last %1 hours, Status Manager processed %2 status messages. Of these, %3 were written to the site database, %4 were replicated to the parent site, %5 were reported as Windows Events on the site server, and %6 were passed as command-line parameters to external programs. During this time, Status Manager received %7 corrupt files that contained one or more status messages that could not be processed. Also during this time, Status Manager used %8 hours of CPU time, which represents a %9 percent utilization of the total CPU time available for the period. Status Manager periodically reports this message for your convenience; you can ignore it if your not interested in monitoring Status Manager's processing performance. Status Manager will report this message again in %10 hours.%12</Description> </Message> <Message> <MessageID>1201</MessageID> <Description>Status Manager successfully initialized the "SMS Status Messages" performance object. Every time Status Manager receives a status message it will update the performance counters contained by this performance object. You can measure Status Manager's processing performance by monitoring this performance object with the Windows Performance Monitor. For example, you can monitor the total number of status messages written to the site database by Status Manager by monitoring the "_Total" instance of the "Written To SMS Database" counter. Status Manager resets all of the counts when it is restarted, and the counts cannot be viewed when Status Manager is not running.%12</Description> </Message> <Message> <MessageID>1202</MessageID> <Description>Due to an internal error, Status Manager could not initialize the "SMS Status Messages" performance object. You can measure Status Manager's processing performance by monitoring this performance object with the Windows Performance Monitor. This problem will not affect Status Manager's ability to process status messages, but it will prevent you from viewing this performance object. You can ignore this problem if you do not need to view this performance object. Please refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.%12</Description> </Message> <Message> <MessageID>1203</MessageID> <Description>Status Manager successfully initialized an in-memory queue to forward status messages to the summarizer component %1. The summarizer distills the stream of status messages into a high-level summary, which you can view under the System Status node of the Configuration Manager Console. You can monitor the performance of the in-memory queue in the Windows Performance Monitor by selecting the "SMS In-Memory Queues" performance object, and then selecting the instance for this summarizer. For example, the "Total Objects Enqueued" counter tells you how many status messages Status Manager has forwarded to the summarizer. The counts are reset when both Status Manager and the summarizer are restarted, which typically occurs when SMS Executive is restarted. The counts cannot be viewed when Status Manager and the summarizer are both not running.%12</Description> </Message> <Message> <MessageID>1204</MessageID> <Description>Status Manager will no longer forward status messages to the summarizer component %1 because the summarizer was disabled. The summarizer distills a stream of status messages into a high-level summary, which you can view under the System Status node of the Configuration Manager Console. If you reenable the summarizer in the Configuration Manager Console, Status Manager will resume forwarding messages to the summarizer.%12</Description> </Message> <Message> <MessageID>1205</MessageID> <Description>Due to an internal error, Status Manager could not initialize an in-memory queue to forward status messages to the summarizer component %1. The summarizer distills the stream of status messages into a high-level summary, which you can view under the System Status node of the Configuration Manager Console. Until this problem is fixed, the high-level summary will be inaccurate or not available. Please refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.%12</Description> </Message> <Message> <MessageID>1209</MessageID> <Description>Status Manager has created %1 instances of the "SMS Status Messages" performance object, which is the maximum allowed number of instances. Every time Status Manager receives a status message it will update the performance counters contained by this performance object. You can measure Status Manager's processing performance by monitoring this performance object with the Windows Performance Monitor. Because the maximum limit was reached, Status Manager will not create any more instances of this performance object. Status Manager builds the list of instances as it receives status messages. You can reset the list by restarting Status Manager.%12</Description> </Message> <Message> <MessageID>1210</MessageID> <Description>Status Manager was instructed by a Status Filter Rule to execute program and command-line arguments "%1" upon receipt of a status message that satisfied the criteria specified by the Status Filter Rule, but the program and command-line arguments are invalid. (Note that for display purposes, the program and command-line arguments were truncated to %2 characters in this message.)</Description> </Message> <Message> <MessageID>1211</MessageID> <Description>Status Manager was instructed by a Status Filter Rule to execute program "%1" with command-line arguments "%2" upon receipt of a status message that satisfied the criteria specified by the Status Filter Rule. (Note that for display purposes, the program and command-line arguments were truncated to %3 characters in this message.) Status Manager failed to execute the program.%12</Description> </Message> <Message> <MessageID>1212</MessageID> <Description>Status Manager was instructed by a Status Filter Rule to execute program "%1" with command-line arguments "%2" upon receipt of a status message that satisfied the criteria specified by the Status Filter Rule. (Note that for display purposes, the program and command-line arguments were truncated to %3 characters in this message.) Status Manager successfully started the program, but the program was still running after 60 seconds.</Description> </Message> <Message> <MessageID>1213</MessageID> <Description>Status Manager received a status message reported by component "%1" running on computer "%2", and the time stamp on the message is more recent than the current system time on the site server.</Description> </Message> <Message> <MessageID>1214</MessageID> <Description>Status Manager received a status message with an invalid time stamp. The status message was reported by component "%1" running on computer "%2".</Description> </Message> <Message> <MessageID>1215</MessageID> <Description>Status Manager received a status message reported by component "%1" running on computer "%2", and the time stamp on the message is more recent than the current system time on the site server.</Description> </Message> <Message> <MessageID>1300</MessageID> <Description>Network Discovery is starting.%12</Description> </Message> <Message> <MessageID>1301</MessageID> <Description>Network Discovery is retrieving information about previously discovered devices and networks from CIM Object Manager.%12 This process can take a long time when many devices are being discovered.</Description> </Message> <Message> <MessageID>1302</MessageID> <Description>Network Discovery protocol modules are initializing.%12</Description> </Message> <Message> <MessageID>1303</MessageID> <Description>Network Discovery is starting protocol operations. Network Discovery is querying network devices to discover devices related to the specified configuration.%12</Description> </Message> <Message> <MessageID>1304</MessageID> <Description>Network Discovery is stopping protocol operations.%12</Description> </Message> <Message> <MessageID>1305</MessageID> <Description>Network Discovery is stopping the Network Discovery protocol modules.%12</Description> </Message> <Message> <MessageID>1306</MessageID> <Description>Network Discovery is storing currently discovered devices and networks in CIM Object Manager, which can take a long time when many devices are being discovered.%12</Description> </Message> <Message> <MessageID>1307</MessageID> <Description>Network Discovery is exporting devices and networks to the Discovery Data Manager. This process can take a long time when many devices are being discovered.%12</Description> </Message> <Message> <MessageID>1308</MessageID> <Description>Network Discovery has stopped.%12</Description> </Message> <Message> <MessageID>1309</MessageID> <Description>Network Discovery failed to connect to a DHCP server due to insufficient access.%12 This error message means that fewer clients and networks will be found than otherwise. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs.</Description> </Message> <Message> <MessageID>1310</MessageID> <Description>Network Discovery failed to connect to a DHCP server due to a connection error. (Network Discovery can communicate only with Microsoft DHCP servers; if you do not use these servers, you can ignore this error.)%12</Description> </Message> <Message> <MessageID>1311</MessageID> <Description>Network Discovery failed to perform a WinSock operation.%12</Description> </Message> <Message> <MessageID>1312</MessageID> <Description>Network Discovery failed to perform a WinSock operation relating to multicast membership. Network Discovery will not discover other routers on your local subnet by listening for OSPF packets. However, if Network Discovery can detect your default gateway using SNMP, it will find those routers anyway.%12</Description> </Message> <Message> <MessageID>1313</MessageID> <Description>Network Discovery did not have time to finish. Therefore, the information in the site database is not as complete as it should be.%12</Description> </Message> <Message> <MessageID>1314</MessageID> <Description>Network Discovery failed to connect to CIM Object Manager. Network Discovery cannot continue because all its configuration information is retrieved from CIM Object Manager.%12</Description> </Message> <Message> <MessageID>1315</MessageID> <Description>Network Discovery detected CIM Object Manager, but could not establish a connection to it. Network Discovery cannot continue because all its configuration information is retrieved from CIM Object Manager.%12</Description> </Message> <Message> <MessageID>1316</MessageID> <Description>Network Discovery failed to read information from CIM Object Manager. Network Discovery cannot continue.%12</Description> </Message> <Message> <MessageID>1317</MessageID> <Description>Network Discovery failed to read information from CIM Object Manager. Network Discovery will continue, but slowly.%12</Description> </Message> <Message> <MessageID>1318</MessageID> <Description>Network Discovery failed to write information to CIM Object Manager. Network Discovery cannot continue.%12</Description> </Message> <Message> <MessageID>1319</MessageID> <Description>Network Discovery failed to write information to CIM Object Manager. Network discovery will continue, but slowly.%12</Description> </Message> <Message> <MessageID>1320</MessageID> <Description>Network Discovery failed to execute a query from CIM Object Manager. Network discovery will continue, but slowly.%12</Description> </Message> <Message> <MessageID>1321</MessageID> <Description>Network Discovery failed to communicate with some SNMP devices because of an internal problem with SNMP resources. Network Discovery will continue, but slowly. The discovery duration might have to elapse before discovery can finish fully.%12</Description> </Message> <Message> <MessageID>1322</MessageID> <Description>Network Discovery failed to export a device to the Discovery Data Manager. Therefore, discovered devices will not appear in the site database.%12</Description> </Message> <Message> <MessageID>1323</MessageID> <Description>Network Discovery failed to export a network to the Discovery Data Manager. Therefore, discovered devices will not appear in the site database.%12</Description> </Message> <Message> <MessageID>1324</MessageID> <Description>Network Discovery failed to enumerate the computers on one or more domains.%12</Description> </Message> <Message> <MessageID>2300</MessageID> <Description>Distribution Manager is beginning to process package "%1" (package ID = %2).%12</Description> </Message> <Message> <MessageID>2301</MessageID> <Description>Distribution Manager successfully processed package "%1" (package ID = %2).%12</Description> </Message> <Message> <MessageID>2302</MessageID> <Description>Distribution Manager failed to process package "%1" (package ID = %2).%12</Description> </Message> <Message> <MessageID>2303</MessageID> <Description>Distribution Manager refreshed package "%1" on distribution point "%2".%12</Description> </Message> <Message> <MessageID>2304</MessageID> <Description>Distribution Manager is retrying to distribute package "%1".%12 Wait to see if the package is successfully distributed on the retry.</Description> </Message> <Message> <MessageID>2305</MessageID> <Description>Distribution Manager failed to process package "%1" without a source directory.%12</Description> </Message> <Message> <MessageID>2306</MessageID> <Description>The source directory "%1" for package "%2" does not exist.%12</Description> </Message> <Message> <MessageID>2307</MessageID> <Description>Distribution Manager failed to access the source directory "%1" for package "%2".%12</Description> </Message> <Message> <MessageID>2308</MessageID> <Description>Distribution Manager failed to remove the previously compressed copy for package "%1" located at "%2".%12</Description> </Message> <Message> <MessageID>2309</MessageID> <Description>Distribution Manager failed to compress package "%1" from "%2" to "%4". The file that failed the compression is "%3".%12</Description> </Message> <Message> <MessageID>2310</MessageID> <Description>Distribution Manager compressed package "%1" from "%2" to "%3".%12</Description> </Message> <Message> <MessageID>2311</MessageID> <Description>Distribution Manager successfully created or updated package "%1".%12</Description> </Message> <Message> <MessageID>2312</MessageID> <Description>Distribution Manager failed to update the distribution source for package "%1".%12</Description> </Message> <Message> <MessageID>2313</MessageID> <Description>Distribution Manager failed to remove package "%1" from "%2".%12</Description> </Message> <Message> <MessageID>2314</MessageID> <Description>Distribution Manager removed package "%1" from "%2" due to changes in the share type or the share name.%12</Description> </Message> <Message> <MessageID>2315</MessageID> <Description>Distribution Manager deleted the compressed image of package "%1" at "%2".%12</Description> </Message> <Message> <MessageID>2316</MessageID> <Description>Distribution Manager failed to delete the compressed image of package "%1" at "%2".%12</Description> </Message> <Message> <MessageID>2317</MessageID> <Description>Distribution Manager is refreshing package "%1" on distribution point "%2".%12</Description> </Message> <Message> <MessageID>2318</MessageID> <Description>Distribution Manager failed to distribute package "%1".%12</Description> </Message> <Message> <MessageID>2319</MessageID> <Description>Distribution Manager failed to decompress package "%1" from "%2".%12</Description> </Message> <Message> <MessageID>2320</MessageID> <Description>There is not enough free disk space on the site server to decompress package "%1".%12</Description> </Message> <Message> <MessageID>2321</MessageID> <Description>Distribution Manager failed to decompress package "%1" from "%2" to "%3". The file that failed to decompress is "%4".%12</Description> </Message> <Message> <MessageID>2322</MessageID> <Description>Distribution Manager decompressed package "%1" from "%2" to "%3".%12</Description> </Message> <Message> <MessageID>2323</MessageID> <Description>Distribution Manager failed to connect to the distribution point.%12</Description> </Message> <Message> <MessageID>2324</MessageID> <Description>Distribution Manager failed to find or create the defined share or folder (%3) on distribution point "%1" for distributing package "%2".%12</Description> </Message> <Message> <MessageID>2325</MessageID> <Description>Distribution Manager failed to create subdirectories on distribution point "%1" for distributing package "%2".%12</Description> </Message> <Message> <MessageID>2326</MessageID> <Description>Distribution Manager failed to save package status for package "%1" to the site database.%12</Description> </Message> <Message> <MessageID>2327</MessageID> <Description>Distribution Manager failed to update the package properties on distribution points for package "%1".%12</Description> </Message> <Message> <MessageID>2328</MessageID> <Description>Distribution Manager failed to copy package "%1" from "%2" to "%3".%12</Description> </Message> <Message> <MessageID>2329</MessageID> <Description>Distribution Manager copied package "%1" from "%2" to "%3".%12</Description> </Message> <Message> <MessageID>2330</MessageID> <Description>Distribution Manager successfully distributed package "%1" to distribution point "%2".%12</Description> </Message> <Message> <MessageID>2331</MessageID> <Description>Distribution Manager successfully removed package "%1" from distribution point "%2".%12</Description> </Message> <Message> <MessageID>2332</MessageID> <Description>Distribution Manager failed to remove package "%1" from distribution path "%2".%12</Description> </Message> <Message> <MessageID>2333</MessageID> <Description>Distribution Manager is preparing to send the compressed image of package "%1" to child site "%2".%12</Description> </Message> <Message> <MessageID>2334</MessageID> <Description>Distribution Manager created a 1.x style instruction to send package "%1" to 1.x child site "%2".%12</Description> </Message> <Message> <MessageID>2335</MessageID> <Description>Distribution Manager instructed Scheduler and Sender to send package "%1" to child site "%2".%12</Description> </Message> <Message> <MessageID>2336</MessageID> <Description>Distribution Manager failed to create a 1.x style instruction to send package "%1" to 1.x child site "%2".%12</Description> </Message> <Message> <MessageID>2337</MessageID> <Description>Distribution Manager failed to instruct Scheduler to send package "%1" to child site "%2".%12</Description> </Message> <Message> <MessageID>2338</MessageID> <Description>Distribution Manager created a 1.x style instruction to send package definition for package "%1" to 1.x child site "%2".%12</Description> </Message> <Message> <MessageID>2339</MessageID> <Description>Distribution Manager instructed Scheduler and Sender to send the package information for package "%1" to child site "%2".%12</Description> </Message> <Message> <MessageID>2340</MessageID> <Description>Distribution Manager failed to create a 1.x style instruction to send the package definition for package "%1" to 1.x child site "%2".%12</Description> </Message> <Message> <MessageID>2341</MessageID> <Description>Distribution Manager failed to send the package information for package "%1" to child site "%2".%12</Description> </Message> <Message> <MessageID>2342</MessageID> <Description>Distribution Manager is starting to distribute package "%1" to distribution point "%2".%12</Description> </Message> <Message> <MessageID>2343</MessageID> <Description>There is not enough free disk space to copy package "%1" to "%2".%12</Description> </Message> <Message> <MessageID>2344</MessageID> <Description>Failed to create virtual directory on the defined share or volume on distribution point "%1".%12</Description> </Message> <Message> <MessageID>2345</MessageID> <Description>Failed to delete virtual directory on the defined share or volume on distribution point "%1".%12</Description> </Message> <Message> <MessageID>2346</MessageID> <Description>Distribution Manager failed to distribute package "%1".%12</Description> </Message> <Message> <MessageID>2347</MessageID> <Description>Distribution Manager upgraded the hidden file ISAPI on the distribution point but was unable to load the file because the original ISAPI was in use. To load the new ISAPI please restart IIS on computer "%1".%12</Description> </Message> <Message> <MessageID>2348</MessageID> <Description>Distribution Manager failed to decompress package "%1" from "%2".%12</Description> </Message> <Message> <MessageID>2349</MessageID> <Description>The WebDAV server extensions are disabled on the distribution point "%1".%12 As a result, clients will not be able to use BITS support on the distribution point. To enable BITS support, enable the WebDAV server extension from the Web Service Extensions node in the Internet Information Services (IIS) administrative tool.</Description> </Message> <Message> <MessageID>2350</MessageID> <Description>Distribution Manager instructed Scheduler and Sender to send a forwarding request to site "%2", requesting that site to forward package "%1" to site "%3".%12</Description> </Message> <Message> <MessageID>2351</MessageID> <Description>Distribution Manager is unable to forward package "%1" to site(s) "%2" because the local version of the package ("%3") is greater than the version requested ("%4").%12</Description> </Message> <Message> <MessageID>2352</MessageID> <Description>Distribution Manager is unable to forward package "%1" to site(s) "%2" because the local version of the package ("%3") is lower than the version requested ("%4").%12</Description> </Message> <Message> <MessageID>2353</MessageID> <Description>Failed to configure ports in IIS on the defined share or volume on distribution point "%1".%12</Description> </Message> <Message> <MessageID>2354</MessageID> <Description>Failed to validate package status file "%1" received from Distribution Point %2 for package %3.%12</Description> </Message> <Message> <MessageID>2355</MessageID> <Description>Package "%1" is not assigned to any standard distribution points for site "%2". Branch distribution points require the package to be assigned to at least one standard distribution point .%12 The branch distribution point downloads package content from a standard distribution point from the site where the branch distribution point client is assigned.</Description> </Message> <Message> <MessageID>2356</MessageID> <Description>Distribution Manager failed to instruct Package Transfer manager to send package "%1" to distribution point "%2".%12</Description> </Message> <Message> <MessageID>2357</MessageID> <Description>Distribution Manager instructed Package Transfer manager to send package "%1" to distribution point "%2".%12</Description> </Message> <Message> <MessageID>2358</MessageID> <Description>"%1" server ("%2") is a 32-bit system. Multicast or File Streaming are not supported distribution point features on 32-bit system.%12 These features can not be enabled on this distribution point.</Description> </Message> <Message> <MessageID>2359</MessageID> <Description>Distribution Manager failed to find a drive on distribution point "%1" on system "%2" which has characteristics appropriate for storing shared folders used by distribution point.%12</Description> </Message> <Message> <MessageID>2360</MessageID> <Description>Distribution Manager failed to verify drive specified by user on distribution point "%1" on system "%2".%12</Description> </Message> <Message> <MessageID>2361</MessageID> <Description>Distribution Manager failed to access the source directory "%1" for content "%2" (content ID = %3).%12</Description> </Message> <Message> <MessageID>2362</MessageID> <Description>Distribution Manager successfully installed IIS component of operating system to distribution point "%1".%12</Description> </Message> <Message> <MessageID>2363</MessageID> <Description>Distribution Manager has not tried to install IIS component of operating system to distribution point "%1" because its operating system is older than Windows Server 2008. Manual installation of IIS component of operating system to distribution point might be needed. Please ensure RDC is also enabled.%12</Description> </Message> <Message> <MessageID>2364</MessageID> <Description>Distribution Manager installed IIS component of operating system to distribution point "%1". Installation process ended with an exit code of %2. Reboot of machine "%1" is needed to complete the configuration of IIS component of operating system. Also please ensure that the http(s) traffic is not blocked on this machine by firewall settings.%12</Description> </Message> <Message> <MessageID>2365</MessageID> <Description>Distribution Manager attempted to run a tool to install IIS component of operating system to distribution point "%1". The tool returned non-zero error code %2. Reboot or manual installation of IIS might be required to complete the configuration of IIS component of operating system. Also please ensure that the http(s) traffic is not blocked on this machine by firewall settings and RDC is enabled.%12</Description> </Message> <Message> <MessageID>2366</MessageID> <Description>Distribution Manager attempted to run a tool to install IIS component of operating system to distribution point "%1". Reboot or manual installation of IIS might be required to complete the configuration of IIS component of operating system. Also please ensure that the http(s) traffic is not blocked on this machine by firewall settings.%12</Description> </Message> <Message> <MessageID>2367</MessageID> <Description>Package "%1" content was successfully imported from a prestaged content file to distribution points on site server "%2" (%3).%12</Description> </Message> <Message> <MessageID>2368</MessageID> <Description>An error occurred during the import of content from a prestaged content file to distribution points on site server "%1" (%2).%12</Description> </Message> <Message> <MessageID>2369</MessageID> <Description>WDS is not installed on distribution point "%1".The PXE service point will not be available.%12</Description> </Message> <Message> <MessageID>2370</MessageID> <Description>Distribution Manager failed to install distribution point %1 on computer %2.%12</Description> </Message> <Message> <MessageID>2371</MessageID> <Description>Distribution Manager is waiting for package %1 content to be prestaged on the distribution point %2. You must manually prestage the package %1 on the distribution point before the content will be available.</Description> </Message> <Message> <MessageID>2372</MessageID> <Description>The content files for package %1 have not yet arrived from the source site %2. Distribution Manager will try again later to distribute the content.</Description> </Message> <Message> <MessageID>2373</MessageID> <Description>PXE is %1 on distribution point %2</Description> </Message> <Message> <MessageID>2374</MessageID> <Description>Multicast is %1 on distribution point %2</Description> </Message> <Message> <MessageID>2375</MessageID> <Description>Created virtual directories on the defined share or volume on distribution point "%1" successfully.</Description> </Message> <Message> <MessageID>2376</MessageID> <Description>Distribution Manager created a snapshot for content %1 successfully.</Description> </Message> <Message> <MessageID>2380</MessageID> <Description>Start to evaluate package "%1" on distribution point "%2".</Description> </Message> <Message> <MessageID>2381</MessageID> <Description>An evaluation task is running. Put package "%1" to wait queue on distribution point "%2".</Description> </Message> <Message> <MessageID>2382</MessageID> <Description>The hash of package "%1" is invalid on distribution point "%2". Please redistribute the package.</Description> </Message> <Message> <MessageID>2383</MessageID> <Description>Failed to validate package "%1" on distribution point "%2". The package may not be present or may be corrupt. Please redistribute it.</Description> </Message> <Message> <MessageID>2384</MessageID> <Description>Package "%1" on distribution point "%2" has been verified successfully.</Description> </Message> <Message> <MessageID>2385</MessageID> <Description>Following file(s) of package "%1" on distribution point "%2" are missing. %3</Description> </Message> <Message> <MessageID>2386</MessageID> <Description>All content on distribution point "%1" has been verified.</Description> </Message> <Message> <MessageID>2387</MessageID> <Description>The hash of the migrated package "%1" is incorrect in the database. Please update the package on the Configuration Manager 2007 site and then migrate the package again.</Description> </Message> <Message> <MessageID>2388</MessageID> <Description>Failed to retrieve the package list on the distribution point %1. Or the package list in content library doesn't match the one in WMI. Review smsdpmon.log for more information about this failure.</Description> </Message> <Message> <MessageID>2389</MessageID> <Description>Failed to copy the package "%1" from "%2" into the content library on the distribution point server "%3".</Description> </Message> <Message> <MessageID>2390</MessageID> <Description>The migrated packages on the distribution point server "%1" have been successfully copied into the content library on the server.</Description> </Message> <Message> <MessageID>2391</MessageID> <Description>Distribution Manager failed to connect to the distribution point %1. Check your network and firewall settings.</Description> </Message> <Message> <MessageID>2392</MessageID> <Description>Distribution Manager has not tried to install IIS component of operating system to distribution point "%1". You should install and configure IIS manually. Please ensure RDC is also enabled.%12</Description> </Message> <Message> <MessageID>2393</MessageID> <Description>Successfully retrieved and validated the package list from the distribution point %1.</Description> </Message> <Message> <MessageID>2394</MessageID> <Description>A reboot is required on the distribution point %1.</Description> </Message> <Message> <MessageID>2397</MessageID> <Description>Detail will be available after the server finishes processing the messages.</Description> </Message> <Message> <MessageID>2398</MessageID> <Description>Starting to process content</Description> </Message> <Message> <MessageID>2399</MessageID> <Description>Successfully completed the installation or upgrade of the distribution point on computer "%1".</Description> </Message> <Message> <MessageID>2400</MessageID> <Description>Database Notification Monitor failed to copy file smsxp.dll from the \SMS\bin\i386 directory to its required place in the\Windows\system32 directory. Smsxp.dll must exist in the system32 directory for all triggering operations to function, such as notification to the server components of a new package or collection.%12</Description> </Message> <Message> <MessageID>2401</MessageID> <Description>Database Notification Monitor failed to execute database maintenance task "%1".%12</Description> </Message> <Message> <MessageID>2402</MessageID> <Description>Database Notification Monitor failed to execute database maintenance SQL Server command "%1".%12</Description> </Message> <Message> <MessageID>2404</MessageID> <Description>The database maintenance SQL Server task "%1" completed successfully. The task deleted %2 items from the site database.</Description> </Message> <Message> <MessageID>2405</MessageID> <Description>Database Notification Monitor is installing trigger "%1" for table "%2" and actions "%3" in the site database. Server components such as Hierarchy Manager, Collection Evaluator, and Discovery Data Manager instruct Database Notification Monitor to install SQL Server triggers. Then, when certain kinds of data are added to, changed in, or removed from the site database, the SQL Server triggers notify Database Notification Monitor. In turn, Database Notification Monitor notifies the appropriate server components.</Description> </Message> <Message> <MessageID>2406</MessageID> <Description>Database Notification Monitor is removing trigger "%1" from the site database. Server components such as Hierarchy Manager, Collection Evaluator, and Discovery Data Manager instruct Database Notification Monitor to install SQL triggers. Then, when certain kinds of data are added to, changed in, or removed from the site database, the SQL Server triggers notify Database Notification Monitor. In turn, Database Notification Monitor notifies the appropriate server components. This trigger is being removed because it is no longer needed.</Description> </Message> <Message> <MessageID>2407</MessageID> <Description>Database Notification Monitor failed to install trigger "%1" in the site database.%12</Description> </Message> <Message> <MessageID>2408</MessageID> <Description>Database Notification Monitor is executing database maintenance SQL Server command/task "%1". You can configure the execution schedule for this SQL Server command/task in the Configuration Manager console under Administration / Overview / Site Configuration / Sites -> Site Maintenance.</Description> </Message> <Message> <MessageID>2409</MessageID> <Description>The Delete Aged Collected Files database maintenance task completed successfully. The task deleted %1 collected files and %2 directories.</Description> </Message> <Message> <MessageID>2410</MessageID> <Description>The Rebuild Indexes database maintenance task successfully recreated index "%1" on table "%2" in the site database. The Rebuild Indexes task periodically recreates the indexes in the site database to provide optimal query performance.</Description> </Message> <Message> <MessageID>2411</MessageID> <Description>The Rebuild Indexes task has dropped index "%1" on table "%2" in the site database. The Rebuild Indexes task periodically recreates the indexes in the site database to provide optimal query performance. The task will drop an index when the index has a density of less than 0.50, which indicates that it is not selective enough to improve query performance.</Description> </Message> <Message> <MessageID>2412</MessageID> <Description>The Monitor Keys and Recreate Views database maintenance task has detected less than 100 values left for key "%1" and has rolled it over to "%2".%12</Description> </Message> <Message> <MessageID>2413</MessageID> <Description>The Software Metering File Usage Summarization task has completed, %1 rows have been added to the summary tables.%12</Description> </Message> <Message> <MessageID>2414</MessageID> <Description>The Software Metering Data Monthly Usage Summarization task has completed, %1 rows have been added or updated in the summary tables.%12</Description> </Message> <Message> <MessageID>2415</MessageID> <Description>The Clear Install Flag for Undiscovered Clients task has completed, %1 rows have been updated in system discovery tables.%12</Description> </Message> <Message> <MessageID>2416</MessageID> <Description>Database Notification Monitor could not start the SMS Backup service on server %1.%12</Description> </Message> <Message> <MessageID>2417</MessageID> <Description>The Delete Inactive Client Discovery Data task has completed, %1 inactive clients have been removed from the database.%12</Description> </Message> <Message> <MessageID>2418</MessageID> <Description>The Delete Obsolete Client Discovery Data task has completed, %1 obsolete clients have been removed from the database.%12</Description> </Message> <Message> <MessageID>2419</MessageID> <Description>The Client Access License Usage Data Summarization task has completed, %1 rows have been added or updated in the summary table.%12</Description> </Message> <Message> <MessageID>2420</MessageID> <Description>The task "%1" is configured to run today, but it could not run within the scheduled time. %12</Description> </Message> <Message> <MessageID>2421</MessageID> <Description>Database Notification Monitor succeed to start task Reset AMT Computer Passwords.%12</Description> </Message> <Message> <MessageID>2422</MessageID> <Description>Database Notification Monitor succeed to start task Evaluate Provisioned AMT Computer Certificates.%12</Description> </Message> <Message> <MessageID>2423</MessageID> <Description>Database Notification Monitor succeed to run task 'Delete Expired Bookmarks'. %1 bookmarks have been removed.%12</Description> </Message> <Message> <MessageID>2424</MessageID> <Description>Database Notification Monitor succeed to run task 'Delete Expired Activities'. %1 activities have been removed.%12</Description> </Message> <Message> <MessageID>2425</MessageID> <Description>Database Notification Monitor succeed to run task 'Delete Expired Activity Facts'. %1 activity facts have been removed.%12</Description> </Message> <Message> <MessageID>2426</MessageID> <Description>Database Notification Monitor successfully ran task 'Delete Obsolete Alerts'. %1 alerts have been removed.%12</Description> </Message> <Message> <MessageID>2427</MessageID> <Description>The database maintenance SQL Server task "%1" completed successfully. %2 catalog rows have been added.</Description> </Message> <Message> <MessageID>2428</MessageID> <Description>The database maintenance SQL Server task "%1" completed successfully. %2 Software rows have been added to summary table.</Description> </Message> <Message> <MessageID>2500</MessageID> <Description>Collection Evaluator failed to enumerate collections.%12</Description> </Message> <Message> <MessageID>2504</MessageID> <Description>Collection Evaluator failed to find collection "%1". Collection Evaluator received a .udc (update collection) or .adc (create collection) file for a collection that does not exist.%12</Description> </Message> <Message> <MessageID>2507</MessageID> <Description>Collection Evaluator failed to delete collection "%1".%12</Description> </Message> <Message> <MessageID>2511</MessageID> <Description>Collection Evaluator failed to update the membership of collection "%1".%12</Description> </Message> <Message> <MessageID>2519</MessageID> <Description>Collection Evaluator failed to enumerate members of collection "%1" at site "%2".%12</Description> </Message> <Message> <MessageID>2521</MessageID> <Description>Collection Evaluator failed to retrieve collection "%1" from the collection source. (On primary sites, the collection source is the site database. On secondary sites, it is \Sms\inboxes\colleval.box.)%12</Description> </Message> <Message> <MessageID>2523</MessageID> <Description>Collection Evaluator failed to enumerate membership rules for collection "%1".%12</Description> </Message> <Message> <MessageID>2524</MessageID> <Description>Collection Evaluator failed to write to file "%1".%12</Description> </Message> <Message> <MessageID>2530</MessageID> <Description>Collection Evaluator failed to update collection "%1" in the collection source. (On primary sites, this is the site database. On secondary sites, this is \Sms\inboxes\colleval.box.)%12</Description> </Message> <Message> <MessageID>2531</MessageID> <Description>Collection Evaluator failed to retrieve a SQL Server command from the collection membership rule.%12</Description> </Message> <Message> <MessageID>2532</MessageID> <Description>Collection Evaluator failed to connect to the site database.%12</Description> </Message> <Message> <MessageID>2533</MessageID> <Description>Collection Evaluator failed to enumerate discovery architectures because it cannot retrieve the discovery architecture list from the database.%12</Description> </Message> <Message> <MessageID>2535</MessageID> <Description>Collection "%1" has no name. Collection Evaluator cannot continue processing the collection without a name.%12</Description> </Message> <Message> <MessageID>2542</MessageID> <Description>Collection Evaluator failed to update the query rule "%1" of collection "%2" (%3).%12</Description> </Message> <Message> <MessageID>2543</MessageID> <Description>Collection Evaluator failed to evalute some of the query rules for collection "%1" (%2).%12</Description> </Message> <Message> <MessageID>2545</MessageID> <Description>Collection Evaluator successfully processed new Collection Settings %1.%12</Description> </Message> <Message> <MessageID>2546</MessageID> <Description>Collection Evaluator successfully processed Update to Collection Settings %1.%12</Description> </Message> <Message> <MessageID>2547</MessageID> <Description>Collection Evaluator successfully removed Collection Settings Policy for Collection %1.%12</Description> </Message> <Message> <MessageID>2548</MessageID> <Description>Collection Evaluator failed to process Collection Settings changes. These changes will be retried on next processing cycle.%12</Description> </Message> <Message> <MessageID>2549</MessageID> <Description>Collection Evaluator failed to process Collection Settings for Collection %1. This Collection Settings will be retried %2 times on the next processing cycles.%12</Description> </Message> <Message> <MessageID>2550</MessageID> <Description>Collection Evaluator failed to process Collection Settings for Collection %1. This Collection Settings has been retried %2 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>2551</MessageID> <Description>Collection Evaluator failed to process Collection Settings Replication File %1 as Collection %2 referenced object of type %3 does not exists. This Collection Settings Replication file has been retried %4 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>2552</MessageID> <Description>Collection Evaluator failed to process Collection Settings Replication File %1. This Collection Settings Replication file has been retried %2 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>2553</MessageID> <Description>Policy Provider failed to process Machine Settings for Machine %1. This Machine Settings will be retried on the next processing cycles.%12</Description> </Message> <Message> <MessageID>2554</MessageID> <Description>Policy Provider failed to process Machine Settings changes. These changes will be retried on next processing cycle.%12</Description> </Message> <Message> <MessageID>2555</MessageID> <Description>Collection Evaluator successfully processed %1 client updates for collection %2. Original clients number: %3, added: %4, deleted: %5.</Description> </Message> <Message> <MessageID>2556</MessageID> <Description>The query rule for the collection "%1" generated a high number of records (%2).%12</Description> </Message> <Message> <MessageID>2557</MessageID> <Description>Policy Provider failed to process User Settings changes. These changes will be retried on next processing cycle.%12</Description> </Message> <Message> <MessageID>2600</MessageID> <Description>Discovery Data Manager failed to synchronize this site's deletions with all secondary site databases. When discovery data is deleted, the deletion must be propagated to all secondary sites. In addition, any licenses associated with the deleted resources must be revoked. Because secondary site data is not synchronized, more licenses will be used than is necessary.%12</Description> </Message> <Message> <MessageID>2601</MessageID> <Description>Discovery Data Manager failed to connect to the discovery database.%12</Description> </Message> <Message> <MessageID>2602</MessageID> <Description>Discovery Data Manager is removing references from deleted site "%1".%12</Description> </Message> <Message> <MessageID>2603</MessageID> <Description>Discovery Data Manager is beginning the process of sending discovery data to the new parent site. (This happens whenever a site attaches to a new parent site.)%12</Description> </Message> <Message> <MessageID>2604</MessageID> <Description>Discovery Data Manager failed to send discovery data to the new parent site. Discovery Data Manager will retry, resuming where it left off.%12</Description> </Message> <Message> <MessageID>2605</MessageID> <Description>Discovery Data Manager failed to move the new parent site notification file to the Data Loader inbox.%12</Description> </Message> <Message> <MessageID>2606</MessageID> <Description>Discovery Data Manager has tried ten times to send the discovery database to the new parent site, and Discovery Data Manager has been unsuccessful each time. Discovery Data Manager is giving up.%12</Description> </Message> <Message> <MessageID>2607</MessageID> <Description>Discovery Data Manager has successfully sent the discovery database to the parent site.%12</Description> </Message> <Message> <MessageID>2608</MessageID> <Description>Discovery Data Manager failed to send file "%1" to site "%2".%12</Description> </Message> <Message> <MessageID>2609</MessageID> <Description>Discovery Data Manager failed to enumerate discovery architectures.%12</Description> </Message> <Message> <MessageID>2610</MessageID> <Description>Discovery Data Manager failed to create the discovery data record (DDR) to send to the new parent site.%12</Description> </Message> <Message> <MessageID>2611</MessageID> <Description>Discovery Data Manager has detected a change in assignment rules. Discovery Data Manager will not process discovery data records (DDRs) until it completes the rule refresh operation.%12</Description> </Message> <Message> <MessageID>2612</MessageID> <Description>Discovery Data Manager failed to complete the rule refresh process.%12</Description> </Message> <Message> <MessageID>2613</MessageID> <Description>Discovery Data Manager failed to read the serial number from the parsed discovery data record (DDR) "%1".%12</Description> </Message> <Message> <MessageID>2614</MessageID> <Description>Discovery Data Manager failed to read the new discovery item from the parsed discovery data record (DDR) "%1".%12</Description> </Message> <Message> <MessageID>2615</MessageID> <Description>Discovery Data Manager failed to parse the new discovery item data from the parsed discovery data record (DDR) %1.%12</Description> </Message> <Message> <MessageID>2616</MessageID> <Description>Discovery Data Manager failed to insert the new item from file "%1" into the data source.%12</Description> </Message> <Message> <MessageID>2617</MessageID> <Description>Discovery Data Manager failed to write the serial number record to file "%1".%12</Description> </Message> <Message> <MessageID>2618</MessageID> <Description>Discovery Data Manager failed to write the item key record to file "%1".%12</Description> </Message> <Message> <MessageID>2619</MessageID> <Description>Discovery Data Manager failed to write item buffer to file "%1". Discovery Data Manager is attempting to send a discovery data record (DDR) to another site or registered consumer, but is unable to write the data for the new item.%12</Description> </Message> <Message> <MessageID>2620</MessageID> <Description>Discovery Data Manager failed to format discovery data into file "%1".%12</Description> </Message> <Message> <MessageID>2621</MessageID> <Description>Discovery Data Manager failed to enumerate properties for architecture "%1".%12</Description> </Message> <Message> <MessageID>2622</MessageID> <Description>Discovery Data Manager failed to process file "%1" because it cannot detect any Name properties. Discovery Data Manager requires that all discovery data records (DDRs) report at least one field that is defined as a Name candidate. The three default architectures--User, User Group, and System--all have one or more defined Name fields. Either this DDR is not of one of those three architectures, or it is an invalid DDR.%12</Description> </Message> <Message> <MessageID>2623</MessageID> <Description>Discovery Data Manager failed to insert discovery data because the site is out of client access licenses.%12</Description> </Message> <Message> <MessageID>2624</MessageID> <Description>Discovery Data Manager failed to read the current site's .ncf (assignment rule) file.%12</Description> </Message> <Message> <MessageID>2625</MessageID> <Description>Discovery Data Manager failed to read the .ncf (assignment rule) file for site "%1".%12</Description> </Message> <Message> <MessageID>2626</MessageID> <Description>Discovery Data Manager failed to open the .ncf (assignment rule) file for site "%1".%12</Description> </Message> <Message> <MessageID>2627</MessageID> <Description>Discovery Data Manager failed to read the site control file for site "%1". Because the site database maintains the site control files for this site and all sites beneath it, Discovery Data Manager reads site control files only from the site database.%12</Description> </Message> <Message> <MessageID>2628</MessageID> <Description>Discovery Data Manager failed to write the .ncf (assignment rule) file "%1". Discovery Data Manager will retry writing this file during its next processing cycle.%12</Description> </Message> <Message> <MessageID>2629</MessageID> <Description>Discovery Data Manager failed to copy the .ncf (assignment rule) file "%1" to Asstdata.box, the point of replication to client access points (CAPs). Discovery Data Manager will retry copying this file during its next processing cycle.%12</Description> </Message> <Message> <MessageID>2630</MessageID> <Description>During a refresh, Discovery Data Manager detected that assignment rules had changed. Therefore, Discovery Data Manager is stopping the refresh now, but will perform it later.%12</Description> </Message> <Message> <MessageID>2631</MessageID> <Description>Discovery Data Manager failed to create a full refresh file to send to the secondary site.%12</Description> </Message> <Message> <MessageID>2632</MessageID> <Description>Discovery Data Manager failed to notify all consumers that a full refresh has occurred and that users need to refresh their data store.%12</Description> </Message> <Message> <MessageID>2633</MessageID> <Description>Discovery Data Manager failed to send file "%1" to site "%2".%12</Description> </Message> <Message> <MessageID>2634</MessageID> <Description>Discovery Data Manager will resume processing because it has successfully completed assignment-rule processing.%12</Description> </Message> <Message> <MessageID>2635</MessageID> <Description>While parsing discovery data record (DDR) "%1", Discovery Data Manager found a blank Architecture field, which makes "%1" a bad DDR.%12</Description> </Message> <Message> <MessageID>2636</MessageID> <Description>Discovery Data Manager failed to process the discovery data record (DDR) "%1", because it cannot update the data source.%12</Description> </Message> <Message> <MessageID>2637</MessageID> <Description>Discovery Data Manager is updating statistics in all tables in the site database, which helps ensure optimal performance of SQL Server 6.5.%12</Description> </Message> <Message> <MessageID>2638</MessageID> <Description>Discovery Data Manager has interpreted discovery data record (DDR) "%1" as a delete request. Therefore, Discovery Data Manager is deleting item "%2" of architecture "%3". DDR "%1" contains an old item, but not a new item.%12</Description> </Message> <Message> <MessageID>2639</MessageID> <Description>Discovery Data Manager has processed a discovery data record (DDR) for computer "%1" with the SMS identifier of "%3" which has reported a new hardware identifier of "%2". %4 existing records sharing this hardware identifier have been marked as obsolete. The data in these records has been superseded by the data in the new record.</Description> </Message> <Message> <MessageID>2640</MessageID> <Description>Discovery Data Manager has processed a discovery data record (DDR) for computer "%1" with the SMS identifier of "%2" which has reported a new SMS ID of "%3". An existing record with the previous SMS identifier has been marked as obsolete. The data in this record has been superseded by the data in the new record.</Description> </Message> <Message> <MessageID>2641</MessageID> <Description>Discovery Data Manager failed to process a client registration request for computer with the identity "%1" and with the SMS identifier "%2" because the SMS identifier has already been registered for another client.%12</Description> </Message> <Message> <MessageID>2642</MessageID> <Description>Configuration Manager has detected a record that might be conflicting with the following client record in the site database: %1.%12</Description> </Message> <Message> <MessageID>2700</MessageID> <Description>Inventory Data Loader failed to read the delta MIF file "%1" and will move the file to the BADMIFs directory.%12</Description> </Message> <Message> <MessageID>2701</MessageID> <Description>Inventory Data Loader encountered a SQL Server problem and is stopping the MIF processing thread.%12</Description> </Message> <Message> <MessageID>2702</MessageID> <Description>Inventory Data Loader failed to process the delta MIF file "%1" because the file does not have a corresponding discovery record. Inventory Data Loader has moved this file to the Orphans directory as file "%2" and will retry processing it within 10 minutes.%12</Description> </Message> <Message> <MessageID>2703</MessageID> <Description>Inventory Data Loader failed to process the delta MIF file "%1" and has moved it to "%2."%12</Description> </Message> <Message> <MessageID>2704</MessageID> <Description>Inventory Data Loader is updating database statistics for all inventory-related tables. By default, statistics are updated to optimize database performance after a certain number of MIF files have been processed. This message indicates that this milestone has been achieved. You can edit this value in the Configuration Manager Console, under Component Configuration, Data Processing and Storage Properties.%12</Description> </Message> <Message> <MessageID>2705</MessageID> <Description>Inventory Data Loader has finished processing %1 MIF files and is terminating the MIF file processing thread.%12 Each time the processing cycle completes, Inventory Data Loader generates this message to report the number of MIF files it has processed.</Description> </Message> <Message> <MessageID>2706</MessageID> <Description>Inventory Data Loader has quit trying to update inventory after failing 10 times. Inventory Data Loader detected that the parent site was changed to a new site, and then Inventory Data Loader tried to send all inventory to the new parent through the inventory update process. However, Inventory Data Loader tried this process 10 times and failed each time.%12</Description> </Message> <Message> <MessageID>2707</MessageID> <Description>Inventory Data Loader failed to send inventory to the new parent site, but it will retry %1 more times before quitting.%12 If you want more information, review the immediately preceding status messages from this component, or look in dadaldr.log. If you ignore this problem, ConfigMgr will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>2708</MessageID> <Description>Inventory Data Loader detected that the parent site has changed to a new site, and now Inventory Data Loader is trying to send all inventory to the new parent through the inventory update process.%12</Description> </Message> <Message> <MessageID>2709</MessageID> <Description>The Inventory Data Loader inventory update process has initialized the inventory update status file, which controls the inventory update process's ability to restart.%12</Description> </Message> <Message> <MessageID>2710</MessageID> <Description>The Inventory Data Loader has detected that the inventory update process has already been completed. Therefore, Inventory Data Loader is not starting the inventory update process. If this information is incorrect, delete the status file Inv_stat.dat to force the inventory update process to restart.%12</Description> </Message> <Message> <MessageID>2711</MessageID> <Description>The Inventory Data Loader inventory update process will use the directory %1. Inventory Data Loader will create delta MIF files in this folder to send to the parent site.%12</Description> </Message> <Message> <MessageID>2712</MessageID> <Description>The Inventory Data Loader inventory update process failed to write the MIF file for machine %1 of architecture %2.%12</Description> </Message> <Message> <MessageID>2713</MessageID> <Description>The Inventory Data Loader inventory update process has finished successfully. All inventory has been sent to the parent site.%12</Description> </Message> <Message> <MessageID>2714</MessageID> <Description>Inventory Data Loader has requested a resynchronization for site %1. Inventory Data Loader requests resynchronization when it receives an Update or Delete request for a nonexistent group.%12</Description> </Message> <Message> <MessageID>2715</MessageID> <Description>Inventory Data Loader has detected a resynchronization request for agent %1. When an agent is specified, the resynchronization is planned only for items reported by that agent. A resynchronization indicates that the current MIF file represents all inventory for the current machine. If any inventory is present in the database that does not occur in the MIF file, Inventory Data Loader deletes it (unless, as with an agent resynchronization, it was reported by a different agent). If many resynchronizations occur, it indicates that inventory was lost at some point.%12</Description> </Message> <Message> <MessageID>2716</MessageID> <Description>Inventory Data Loader is going to widen attribute %2 of group %1 from %3 to %4. Inventory Data Loader has received a MIF file that contains a referenced attribute that exceeds the current maximum length. Inventory Data Loader will attempt to widen the column before it inserts the data.%12</Description> </Message> <Message> <MessageID>2717</MessageID> <Description>Inventory Data Loader has added group %1 to architecture %2. Inventory Data Loader found a group that it had not found before and successfully added the group to the inventory database.%12</Description> </Message> <Message> <MessageID>2718</MessageID> <Description>Inventory Data Loader has added the architecture %1. Inventory Data Loader found an architecture that it had not found before and successfully added it to the inventory database. A custom MIF file, either from this site or from one beneath it, caused this action.%12</Description> </Message> <Message> <MessageID>2719</MessageID> <Description>Inventory Data Loader failed to process the file %1 because it is larger than the defined maximum allowable size of %2.%12</Description> </Message> <Message> <MessageID>2720</MessageID> <Description>Inventory Data Loader has detected that a resource with GUID %1 needs to be resynchronized, but the resource will not be resynchronized because the registry key HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Resynchronize Clients on the resource computer has been turned off. Data will not be processed for this resource until it has been resynchronized.%12</Description> </Message> <Message> <MessageID>2721</MessageID> <Description>Inventory Data Loader failed to compile %1. The failing MOF file has been moved to %2, and the last successfully compiled version has been restored.%12</Description> </Message> <Message> <MessageID>2722</MessageID> <Description>Inventory Data Loader has requested a resynchronization for machine %1. Inventory Data Loader requests resynchronization when it receives an Update or Delete request for a nonexistent group.%12</Description> </Message> <Message> <MessageID>2723</MessageID> <Description>Inventory Data Loader requested a resynchronization for machine "%1" because a hardware inventory file was sent without a public key information.%12</Description> </Message> <Message> <MessageID>2724</MessageID> <Description>Inventory Data Loader detected more than %1 class redefinitions in %2 minutes. Will switch to single-threaded operation after exceeding %3.%12</Description> </Message> <Message> <MessageID>2725</MessageID> <Description>Inventory Data Loader detected more than %1 class redefinitions in %2 minutes. Switching to single-threaded operation for the next %3 minutes.%12</Description> </Message> <Message> <MessageID>2800</MessageID> <Description>Site Control Manager is beginning to process delta site control file "%1".%12 Configuration Manager Server Components and SMS Provider clients (such as the Configuration Manager Console) submit delta site control files to change the configuration of the site. A delta site control file contains one or more required changes to the actual site control file ("%2" at this site). The actual site control file contains the site configuration currently in use. The site is successfully reconfigured only after Site Control Manager receives and processes a delta site control file and then updates the actual site control file with the new configuration data.</Description> </Message> <Message> <MessageID>2801</MessageID> <Description>Site Control Manager successfully processed delta site control file %1.</Description> </Message> <Message> <MessageID>2802</MessageID> <Description>Site Control Manager could not completely process delta site control file %1.%12</Description> </Message> <Message> <MessageID>2803</MessageID> <Description>A non-critical problem occurred while Site Control Manager was processing delta site control file %1.%12</Description> </Message> <Message> <MessageID>2804</MessageID> <Description>Site Control Manager aborted the processing of delta site control file %1.%12</Description> </Message> <Message> <MessageID>2805</MessageID> <Description>The delta site control file %1 contains a corrupt site configuration change request. This site configuration change request and the remaining site configuration change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2806</MessageID> <Description>The delta site control file %1 contains a site configuration change request that is missing a "%2" item, or that item is corrupt or invalid. The site configuration change request cannot be processed without this item.%12</Description> </Message> <Message> <MessageID>2807</MessageID> <Description>The delta site control file %1 contains a site configuration change request submitted by the "%2" SMS Provider client running as user "%3" on computer "%4" at site "%5" at "%6".%12 The site configuration change request was assigned the serial number %7 at site "%5". Site Control Manager uses this serial number to ensure that it does not process the same site configuration change request from an SMS Provider client (such as the Configuration Manager Console) more than once. When an SMS Provider client submits a delta site control file containing a site configuration change request, Hierarchy Manager at the site submitting the file will report status message 3307. You can track the time on message 3307 and this one to determine when the site configuration change request was submitted and when it actually went into effect.</Description> </Message> <Message> <MessageID>2808</MessageID> <Description>The delta site control file %1 contains a site configuration change request submitted by the server component "%2" running as user "%3" on computer "%4" at "%5".%12</Description> </Message> <Message> <MessageID>2809</MessageID> <Description>Site Control Manager will ignore this site configuration change request ("%1" from site "%2").%12 This change request was already processed as part of an older delta site control file. Hierarchy Manager at site "%2" will continue to submit this site configuration change request until it receives a copy of the new actual site control file from site "%3" that confirms the change was successfully processed. If you find that Hierarchy Manager continues to submit this site configuration change request for an extraordinarily long time, there might be a problem with Hierarchy Manager at any of the sites between and including sites "%2" and "%3". Or, if "%2" and "%3" are different sites, there might be a communication problem between them or any sites between them. If you suspect this is happening, check for Warning and Error status messages from Hierarchy Manager, Replication Manager, Scheduler, and the Sender components at these sites.</Description> </Message> <Message> <MessageID>2810</MessageID> <Description>Site Control Manager created the temporary file "%1".%12 In a moment, Site Control Manager will rename this file to %2, and it will become the new actual site control file.%12</Description> </Message> <Message> <MessageID>2811</MessageID> <Description>Site Control Manager created serial number %2 of the actual site control file %1.%12 This creation occurred in response to a site configuration change request contained in delta site control file %3. The other Configuration Manager Server Components will detect that a new actual site control file is available, read it, and reconfigure themselves accordingly.</Description> </Message> <Message> <MessageID>2812</MessageID> <Description>Site Control Manager created serial number %2 of the actual site control file %1 as a result of processing delta site control file %3.%12 No changes were made to the site configuration.</Description> </Message> <Message> <MessageID>2813</MessageID> <Description>Site Control Manager added a "%1" item named "%2" to the actual site control file %5.%12 This addition occurred as a result of a site configuration change request in delta site control file %4. The change will take effect in serial number %3 of the actual site control file.</Description> </Message> <Message> <MessageID>2814</MessageID> <Description>Site Control Manager modified the properties of the "%1" item named "%2" in the actual site control file %7.%12 This modification occurred as a result of a site configuration change request in delta site control file %6. The change will take effect in serial number %5 of the actual site control file. You can compare the file %3 with the file %4 to determine which properties changed.</Description> </Message> <Message> <MessageID>2815</MessageID> <Description>Site Control Manager deleted the "%1" item named "%2" from the actual site control file %5.%12 This deletion occurred as a result of a site configuration change request contained in delta site control file %4. The change will take effect in serial number %3 of the actual site control file.</Description> </Message> <Message> <MessageID>2816</MessageID> <Description>The actual site control file %1 does not exist.%12</Description> </Message> <Message> <MessageID>2817</MessageID> <Description>This computer "%1" is not the site server (%2).%12</Description> </Message> <Message> <MessageID>2818</MessageID> <Description>The actual site control file %1 does not contain a "%2" item.%12</Description> </Message> <Message> <MessageID>2819</MessageID> <Description>Site Control Manager will maintain copies of the %1 most recent actual site control files in the directory "%2".%12 The actual site control file %3 contains the configuration currently in use at this site. You can compare the files in the "%2" directory with each other to determine how the site configuration has changed over time. Each file is named ????????.ct0, where ???????? is the actual site control file serial number in hexadecimal format. For example, actual site control file 20 would be named 00000014.ct0. Also, if the current actual site control file %3 ever becomes corrupted or is ever accidentally deleted, you can restore it from one of the versions in the "%2" directory. Contact Microsoft for help before attempting to restore "%3" from one of these versions.</Description> </Message> <Message> <MessageID>2820</MessageID> <Description>Site Control Manager wrote a copy of the actual site control file %1 to %2.%12 In a moment, Site Control Manager will move this file into the Hierarchy Manager inbox ("%3") for processing.</Description> </Message> <Message> <MessageID>2821</MessageID> <Description>Site Control Manager could not write a copy of the actual site control file %1 to %2. Consequently, Hierarchy Manager will not be notified that the site configuration has changed, and it might appear that the site has not been fully reconfigured.%12</Description> </Message> <Message> <MessageID>2822</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not identify the change request as being valid. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2823</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify which site should receive the change request. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2824</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies that the change request should be submitted to site "%3" instead of this site ("%4"). This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2825</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify which site submitted the change request. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2826</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify which computer submitted the change request. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2827</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify which user submitted the change request. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2828</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify which component submitted the change request. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2829</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 was submitted by a server component at site "%3", instead of this site ("%4"). This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2830</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies a site type that does not match the current site's type. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2831</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify a site code. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2832</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies a site code (%3) that does not match the current site's code (%4). This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2833</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify a site name. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2834</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies a site name ("%3") that does not match the current site's name ("%4"). This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2835</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the site server. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2836</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies a site server name ("%3") that does not match the name of the current site server ("%4"). This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2837</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the domain of the site server. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2838</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies a site server domain (%3) that does not match the site server's domain (%4). This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2839</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the site server's platform. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2840</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the site server installation directory. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2841</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies a site server installation directory ("%3") that does not match the current site's installation directory ("%4"). This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2842</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2does not specify the domain of the service account. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2843</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the service account. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2844</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the plain text name of the service account. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2845</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the password for the service account. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2846</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2does not specify the public key for decrypting the service account and password. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2847</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies an invalid public key for decrypting the service account and password. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2848</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies an service account name and/or password that cannot be decrypted with the specified public key. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2849</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the public key for decrypting the address accounts and passwords. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2850</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL Server in use at this site. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2851</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the site database. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2852</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the name of the SQL administrator account. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2853</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 does not specify the password for the SQL administrator account. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2854</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2does not specify the public key for decrypting the SQL administrator account and password. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2855</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2 specifies a SQL administrator account name and/or password that cannot be decrypted with the specified public key. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>2864</MessageID> <Description>The "%1" item in the actual site control file %2 does not contain a "%3" item named "%4", or that item is corrupt. As a result, the Configuration Manager Server Components might not be using the site system connection accounts you created in the Configuration Manager Console and might be unable to access some site systems.%12</Description> </Message> <Message> <MessageID>2865</MessageID> <Description>Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to Hierarchy Manager.%12 This is the new actual site control file that contains the current configuration of this site. If this is a primary site, Hierarchy Manager will update this site's database with the copy. If this is a child site of another site, Hierarchy Manager will replicate the copy up the site hierarchy, updating each parent site's database.</Description> </Message> <Message> <MessageID>2866</MessageID> <Description>Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to Hierarchy Manager as a heartbeat site control file.%12 Site Control Manager periodically submits heartbeat site control files to Hierarchy Manager to ensure that this site and all of its parent sites contain an up-to-date copy of this site's configuration. If this is a primary site, Hierarchy Manager will ensure that this site's database contains the up-to-date configuration. If this is a child site of another site, Hierarchy Manager will replicate the copy up the site hierarchy and ensure that each parent site's database contains the up-to-date configuration. Site Control Manager will then submit a heartbeat site control file to Hierarchy Manager at "%3".</Description> </Message> <Message> <MessageID>2867</MessageID> <Description>Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to Hierarchy Manager as a heartbeat site control file.%12 Site Control Manager periodically submits heartbeat site control files to Hierarchy Manager to ensure that this site and all of its parent sites contain an up-to-date copy of this site's configuration. If this is a primary site, Hierarchy Manager will ensure that this site's database contains the up-to-date configuration. If this is a child site of another site, Hierarchy Manager will replicate the copy up the site hierarchy and ensure that each parent site's database contains the up-to-date configuration.</Description> </Message> <Message> <MessageID>2868</MessageID> <Description>Site Control Manager is configured so that no more heartbeat site control files will be submitted to Hierarchy Manager.%12</Description> </Message> <Message> <MessageID>2869</MessageID> <Description>The schedule at which Site Control Manager submits heartbeat site control files to Hierarchy Manager has changed.%12 The next heartbeat site control file will be submitted at "%1". Site Control Manager periodically submits heartbeat site control files to Hierarchy Manager to ensure that this site and all of its parent sites contain an up-to-date copy of this site's configuration. If this is a primary site, Hierarchy Manager will ensure that this site's database contains the up-to-date configuration. If this is a child site of another site, Hierarchy Manager will replicate the heartbeat site control file up the site hierarchy and ensure that each parent site's database contains the up-to-date configuration.</Description> </Message> <Message> <MessageID>2870</MessageID> <Description>The "%1" item in a site configuration change request in delta site control file %2contains a full version that's older than the current full version. This site configuration change request and the remaining change requests in the file are unusable.%12</Description> </Message> <Message> <MessageID>3000</MessageID> <Description>Client Configuration Manager failed to read the site control file for site "%1."%12</Description> </Message> <Message> <MessageID>3001</MessageID> <Description>Client Configuration Manager failed to read the site identification values from the registry in \HKLM\Software\Microsoft\SMS\Identification key.%12</Description> </Message> <Message> <MessageID>3002</MessageID> <Description>Client Configuration Manager failed to connect to the registry of site server %1.%12</Description> </Message> <Message> <MessageID>3003</MessageID> <Description>Client Configuration Manager failed to read the account information for site %1.%12</Description> </Message> <Message> <MessageID>3004</MessageID> <Description>Client Configuration Manager failed to read the component item "%1" from the site control file on the server "%2".%12</Description> </Message> <Message> <MessageID>3005</MessageID> <Description>Client Configuration Manager failed to create a thread.%12</Description> </Message> <Message> <MessageID>3006</MessageID> <Description>Client Configuration Manager failed to establish inbox "%1" on the site server.%12</Description> </Message> <Message> <MessageID>3008</MessageID> <Description>Client Configuration Manager failed to create an inbox rule to copy files "%1" from inbox "%2" to inbox "%3."%12</Description> </Message> <Message> <MessageID>3009</MessageID> <Description>Client Configuration Manager reports that queue "%1" contains %2 Client Configuration Requests (CCRs), which exceeds the queue's threshold.%12</Description> </Message> <Message> <MessageID>3010</MessageID> <Description>In the past %3 hours, Client Configuration Manager has made %1 unsuccessful attempts to install the ConfigMgr client "%2". CCM will continue to attempt to install this client.%12</Description> </Message> <Message> <MessageID>3011</MessageID> <Description>Client Configuration Manager failed to complete the ConfigMgr installation on client "%1". In the past %3 hours, CCM has made %2 unsuccessful attempts.%12</Description> </Message> <Message> <MessageID>3012</MessageID> <Description>Client Configuration Manager failed to complete its periodic account maintenance cycle.%12</Description> </Message> <Message> <MessageID>3013</MessageID> <Description>The Client Push Installation account list has been reset to a single account.%12</Description> </Message> <Message> <MessageID>3014</MessageID> <Description>Client Configuration Manager cannot connect to the machine "%1".%12</Description> </Message> <Message> <MessageID>3015</MessageID> <Description>Client Configuration Manager cannot find machine "%1" on the network.%12</Description> </Message> <Message> <MessageID>3016</MessageID> <Description>Client Configuration Manager cannot install a client to machine "%1", because it is not a supported platform for this action. Refer to the ConfigMgr documentation for the list of supported platforms.</Description> </Message> <Message> <MessageID>3017</MessageID> <Description>Client Configuration Manager cannot install a client to machine "%1", because it is a domain controler. CCM is currently configured to not install to domain controllers.</Description> </Message> <Message> <MessageID>3019</MessageID> <Description>Client Configuration Manager cannot install the client to machine "%1". This platform is not supported. Refer to the ConfigMgr documentation for the list of supported platforms.</Description> </Message> <Message> <MessageID>3200</MessageID> <Description>Inventory Processor failed to process MIF file %1.%12</Description> </Message> <Message> <MessageID>3201</MessageID> <Description>Inventory Processor failed to process inventory RAW file %1.%12</Description> </Message> <Message> <MessageID>3300</MessageID> <Description>Site "%1" (%2) is trying to report to a site that already reports to site "%1". This configuration is illegal because it creates a "loop" in the site hierarchy.</Description> </Message> <Message> <MessageID>3301</MessageID> <Description>Site "%1" (%2) has the same site code as another site.</Description> </Message> <Message> <MessageID>3302</MessageID> <Description>The parent site for this site cannot be changed from site "%1" (%2).</Description> </Message> <Message> <MessageID>3303</MessageID> <Description>Hierarchy Manager cannot connect to the site database.%12</Description> </Message> <Message> <MessageID>3304</MessageID> <Description>Hierarchy Manager cannot save site information to the site database for site "%1". %12</Description> </Message> <Message> <MessageID>3305</MessageID> <Description>Hierarchy Manager detected that site code "%1" is already in use by existing site "%2".%12</Description> </Message> <Message> <MessageID>3306</MessageID> <Description>Hierarchy Manager successfully processed "%1", which represented the site control file for site "%2" (%3). If this site is a primary site, Hierarchy Manager stored this site control file in the site database. If this site reports to a parent site, Hierarchy Manager instructed Replication Manager to replicate this file to the parent site at high priority.</Description> </Message> <Message> <MessageID>3307</MessageID> <Description>Hierarchy Manager detected that a change was requested by this site to the configuration of site "%1". Hierarchy Manager created a delta site control file for this request. If this site is site "%1", Hierarchy Manager submitted this file to Site Control Manager at this site. If site "%1" is a child site, Hierarchy Manager instructed Replication Manager to deliver the file to Site Control Manager at site "%1" at high priority.</Description> </Message> <Message> <MessageID>3308</MessageID> <Description>Hierarchy Manager cannot reinstall the Site Component Manager.</Description> </Message> <Message> <MessageID>3309</MessageID> <Description>Hierarchy Manager reinstalled Site Component Manager. Site Component Manager will now reinstall all of the other server components at this site.</Description> </Message> <Message> <MessageID>3310</MessageID> <Description>Hierarchy Manager has initiated remote installation of secondary site "%1". To track the progress of this operation, you should also monitor the messages reported by the Sender components.</Description> </Message> <Message> <MessageID>3311</MessageID> <Description>Hierarchy Manager has initiated remote upgrade of secondary site "%1". To track the progress of this operation, you should also monitor the messages reported by the Sender components.</Description> </Message> <Message> <MessageID>3312</MessageID> <Description>Hierarchy Manager has initiated remote deinstallation of secondary site "%1". To track the progress of this operation, you should also monitor the messages reported by the Sender components.</Description> </Message> <Message> <MessageID>3313</MessageID> <Description>Hierarchy Manager failed to execute site maintenance task "%1".%12</Description> </Message> <Message> <MessageID>3317</MessageID> <Description>Hierarchy Manager cannot add machine account %1 for secondary site %2 to the address group %3, this must be done manually.</Description> </Message> <Message> <MessageID>3318</MessageID> <Description>Hierarchy Manager cannot add address account %1 for secondary site %2 to the address group %3, this must be done manually.</Description> </Message> <Message> <MessageID>3320</MessageID> <Description>The secondary site upgrade failed because either the prerequisite checker has not been run without errors on secondary site %1 in the past seven days or it has not been run at all. Follow the corrective steps that are required for the failed prerequisite rules to pass. You must restart the secondary site upgrade after the prerequisite checker has been re-run and passed without errors.</Description> </Message> <Message> <MessageID>3321</MessageID> <Description>Hierarchy Manager detected that this site's client computer communication method is set to allow HTTPS only.</Description> </Message> <Message> <MessageID>3322</MessageID> <Description>Hierarchy Manager cannot remove the computer account of site system %1 from database role %2. This needs to be done manually.</Description> </Message> <Message> <MessageID>3323</MessageID> <Description>Hierarchy Manager detected that this site's client computer communication method is set to allow either HTTPS or HTTP.</Description> </Message> <Message> <MessageID>3324</MessageID> <Description>Hierarchy Manager detected that the public key of this site in the site control file is no longer valid and has updated it with the new public key. %12 The password of all the accounts need to be reset through the Configuration Manager Console. The bootmedia CDs created on the site may also need to be recreated. Please refer to your Configuration Manager documentation or the Microsoft Knowledge Base for further information.</Description> </Message> <Message> <MessageID>3330</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 machine certificate is still valid.</Description> </Message> <Message> <MessageID>3331</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 machine certificate has missed.</Description> </Message> <Message> <MessageID>3332</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 machine certificate has missed. It is failed to remediate with Error %2.</Description> </Message> <Message> <MessageID>3333</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 machine certificate has been remediated.</Description> </Message> <Message> <MessageID>3334</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Service Broker certificate is still valid.</Description> </Message> <Message> <MessageID>3335</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Service Broker certificate has missed.</Description> </Message> <Message> <MessageID>3336</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Service Broker certificate has been expired.</Description> </Message> <Message> <MessageID>3337</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Service Broker certificate has missed or is expired, and failed to remediate with Error %2.</Description> </Message> <Message> <MessageID>3338</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Service Broker certificate has been remediated.</Description> </Message> <Message> <MessageID>3339</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Port %2 still valid.</Description> </Message> <Message> <MessageID>3340</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Port %2 has been changed to %3.</Description> </Message> <Message> <MessageID>3341</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Port %2 has been changed to %3, and failed to remediate with Error %4.</Description> </Message> <Message> <MessageID>3342</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server %1 Port %2 has been remediated from %3.</Description> </Message> <Message> <MessageID>3343</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server Service Broker %1 Port %2 still valid.</Description> </Message> <Message> <MessageID>3344</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server Service Broker %1 Port %2 has been changed to %3.</Description> </Message> <Message> <MessageID>3345</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server Service Broker %1 Port %2 has been changed to %3, and failed to remediate with Error %4.</Description> </Message> <Message> <MessageID>3346</MessageID> <Description>Hierarchy Monitoring detected that the SQL Server Service Broker %1 Port %2 has been remediated from %3.</Description> </Message> <Message> <MessageID>3347</MessageID> <Description>Hierarchy Monitoring detected that all ConfigMgr SQL Server Roles are still valid.</Description> </Message> <Message> <MessageID>3348</MessageID> <Description>Hierarchy Monitoring detected that the following ConfigMgr SQL Server Roles [%1] are missing.</Description> </Message> <Message> <MessageID>3349</MessageID> <Description>Hierarchy Monitoring detected that the following ConfigMgr SQL Server Roles [%1] are missing.</Description> </Message> <Message> <MessageID>3350</MessageID> <Description>The following missing ConfigMgr SQL Server Roles [%1] have been added back.</Description> </Message> <Message> <MessageID>3351</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr SQL Server ports %1 are still active on Firewall exception.</Description> </Message> <Message> <MessageID>3352</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr SQL Server ports %1 are not active on Firewall exception.</Description> </Message> <Message> <MessageID>3353</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr SQL Server %2 ports %1 are not active on Firewall exception.</Description> </Message> <Message> <MessageID>3354</MessageID> <Description>Hierarchy Monitoring has added the ConfigMgr SQL Server ports %1 into the Firewall exception.</Description> </Message> <Message> <MessageID>3355</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Site Server Account %1 still valid.</Description> </Message> <Message> <MessageID>3356</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Site Server Account %1 is missing.</Description> </Message> <Message> <MessageID>3357</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Site Server Account %1 is missing.</Description> </Message> <Message> <MessageID>3358</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Site Server Account %1 is valid after remediation.</Description> </Message> <Message> <MessageID>3359</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Database file location is still valid.</Description> </Message> <Message> <MessageID>3360</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Database file location is invalid.</Description> </Message> <Message> <MessageID>3361</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Database file location is invalid.</Description> </Message> <Message> <MessageID>3362</MessageID> <Description>Hierarchy Monitoring detected that the ConfigMgr Database File Disk still has enough free space.</Description> </Message> <Message> <MessageID>3363</MessageID> <Description>Hierarchy Monitoring detected that the Database File Disk (%1) is short of space.</Description> </Message> <Message> <MessageID>3364</MessageID> <Description>Hierarchy Monitoring detected that the Database File Disk (%1) is running out of space.</Description> </Message> <Message> <MessageID>3365</MessageID> <Description>Hierarchy Monitoring detected that the Database File Disk still has enough free space. But there is no alert configured. Please use Site System properties to configure alerts.</Description> </Message> <Message> <MessageID>3366</MessageID> <Description>Hierarchy Manager cannot search the Active Directory.%12</Description> </Message> <Message> <MessageID>3400</MessageID> <Description>Scheduler does not have an address defined at site "%2" for site "%1". Files cannot be sent from site "%2" to site "%1" until an address is defined.%12</Description> </Message> <Message> <MessageID>3401</MessageID> <Description>Scheduler has data to send to site "%1", and addresses defined at site "%2" for site "%1", but none of them are available for sending at this time.</Description> </Message> <Message> <MessageID>3402</MessageID> <Description>Scheduler at site %1 has received package %2 version %3 and has instructed the Sender to send the package to the following sites: %4.%12</Description> </Message> <Message> <MessageID>3500</MessageID> <Description>The sender cannot connect to remote site "%1" over the LAN.%12</Description> </Message> <Message> <MessageID>3501</MessageID> <Description>The sender cannot connect to site "%1" over RAS.%12</Description> </Message> <Message> <MessageID>3502</MessageID> <Description>The address to site "%1" is invalid.%12</Description> </Message> <Message> <MessageID>3503</MessageID> <Description>The address to site "%1" is invalid.%12</Description> </Message> <Message> <MessageID>3504</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2".%12</Description> </Message> <Message> <MessageID>3505</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because the sender cannot create the Bootstrap initialization file "%3".%12</Description> </Message> <Message> <MessageID>3506</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because it cannot retrieve the encryption public key.%12 Please refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </Message> <Message> <MessageID>3507</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because it cannot query the status of the Configuration Manager Bootstrap service on server "%2".%12</Description> </Message> <Message> <MessageID>3508</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because it cannot stop the Configuration Manager Bootstrap service on server "%2".%12</Description> </Message> <Message> <MessageID>3509</MessageID> <Description>The sender cannot install, upgrade, or deinstall secondary site "%1" on server "%2".%12</Description> </Message> <Message> <MessageID>3510</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2".%12</Description> </Message> <Message> <MessageID>3511</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because the sender could not copy the Configuration Manager Bootstrap service file from "%3" to "%4".%12</Description> </Message> <Message> <MessageID>3512</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because the sender failed to install the Configuration Manager Bootstrap service.%12</Description> </Message> <Message> <MessageID>3513</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because the sender cannot start the Configuration Manager Bootstrap service.%12</Description> </Message> <Message> <MessageID>3514</MessageID> <Description>The sender has installed the Configuration Manager Bootstrap service on server "%1". The Configuration Manager Bootstrap service will finish the installation of secondary site "%2" by running Configuration Manager Setup with a script that specifies the installation parameters for site "%2". You can track the progress of Configuration Manager Bootstrap by monitoring the "bootstrp.log" file on server "%1", and the progress of Configuration Manager Setup by monitoring "smssetup.log" on server "%1".</Description> </Message> <Message> <MessageID>3515</MessageID> <Description>The sender has installed the Configuration Manager Bootstrap service on server "%1". The Configuration Manager Bootstrap service will finish the upgrade of secondary site "%2" by running Configuration Manager Setup with a script that specifies the upgrade parameters for site "%2". You can track the progress of Configuration Manager Bootstrap by monitoring the "bootstrp.log" file on server "%1", and the progress of Configuration Manager Setup by monitoring "smssetup.log" on server "%1".</Description> </Message> <Message> <MessageID>3516</MessageID> <Description>The sender has installed the Configuration Manager Bootstrap service on server "%1". The Configuration Manager Bootstrap service will finish the deinstallation of secondary site "%2" by running Configuration Manager Setup with a script that specifies the deinstallation parameters for site "%2". You can track the progress of Configuration Manager Bootstrap by monitoring the "bootstrp.log" file on server "%1", and the progress of Configuration Manager Setup by monitoring "smssetup.log" on server "%1".</Description> </Message> <Message> <MessageID>3517</MessageID> <Description>Sender failed to send files to destination site %1. Make sure the address account has full access to directory "%2" on the destination site server and the destination site server has sufficient free disk space on the ConfigMgr installation drive.%12</Description> </Message> <Message> <MessageID>3518</MessageID> <Description>%1 failed to start.%12</Description> </Message> <Message> <MessageID>3522</MessageID> <Description>The sender cannot install secondary site "%1" on server "%2" because some fatal error occured in Configuration Manager Bootstrap service running on secondary site server. Please review smssetup.log on the secondary site server for troubleshooting the problem. The smssetup.log is located at the root of the system drive. Once the problem is resolved, delete the secondary site object in the Configuration Manager Administrator's Console and rerun the secondary site creation wizard.%12</Description> </Message> <Message> <MessageID>3523</MessageID> <Description>The Configuration Manager Bootstrap service running on secondary site "%1" on server "%2", started Configuration Manager Setup successfully.%12</Description> </Message> <Message> <MessageID>3524</MessageID> <Description>The Configuration Manager Bootstrap service running on secondary site "%1" on server "%2", failed to start Configuration Manager Setup. Please check the logs on secondary site.%12</Description> </Message> <Message> <MessageID>3525</MessageID> <Description>The Configuration Manager Setup running on secondary site "%1" on server "%2" has completed.%12</Description> </Message> <Message> <MessageID>3526</MessageID> <Description>The Configuration Manager Setup running on secondary site "%1" on server "%2", failed. Please check the logs on secondary site.%12</Description> </Message> <Message> <MessageID>3527</MessageID> <Description>The Configuration Manager Bootstrap service running on secondary site "%1" on server "%2", started package decompression.%12</Description> </Message> <Message> <MessageID>3528</MessageID> <Description>The Configuration Manager Bootstrap service running on secondary site "%1" on server "%2", completed successfully.%12</Description> </Message> <Message> <MessageID>3529</MessageID> <Description>The Configuration Manager Bootstrap service running on secondary site "%1" on server "%2", failed to connect to parent site.%12</Description> </Message> <Message> <MessageID>3530</MessageID> <Description>The sender cannot connect to remote site "%1" over the LAN.%12</Description> </Message> <Message> <MessageID>3531</MessageID> <Description>Sender is currently sending software distribution package %1 version %2 to site %3, %4 percent of the sending has already completed.</Description> </Message> <Message> <MessageID>3532</MessageID> <Description>Sender encountered errors while sending software distribution package %1 version %2 to site %3, %4 percent of the sending has already completed.</Description> </Message> <Message> <MessageID>3533</MessageID> <Description>Sender has successfully sent software distribution package %1 version %2 to site %3.</Description> </Message> <Message> <MessageID>3600</MessageID> <Description>Inbox Manager cannot copy files from "%1" to "%2".%12</Description> </Message> <Message> <MessageID>3601</MessageID> <Description>Inbox Manager cannot create directory "%1" with the desired security rights on server "%2".%12</Description> </Message> <Message> <MessageID>3603</MessageID> <Description>Inbox Manager cannot create directory "%1" with the desired security rights on site system "%2". (The site system is shown here as a network abstraction layer (NAL) path.)%12</Description> </Message> <Message> <MessageID>3604</MessageID> <Description>Inbox Manager Assistant running on the client access point "%1" cannot connect to site server "%2".%12</Description> </Message> <Message> <MessageID>3605</MessageID> <Description>Inbox Manager cannot create the client access point on site system "%1".%12</Description> </Message> <Message> <MessageID>3606</MessageID> <Description>SMS Inbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12</Description> </Message> <Message> <MessageID>3607</MessageID> <Description>SMS Outbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12</Description> </Message> <Message> <MessageID>3700</MessageID> <Description>Software Inventory Processor successfully processed %1 software inventory files.%12</Description> </Message> <Message> <MessageID>3701</MessageID> <Description>Software Inventory Processor failed to process software inventory file "%1," and has moved it to "%2."%12</Description> </Message> <Message> <MessageID>3702</MessageID> <Description>Software Inventory Processor is terminating its processing cycle due to a SQL Server problem.%12</Description> </Message> <Message> <MessageID>3703</MessageID> <Description>Software Inventory Processor requested a resynchronization for machine "%1" because an attempt was made to update inventory information in the site database that does not already exist.%12</Description> </Message> <Message> <MessageID>3704</MessageID> <Description>Software Inventory Processor has removed the oldest revision of collected file "%1" for resource "%2". The maximum revision number for a collected file has been reached, so the oldest copy has been replaced by the most recent copy.%12</Description> </Message> <Message> <MessageID>3705</MessageID> <Description>Software Inventory Processor is updating database statistics.%12 By default, statistics are updated to optimize SQL Server database performance after every 500 software inventory files have been processed. You can edit this value in the Configuration Manager Console, under Component Configuration, Data Processing and Storage Properties.</Description> </Message> <Message> <MessageID>3706</MessageID> <Description>Software Inventory Processor was unable to store collected file "%1" for resource "%2".%12</Description> </Message> <Message> <MessageID>3707</MessageID> <Description>Software Inventory Processor failed to process software inventory file "%1" because the file does not have a corresponding discovery record. Software Inventory Processor has moved this file to the Orphans directory as file "%2" and will retry processing it later.%12 When Software Inventory Processor receives a software inventory file, it acquires the unique numeric ID for the file it is processing from the discovery data in the site database. If this cannot be found, a discovery data record (DDR) is generated, and the software inventory file is temporarily moved to the Orphans directory, where Software Inventory Processor retries the file every 10 minutes.</Description> </Message> <Message> <MessageID>3708</MessageID> <Description>Software Inventory Processor failed to process the file %1 because it is larger than the defined maximum allowable size of %2.%12</Description> </Message> <Message> <MessageID>3709</MessageID> <Description>Software Inventory Processor requested a resynchronization for machine "%1" because a software inventory file was sent without a public key information.%12</Description> </Message> <Message> <MessageID>3800</MessageID> <Description>Received more than 10 NULL status message pointers from the Offer Status Queue.%12</Description> </Message> <Message> <MessageID>3801</MessageID> <Description>Unable to create a file to store the replication data at %1.%12</Description> </Message> <Message> <MessageID>3802</MessageID> <Description>Unable to open the incoming %1 replication file.%12</Description> </Message> <Message> <MessageID>3803</MessageID> <Description>While initializing, no records of the proper type were found in the data store.%12</Description> </Message> <Message> <MessageID>3804</MessageID> <Description>Received a status message from site %1, but this is site %2. Ignoring message.%12</Description> </Message> <Message> <MessageID>3805</MessageID> <Description>The Offer summary %1,%2 has not been heard from for %3 days. This summary has been marked for deletion.%12</Description> </Message> <Message> <MessageID>3806</MessageID> <Description>Failed to send the replication file. Will try again later.%12</Description> </Message> <Message> <MessageID>3807</MessageID> <Description>Interval %1 not found in OfferSummaryDetail record.%12</Description> </Message> <Message> <MessageID>3808</MessageID> <Description>No data store was found at %1 to initialize from.%12</Description> </Message> <Message> <MessageID>3809</MessageID> <Description>The file %1 is not the correct type of replication file for this summarizer, deleting the file.%12</Description> </Message> <Message> <MessageID>3810</MessageID> <Description>Unable to create a file to store the summary data. Will try again in %1 seconds.%12</Description> </Message> <Message> <MessageID>3811</MessageID> <Description>Unable to send changed records to the data store. Will try again in %1 seconds.%12</Description> </Message> <Message> <MessageID>3812</MessageID> <Description>Offer Status Summarizer cannot process a status message because it has an invalid message ID %1. The message ID must be within the range 10000 to 10099. As a result, the deployment Status summary data in the Configuration Manager Console may be inaccurate. The message was reported by component "%2" on computer "%3" at site %4 on %5. Please refer to the Microsoft Knowledge Base for more information.</Description> </Message> <Message> <MessageID>3813</MessageID> <Description>Offer Status Summarizer cannot process a status message because it does not contain a deployment ID. As a result, the deployment Status summary data in the Configuration Manager Console may be inaccurate. The message (ID %1) was reported by component "%2" on computer "%3" at site %4 on %5. Please refer to the Microsoft Knowledge Base for more information.</Description> </Message> <Message> <MessageID>3814</MessageID> <Description>Offer Status Summarizer cannot process a status message because it contains the invalid deployment ID "%6". As a result, the deployment Status summary data in the Configuration Manager Console may be inaccurate. The message (ID %1) was reported by component "%2" on computer "%3" at site %4 on %5. Please refer to the Microsoft Knowledge Base for more information.</Description> </Message> <Message> <MessageID>3900</MessageID> <Description>SMS Offer Manager successfully processed new deployment %1.%12</Description> </Message> <Message> <MessageID>3901</MessageID> <Description>SMS Offer Manager successfully removed deployment %1.%12</Description> </Message> <Message> <MessageID>4000</MessageID> <Description>Replication Manager successfully instructed Scheduler to send files to site "%1".</Description> </Message> <Message> <MessageID>4001</MessageID> <Description>Replication Manager received files from the "%1" component at a child site, but that component is not enabled at the current site. Replication Manager will throw away these files.</Description> </Message> <Message> <MessageID>4200</MessageID> <Description>Server Discovery Agent failed to read the necessary registry information.%12</Description> </Message> <Message> <MessageID>4201</MessageID> <Description>Server Discovery Agent failed to read the location of the outbox.%12</Description> </Message> <Message> <MessageID>4202</MessageID> <Description>Server Discovery Agent read the system roles and found %1 server role entries in the site control file. Windows NT Server Discovery Agent identified %2 unique servers in the server roles and generated %3 discovery data records (DDRs) and %4 errors while attempting to create DDRs.%12</Description> </Message> <Message> <MessageID>4400</MessageID> <Description>Despooler successfully stored the compressed binaries for package "%1" at "%2".%12</Description> </Message> <Message> <MessageID>4401</MessageID> <Description>Despooler failed to decompress package "%1" from "%2".%12</Description> </Message> <Message> <MessageID>4402</MessageID> <Description>Despooler failed to merge delta to the compressed package "%1".%12</Description> </Message> <Message> <MessageID>4403</MessageID> <Description>Obsolete.</Description> </Message> <Message> <MessageID>4404</MessageID> <Description>Despooler received an instruction and package file from site %1 that contains that site's public key, however the despooler cannot find a valid public key to verify the signature of the package. Because this site does not allow unsigned key exchange between sites, the instruction cannot be processed and will be retried.</Description> </Message> <Message> <MessageID>4405</MessageID> <Description>Despooler received an instruction and package file from site %1 that contains either software distribution data or inter-site replication data, however the despooler does not have the public key to verify the signature of the package. The instruction cannot be processed and will be retried.</Description> </Message> <Message> <MessageID>4406</MessageID> <Description>Despooler received an instruction and package file from site %1 that contains either software distribution data or inter-site replication data, however either the signature on the package or the hash algorithm ID used for the signature is not valid, the despooler will delete the instruction and the package file.</Description> </Message> <Message> <MessageID>4407</MessageID> <Description>Despooler successfully received the compressed image for package %1 version %2.%12</Description> </Message> <Message> <MessageID>4500</MessageID> <Description>Sent a replication file to %1.%12</Description> </Message> <Message> <MessageID>4501</MessageID> <Description>A replication file has been created, the replication file is %1.%12</Description> </Message> <Message> <MessageID>4502</MessageID> <Description>Processing the incoming replication file %1.%12</Description> </Message> <Message> <MessageID>4503</MessageID> <Description>The file %1 is not a replication file for this summarizer, deleting the file.%12</Description> </Message> <Message> <MessageID>4504</MessageID> <Description>Unable to decrypt the SQL Server login user name and/or password.%12</Description> </Message> <Message> <MessageID>4505</MessageID> <Description>Unable to find this summarizer's component section in the site control file.%12</Description> </Message> <Message> <MessageID>4506</MessageID> <Description>Unable to open the site control file.%12</Description> </Message> <Message> <MessageID>4507</MessageID> <Description>Unable to read the site configuration.%12</Description> </Message> <Message> <MessageID>4508</MessageID> <Description>An error occurred while setting or resetting a change notification for the site control file.%12</Description> </Message> <Message> <MessageID>4509</MessageID> <Description>An error occurred while setting or resetting a change notification for the summarizer's inbox.%12</Description> </Message> <Message> <MessageID>4510</MessageID> <Description>Unable to create the status message queue.%12</Description> </Message> <Message> <MessageID>4511</MessageID> <Description>Failed to send a replication file to site %1.%12</Description> </Message> <Message> <MessageID>4512</MessageID> <Description>The data store %1 was not found.%12</Description> </Message> <Message> <MessageID>4513</MessageID> <Description>.Could not read all of the records in the file %1. The error code is %2.%12</Description> </Message> <Message> <MessageID>4514</MessageID> <Description>Unable to write changed records to the data store.%12</Description> </Message> <Message> <MessageID>4515</MessageID> <Description>Unable to initialize the summarizer. The returned error code is %1.%12</Description> </Message> <Message> <MessageID>4516</MessageID> <Description>The site properties are not set in the registry.%12</Description> </Message> <Message> <MessageID>4517</MessageID> <Description>The error %1 has occurred while initializing the status message queue.%12</Description> </Message> <Message> <MessageID>4518</MessageID> <Description>The summarizer cannot continue and is stopping. The exit code is %1.%12</Description> </Message> <Message> <MessageID>4519</MessageID> <Description>The reset request list %1 is too old. It was sent on %2 from %3, by user %4, on system %5, at site %6.%12</Description> </Message> <Message> <MessageID>4520</MessageID> <Description>Reset specific tally intervals as requested from %1, by user %2, on system %3, at site %4.%12</Description> </Message> <Message> <MessageID>4600</MessageID> <Description>Component Status Summarizer detected that the list of Component Status Display Intervals specified in the site control file has changed.%12 Component Status Summarizer will reconfigure itself to use the new set of Display Intervals.</Description> </Message> <Message> <MessageID>4601</MessageID> <Description>Component Status Summarizer detected that entry "%1" of the Component Thresholds property list in the site control file is corrupt.%12</Description> </Message> <Message> <MessageID>4602</MessageID> <Description>Component Status Summarizer received a status message from component "%1", running on computer "%2", but there is no record of this component in the site control file.%12</Description> </Message> <Message> <MessageID>4603</MessageID> <Description>Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Informational status messages during the Component Status Threshold Period.%12</Description> </Message> <Message> <MessageID>4604</MessageID> <Description>Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Warning status messages during the Component Status Threshold Period.%12</Description> </Message> <Message> <MessageID>4605</MessageID> <Description>Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Error status messages during the Component Status Threshold Period.%12</Description> </Message> <Message> <MessageID>4606</MessageID> <Description>Component Status Summarizer detected that component "%1" running on computer "%2" has reported %3 or more Informational status messages during the Component Status Threshold Period.%12</Description> </Message> <Message> <MessageID>4607</MessageID> <Description>Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Warning status messages during the Component Status Threshold Period.%12</Description> </Message> <Message> <MessageID>4608</MessageID> <Description>Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Error status messages during the Component Status Threshold Period.%12</Description> </Message> <Message> <MessageID>4609</MessageID> <Description>Component Status Summarizer set the status of component "%1", running on computer "%2", to Critical.%12</Description> </Message> <Message> <MessageID>4610</MessageID> <Description>Component Status Summarizer set the status of component "%1" running on computer "%2" to Warning.%12</Description> </Message> <Message> <MessageID>4611</MessageID> <Description>Component Status Summarizer reset the status of component "%1", running on computer "%2", to OK.%12 Component Status Summarizer will automatically reset a component's status to OK every time the Component Status Threshold Period elapses and a new Threshold Period begins. For example, if the Threshold Period is "Since 12:00:00 AM", Component Status Summarizer will reset the component's status to OK every 24 hours at midnight. At this time, the counts of status messages reported by the component for the Threshold Period will be reset to zero.</Description> </Message> <Message> <MessageID>4612</MessageID> <Description>Component Status Summarizer has not received a status message from component "%1", running on computer "%2", in %3 hours.%12</Description> </Message> <Message> <MessageID>4613</MessageID> <Description>Component Status Summarizer received a status message that was reported by component "%1", running on computer "%2" at site "%3", which is not the site where Component Status Summarizer is running.%12</Description> </Message> <Message> <MessageID>4614</MessageID> <Description>Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (%9 is a 24-hour interval).%12 The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".</Description> </Message> <Message> <MessageID>4615</MessageID> <Description>Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (1 is Sunday, 2 is Monday, and so on).%12 The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".</Description> </Message> <Message> <MessageID>4616</MessageID> <Description>Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the "Since Day %9 of the Month" Display Interval.%12 The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".</Description> </Message> <Message> <MessageID>4617</MessageID> <Description>Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the "Since Site Installation" Display Interval.%12 The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".</Description> </Message> <Message> <MessageID>4618</MessageID> <Description>Component Status Summarizer reset the count of Error status messages reported by component "%1" on computer "%2" for the "%9" Display Interval.%12 The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".</Description> </Message> <Message> <MessageID>4619</MessageID> <Description>Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (%9 is a 24-hour interval). The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4620</MessageID> <Description>Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (1 is Sunday, 2 is Monday, and so on). The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4621</MessageID> <Description>Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the "Since Day %9 of the Month" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4622</MessageID> <Description>Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the "Since Site Installation" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4623</MessageID> <Description>Component Status Summarizer reset the count of Warning status messages reported by component "%1" on computer "%2" for the "%9" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". "%9" is an encrypted version of the custom Display Interval you configured the Component Status Summarizer to use. Component Status Summarizer cannot display an unencrypted version of "%9" in a status message.%12</Description> </Message> <Message> <MessageID>4624</MessageID> <Description>Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (%9 is a 24-hour interval). The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4625</MessageID> <Description>Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" for the "Since %9" Display Interval (1 is Sunday, 2 is Monday, and so on). The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4626</MessageID> <Description>Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" for the "Since Day %9 of the Month" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4627</MessageID> <Description>Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" for the "Since Site Installation" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8".%12</Description> </Message> <Message> <MessageID>4628</MessageID> <Description>Component Status Summarizer reset the count of Informational status messages reported by component "%1" on computer "%2" for the "%9" Display Interval. The count is now %3; before the reset, the count was %4. The reset was requested on "%5" by user "%6" running the "%7" application on computer "%8". "%9" is an encrypted version of the custom Display Interval that you configured the Component Status Summarizer to use. Component Status Summarizer cannot display an unencrypted version of "%9" in a status message.%12</Description> </Message> <Message> <MessageID>4629</MessageID> <Description>Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Online.</Description> </Message> <Message> <MessageID>4630</MessageID> <Description>Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Failed.%12</Description> </Message> <Message> <MessageID>4631</MessageID> <Description>Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Degraded.%12</Description> </Message> <Message> <MessageID>4632</MessageID> <Description>Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Offline.%12</Description> </Message> <Message> <MessageID>4633</MessageID> <Description>Component Status Summarizer detected that the availability of component "%1" on computer "%2" has changed to Unknown.%12</Description> </Message> <Message> <MessageID>4700</MessageID> <Description>Site System Status Summarizer could not access storage object "%1" on site system "%2".%12</Description> </Message> <Message> <MessageID>4701</MessageID> <Description>Site System Status Summarizer still cannot access storage object "%1" on site system "%2".%12</Description> </Message> <Message> <MessageID>4702</MessageID> <Description>Site System Status Summarizer successfully accessed storage object "%1" on site system "%2".%12</Description> </Message> <Message> <MessageID>4703</MessageID> <Description>Site System Status Summarizer could not access the "%1" database on site database Server "%2".</Description> </Message> <Message> <MessageID>4704</MessageID> <Description>Site System Status Summarizer still cannot access the "%1" database on site database Server "%2".%12</Description> </Message> <Message> <MessageID>4705</MessageID> <Description>Site System Status Summarizer successfully accessed the "%1" database on SQL Server "%2".%12</Description> </Message> <Message> <MessageID>4706</MessageID> <Description>Site System Status Summarizer could not access the transaction log for the "%1" database on SQL Server "%2".%12</Description> </Message> <Message> <MessageID>4707</MessageID> <Description>Site System Status Summarizer still cannot access the transaction log for the "%1" database on SQL Server "%2".%12</Description> </Message> <Message> <MessageID>4708</MessageID> <Description>Site System Status Summarizer successfully accessed the transaction log for the "%1" database on SQL Server "%2". The transaction log had been inaccessible since %3. Providing that the transaction log has sufficient free space, Site System Status Summarizer will now restore the status of the transaction log to OK in the Site System Status summary in the Configuration Manager Console.</Description> </Message> <Message> <MessageID>4709</MessageID> <Description>Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, which is above the Free Space Thresholds for this storage object. Site System Status Summarizer will now set the status of the storage object to OK in the Site System Status summary in the Configuration Manager Console.</Description> </Message> <Message> <MessageID>4710</MessageID> <Description>Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, which is less than or equal to the Warning Free Space Threshold of %4 KB.</Description> </Message> <Message> <MessageID>4711</MessageID> <Description>Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, which is less than or equal to the Critical Free Space Threshold of %4 KB.</Description> </Message> <Message> <MessageID>4712</MessageID> <Description>Site System Status Summarizer detected that the "%1" database on site database server "%2" has %3 KB of free space, which is above the Free Space Thresholds for the database. Site System Status Summarizer will now set the status of the database to OK in the Site System Status summary in the Configuration Manager Console.</Description> </Message> <Message> <MessageID>4713</MessageID> <Description>Site System Status Summarizer detected that the "%1" database on site database server "%2" has %3 KB of free space, which is less than or equal to the Warning Free Space Threshold of %4 KB.</Description> </Message> <Message> <MessageID>4714</MessageID> <Description>Site System Status Summarizer detected that the database "%1" on site database server "%2" has %3 KB of free space, which is less than or equal to the Critical Free Space Threshold of %4 KB.</Description> </Message> <Message> <MessageID>4715</MessageID> <Description>Site System Status Summarizer detected that the transaction log for the "%1" database on site database server "%2" has %3 KB of free space, which is above the Free Space Thresholds for the transaction log. Site System Status Summarizer will now set the status of the transaction log to OK in the Site System Status summary in the Configuration Manager Console.</Description> </Message> <Message> <MessageID>4716</MessageID> <Description>Site System Status Summarizer detected that the transaction log for the "%1" database on site database server "%2" has %3 KB of free space, which is less than or equal to the Warning Free Space Threshold of %4 KB.</Description> </Message> <Message> <MessageID>4717</MessageID> <Description>Site System Status Summarizer detected that the transaction log for the "%1" database on site database server "%2" has %3 KB of free space, which is less than or equal to the Critical Free Space Threshold of %4 KB.</Description> </Message> <Message> <MessageID>4718</MessageID> <Description>Site System Status Summarizer has not been able to access the storage object "%1" on Site Object "%2" for %3 hours. Site System Status Summarizer will now assume that you no longer intend to use the storage object and will no longer monitor the storage object.</Description> </Message> <Message> <MessageID>4719</MessageID> <Description>Site System Status Summarizer detected that the storage object "%1" on Branch Distribution Point site system "%2" has %3 KB of free storage space, which is less than or equal to the Critical Free Space Threshold of %4 KB.</Description> </Message> <Message> <MessageID>4720</MessageID> <Description>Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Online.</Description> </Message> <Message> <MessageID>4721</MessageID> <Description>Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Failed.%12</Description> </Message> <Message> <MessageID>4722</MessageID> <Description>Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Degraded.%12</Description> </Message> <Message> <MessageID>4723</MessageID> <Description>Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Offline.%12</Description> </Message> <Message> <MessageID>4724</MessageID> <Description>Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Unknown.%12</Description> </Message> <Message> <MessageID>4900</MessageID> <Description>Site Component Manager is deinstalling all Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>4901</MessageID> <Description>Site Component Manager successfully deinstalled all Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>4902</MessageID> <Description>Site Component Manager failed to deinstall all Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>4903</MessageID> <Description>Site Component Manager failed to deinstall all Configuration Manager Server Components from site system "%1".</Description> </Message> <Message> <MessageID>4904</MessageID> <Description>Site Component Manager successfully installed the performance counters for this component on this site system.</Description> </Message> <Message> <MessageID>4905</MessageID> <Description>Site Component Manager failed to install the performance counters for this component on this site system.</Description> </Message> <Message> <MessageID>4906</MessageID> <Description>Site Component Manager successfully removed the performance counters for this component from this site system.</Description> </Message> <Message> <MessageID>4907</MessageID> <Description>Site Component Manager failed to remove the performance counters for this component from this site system.</Description> </Message> <Message> <MessageID>4908</MessageID> <Description>Site Component Manager could not add machine account "%1" to the SQL Access Group "%2" on the SQL Server machine "%3".</Description> </Message> <Message> <MessageID>4909</MessageID> <Description>Configuration Manager could not locate the "System Management" container in Active Directory (%1). Nor could it create a default container. This will prevent Site Component Manager and Hierarchy Manager from updating or adding any objects to Active Directory.</Description> </Message> <Message> <MessageID>4910</MessageID> <Description>Configuration Manager created a default "System Management" container in Active Directory (%1). This will be used to publish all necessary Active Directory objects for this site.</Description> </Message> <Message> <MessageID>4911</MessageID> <Description>Configuration Manager successfully created the object "%1" in Active Directory (%2).</Description> </Message> <Message> <MessageID>4912</MessageID> <Description>Configuration Manager cannot update the already existing object "%1" in Active Directory (%2).</Description> </Message> <Message> <MessageID>4913</MessageID> <Description>Configuration Manager cannot create the object "%1" in Active Directory (%2).</Description> </Message> <Message> <MessageID>4914</MessageID> <Description>Configuration Manager successfully deleted the object "%1" from Active Directory (%2).</Description> </Message> <Message> <MessageID>4915</MessageID> <Description>Configuration Manager cannot delete the object "%1" in Active Directory (%2).</Description> </Message> <Message> <MessageID>4918</MessageID> <Description>Configuration Manager cannot update the dNSHostName property for the existing object "%1" in Active Directory (%2). This property is used to publish fully qualified host names in Active Directory.</Description> </Message> <Message> <MessageID>4919</MessageID> <Description>Site Component Manager successfully installed the COM access registry keys for this component on this site system.</Description> </Message> <Message> <MessageID>4920</MessageID> <Description>Site Component Manager failed to install the COM access registry keys for this component on this site system.</Description> </Message> <Message> <MessageID>4921</MessageID> <Description>Site Component Manager successfully removed the COM access registry keys for this component from this site system.</Description> </Message> <Message> <MessageID>4922</MessageID> <Description>Site Component Manager failed to remove the COM access registry for this component from this site system.</Description> </Message> <Message> <MessageID>4923</MessageID> <Description>SMS System Health Validator %1 encountered an error. ErrorCode = %2.%12</Description> </Message> <Message> <MessageID>4924</MessageID> <Description>Site Component Manager failed to add machine account %1 to the user group %2, this must be done manually.</Description> </Message> <Message> <MessageID>4950</MessageID> <Description>Site Component Manager failed to install this component, because it can't configure Microsoft Internet Information Services (IIS).</Description> </Message> <Message> <MessageID>4951</MessageID> <Description>Site Component Manager failed to install this component, because the Microsoft Installer File for this component (%1) could not install. Refer to the %2, the %3, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.</Description> </Message> <Message> <MessageID>4952</MessageID> <Description>Site Component Manager failed to install this component because at least one file necessary for installation is missing. Refer to the component's installation log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.</Description> </Message> <Message> <MessageID>4956</MessageID> <Description>Site Component Manager successfully installed this component, However a reboot is required to complete the installation.</Description> </Message> <Message> <MessageID>4957</MessageID> <Description>Site Component Manager failed to install this component, because it either can't find or configure Internet Information Services Background Intelligent Transfer Service (BITS) Server Extensions.</Description> </Message> <Message> <MessageID>4958</MessageID> <Description>Site Component Manager failed to install this component, because it couldn't determine the the name of the IIS anonymous user account.</Description> </Message> <Message> <MessageID>4959</MessageID> <Description>Site Component Manager successfully installed this component. However the SQL Server Principal Name (SPN) could not be validated in Active Directory.</Description> </Message> <Message> <MessageID>4960</MessageID> <Description>Site Component Manager failed to install this component, because the designated Web Site of Internet Information Services is not running or started.</Description> </Message> <Message> <MessageID>4961</MessageID> <Description>Site Component Manager failed to install this component. The Distributed Transaction Coordinater Service (DTC) is not running. This service is needed to complete the Management Point installation. Please start the service, and try again.</Description> </Message> <Message> <MessageID>4962</MessageID> <Description>Site Component Manager failed to install this component. The Task Scheduler Service is not running. This service is needed to complete the Management Point installation. Please start the service, and try again.</Description> </Message> <Message> <MessageID>4963</MessageID> <Description>MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory.%12</Description> </Message> <Message> <MessageID>4964</MessageID> <Description>Site Component Manager failed to install this component, because Secure Sockets Layer (SSL) is not configured properly on the Internet Information Server.</Description> </Message> <Message> <MessageID>4965</MessageID> <Description>Site Component Manager failed to install this component, because it can't configure Microsoft Network Policy Server (NPS).</Description> </Message> <Message> <MessageID>4966</MessageID> <Description>Site Component Manager detected that site system "%1" is running the Microsoft Windows Server operating system version %2 service pack %3, which is not a supported operating system for System Health Validator point.</Description> </Message> <Message> <MessageID>4967</MessageID> <Description>Site Component Manager failed to install this component, because it can't configure Microsoft Windows Deployement Services (WDS).</Description> </Message> <Message> <MessageID>4968</MessageID> <Description>Site Component Manager failed to install this component, because it either can't find or configure WSUS.</Description> </Message> <Message> <MessageID>4969</MessageID> <Description>Site Component Manager failed to install WSUS role on server %1. Refer to the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.</Description> </Message> <Message> <MessageID>4970</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. The WebDAV server extension is either not installed or not configured properly.</Description> </Message> <Message> <MessageID>4971</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. The WCF is not activated.</Description> </Message> <Message> <MessageID>4972</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. The IIS Windows Authentication component is not installed.</Description> </Message> <Message> <MessageID>4973</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. The IIS ASP.NET component is not installed.</Description> </Message> <Message> <MessageID>4974</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. The IIS ASP.NET is not registered correctly.</Description> </Message> <Message> <MessageID>4975</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. The .NET Framework 3.5 is not installed.</Description> </Message> <Message> <MessageID>4976</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. The .NET Framework 4.0 Full Profile is not installed.</Description> </Message> <Message> <MessageID>4977</MessageID> <Description>Site Component Manager failed to install component %1 on server %2. SCEPInstall.exe returns error %3.%12</Description> </Message> <Message> <MessageID>5000</MessageID> <Description>Site Backup was unable to open control file "%1". Site backup did not occur.%12</Description> </Message> <Message> <MessageID>5001</MessageID> <Description>Site Backup stopped the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>5002</MessageID> <Description>Site Backup could not stop the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>5003</MessageID> <Description>Site Backup started the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>5004</MessageID> <Description>Site Backup could not start the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>5005</MessageID> <Description>Site Backup stopped the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>5006</MessageID> <Description>Site Backup could not stop the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>5007</MessageID> <Description>Site Backup started the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>5008</MessageID> <Description>Site Backup could not start the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>5009</MessageID> <Description>Site Backup successfully backed up file system object %1 to %2.%12</Description> </Message> <Message> <MessageID>5010</MessageID> <Description>Site Backup was unable to back up file system object %1 to %2.%12</Description> </Message> <Message> <MessageID>5011</MessageID> <Description>Site Backup successfully backed up registry key %1 to %2.%12</Description> </Message> <Message> <MessageID>5012</MessageID> <Description>Site Backup was unable to back up registry key %1 to %2.%12</Description> </Message> <Message> <MessageID>5013</MessageID> <Description>Site Backup successfully backed up %1 database %2 to %3.%12</Description> </Message> <Message> <MessageID>5014</MessageID> <Description>Site Backup was unable to back up %1 database %2 to %3.%12</Description> </Message> <Message> <MessageID>5015</MessageID> <Description>Site Backup successfully ran command line "%1", which completed with exit status %2.%12</Description> </Message> <Message> <MessageID>5016</MessageID> <Description>Site Backup was unable to run command line "%1" (error #%2).%12</Description> </Message> <Message> <MessageID>5017</MessageID> <Description>Site Backup reported that the backup control data ended unexpectedly at line %1. This problem might cause part of the site backup to be skipped.%12</Description> </Message> <Message> <MessageID>5018</MessageID> <Description>Site Backup is ignoring the invalid definition on line %1 of the backup control file. This problem may cause part of the site backup to be skipped.%12</Description> </Message> <Message> <MessageID>5019</MessageID> <Description>Site Backup is ignoring the invalid section starting on line %1 of the backup control file. This problem might cause part of the site backup to be skipped.%12</Description> </Message> <Message> <MessageID>5020</MessageID> <Description>Site Backup stopped the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>5021</MessageID> <Description>The %1 ConfigMgr client application on the local computer did not respond to Site Backup's stop request.%12</Description> </Message> <Message> <MessageID>5022</MessageID> <Description>Site Backup could not stop the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>5023</MessageID> <Description>Site Backup started the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>5024</MessageID> <Description>Site Backup could not start the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>5025</MessageID> <Description>Site Backup was run, but the %1 token had no value. Site backup did not occur.%12</Description> </Message> <Message> <MessageID>5026</MessageID> <Description>Site Backup was run, but the backup destination directory ( %1 ) is invalid. Site backup did not occur.%12</Description> </Message> <Message> <MessageID>5027</MessageID> <Description>Site Backup found syntax errors on the following lines:%1 in backup control file. Site backup did not occur.%12</Description> </Message> <Message> <MessageID>5028</MessageID> <Description>The following utility tools were not available to be run: %1 Their output is not provided so you might miss some configuration information.%12</Description> </Message> <Message> <MessageID>5029</MessageID> <Description>Unable to verify the installation of the service : %1 This service will not be stopped or restarted.%12</Description> </Message> <Message> <MessageID>5030</MessageID> <Description>Maximum sleep time is 15 minutes. Time given in Backup Control File exceeds this limit so it is being reset to this maximum limit.%12</Description> </Message> <Message> <MessageID>5031</MessageID> <Description>Token Symbol (%1) already defined. First value (%2) will be used.%12</Description> </Message> <Message> <MessageID>5032</MessageID> <Description>Site Backup was unable to back up registry key %1 to %2.%12</Description> </Message> <Message> <MessageID>5033</MessageID> <Description>Site Backup was unable to back up %1 database %2 to %3.%12</Description> </Message> <Message> <MessageID>5034</MessageID> <Description>Site Backup could not start the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>5035</MessageID> <Description>Site Backup completed successfully with zero errors but still there could be some warnings.%12</Description> </Message> <Message> <MessageID>5036</MessageID> <Description>Site Backup tried to stop the %1 service on site system %2. This service is already stopped.%12</Description> </Message> <Message> <MessageID>5037</MessageID> <Description>Site Backup tried to stop the %1 executable. This executable is already stopped.%12</Description> </Message> <Message> <MessageID>5038</MessageID> <Description>Site Backup service was stopped manually. Backup operation is not completed.%12</Description> </Message> <Message> <MessageID>5039</MessageID> <Description>%1 utility initiated by Site Backup did not complete in timely fashion. Terminating this utility. You may need to get its generated information manually.%12</Description> </Message> <Message> <MessageID>5040</MessageID> <Description>Site Backup successfully initiated command file "%1".%12</Description> </Message> <Message> <MessageID>5041</MessageID> <Description>Site Backup was unable to initiate command file "%1" .%12</Description> </Message> <Message> <MessageID>5042</MessageID> <Description>Site Backup did not find command file "%1" at its predefined location. Command file "%1" not launched.%12</Description> </Message> <Message> <MessageID>5043</MessageID> <Description>Site Backup was unable to back up file system object %1 to %2.%12</Description> </Message> <Message> <MessageID>5044</MessageID> <Description>Site Backup failed to initialize the VSS services. Aborting the backup operation. Please verify that the VSS services are up and running.%12</Description> </Message> <Message> <MessageID>5045</MessageID> <Description>Site Backup could not find the SMS Writer in the list of writers provided by the VSS. Aborting the backup operation. Please verify that the SMS Writer service is up and running.%12</Description> </Message> <Message> <MessageID>5046</MessageID> <Description>Site Backup failed while reading the VSS writers meta data. Aborting the backup operation.%12</Description> </Message> <Message> <MessageID>5047</MessageID> <Description>Site Backup failed while creating the snapshot using the VSS services. Aborting the backup operation.%12</Description> </Message> <Message> <MessageID>5048</MessageID> <Description>Site Backup failed while trying to copy the files to the destination. Backup operation is not completed.</Description> </Message> <Message> <MessageID>5049</MessageID> <Description>Site Backup could not connect to the registry on the SQL Server machine. Aborting the backup operation. Verify that the site server computer accounthas administrative rights on the SQL Server .%12</Description> </Message> <Message> <MessageID>5050</MessageID> <Description>Site Backup could not find the registry entries on the SQL Server machine. SMS SQL Backup service might not be running on the SQL Server machine.%12</Description> </Message> <Message> <MessageID>5051</MessageID> <Description>Site Backup found that the SMS SQL Backup service on the SQL machine is currently backing up the site database. It cannot start the new backup until the previous backup task is completed.%12</Description> </Message> <Message> <MessageID>5052</MessageID> <Description>SMS SQL Backup service on the SQL Server %1 failed to backup the site database %2. The error reported by the service is %3. Backup operation is not completed.%12</Description> </Message> <Message> <MessageID>5053</MessageID> <Description>SMS SQL Backup service on the SQL Server %1 did not start the database backup. SMS SQL Backup service might not be running on the SQL Server machine.%12</Description> </Message> <Message> <MessageID>5054</MessageID> <Description>SMS SQL Backup service on the SQL Server %1 successfully backed up the site database.%12</Description> </Message> <Message> <MessageID>5055</MessageID> <Description>Site Backup task is starting. This task will interact with the windows VSS services and the appropriate writers to create a volume snapshot and then back up the required files to the specified destination.%12</Description> </Message> <Message> <MessageID>5056</MessageID> <Description>Site Backup is starting to copy the files from the snapshot.%12</Description> </Message> <Message> <MessageID>5057</MessageID> <Description>Site Backup has successfully completed copying the files from the snapshot.%12</Description> </Message> <Message> <MessageID>5058</MessageID> <Description>SQL Server Backup path is empty or invalid. For remote SQL Server scenarios you should provide either a UNC path for entire backup or provide a local path on the site server for site backup and a local path on the SQL Server for the SQL backup. For the site database backup to succeed, you must update the SQL Server backup location in the Backup Configuration Manager maintenance task properties in the Configuration Manager Console.%12</Description> </Message> <Message> <MessageID>5059</MessageID> <Description>Site Backup failed to copy the files from the snapshot.%12</Description> </Message> <Message> <MessageID>5060</MessageID> <Description>Site Backup failed. The error reported by the service is %1. Backup operation is not completed. Please see smsbkup.log for more information.%12</Description> </Message> <Message> <MessageID>5100</MessageID> <Description>Policy Provider successfully created a policy and a policy assignment based on package %1 (%2), program %3 and deployment %4 (%5).%12</Description> </Message> <Message> <MessageID>5101</MessageID> <Description>Policy Provider successfully updated the policy and the policy assignment that were created from package %1 (%2), program %3 and deployment %4 (%5).%12</Description> </Message> <Message> <MessageID>5102</MessageID> <Description>Policy Provider successfully removed policy %1 and the related policy assignment.%12</Description> </Message> <Message> <MessageID>5103</MessageID> <Description>Policy Provider successfully created a settings policy and a settings policy assignment.%12</Description> </Message> <Message> <MessageID>5104</MessageID> <Description>Policy Provider successfully updated a settings policy and a settings policy assignment.%12</Description> </Message> <Message> <MessageID>5105</MessageID> <Description>Policy Provider successfully created a metering policy and a metering policy assignment.%12</Description> </Message> <Message> <MessageID>5106</MessageID> <Description>Policy Provider successfully updated a metering policy and a metering policy assignment.%12</Description> </Message> <Message> <MessageID>5107</MessageID> <Description>Policy Provider successfully created a policy and a policy assignment based on Distribution Point %1 (%2).%12</Description> </Message> <Message> <MessageID>5108</MessageID> <Description>Policy Provider successfully updated the policy and the policy assignment that were created from Distribution Point %1 (%2).%12</Description> </Message> <Message> <MessageID>5109</MessageID> <Description>Policy Provider successfully created a policy and a policy assignment based on package %1.%12</Description> </Message> <Message> <MessageID>5110</MessageID> <Description>Policy Provider successfully updated the policy and the policy assignment that were created from package %1.%12</Description> </Message> <Message> <MessageID>5111</MessageID> <Description>The site server signing certificate with hashcode '%1' is missing in the Certificate Store.%12</Description> </Message> <Message> <MessageID>5112</MessageID> <Description>The site server signing certificate will expire in %1 day(s). Please ensure that this certificate is renewed for the proper operation of the ConfigMgr site.%12</Description> </Message> <Message> <MessageID>5113</MessageID> <Description>The site server signing certificate has expired %1 day(s) ago. Please replace/renew the certificate. The Policies at this Site will be re-signed by the Site Server using the new signing certificate.%12</Description> </Message> <Message> <MessageID>5114</MessageID> <Description>The site server signing certificate has changed. The Policy at this Site will be re-signed by the Site Server using the new signing certificate.%12</Description> </Message> <Message> <MessageID>5115</MessageID> <Description>Policy Provider has failed to sign one or more policy assignments. It will retry this operation automatically.%12</Description> </Message> <Message> <MessageID>5116</MessageID> <Description>Policy Provider successfully signed all policy assignments with the new Site Server Signing Certificate.%12</Description> </Message> <Message> <MessageID>5117</MessageID> <Description>The hashing algorithm has changed. The Policy at this Site will be re-signed by the Site Server.%12</Description> </Message> <Message> <MessageID>5118</MessageID> <Description>Policy Provider has noted that the Program: %1 (Package ID: %2) is set to only run on one or more deprecated platforms that are no longer supported. The deployment (ID: %3)will not run on clients until the platform requirements are corrected.%12</Description> </Message> <Message> <MessageID>5119</MessageID> <Description>Policy Provder has detected policy changes for Collection %1. %2 are added. %3 are deleted.</Description> </Message> <Message> <MessageID>5200</MessageID> <Description>Active Directory System Discovery Agent failed to read the necessary registry information.%12</Description> </Message> <Message> <MessageID>5201</MessageID> <Description>Active Directory System Discovery Agent failed to read the location of the outbox.%12</Description> </Message> <Message> <MessageID>5202</MessageID> <Description>Active Directory System Discovery Agent read the AD Containers and found %1 valid AD Container entries in the site control file. Active Directory System Discovery Agent identified %2 systems in the AD Containers and generated %3 system discovery data records (DDRs) and %4 errors while attempting to create DDRs.%12</Description> </Message> <Message> <MessageID>5203</MessageID> <Description>Active Directory System Discovery Agent reported errors for %1 objects. DDRs were generated for %2 objects that had errors while reading non-critical properties. DDRs were not generated for %3 objects that had errors while reading critical properties.%12</Description> </Message> <Message> <MessageID>5204</MessageID> <Description>Active Directory System Discovery Agent failed to bind to container %1. Error: %2.%12</Description> </Message> <Message> <MessageID>5300</MessageID> <Description>Active Directory User Discovery Agent failed to read the necessary registry information.%12</Description> </Message> <Message> <MessageID>5301</MessageID> <Description>Active Directory User Discovery Agent failed to read the location of the outbox.%12</Description> </Message> <Message> <MessageID>5302</MessageID> <Description>Active Directory User Discovery Agent read the AD Containers and found %1 valid AD Container entries in the site control file. Active Directory User Discovery Agent identified %2 users in the AD Containers and generated %3 user discovery data records (DDRs) and %4 errors while attempting to create DDRs.%12</Description> </Message> <Message> <MessageID>5303</MessageID> <Description>Active Directory User Discovery Agent reported errors for %1 objects. DDRs were generated for %2 objects that had errors while reading non-critical properties. DDRs were not generated for %3 objects that had errors while reading critical properties.%12</Description> </Message> <Message> <MessageID>5304</MessageID> <Description>Active Directory User Discovery Agent failed to bind to container %1. Error: %2.%12</Description> </Message> <Message> <MessageID>5350</MessageID> <Description>Active Directory Security Group Discovery Agent failed to read the necessary registry information.%12</Description> </Message> <Message> <MessageID>5351</MessageID> <Description>Active Directory Security Group Discovery Agent failed to read the location of the outbox.%12</Description> </Message> <Message> <MessageID>5352</MessageID> <Description>Active Directory Security Group Discovery Agent read the AD Containers and found %1 valid AD Container entries in the site control file. Active Directory Security Group Discovery Agent identified %2 security group(s) in the AD Containers and generated %3 security group discovery data records (DDRs). %12</Description> </Message> <Message> <MessageID>5353</MessageID> <Description>Active Directory Security Group Discovery Agent reported warnings for %1 object(s). DDRs were generated for %2 object(s) that had warning(s) while reading non-critical properties. DDRs were not generated for %3 object(s) that had warnings while reading critical properties.%12</Description> </Message> <Message> <MessageID>5354</MessageID> <Description>Active Directory Security Group Discovery Agent failed to bind to container %1. Error: %2.%12</Description> </Message> <Message> <MessageID>5400</MessageID> <Description>MP File Dispatch Manager running on the management point "%1" cannot connect to site server "%2".%12</Description> </Message> <Message> <MessageID>5401</MessageID> <Description>MP File Dispatch Manager cannot copy files from "%1" to "%2".%12</Description> </Message> <Message> <MessageID>5410</MessageID> <Description>MP common layer cannot read the registry configuration when processing %1.%12</Description> </Message> <Message> <MessageID>5411</MessageID> <Description>MP has experienced out of memory condition when processing %1.%12</Description> </Message> <Message> <MessageID>5412</MessageID> <Description>MP has incurred an unexpected error when processing %1.%12</Description> </Message> <Message> <MessageID>5413</MessageID> <Description>MP has discarded a report when processing %1.%12</Description> </Message> <Message> <MessageID>5414</MessageID> <Description>MP could not complete a task when processing %1.%12 Check the logs for clues.</Description> </Message> <Message> <MessageID>5415</MessageID> <Description>MP cannot load the hardware inventory class mapping table when processing %1.%12</Description> </Message> <Message> <MessageID>5416</MessageID> <Description>MP needs to reload the hardware inventory class mapping table when processing %1. The MP hardware inventory manager cannot find a WMI class definition in the mapping table when processing a report. This should only happen if new definitions beyond those known to the site are added to the collected classes.%12</Description> </Message> <Message> <MessageID>5417</MessageID> <Description>MP could not process a message itself or spawn a task for message processing and discarded the message when processing %1. This is benign.%12</Description> </Message> <Message> <MessageID>5418</MessageID> <Description>MP could not find some class or property definitions when processing %1 as they are apparently missing in sms_def.mof. Unknown classes and properties have been ignored and a MIF file generated with all the classes and properties that could be found. %12</Description> </Message> <Message> <MessageID>5419</MessageID> <Description>MP retry component gave up on a report when processing %1 and moved it to the bad report directory. %12</Description> </Message> <Message> <MessageID>5420</MessageID> <Description>Management Point encountered an error when connecting to the database %3 on SQL Server %2. The OLEDB error code was %4. %12</Description> </Message> <Message> <MessageID>5421</MessageID> <Description>The Management Point was repaired.%12</Description> </Message> <Message> <MessageID>5430</MessageID> <Description>MP failed to register with the local WINS server.%12</Description> </Message> <Message> <MessageID>5431</MessageID> <Description>MP failed to unregister from the local WINS server.%12</Description> </Message> <Message> <MessageID>5432</MessageID> <Description>MP could not write out CCM setting to WMI.%12</Description> </Message> <Message> <MessageID>5433</MessageID> <Description>MP could not update its settings to the new values.%12</Description> </Message> <Message> <MessageID>5434</MessageID> <Description>Some or all of the MP Component Managers could not be started.%12</Description> </Message> <Message> <MessageID>5435</MessageID> <Description>Some or all of the MP Component Managers could not be stopped.%12</Description> </Message> <Message> <MessageID>5436</MessageID> <Description>MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>5437</MessageID> <Description>MP Control Manager detected NLB MP is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>5438</MessageID> <Description>MP Control Manager detected MP is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>5439</MessageID> <Description>MP Control Manager detected NLB MP is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>5441</MessageID> <Description>The SMS Agent Host (CCMEXEC) was unable to update certificate information in the Active Directory.%12</Description> </Message> <Message> <MessageID>5442</MessageID> <Description>The SMS Agent Host (CCMEXEC) successfuly updated certificate information in the Active Directory. %12</Description> </Message> <Message> <MessageID>5443</MessageID> <Description>MP has rejected a message from client %2 because it was not signed using the hash algorithm that is required by this site.%12</Description> </Message> <Message> <MessageID>5444</MessageID> <Description>MP has rejected policy request from %2 because this SMSID is marked as blocked.%12</Description> </Message> <Message> <MessageID>5445</MessageID> <Description>MP has rejected registration request due to failure in client certificate (Subject Name: %2) chain validation. If this is a valid client, Configuration Manager Administrator needs to place the Root Certification Authority and Intermediate Certificate Authorities in the MPÆs Certificate store or configure Trusted Root Certification Authorities in primary site settings.%12</Description> </Message> <Message> <MessageID>5446</MessageID> <Description>MP has rejected the request because %2 certificate has expired.%12</Description> </Message> <Message> <MessageID>5447</MessageID> <Description>MP has rejected a message from %2 because the signature could not be validated. If this is a valid client, it will attempt to re-register automatically so its signature can be correctly validated.%12</Description> </Message> <Message> <MessageID>5448</MessageID> <Description>MP has rejected a policy request from %2 because this client is not approved.%12</Description> </Message> <Message> <MessageID>5449</MessageID> <Description>MP has rejected a message from Client %2 because it was not signed.%12</Description> </Message> <Message> <MessageID>5450</MessageID> <Description>MP has rejected registration request from %2 because the Client Certificate has insufficient key length.%12</Description> </Message> <Message> <MessageID>5460</MessageID> <Description>MP Control Manager verified that Management Point is responding to HTTP requests.</Description> </Message> <Message> <MessageID>5461</MessageID> <Description>MP Control Manager verified that Device Management Point is responding to HTTP requests.</Description> </Message> <Message> <MessageID>5462</MessageID> <Description>MP Control Manager verified that Device Management Point Proxy is responding to HTTP requests.</Description> </Message> <Message> <MessageID>5480</MessageID> <Description>MP Control Manager detected DMP is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>5481</MessageID> <Description>MP Control Manager detected DMP is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>5482</MessageID> <Description>MP Control Manager detected that this node of the NLB MP is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>5483</MessageID> <Description>MP Control Manager detected that this node of the NLB MP is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>5484</MessageID> <Description>MP Control Manager detected that this node of the NLB MP is online. Node status code is %1 (%2).%12</Description> </Message> <Message> <MessageID>5485</MessageID> <Description>MP Control Manager detected that this node of the NLB MP is degraded. Node status code is %1 (%2).%12</Description> </Message> <Message> <MessageID>5486</MessageID> <Description>MP Control Manager detected that this node of the NLB MP is offline. Node status code is %1 (%2).%12</Description> </Message> <Message> <MessageID>5487</MessageID> <Description>MP Control Manager detected that the SQL Server hosting the database configured for the Management Point has its Common Language Runtime (CLR) disabled. This will cause multiple features of Configuration Manager requiring SQL CLR to fail.%12</Description> </Message> <Message> <MessageID>5488</MessageID> <Description>MP Control Manager detected DMP Proxy is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>5489</MessageID> <Description>MP Control Manager detected DMP Proxy is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>5600</MessageID> <Description>Software Metering Processor failed to read and configure the registry keys necessary for this component.%12</Description> </Message> <Message> <MessageID>5601</MessageID> <Description>Software Metering Processor failed to process the usage file "%1" for client "%2".%12</Description> </Message> <Message> <MessageID>5602</MessageID> <Description>Software Metering Processor was unable to copy the definition for rule %1 to the master rule file for this site. %12</Description> </Message> <Message> <MessageID>5603</MessageID> <Description>Software Metering Processor failed to completely process local rule changes, the rule change log has not been cleared and the changes will be processed again. %12</Description> </Message> <Message> <MessageID>5604</MessageID> <Description>Software Metering Processor failed to replicate the definition for rule %1 to child sites. %12</Description> </Message> <Message> <MessageID>5605</MessageID> <Description>Software Metering Processor failed to process a rule replicated from the parent site. %12</Description> </Message> <Message> <MessageID>5606</MessageID> <Description>Software Metering Processor failed to replicate summary data to the parent site.%12</Description> </Message> <Message> <MessageID>5607</MessageID> <Description>Software Metering Processor could not process replicated summary data from a child site.%12</Description> </Message> <Message> <MessageID>5608</MessageID> <Description>Software Metering Processor failed to process usage data file %1 and moved it to the retry directory. The file will be reprocessed at a later time.%12</Description> </Message> <Message> <MessageID>5609</MessageID> <Description>Software Metering Processor successfully processed a change for the rule %1 which was last modified on %2, the rule is enabled.</Description> </Message> <Message> <MessageID>5610</MessageID> <Description>Software Metering Processor successfully processed a change for the rule %1 which was last modified on %2, the rule is disabled.</Description> </Message> <Message> <MessageID>5611</MessageID> <Description>Software Metering Processor maintenance cycle deleted %1 files from directory %2.</Description> </Message> <Message> <MessageID>5612</MessageID> <Description>Software Metering Processor experienced an error while processing and forwarding usage data to the parent site.%12</Description> </Message> <Message> <MessageID>5613</MessageID> <Description>Software Metering Processor has retried the usage data file "%1" the maxumum number of times and has moved it to the discard directory. The file will be deleted when the minimum clean up age has been reached. %12</Description> </Message> <Message> <MessageID>5614</MessageID> <Description>Software Metering Processor failed to process the usage file "%1" for client "%2" because a record contained a bad usage start or end time value. Usage times are rejected if the start time is greater than the end time, the end time is in the future, or the end time is more than 90 days old.%12</Description> </Message> <Message> <MessageID>5615</MessageID> <Description>Software Metering Processor moved file "%1" to the corrupt directory. The file will be deleted when the minimum clean up age has been reached. See the previous and following error status messages for more details.</Description> </Message> <Message> <MessageID>5616</MessageID> <Description>Software Metering Processor could not process a summary file sent from a child site because a referenced computer was not found in the database. The file will be retried later.%12</Description> </Message> <Message> <MessageID>5617</MessageID> <Description>Software Metering Processor could not process a summary file sent from a child site because a referenced computer was not found in the database. The file will not be retried again.%12</Description> </Message> <Message> <MessageID>5700</MessageID> <Description>Device Management Point has encountered an unexpected error when processing %1.%12</Description> </Message> <Message> <MessageID>5701</MessageID> <Description>Device Management Point has experienced out of memory condition when processing %1. %12</Description> </Message> <Message> <MessageID>5702</MessageID> <Description>Device Management Point encountered an error when connecting to its database. %12</Description> </Message> <Message> <MessageID>5703</MessageID> <Description>Device Management Point failed to authenticate the client %1. %12</Description> </Message> <Message> <MessageID>5720</MessageID> <Description>Received an undefined message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5721</MessageID> <Description>Received message from unknown or unauthorized client %1.%12</Description> </Message> <Message> <MessageID>5722</MessageID> <Description>Received an invalid poll message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5723</MessageID> <Description>Received an invalid download instructions request message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5724</MessageID> <Description>Received an invalid package location request message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5725</MessageID> <Description>Received an invalid status message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5726</MessageID> <Description>Received an invalid hardware inventory message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5727</MessageID> <Description>Received an invalid software inventory message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5728</MessageID> <Description>Received an invalid file collection message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5729</MessageID> <Description>Received an invalid registration message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5740</MessageID> <Description>Error generating or sending discovery message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5741</MessageID> <Description>Error generating or sending hardware inventory message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5742</MessageID> <Description>Error generating or sending software inventory message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5743</MessageID> <Description>Error generating or sending file collection message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5744</MessageID> <Description>Error generating or sending status message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5745</MessageID> <Description>Error generating or sending package location request message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5746</MessageID> <Description>Error processing download instructions request message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5747</MessageID> <Description>Error processing registration request message. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5748</MessageID> <Description>Device Management Point encountered an error when processing App model policy. %12</Description> </Message> <Message> <MessageID>5749</MessageID> <Description>Device Management Point encountered an error when sending Compliance Report. %12</Description> </Message> <Message> <MessageID>5750</MessageID> <Description>Device Management Point encountered an error when processing DCM CI. %12</Description> </Message> <Message> <MessageID>5751</MessageID> <Description>Device Management Point encountered an error while reading policy xml. %12</Description> </Message> <Message> <MessageID>5752</MessageID> <Description>Device Management Point encountered an error when processing Schedule policy. %12</Description> </Message> <Message> <MessageID>5753</MessageID> <Description>Device Management Point encountered an error when processing Data policy. %12</Description> </Message> <Message> <MessageID>5754</MessageID> <Description>Device Management Point encountered an error when processing prequisite applications policy. %12</Description> </Message> <Message> <MessageID>5755</MessageID> <Description>Device Management Point encountered an error when registering a device. %12</Description> </Message> <Message> <MessageID>5756</MessageID> <Description>Device Management Point encountered an error when processing client certificate. %12</Description> </Message> <Message> <MessageID>5760</MessageID> <Description>Error sending poll response. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5761</MessageID> <Description>Error sending download instructions. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5762</MessageID> <Description>Error sending package location response. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5763</MessageID> <Description>Error sending registration response. Client ID is %1.%12</Description> </Message> <Message> <MessageID>5800</MessageID> <Description>CI Assignment Manager successfully processed new CI Assignment %1.%12</Description> </Message> <Message> <MessageID>5801</MessageID> <Description>CI Assignment Manager successfully processed Update to CI Assignment %1.%12</Description> </Message> <Message> <MessageID>5802</MessageID> <Description>CI Assignment Manager successfully removed CI Assignment %1.%12</Description> </Message> <Message> <MessageID>5803</MessageID> <Description>SMS CI Assignment has been directly deleted from the site Database. Deletion of collection may cause the deletion of all the CI Assignments assigned to that collection. It is not recommended directly deleting CI Assignments from the site database, to verify this deletion was due to Collection delete review the CI Assignment Manager and Collection Evaluator Logs.%12</Description> </Message> <Message> <MessageID>5804</MessageID> <Description>CI Assignment Manager failed to process CI Assignment changes. These changes will be retried on next processing cycle.%12</Description> </Message> <Message> <MessageID>5805</MessageID> <Description>CI Assignment Manager failed to process CI Assignment %1. This CI Assignment will be retried %2 times on the next processing cycles.%12</Description> </Message> <Message> <MessageID>5806</MessageID> <Description>CI Assignment Manager failed to process CI Assignment %1. This CI Assignment has been retried %2 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>5807</MessageID> <Description>CI Assignment Manager failed to process CI Assignment Replication File %1 as CI Assignment %2 referenced object of type %3 does not exists. This CI Assignment Replication file has been retried %4 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>5808</MessageID> <Description>CI Assignment Manager failed to process CI Assignment Replication File %1. This CI Assignment Replication file has been retried %2 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>6000</MessageID> <Description>Object Replication Manager successfully processed Object %1 of Type %2.%12</Description> </Message> <Message> <MessageID>6001</MessageID> <Description>Object Replication Manager successfully processed modification to Object %1 of Type %2.%12</Description> </Message> <Message> <MessageID>6002</MessageID> <Description>Object Replication Manager successfully removed Object %1 of Type %2.%12</Description> </Message> <Message> <MessageID>6003</MessageID> <Description>Object Replication Manager failed to process Object %1 of Type %2. This Object has been retried %3 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>6004</MessageID> <Description>Object Replication Manager failed to process Object changes. These changes will be retried on next processing cycle.%12</Description> </Message> <Message> <MessageID>6005</MessageID> <Description>Object Replication Manager failed to process Object Replication File %1. This Object Replication file has been retried %2 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>6006</MessageID> <Description>Object Replication Manager failed to process Object %1 of Type %2. This Object will be retried %3 times on the next processing cycles.%12</Description> </Message> <Message> <MessageID>6007</MessageID> <Description>Object Replication Manager failed to process Object Replication File %1 as Object %2 of Type %3 referenced object of type %4 does not exists. This Object Replication file has been retried %5 times and has reached the maximum retry limit.%12</Description> </Message> <Message> <MessageID>6100</MessageID> <Description>The State System failed to read and configure the registry keys necessary for this component.%12</Description> </Message> <Message> <MessageID>6101</MessageID> <Description>The State System message file processing experienced a severe error and suspended file processing. Review the statesys.log file for further details.%12</Description> </Message> <Message> <MessageID>6103</MessageID> <Description>The State System summary task '%1' failed to execute. Review the statesys.log file for further details.%12</Description> </Message> <Message> <MessageID>6104</MessageID> <Description>The State System message file processing could not process file '%1' and moved it to the corrupt directory. Review the statesys.log file for further details.%12</Description> </Message> <Message> <MessageID>6105</MessageID> <Description>The State System message file processing processed one or more files that contained errors or invalid data. Review the statesys.log file for further details.%12</Description> </Message> <Message> <MessageID>6200</MessageID> <Description>The State Migration Point failed to read and configure the registry keys necessary for this component.</Description> </Message> <Message> <MessageID>6201</MessageID> <Description>The State Migration Point reached the minimum disk space threshold on all drives of computer %1.</Description> </Message> <Message> <MessageID>6202</MessageID> <Description>The State Migration Point has reached the maximum client threshold on all drives on computer %1.</Description> </Message> <Message> <MessageID>6203</MessageID> <Description>Client with GUID %1 requested capture request while the store from previous request exists.%12</Description> </Message> <Message> <MessageID>6204</MessageID> <Description>The State Migration Point has reached the minimum disk space threshold of %1 %2 on drive %3 of computer %4. Current free space is %5 %2.%12</Description> </Message> <Message> <MessageID>6205</MessageID> <Description>The State Migration Point has removed the state store %2 on computer %1.%12</Description> </Message> <Message> <MessageID>6206</MessageID> <Description>The State Migration Point can not authenticate the client %1.</Description> </Message> <Message> <MessageID>6207</MessageID> <Description>SMP Control Manager detected SMP is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>6208</MessageID> <Description>SMP Control Manager detected SMP is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>6209</MessageID> <Description>State Migration Point cannot access the state store %1 on computer %2.%12</Description> </Message> <Message> <MessageID>6210</MessageID> <Description>State Migration Point failed to read the SignedSerializedSMPKey from the registry on computer %1. Possible reasons are SMP certificate is not yet signed by Site Server. %12</Description> </Message> <Message> <MessageID>6211</MessageID> <Description>There is enough free disk on computer %1.</Description> </Message> <Message> <MessageID>6300</MessageID> <Description>The PXE Service Point failed to read and configure the registry keys necessary for this component.</Description> </Message> <Message> <MessageID>6301</MessageID> <Description>The PXE Service Point failed to initialize the WDS PXE Provider. Check Previous Messages for more error information.</Description> </Message> <Message> <MessageID>6302</MessageID> <Description>The PXE Service Point failed to perform a clean shutdown.</Description> </Message> <Message> <MessageID>6303</MessageID> <Description>The PXE Service Point failed to initialize performance counters.</Description> </Message> <Message> <MessageID>6304</MessageID> <Description>The PXE Service Point failed to initialize worker threads.</Description> </Message> <Message> <MessageID>6305</MessageID> <Description>The PXE Service Point failed to process PXE request.</Description> </Message> <Message> <MessageID>6306</MessageID> <Description>The PXE Service Point is not actively processing PXE messages. Ignoring request from device. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6307</MessageID> <Description>The PXE Service Point failed to Lookup device in the database. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6308</MessageID> <Description>The PXE Service Point failed to get boot action from database for device. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6309</MessageID> <Description>The PXE Service Point failed to find boot image for package %3 while handling device. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6310</MessageID> <Description>The PXE Service Point failed to find boot image for package %3 while handling device. Stalling device until package becomes available. If this situation persists the device might become unmanageable. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6311</MessageID> <Description>The PXE Service Point instructed the device to boot to the bootimage %3 based on deployment %4. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6312</MessageID> <Description>The PXE Service Point encountered an unknown device. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6313</MessageID> <Description>The PXE Service Point intructed device to boot normally since it already had executed deployment %3. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6314</MessageID> <Description>The PXE Service Point intructed device to boot normally since it has no PXE deployment assigned. Device MAC Address:%1 SMBIOS GUID:%2.</Description> </Message> <Message> <MessageID>6315</MessageID> <Description>The PXE Service Point failed to Initialize the Database Connection.</Description> </Message> <Message> <MessageID>6316</MessageID> <Description>The PXE Certificate used for PXE clients is not valid. Please provide a valid certificate.</Description> </Message> <Message> <MessageID>6317</MessageID> <Description>The PXE Certificate used for PXE clients will expire soon. Please renew the certificate.</Description> </Message> <Message> <MessageID>6318</MessageID> <Description>PXE control manager could not update its settings to the new values.%12</Description> </Message> <Message> <MessageID>6319</MessageID> <Description>PXE Control Manager detected PXE service point is not responding to PXE requests. The error is %1.%12</Description> </Message> <Message> <MessageID>6320</MessageID> <Description>PXE Control Manager detected PXE service point is not responding to PXE requests. The status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>6321</MessageID> <Description>The PXE Service Point does not have a boot image matching the processor architetcure of the PXE booting device. Device MAC Address:%1 SMBIOS GUID:%2. Boot Image Architecture:%3.</Description> </Message> <Message> <MessageID>6322</MessageID> <Description>The PXE Service Point does not have a boot program matching the processor architetcure of the PXE booting device. Device MAC Address:%1 SMBIOS GUID:%2. Boot Program Architecture:%3.</Description> </Message> <Message> <MessageID>6400</MessageID> <Description>Component Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12</Description> </Message> <Message> <MessageID>6500</MessageID> <Description>The Wake On LAN component has failed to read the site control file settings.</Description> </Message> <Message> <MessageID>6501</MessageID> <Description>The Wake On LAN component was enabled by the Configuration Manager Administrator.%12</Description> </Message> <Message> <MessageID>6502</MessageID> <Description>The Wake On LAN component was disabled by the Configuration Manager Administrator.%12</Description> </Message> <Message> <MessageID>6503</MessageID> <Description>The Wake On LAN component settings have been updated by the Configuration Manager Administrator.%12</Description> </Message> <Message> <MessageID>6504</MessageID> <Description>The Wake On LAN component is starting to send wakeup packets for the object id=%1 of type=%2.%12</Description> </Message> <Message> <MessageID>6505</MessageID> <Description>The Wake On LAN component component completed sending wakeup packets for the object id=%1 of type=%2.%12</Description> </Message> <Message> <MessageID>6506</MessageID> <Description>The Wake On LAN component component successfully sent wakeup packets to all clients targeted for the object id=%1 of type=%2.%12</Description> </Message> <Message> <MessageID>6507</MessageID> <Description>The Wake On LAN component component failed to send wakeup packets for some clients targeted by object id=%1 of type=%2.</Description> </Message> <Message> <MessageID>6508</MessageID> <Description>The Wake On LAN component component failed to start sending wakeup packets for object id=%1 of type=%2.</Description> </Message> <Message> <MessageID>6509</MessageID> <Description>The Wake On LAN component failed access the database.</Description> </Message> <Message> <MessageID>6510</MessageID> <Description>The Wake On LAN component successfully processed wakeup information for the object id=%1 of type=%2.%12</Description> </Message> <Message> <MessageID>6511</MessageID> <Description>The Wake On LAN component failed to process wakeup information for the object id=%1 of type=%2.</Description> </Message> <Message> <MessageID>6512</MessageID> <Description>The Wake On LAN component has recovered from an unavailable state. The component is now online.%12</Description> </Message> <Message> <MessageID>6513</MessageID> <Description>The Wake On LAN component has entered an unavailable state due to a high number of failures. The component's services may not be available.%12</Description> </Message> <Message> <MessageID>6600</MessageID> <Description>WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "%1".%12</Description> </Message> <Message> <MessageID>6602</MessageID> <Description>WSUS Configuration Manager failed to get update categories, classifications and locales from WSUS Server "%1".%12</Description> </Message> <Message> <MessageID>6603</MessageID> <Description>WSUS Configuration Manager failed to subscribe to update categories and classifications on WSUS Server "%1".%12</Description> </Message> <Message> <MessageID>6607</MessageID> <Description>WSUS Configuration Manager will not be able to configure WSUS Server "%1" as the WSUS Server remoting API's of version 3.0 SP2 or greater are not installed on this site server.%12</Description> </Message> <Message> <MessageID>6609</MessageID> <Description>WSUS Configuration Manager has configured WSUS Server "%1" to sync from the parent WSUS Server instead of sync from Microsoft Update.%12</Description> </Message> <Message> <MessageID>6610</MessageID> <Description>WSUS Configuration Manager has detected that WSUS Server "%1" cannot sync from the parent WSUS Server as there is no parent WSUS Server. Choose the option from the Configuration Manager Console to sync from either Microsoft Update or Do not Sync.%12</Description> </Message> <Message> <MessageID>6611</MessageID> <Description>WSUS Configuration Manager has detected that Software Updates Point is not configured yet. client boot-strapper packag publishing will be tried later.%12</Description> </Message> <Message> <MessageID>6612</MessageID> <Description>WSUS Configuration Manager failed to get client package info.%12</Description> </Message> <Message> <MessageID>6613</MessageID> <Description>WSUS Configuration Manager failed to publish client boot-strapper package "%1" with version "%2" to the Software Updates Point.%12</Description> </Message> <Message> <MessageID>6614</MessageID> <Description>WSUS Configuration Manager failed to unpublish client boot-strapper package "%1" with version "%2" from the Software Updates Point.%12</Description> </Message> <Message> <MessageID>6615</MessageID> <Description>WSUS Configuration Manager successfully published client boot-strapper package "%1" with version "%2" to the Software Updates Point.%12</Description> </Message> <Message> <MessageID>6616</MessageID> <Description>WSUS Configuration Manager successfully unpublished client boot-strapper package "%1" with version "%2" to the Software Updates Point.%12</Description> </Message> <Message> <MessageID>6617</MessageID> <Description>WSUS Configuration Manager failed to unpublish client boot-strapper package "%1" from the Software Updates Point.%12</Description> </Message> <Message> <MessageID>6618</MessageID> <Description>WSUS Configuration Manager successfully unpublished client boot-strapper package "%1" to the Software Updates Point.%12</Description> </Message> <Message> <MessageID>6700</MessageID> <Description> SMS WSUS Sync Manager error. Message: %2. Source: %1. %12</Description> </Message> <Message> <MessageID>6701</MessageID> <Description> WSUS Synchronization started. %12</Description> </Message> <Message> <MessageID>6702</MessageID> <Description> WSUS Synchronization done. %12</Description> </Message> <Message> <MessageID>6703</MessageID> <Description> WSUS Synchronization failed. Message: %2. Source: %1. %12</Description> </Message> <Message> <MessageID>6704</MessageID> <Description> WSUS Synchronization in progress. Current phase: Synchronizing WSUS Server. %12</Description> </Message> <Message> <MessageID>6705</MessageID> <Description> WSUS Synchronization in progress. Current phase: Synchronizing site database. %12</Description> </Message> <Message> <MessageID>6706</MessageID> <Description> WSUS Synchronization in progress. Current phase: Synchronizing Internet facing WSUS Server. %12</Description> </Message> <Message> <MessageID>6707</MessageID> <Description>Content of WSUS Server %1 is out of sync with upstream server %2.%12</Description> </Message> <Message> <MessageID>6708</MessageID> <Description> WSUS synchronization complete, with pending license terms downloads. %12</Description> </Message> <Message> <MessageID>6800</MessageID> <Description>SMS Writer was unable to open control file "%1". Site backup will fail.%12</Description> </Message> <Message> <MessageID>6801</MessageID> <Description>SMS Writer stopped the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>6802</MessageID> <Description>SMS Writer could not stop the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>6803</MessageID> <Description>SMS Writer started the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>6804</MessageID> <Description>SMS Writer could not start the "%1" executable on the local computer.%12</Description> </Message> <Message> <MessageID>6805</MessageID> <Description>SMS Writer stopped the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>6806</MessageID> <Description>SMS Writer could not stop the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>6807</MessageID> <Description>SMS Writer started the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>6808</MessageID> <Description>SMS Writer could not start the %1 service on site system %2.%12</Description> </Message> <Message> <MessageID>6809</MessageID> <Description>SMS Writer stopped the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>6810</MessageID> <Description>The %1 ConfigMgr client application on the local computer did not respond to SMS Writer's stop request.%12</Description> </Message> <Message> <MessageID>6811</MessageID> <Description>SMS Writer could not stop the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>6812</MessageID> <Description>SMS Writer started the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>6813</MessageID> <Description>SMS Writer could not start the %1 ConfigMgr client application on the local computer.%12</Description> </Message> <Message> <MessageID>6814</MessageID> <Description>SMS Writer found syntax errors on the following lines:%1 in backup control file. Site backup will fail.%12</Description> </Message> <Message> <MessageID>6815</MessageID> <Description>The following utility tools were not available to be run: %1 Their output is not provided so you might miss some configuration information.%12</Description> </Message> <Message> <MessageID>6816</MessageID> <Description>Unable to verify the installation of the service : %1 This service will not be stopped or restarted.%12</Description> </Message> <Message> <MessageID>6817</MessageID> <Description>Maximum sleep time is 15 minutes. Time given in Backup Control File exceeds this limit so it is being reset to this maximum limit.%12</Description> </Message> <Message> <MessageID>6818</MessageID> <Description>Token Symbol (%1) already defined. First value (%2) will be used.%12</Description> </Message> <Message> <MessageID>6819</MessageID> <Description>SMS Writer was unable to locate the file system object %1.%12</Description> </Message> <Message> <MessageID>6820</MessageID> <Description>SMS Writer was unable to export the registry key %1 to %2.%12</Description> </Message> <Message> <MessageID>6821</MessageID> <Description>SMS Writer was unable to write the machine info to the temporary backup destination %1.%12</Description> </Message> <Message> <MessageID>6822</MessageID> <Description>SMS Writer tried to stop the %1 service on site system %2. This service is already stopped.%12</Description> </Message> <Message> <MessageID>6823</MessageID> <Description>SMS Writer tried to stop the %1 executable. This executable is already stopped.%12</Description> </Message> <Message> <MessageID>6824</MessageID> <Description>SMS Writer service was stopped manually. All the backup operations will be affected and cannot be completed.%12</Description> </Message> <Message> <MessageID>6825</MessageID> <Description>SMS Writer was unable to initialize the service.%12</Description> </Message> <Message> <MessageID>6826</MessageID> <Description>SMS Writer was unable to subscribe to the VSS services.%12</Description> </Message> <Message> <MessageID>6827</MessageID> <Description>SMS Writer failed to build the metadata. Site Backup tasks will fail.%12</Description> </Message> <Message> <MessageID>6828</MessageID> <Description>The backup application has not included all the required components in the backup list.%12</Description> </Message> <Message> <MessageID>6829</MessageID> <Description>SMS Writer is about to stop the ConfigMgr Services as part of the preparation for the Site backup.%12</Description> </Message> <Message> <MessageID>6830</MessageID> <Description>The snapshots of the volumes required for the Site Backup have been successfully created.%12</Description> </Message> <Message> <MessageID>6831</MessageID> <Description>SMS Writer has started the ConfigMgr Services successfully. %12</Description> </Message> <Message> <MessageID>6832</MessageID> <Description>Site Backup task has been aborted.%12</Description> </Message> <Message> <MessageID>6833</MessageID> <Description>Site Backup task has completed successfully.%12</Description> </Message> <Message> <MessageID>6900</MessageID> <Description>The Fallback Status Point failed to read and configure the registry keys necessary for this component.</Description> </Message> <Message> <MessageID>6901</MessageID> <Description>The Fallback Status Point can not authenticate the client %1.</Description> </Message> <Message> <MessageID>6902</MessageID> <Description>The Fallback Status Point can not process any more messages.</Description> </Message> <Message> <MessageID>6903</MessageID> <Description>The Fallback Status Point could not load valid topics from registry.</Description> </Message> <Message> <MessageID>6904</MessageID> <Description>The Fallback Status Point could not write messages to the staging folder.</Description> </Message> <Message> <MessageID>6905</MessageID> <Description>The Fallback Status Point could not transfer messages from the staging folder to the outbox.</Description> </Message> <Message> <MessageID>7000</MessageID> <Description>WSUS Control Manager failed to configure proxy settings on WSUS Server "%1".%12</Description> </Message> <Message> <MessageID>7001</MessageID> <Description>Failures were reported on WSUS Server "%1" for WSUS components "%2".%12</Description> </Message> <Message> <MessageID>7002</MessageID> <Description>Failures were reported on WSUS Server "%1" while trying to make WSUS database connection with SQL Server Exception error code %2.%12</Description> </Message> <Message> <MessageID>7003</MessageID> <Description>WSUS Control Manager failed to monitor WSUS Server "%1".%12</Description> </Message> <Message> <MessageID>7004</MessageID> <Description>WSUS Control Manager will not be able to configure WSUS Server "%1" as the WSUS Server of version 3.0 SP2 or greater is not installed on this site system.%12</Description> </Message> <Message> <MessageID>7100</MessageID> <Description>The Multicast Service Point failed to open multicast session.</Description> </Message> <Message> <MessageID>7101</MessageID> <Description>MCS Control Manager detected MCS is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>7102</MessageID> <Description>MCS Control Manager detected MCS is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>7103</MessageID> <Description>Multicast Service was unable to create a WDS multicast namaspace for package with UNC "%2" and packageID "%3". The error is %1.%12</Description> </Message> <Message> <MessageID>7104</MessageID> <Description>Multicast Service was unable to initialize multicast service. The error is %1.%12</Description> </Message> <Message> <MessageID>7105</MessageID> <Description>Multicast Service was unable to initialize multicast provider. The error is %1.%12</Description> </Message> <Message> <MessageID>7106</MessageID> <Description>Multicast Service was unable to initialize ISAPI. The error is %1.%12</Description> </Message> <Message> <MessageID>7107</MessageID> <Description>Multicast Service did not grant access to directory %2 for client with account %3. The error is %1.%12</Description> </Message> <Message> <MessageID>7108</MessageID> <Description>Multicast Service failed to read the SignedSerializedMCSKey from the registry on computer %1. Possible reasons are MCS certificate is not yet signed by Site Server. %12</Description> </Message> <Message> <MessageID>7109</MessageID> <Description>Multicast Service has rejected a request from %2 for site %3 because it is not approved.%12</Description> </Message> <Message> <MessageID>7110</MessageID> <Description>Multicast Service has rejected request from %2 because this SMSID is marked as blocked.%12</Description> </Message> <Message> <MessageID>7111</MessageID> <Description>Multicast Service has rejected the request because %2 certificate has expired.%12</Description> </Message> <Message> <MessageID>7112</MessageID> <Description>Multicast Service rejected a request because %2 signature is invalid.%12</Description> </Message> <Message> <MessageID>7150</MessageID> <Description>The Multicast Service failed to initialize properly. The error encountered was %1.</Description> </Message> <Message> <MessageID>7200</MessageID> <Description>The out of band service point failed to read notification registry.</Description> </Message> <Message> <MessageID>7201</MessageID> <Description>The out of band service point failed to initialize the inbox of %1. %</Description> </Message> <Message> <MessageID>7202</MessageID> <Description>The out of band service point is starting to send packets to completion port.</Description> </Message> <Message> <MessageID>7203</MessageID> <Description>The out of band service point completed sending %1 packet(s) to completion port. %2 packet(s) are in pending list. %3 packet(s) are failed to be sent to completion port.</Description> </Message> <Message> <MessageID>7204</MessageID> <Description>WinRM out of band service is not enabled.</Description> </Message> <Message> <MessageID>7205</MessageID> <Description>The port specified for incoming Hello packets is in use by another application.</Description> </Message> <Message> <MessageID>7206</MessageID> <Description>The out of band service point failed to provision %1 with error %2: %3.%12</Description> </Message> <Message> <MessageID>7207</MessageID> <Description>The out of band service point failed to %1 %2 with error %3.%12</Description> </Message> <Message> <MessageID>7208</MessageID> <Description>Provisioning failed because of an unsupported provisioning scenario. 12</Description> </Message> <Message> <MessageID>7209</MessageID> <Description>Provisioning for %1 %2 failed due to an improper or missing provisioning certificate.%12</Description> </Message> <Message> <MessageID>7210</MessageID> <Description>The provisioning certificate with the thumbprint %1 will expire in %2 day(s). Please ensure that this certificate is renewed.%12</Description> </Message> <Message> <MessageID>7211</MessageID> <Description>The provisioning certificate with the thumbprint %1 will expire in %2 day(s). Please ensure that this certificate is renewed.%12</Description> </Message> <Message> <MessageID>7212</MessageID> <Description>The out of band service point failed to provision %1 with error %2: %3.%12</Description> </Message> <Message> <MessageID>7213</MessageID> <Description>Provisioning for %1 %2 failed due to all accounts failed to authentication with target device.%12</Description> </Message> <Message> <MessageID>7214</MessageID> <Description>The provisioning certificate with the thumbprint %1 failed to pass revocation check with error %2.%12</Description> </Message> <Message> <MessageID>7215</MessageID> <Description>The provisioning certificate with the thumbprint %1 is invalid. Please ensure that CN name or OID is correct.</Description> </Message> <Message> <MessageID>7216</MessageID> <Description>The out of band service point failed to run %1 on %2 with error %3.%12</Description> </Message> <Message> <MessageID>7217</MessageID> <Description>The computer is configured to use IPv6 before IPv4. When out of band management uses IPv4 only, this configuration can negatively impact the performance of managing this computer out of band.</Description> </Message> <Message> <MessageID>7218</MessageID> <Description>The out of band service point failed to request a certificate by using the enrollment point.</Description> </Message> <Message> <MessageID>7219</MessageID> <Description>The out of band service point cannot connect to the enrollment point.</Description> </Message> <Message> <MessageID>7220</MessageID> <Description>The out of band service point can connect to the enrollment point.</Description> </Message> <Message> <MessageID>7300</MessageID> <Description>Asset Intelligence Update Service site role failed to install on "%1".%12</Description> </Message> <Message> <MessageID>7400</MessageID> <Description>Reporting Point site role failed to configure SQL Reporting Services on "%1".</Description> </Message> <Message> <MessageID>7401</MessageID> <Description>SQL Reporting Services install is invalid on "%1".</Description> </Message> <Message> <MessageID>7402</MessageID> <Description> Reporting Point failed to monitor SQL Reporting Services Server on "%1".</Description> </Message> <Message> <MessageID>7403</MessageID> <Description>The report server service is not running on Reporting Service Point server "%1"; start the service to enable reporting.</Description> </Message> <Message> <MessageID>7404</MessageID> <Description>SQL Reporting Services is not installed or properly configured on Reporting point server "%1".</Description> </Message> <Message> <MessageID>7405</MessageID> <Description>SQL Reporting Services root folder "%1" is not present or not properly configured on the Reporting point server "%2".</Description> </Message> <Message> <MessageID>7406</MessageID> <Description>The SQL Reporting Services datasource on Reporting point server "%1" is missing or has been changed outside of Configuration Manager. It will be rebuilt based on the RSP configuration.</Description> </Message> <Message> <MessageID>7502</MessageID> <Description>Asset Intelligence KB Manager encountered errors processing file %1 from online service. This file and subsequent data will be deleted, subsequent sync will bring the data again.</Description> </Message> <Message> <MessageID>7600</MessageID> <Description>Failure: The AMT Proxy Manager failed to apply certificate for "%1" from CA at "%2" with error CR_DISP_DENIED: (CERTSRV_E_ENROLL_DENIED(0x80094011L) : The permissions on this certification authority do not allow the current user to enroll for certificates.)%12</Description> </Message> <Message> <MessageID>7601</MessageID> <Description>Failure: The AMT Proxy Manager failed to apply certificate for "%1" from CA at "%2" with certificate trust error.%12</Description> </Message> <Message> <MessageID>7602</MessageID> <Description>Failure: The AMT Proxy Manager failed to add a object into AD. FQDN: %1, ADDN: %2, UUID: %3, AMT Version: %4.%12</Description> </Message> <Message> <MessageID>7603</MessageID> <Description>Failure: The AMT Proxy Manager failed to remove a object into AD. FQDN: %1, ADDN: %2.%12</Description> </Message> <Message> <MessageID>7604</MessageID> <Description>Failure: The AMT Proxy Manager failed to update a object in the AD. FQDN: %1, ADDN: %2.%12</Description> </Message> <Message> <MessageID>7605</MessageID> <Description>Warning: The AMT Proxy Manager failed to apply certificate for "%1" from CA at "%2" with certificate request pending.%12 Please wait for a certification authority administrator to issue the certificate and the AMT Proxy Manager will retrieve it.</Description> </Message> <Message> <MessageID>7606</MessageID> <Description>The out of band service point failed to register the %1 in DNS. The machine's FQDN is %2.%12</Description> </Message> <Message> <MessageID>7607</MessageID> <Description>The out of band service point failed to unregister the %1 in DNS.%12</Description> </Message> <Message> <MessageID>7608</MessageID> <Description>The AMT Proxy Manager failed to replicate file %1 to out of band service point for the %2 time. The file will be re-send again later.</Description> </Message> <Message> <MessageID>7609</MessageID> <Description>The AMT Proxy Manager failed %2 times while replicating file %1 to out of band service point. The file has been moved to the BAD file inbox.</Description> </Message> <Message> <MessageID>7700</MessageID> <Description>The Client Health Manager failed to read and configure the registry keys necessary for this component.%12</Description> </Message> <Message> <MessageID>7800</MessageID> <Description>The RCM Control failed to read and configure the registry keys necessary for this component.%12</Description> </Message> <Message> <MessageID>7801</MessageID> <Description>Site %1 is requesting initialization for replication group %2 from site %3.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7802</MessageID> <Description>Received initialization request from Site %1 for replication group "%2".</Description> </Message> <Message> <MessageID>7803</MessageID> <Description>Snapshot for replication group "%1" for Site %2 created successfully.</Description> </Message> <Message> <MessageID>7804</MessageID> <Description>Failed to create snapshot for replication group "%1" for Site %2.%12 Error: %3 %12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7805</MessageID> <Description>Snapshot for replication group "%1" from Site %2 applied successfully.</Description> </Message> <Message> <MessageID>7806</MessageID> <Description>Snapshot for replication group "%1" from Site %2 failed to be applied successfully.%12 Error: %3 %12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7809</MessageID> <Description>The replication status for this site has changed from "%1" to "%2".</Description> </Message> <Message> <MessageID>7810</MessageID> <Description>Site %1 is ready for replication.</Description> </Message> <Message> <MessageID>7811</MessageID> <Description>A transmission error has been detected for messages going to site %1.%12 Error: %2.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7812</MessageID> <Description>The queue %1 for site %2 is currently disabled.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7815</MessageID> <Description>Unable to determine link status for site %1 at this time. Setting link status to site %1 to unknown.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7816</MessageID> <Description>The link status to site %1 is degraded at this time.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7817</MessageID> <Description>The replication system has experienced an error and is attempting to recover. All synchronizations are currently stopped.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7818</MessageID> <Description>The replication system has experienced an unrecoverable error and all synchronizations are currently stopped.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7819</MessageID> <Description>The replication system has recovered and is synchronizing with other sites again.</Description> </Message> <Message> <MessageID>7820</MessageID> <Description>This site is now in maintenance mode. Replication has been stopped until maintenance is complete.</Description> </Message> <Message> <MessageID>7821</MessageID> <Description>Maintenance is complete and replication has restarted.</Description> </Message> <Message> <MessageID>7822</MessageID> <Description>The link status to site %1 is failed at this time.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7825</MessageID> <Description>Site %1 is detaching.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7826</MessageID> <Description>Site %1 has failed to detach.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7827</MessageID> <Description>Site %1 has successfully detached.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7828</MessageID> <Description>The link status to site %1 has changed to active.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7829</MessageID> <Description>The link status to site %1 is in an error state at this time.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7830</MessageID> <Description>Detected Service Broker is not enabled on site %1. To fix this, put the database in single user mode and execute 'ALTER DATABASE [%2] SET ENABLE_BROKER'.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7831</MessageID> <Description>On site %1, found service broker queue %2 disabled. It has been enabled now.%12 Refer to the SQL view vLogs for more information.</Description> </Message> <Message> <MessageID>7832</MessageID> <Description>An unhandled exception has occurred - %1.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7833</MessageID> <Description>When RCM creates the linked server for %1, an exception has occurred - %2.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7834</MessageID> <Description>When RCM drops the linked server for %1, an exception has occurred - %2.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7835</MessageID> <Description>When RCM configures dview for table table %1, an exception has occurred - %2.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7836</MessageID> <Description>When RCM renames table %1 to %2_RCM for dview, an exception has occurred - %3.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7837</MessageID> <Description>When RCM tries to clean old replicated data on table %1 for dview, an exception has occurred - %2.%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7838</MessageID> <Description>RCM has successfully configured dview on CAS for replicationgroup [%1].%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7839</MessageID> <Description>RCM is currently configuring dview on CAS for replicationgroup [%1].%12 Refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7840</MessageID> <Description>RCM received resync request for replicationgroup [%1] to version %2.Please refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7841</MessageID> <Description>RCM has finished processing resync for replicationgroup [%1] to version %2.Please refer to rcmctrl.log for further details.</Description> </Message> <Message> <MessageID>7900</MessageID> <Description>Offline Image Servicing Manager started processing of schedule with ID %1 and name %2.</Description> </Message> <Message> <MessageID>7901</MessageID> <Description>Offline Image Servicing Manager completed processing of schedule with ID %1 and name %2.</Description> </Message> <Message> <MessageID>7902</MessageID> <Description>Offline Image Servicing Manager cancelled processing of schedule with ID %1 and Name %2.</Description> </Message> <Message> <MessageID>7903</MessageID> <Description>Offline Image Servicing Manager started copying image with ID %1 from image package source to local staging folder.</Description> </Message> <Message> <MessageID>7904</MessageID> <Description>Offline Image Servicing Manager started copying updated image with ID %1 from staging folder to the image package folder.</Description> </Message> <Message> <MessageID>7905</MessageID> <Description>Offline Image Servicing Manager completed copying image with ID %1.</Description> </Message> <Message> <MessageID>7906</MessageID> <Description>Offline Image Servicing Manager started applying updates on image with ID %1.</Description> </Message> <Message> <MessageID>7907</MessageID> <Description>Offline Image Servicing Manager completed installing updates on image with ID %1.</Description> </Message> <Message> <MessageID>7908</MessageID> <Description>Offline Image Servicing Manager successfully installed update with ID %1 on image with ID %2 (image index %3).</Description> </Message> <Message> <MessageID>7909</MessageID> <Description>Offline Image Servicing Manager determined that update with ID %1 is not required on image with ID %2 (image index %3).</Description> </Message> <Message> <MessageID>7910</MessageID> <Description>Offline Image Servicing Manager failed to process schedule with ID %1 and name %2.</Description> </Message> <Message> <MessageID>7911</MessageID> <Description>Offline Image Servicing Manager failed to apply update with ID %1 on image with ID %2 (image index %3).</Description> </Message> <Message> <MessageID>7912</MessageID> <Description>Offline Image Servicing Manager failed to mount image with ID %1 (image index %2) to mount directory %3. Error : %4.</Description> </Message> <Message> <MessageID>7913</MessageID> <Description>Offline Image Servicing Manager failed to unmount image with ID %1 (image index %2) from mount directory %3. Error : %4.</Description> </Message> <Message> <MessageID>7914</MessageID> <Description>Offline Image Servicing Manager failed because there is not enough free disk space left on the staging drive %1. Required disk Space = %2 MB, available free disk space = %3 MB.</Description> </Message> <Message> <MessageID>7915</MessageID> <Description>Offline Image Servicing Manager cannot write to the image package source location for the image with ID %1. Please make sure that the image package source folder can be written to.</Description> </Message> <Message> <MessageID>7916</MessageID> <Description>Offline Image Servicing Manager does not support image with ID %1 (image index %2) and therefore will not process this image.</Description> </Message> <Message> <MessageID>7917</MessageID> <Description>Offline Image Servicing Manager could not determine if binary %1 from an update with ID %2 is supported.</Description> </Message> <Message> <MessageID>7918</MessageID> <Description>Offline Image Servicing Manager: applicability check failed for binary %1 from an update with ID %2.</Description> </Message> <Message> <MessageID>7919</MessageID> <Description>Offline Image Servicing Manager failed to apply one or more updates on image with package ID %1 (image index %2), but continued offline servicing of the image on error per selected by user option.</Description> </Message> <Message> <MessageID>8000</MessageID> <Description>Portal Web Site Control Manager detected PORTALWEB is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>8001</MessageID> <Description>Portal Web Site Control Manager detected PORTALWEB is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>8002</MessageID> <Description>Portal Web Site Control Manager detected PORTALWEB is responding to HTTP requests.</Description> </Message> <Message> <MessageID>8003</MessageID> <Description>Portal Web Site Control Manager detected PORTALWEB is not able to save the Web.config.</Description> </Message> <Message> <MessageID>8004</MessageID> <Description>Portal Web Site Control Manager detected PORTALWEB can update the Web.config file.</Description> </Message> <Message> <MessageID>8005</MessageID> <Description>The application catalog website role did not find an SSL certificate required to communicate with the application catalog web service role.</Description> </Message> <Message> <MessageID>8100</MessageID> <Description>Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>8101</MessageID> <Description>Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>8102</MessageID> <Description>Application Web Service Control Manager detected AWEBSVC is responding to HTTP requests.</Description> </Message> <Message> <MessageID>8103</MessageID> <Description>Application Web Service Control Manager detected AWEBSVC is not able to save the Web.config.</Description> </Message> <Message> <MessageID>8104</MessageID> <Description>Application Web Service Control Manager detected AWEBSVC can update the Web.config file.</Description> </Message> <Message> <MessageID>8200</MessageID> <Description>Package Transfer Manager has successfully sent software distribution package "%1" version %2 to distibution point "%3".</Description> </Message> <Message> <MessageID>8201</MessageID> <Description>The address to distribution point server "%1" is invalid.%12</Description> </Message> <Message> <MessageID>8202</MessageID> <Description>The Package Transfer Manager cannot connect to distribution point server "%1" over the LAN.%12</Description> </Message> <Message> <MessageID>8203</MessageID> <Description>The Package Transfer Manager failed to send files to destination server "%1". Make sure the site server machine account or the site system connection account has full access to directory "%2" on the destination site server and the destination site server has sufficient free disk space.%12</Description> </Message> <Message> <MessageID>8204</MessageID> <Description>Package Transfer Manager is currently sending software distribution package %1 to distribution point server %2, %3 percent of the sending has already completed.</Description> </Message> <Message> <MessageID>8205</MessageID> <Description>Package Transfer Manager encountered errors while sending software distribution package %1 to distribution point server %2, %3 percent of the sending has already completed.</Description> </Message> <Message> <MessageID>8206</MessageID> <Description>Package Transfer Manager is retrying to distribute package "%1" to distribution point %2.%12 Wait to see if the package is successfully distributed on the retry.</Description> </Message> <Message> <MessageID>8207</MessageID> <Description>Package Transfer Manager has failed to distribute package "%1" to distribution point %2.%12 Please try to distribute the package again to this distribution point server.</Description> </Message> <Message> <MessageID>8208</MessageID> <Description>Package Transfer Manager has failed to verify hash for package "%1", Version %2 on distribution point %3.%12 Please try to distribute the package again to this distribution point server. If this package has been marked for prestaging on the distribution points then make sure the package has been correctly copied to the appropriate package folder on the distribution point server.</Description> </Message> <Message> <MessageID>8209</MessageID> <Description>Package Transfer Manager has successfully verified that the package "%1", Version %2 has been prestaged on distribution point %3.</Description> </Message> <Message> <MessageID>8210</MessageID> <Description>Package Transfer Manager has successfully updated the package "%1", Version %2 on distribution point %3.</Description> </Message> <Message> <MessageID>8211</MessageID> <Description>Package Transfer Manager failed to update the package "%1", Version %2 on distribution point %3. Review PkgXferMgr.log for more information about this failure.</Description> </Message> <Message> <MessageID>8212</MessageID> <Description>Package Transfer Manager failed to update the package "%1", Version %2 on pull distribution point %3. This pull distribution point has no sources from which it can download content. We will try again later.</Description> </Message> <Message> <MessageID>8300</MessageID> <Description>Enrollment Point Control Manager detected that the Enrollment Point is not responding to HTTP/HTTPS requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>8301</MessageID> <Description>Enrollment Point Control Manager detected Enrollment Point is not responding to HTTP/HTTPS requests. The http status code is %1.%12</Description> </Message> <Message> <MessageID>8302</MessageID> <Description>Enrollment Server is starting....</Description> </Message> <Message> <MessageID>8303</MessageID> <Description>Enrollment Point fails to connect to SQL server.%12</Description> </Message> <Message> <MessageID>8304</MessageID> <Description>Enrollment Point cannot accomplish tasks on the CA.%12</Description> </Message> <Message> <MessageID>8306</MessageID> <Description>ConfigMgr server cannot accomplish tasks in Active Directory.%12</Description> </Message> <Message> <MessageID>8307</MessageID> <Description>The Enrollment Point failed to revoke the certificate (Cert Serial Number: %1) issued to the device/requester %2 on the Certification Authority %3.%12</Description> </Message> <Message> <MessageID>8400</MessageID> <Description>Enrollment Point AD Service Control failed to read and configure the registry keys necessary for this component.%12</Description> </Message> <Message> <MessageID>8500</MessageID> <Description>Enrollment Proxy Point Control Manager detected that the Enrollment Proxy Point Component is not responding to HTTP/HTTPS requests. The http status code and text is %1, %2.%12</Description> </Message> <Message> <MessageID>8501</MessageID> <Description>Enrollment Proxy Point Control Manager detected that the Enrollment Proxy Point Component is not responding to HTTP/HTTPS requests. The http error is %1.%12</Description> </Message> <Message> <MessageID>8502</MessageID> <Description>Enrollment Proxy Point is starting....</Description> </Message> <Message> <MessageID>8600</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" was able to connect and authenticate successfully to Configuration Manager 2007 site server "%2".</Description> </Message> <Message> <MessageID>8601</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" was unable to connect to Configuration Manager 2007 site server "%2" due to network connection time out. Check the network connection and the firewall configuration between the two servers.</Description> </Message> <Message> <MessageID>8602</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" was unable to connect to Configuration Manager 2007 site server "%2" due to insufficient permissions. Ensure the account specified for the specified source Configuration Manager site is part of the local "SMS Admins" security group and has been granted full permissions to Configuration Manager 2007 site.</Description> </Message> <Message> <MessageID>8603</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" detected the specified site "%2" is not a valid Configuration Manager 2007 top-level site or stand-alone primary site. Please specify the fully qualified domain name of a Configuration Manager 2007 top-level site or stand-alone primary site as the source hierarchy.</Description> </Message> <Message> <MessageID>8604</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" has the same site code as the specified site "%2". Configuration Manager cannot migrate from sites with the same sitecode. Ensure the site codes are unique across both your Configuration Manager 2007 hierarchy and Configuration Manager 2012 hierarchy.</Description> </Message> <Message> <MessageID>8605</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" finished the data gathering process with Configuration Manager 2007 site server "%2".</Description> </Message> <Message> <MessageID>8606</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" started the migration job "%2 (%3)" to migrate "%4" objects from the source hierarchy.</Description> </Message> <Message> <MessageID>8607</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" stopped the migration job "%2 (%3)" per manual request through SDK or Console.</Description> </Message> <Message> <MessageID>8608</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" finished the migration job "%2 (%3)".</Description> </Message> <Message> <MessageID>8609</MessageID> <Description>The source hierarchy "%1" specified is not a valid Configuration Manager 2007 top-level site or stand-alone primary site.</Description> </Message> <Message> <MessageID>8610</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" was unable to complete the SQL operation on the SQL Server "%2" of Configuration Manager 2007 due to error "%3".</Description> </Message> <Message> <MessageID>8611</MessageID> <Description>The value "%1" configured for the parameter "%2" of Migration Manager is invalid.</Description> </Message> <Message> <MessageID>8612</MessageID> <Description>The migration job "%1" failed to copy content for some packages due to error "%2".</Description> </Message> <Message> <MessageID>8613</MessageID> <Description>Object %1 with path %2 have failed to migrate as part of migration job %3 (%4) which ran on site server %5 with error %6.</Description> </Message> <Message> <MessageID>8614</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" encountered a SQL query timeout. Please consider increasing the timeout value for the Migraton Manager by configuring the registry.</Description> </Message> <Message> <MessageID>8615</MessageID> <Description>The object "%1" being migrated is missing a dependency "%2". Confirm the configuration of the object "%1" in the Configuration Manager 2007 environment and initiate the "Gather Data Now" action in the console and recreate the migration job.</Description> </Message> <Message> <MessageID>8616</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" gathered from Configuration Manager 2007 site server "%3" "%2" new source sites.</Description> </Message> <Message> <MessageID>8617</MessageID> <Description>An unexpected error occurred in the Migration Manager on Configuration Manager site server "%1". Please refer to the migmctrl.log file for details.</Description> </Message> <Message> <MessageID>8618</MessageID> <Description>The Migration Manager on Configuration Manager site server "%1" encountered an error "%2" while performing SQL operations. Please refer to the migmctrl.log file for details.</Description> </Message> <Message> <MessageID>8619</MessageID> <Description>Updates Assignment "%1" includes Update "%2" (BulletinID "%3", ArticleID "%4", CI_ID "%5") which is not available on the destination site. Please ensure updates have been synchronized at the destination, or remove this Update from the Updates Assignment.</Description> </Message> <Message> <MessageID>8620</MessageID> <Description>The data gathering agent configuration type "%1" is not recognized.</Description> </Message> <Message> <MessageID>8621</MessageID> <Description>When connecting to "%1", the migration data gathering process encountered a source site code ("%2") already being used for mapping "%3" to "%4" (%5).</Description> </Message> <Message> <MessageID>8622</MessageID> <Description>The CI "%1" was made applicable to all platforms during migration.</Description> </Message> <Message> <MessageID>8623</MessageID> <Description>The CI "%1" is not applicable to any platforms after migration.</Description> </Message> <Message> <MessageID>8700</MessageID> <Description> SMS Rule Engine error. Message: %2. Source: %1. %12</Description> </Message> <Message> <MessageID>8701</MessageID> <Description> Rule Evaluation started. %12</Description> </Message> <Message> <MessageID>8702</MessageID> <Description> Rule Evaluation completed. %12</Description> </Message> <Message> <MessageID>8703</MessageID> <Description> Rule Evaluation failed. Message: %2. Source: %1. %12</Description> </Message> <Message> <MessageID>8704</MessageID> <Description> Content download started. %12</Description> </Message> <Message> <MessageID>8705</MessageID> <Description> Content download completed. %12</Description> </Message> <Message> <MessageID>8706</MessageID> <Description> Content download failed. Message: %2. Source: %1. %12</Description> </Message> <Message> <MessageID>8707</MessageID> <Description> Update group creation failed. Message: %2. Source: %1. %12</Description> </Message> <Message> <MessageID>8708</MessageID> <Description> Deployment creation failed. Message: %2. Source: %1. %12</Description> </Message> <Message> <MessageID>8800</MessageID> <Description>Connection to Exchange server %1 failed. Message: %2. %12</Description> </Message> <Message> <MessageID>8801</MessageID> <Description>Connection to Exchange server %1 failed.</Description> </Message> <Message> <MessageID>8802</MessageID> <Description>Connection to Exchange server %1 failed.</Description> </Message> <Message> <MessageID>8803</MessageID> <Description>Connection to Exchange server %1 failed.</Description> </Message> <Message> <MessageID>8810</MessageID> <Description>PowerShell 2.0 is not installed which is required by Exchange Connector component.</Description> </Message> <Message> <MessageID>8811</MessageID> <Description>Configuration is corrupted for %1.</Description> </Message> <Message> <MessageID>8812</MessageID> <Description>Policy setting %1 is invalid.</Description> </Message> <Message> <MessageID>8813</MessageID> <Description>Configured setting name %1 is invalid.</Description> </Message> <Message> <MessageID>8814</MessageID> <Description>Ignore configured on-premise Exchange server %1. The Exchange organization %2 for this server has already been configured on site %3 as server %4. %12</Description> </Message> <Message> <MessageID>8815</MessageID> <Description>Ignore configured hosted Exchange server %1. The Exchange organization %2 for this server has already been configured on site %3 as server %4 with credential %5. %12</Description> </Message> <Message> <MessageID>8816</MessageID> <Description>No default policy for Exchange server %1.</Description> </Message> <Message> <MessageID>8817</MessageID> <Description>Exchange cmdlet call failed. Cmdlet %1. ErrorId: %2 Message: %3 %12</Description> </Message> <Message> <MessageID>8818</MessageID> <Description>Exchange cmdlet %1 is not found.</Description> </Message> <Message> <MessageID>8819</MessageID> <Description>Exchange ActiveSync device %1 is not found in Exchange server %2.</Description> </Message> <Message> <MessageID>8831</MessageID> <Description>Connected to Exchange Server %1. Start full synchronization. %12</Description> </Message> <Message> <MessageID>8832</MessageID> <Description>Successfully ran the full synchronization on Exchange Server %1. %2 mobile devices has been discovered. %12</Description> </Message> <Message> <MessageID>8833</MessageID> <Description>Successfully ran the delta synchronization on Exchange Server %1. %2 mobile devices are updated. %12</Description> </Message> <Message> <MessageID>8834</MessageID> <Description>Global mobile device setting has been successfully synchronized to Exchange Server %1. %12</Description> </Message> <Message> <MessageID>8835</MessageID> <Description>Successfully send wipe request of the device %1 to Exchange Server %2. Waiting for the wipe confirmation. %12</Description> </Message> <Message> <MessageID>8836</MessageID> <Description>Received the wipe confirmation of the device %1. The device has been successfully wiped. %12</Description> </Message> <Message> <MessageID>8837</MessageID> <Description>Connected to Exchange Server %1. Start delta synchronization. %12</Description> </Message> <Message> <MessageID>8838</MessageID> <Description>Allow access request for Device %1 has been successfully sent to Exchange Server %2. %12</Description> </Message> <Message> <MessageID>8839</MessageID> <Description>Block access request for Device %1 has been successfully sent to Exchange Server %2. %12</Description> </Message> <Message> <MessageID>8840</MessageID> <Description>Organization DefaultAccessLevel and AdminEmailRecipients has been successfully synchronized to Exchange Server %1. %12</Description> </Message> <Message> <MessageID>8841</MessageID> <Description>Exchange ActiveSync access rule %1 has been successfully created on Exchange Server %2. %12</Description> </Message> <Message> <MessageID>8842</MessageID> <Description>Exchange ActiveSync access rule %1 has been successfully removed from Exchange Server %2. %12</Description> </Message> <Message> <MessageID>8900</MessageID> <Description>Active Directory Forest Discovery was run for forest %1 and discovered %5 IP subnets and %6 Active Directory sites.</Description> </Message> <Message> <MessageID>8901</MessageID> <Description>Active Directory Forest Discovery was run for forest %1 and it could not complete. The error code returned was %5.</Description> </Message> <Message> <MessageID>8902</MessageID> <Description>Active Directory Forest Discovery was not able to connect to Site Server database. Please see ADForestDisc.log for details. Active Directory Forest Discovery will be attempted on next cycle.</Description> </Message> <Message> <MessageID>8903</MessageID> <Description>Active Directory Forest Discovery was not able to use credentials supplied for account %5 to discover forest %1. Please check if credentials supplied to discovery the forest are valid.</Description> </Message> <Message> <MessageID>8904</MessageID> <Description>Active Directory Forest Discovery was not able to connect to forest %1. Error code returned is: %5. Forest discovery for this forest will be attempted again on next cycle.</Description> </Message> <Message> <MessageID>9100</MessageID> <Description>Alert notification sent notification email for Alert (ID:%1) successfully. %12</Description> </Message> <Message> <MessageID>9101</MessageID> <Description>Alert notification sent notification email failed for Alert (ID:%1), please check the email addresses of the sender(%2) and recipients(%3). %12</Description> </Message> <Message> <MessageID>9102</MessageID> <Description>Alert notification sent notification email failed for Alert (ID:%1), the email could not be delivered to recipients(%2). %12</Description> </Message> <Message> <MessageID>9103</MessageID> <Description>Alert notification sent notification email failed for Alert (ID:%1), an SMTP exception occured. %12</Description> </Message> <Message> <MessageID>9104</MessageID> <Description>Alert notification failed to initialize the SMTP client, please check the credential of user "%1". %12</Description> </Message> <Message> <MessageID>9200</MessageID> <Description>Endpoint Protection Control Manager failed to update malware definition. Verify that the Endpoint Protection client is installed and running on the Endpoint Protection role server. Verify that the Endpoint Protection client on the role server can receive updated definitions. Error code returned is:"%1". %12</Description> </Message> <Message> <MessageID>9201</MessageID> <Description>Endpoint Protection Manager failed to generate malware detection alerts for type:"%1". Verify that the site database is configured correctly. Error code returned is:"%2". %12</Description> </Message> <Message> <MessageID>9300</MessageID> <Description>Cloud Content Manager encountered an internal error [%1] Check logs for details.</Description> </Message> <Message> <MessageID>9301</MessageID> <Description>Cloud Content Manager was unable to encrypt content for the package %1.</Description> </Message> <Message> <MessageID>9302</MessageID> <Description>Cloud Content Manager was unable to connect to the service %1.</Description> </Message> <Message> <MessageID>9303</MessageID> <Description>Cloud Content Manager was unable to determine the upload location for the package %1.</Description> </Message> <Message> <MessageID>9304</MessageID> <Description>Cloud Content Manager was unable to find the content source [%1] for package %2.</Description> </Message> <Message> <MessageID>9305</MessageID> <Description>Cloud Content Manager was unable to encrypt the file %1.</Description> </Message> <Message> <MessageID>9306</MessageID> <Description>Cloud Content Manager was unable to access the storage account for %1.</Description> </Message> <Message> <MessageID>9307</MessageID> <Description>Cloud Content Manager was unable to get content key for content %1.</Description> </Message> <Message> <MessageID>9308</MessageID> <Description>Cloud Content Manager encountered blank content XML for %1.</Description> </Message> <Message> <MessageID>9309</MessageID> <Description>Cloud Content Manager was unable to mark the upload status as completed for %1.</Description> </Message> <Message> <MessageID>9310</MessageID> <Description>Cloud Content Manager encountered an empty download address from content upload for package %1.</Description> </Message> <Message> <MessageID>9311</MessageID> <Description>Cloud Content Manager was unable to connect to the cloud distribution point service when trying to distribute package %1.</Description> </Message> <Message> <MessageID>9400</MessageID> <Description>Cloud Services Manager encountered an internal error, %1.</Description> </Message> <Message> <MessageID>9401</MessageID> <Description>Cloud Services Manager task [%1] has failed, exception %2.</Description> </Message> <Message> <MessageID>9402</MessageID> <Description>Cloud Services Manager task [%1] has been canceled.</Description> </Message> <Message> <MessageID>9403</MessageID> <Description>Cloud Services Manager created service %1 in region %2.</Description> </Message> <Message> <MessageID>9404</MessageID> <Description>Cloud Services Manager created a deployment for service %1 in region %2.</Description> </Message> <Message> <MessageID>9405</MessageID> <Description>Cloud Services Manager has started provisioning service %1 in region %2.</Description> </Message> <Message> <MessageID>9406</MessageID> <Description>Cloud Services Manager has configured storage account %1 for service %2.</Description> </Message> <Message> <MessageID>9407</MessageID> <Description>Cloud Services Manager has uploaded the service package for service %1 to %2.</Description> </Message> <Message> <MessageID>9408</MessageID> <Description>Service %1 in region %2 is ready for use.</Description> </Message> <Message> <MessageID>9409</MessageID> <Description>Cloud Services Manager has successfully provisioned service %1 in region %2.</Description> </Message> <Message> <MessageID>9410</MessageID> <Description>Cloud Services Manager failed to provision service %1 in region %2. Please see cloudmgr.log for more details.</Description> </Message> <Message> <MessageID>9411</MessageID> <Description>Cloud Services Manager is unable to connect to Windows Azure for subscription Id %1. Please check your proxy configuration.</Description> </Message> <Message> <MessageID>9412</MessageID> <Description>Cloud Services Manager is starting to uninstall service %1.</Description> </Message> <Message> <MessageID>9413</MessageID> <Description>Cloud Services Manager has completed the uninstall for service %1.</Description> </Message> <Message> <MessageID>9414</MessageID> <Description>Cloud Services Manager has failed to uninstall service %1. Please delete the deployment using the Windows Azure portal.</Description> </Message> <Message> <MessageID>9415</MessageID> <Description>Cloud Services Manager has failed to authenticate for subscription Id %1. Please check that the management certificate is property configured.</Description> </Message> <Message> <MessageID>9416</MessageID> <Description>Cloud Services Manager has started maintenance for service %1.</Description> </Message> <Message> <MessageID>9417</MessageID> <Description>Cloud Services Manager has completed maintenance for service %1.</Description> </Message> <Message> <MessageID>9418</MessageID> <Description>Cloud Services Manager has failed to complete maintenance for service %1.</Description> </Message> <Message> <MessageID>9419</MessageID> <Description>Cloud Services Manager has requested the deployment to start for service %1.</Description> </Message> <Message> <MessageID>9420</MessageID> <Description>Cloud Services Manager has started the deployment for service %1.</Description> </Message> <Message> <MessageID>9421</MessageID> <Description>Cloud Services Manager has failed to start the deployment for service %1. Exception %2.</Description> </Message> <Message> <MessageID>9422</MessageID> <Description>Cloud Services Manager has requested the deployment to stop for service %1.</Description> </Message> <Message> <MessageID>9423</MessageID> <Description>Cloud Services Manager has stopped the deployment for service %1.</Description> </Message> <Message> <MessageID>9424</MessageID> <Description>Cloud Services Manager has failed to stop the deployment for service %1. Exception %2.</Description> </Message> <Message> <MessageID>9425</MessageID> <Description>The %1 certificate was invalid for cloud service %2. Please check CloudMgr.log for further details.</Description> </Message> <Message> <MessageID>9426</MessageID> <Description>Service Monitor could not find service %1. Please check the status of the service through the azure portal.</Description> </Message> <Message> <MessageID>9427</MessageID> <Description>Service Monitor found that the Deployment %1 is in %2 state. Expected state is 'Running'. Please check the status of the deployment through the azure portal.</Description> </Message> <Message> <MessageID>9428</MessageID> <Description>Service Monitor could not find the Deployment %1. Please check the status of the deployment through the azure portal.</Description> </Message> <Message> <MessageID>9429</MessageID> <Description>Service Monitor received exception while monitoring service %1. Please check CloudMgr.log for further details. Exception: %2.</Description> </Message> <Message> <MessageID>9430</MessageID> <Description>Service Monitor found the deployment in running state for service %1.</Description> </Message> <Message> <MessageID>9431</MessageID> <Description>Storage account was not found for service %1.</Description> </Message> <Message> <MessageID>9500</MessageID> <Description>PXE is enabled on distribution point %1</Description> </Message> <Message> <MessageID>9501</MessageID> <Description>PXE is disabled on distribution point %1</Description> </Message> <Message> <MessageID>9502</MessageID> <Description>Multicast is enabled on distribution point %1</Description> </Message> <Message> <MessageID>9503</MessageID> <Description>Multicast is disabled on distribution point %1</Description> </Message> <Message> <MessageID>9504</MessageID> <Description>Distribution Point un-installation successfully completed on server "%1".</Description> </Message> <Message> <MessageID>9505</MessageID> <Description>Distribution Point un-installation failed to complete on server "%1".</Description> </Message> <Message> <MessageID>9506</MessageID> <Description>Package distribution cancelled by user for package "%1" on distribution point "%2".</Description> </Message> <Message> <MessageID>9507</MessageID> <Description>Pull Distribution Point "%1" started downloading package "%2".</Description> </Message> <Message> <MessageID>9508</MessageID> <Description>Pull Distribution Point "%1" is currently downloading package "%2". %3 percent download has completed.</Description> </Message> <Message> <MessageID>9509</MessageID> <Description>Pull Distribution Point "%1" completed downloading package "%2" and is now performing post download actions.</Description> </Message> <Message> <MessageID>9510</MessageID> <Description>Distribution Manager is sending package "%1" to connector on "%2".%12</Description> </Message> <Message> <MessageID>9511</MessageID> <Description>Distribution Manager failed to send package "%1" to connector on "%2".%12</Description> </Message> <Message> <MessageID>9512</MessageID> <Description>Distribution Manager sent package "%1" to connector on "%2".%12</Description> </Message> <Message> <MessageID>9513</MessageID> <Description>Connector is unable to upload version %1 of package "%2" to Windows Intune because a newer version of the package exists. %12</Description> </Message> <Message> <MessageID>9514</MessageID> <Description>The hash of package "%1" is invalid on connector "%2". Please redistribute the package.</Description> </Message> <Message> <MessageID>9515</MessageID> <Description>Successfully validated the content of package "%1" on connector "%2".</Description> </Message> <Message> <MessageID>9516</MessageID> <Description>Started uploading package "%1" to Windows Azure Intune from connector "%2".</Description> </Message> <Message> <MessageID>9517</MessageID> <Description>Failed to validate package "%1" on package share on distribution point "%2".</Description> </Message> <Message> <MessageID>9518</MessageID> <Description>The hash of package "%1" on package share on distribution point "%2", is invalid. Please redistribute it.</Description> </Message> <Message> <MessageID>9519</MessageID> <Description>The package "%1" was processed successfully, but was not copied to the Windows Intune distribution point. To be copied to the Windows Intune distribution point, the package must contain a deployment type that is supported by devices that are enrolled by Windows Intune which include Windows RT, Windows Phone 8, Android, or iOS.</Description> </Message> <Message> <MessageID>9600</MessageID> <Description>Failed to initialize. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9601</MessageID> <Description>Site has finished processing resync request for replicationgroup [%1]. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9602</MessageID> <Description>Received drs_syncstart message for replicationgroup [%1], however it is pending resync. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9603</MessageID> <Description>Received resync request for replicationgroup [%1] to version %2. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9604</MessageID> <Description>StartUpload replicationgroup [%1] last sync version %2 failed with status code %3 and error code %4. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9605</MessageID> <Description>Upload transmission [%1] blockID %2 failed with status code %3 and error code %4. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9606</MessageID> <Description>EndUpload transmission [%1] blockID %2 failed with status code %3 and error code %4. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9607</MessageID> <Description>Failed to upload. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9608</MessageID> <Description>Site has finished uploading. Please refer to dmpuploader.log for further details.</Description> </Message> <Message> <MessageID>9700</MessageID> <Description>Failed to initialize. Please refer to dmpdownloader.log for further details.</Description> </Message> <Message> <MessageID>9701</MessageID> <Description>Failed to download. Please refer to dmpdownloader.log for further details.</Description> </Message> <Message> <MessageID>9702</MessageID> <Description>Site has finished uploading. Please refer to dmpdownloader.log for further details.</Description> </Message> <Message> <MessageID>9800</MessageID> <Description>Notification Server on %1 failed to initialize.%12</Description> </Message> <Message> <MessageID>9801</MessageID> <Description>Notification Server on %1 initialized successfully.</Description> </Message> <Message> <MessageID>9802</MessageID> <Description>Windows Firewall on %1 does not allow clients to connect to the Notification Server via TCP port %2.%12</Description> </Message> <Message> <MessageID>9803</MessageID> <Description>Windows Firewall on %1 allows clients to connect to Notification Server via TCP port %2.</Description> </Message> <Message> <MessageID>9804</MessageID> <Description>Notification Server on %1 failed to connect to the site database %2.%12</Description> </Message> <Message> <MessageID>9805</MessageID> <Description>Notification Server on %1 successfully connected to the site database %2.</Description> </Message> <Message> <MessageID>9806</MessageID> <Description>Notification Server on %1 failed to initialize the TCP listener on port %2.%12</Description> </Message> <Message> <MessageID>9807</MessageID> <Description>Notification Server on %1 successfully initialized the TCP listener on port %2.</Description> </Message> <Message> <MessageID>9900</MessageID> <Description>Notification Manager failed to initialize.%12</Description> </Message> <Message> <MessageID>9901</MessageID> <Description>Notification Manager initialized successfully.</Description> </Message> <Message> <MessageID>9902</MessageID> <Description>The SQL Server Service Broker %1 used by Notification Manager is disabled.%12</Description> </Message> <Message> <MessageID>9903</MessageID> <Description>The SQL Server Service Broker %1 used by Notification Manager is enabled.</Description> </Message> <Message> <MessageID>10000</MessageID> <Description>Failed to initialize. Please refer to cloudusersync.log for further details.</Description> </Message> <Message> <MessageID>10001</MessageID> <Description>A data integrity error was detected for package "%1" (%2%1.pkg).%12</Description> </Message> <Message> <MessageID>10002</MessageID> <Description>Deployment "%1" was received from site "%2".%12 The client passes any supported platform requirements and Configuration Manager will add the Deployment's program to the list that will be displayed to users and/or run via assignment. If a deployment is received but not displayed on a client, verify that the current time on the client is between the deployment start and expiration times, and that the program specified in the deployment is enabled.</Description> </Message> <Message> <MessageID>10003</MessageID> <Description>An error occurred while preparing to run the program for deployment "%1" ("%4" - "%5").%12Additional program properties: Command line: %2 Working directory: %3 Drive letter (? = any): %6</Description> </Message> <Message> <MessageID>10004</MessageID> <Description>The program for deployment "%1" could not be executed ("%4" - "%5").%12Additional program properties: Command line: %2 Working directory: %3 The command line for the program cannot be executed successfully.</Description> </Message> <Message> <MessageID>10005</MessageID> <Description>Program started for deployment "%1" ("%4" - "%5").%12 Command line: %2 Working directory: %3 User context: %9</Description> </Message> <Message> <MessageID>10006</MessageID> <Description>CloudUserSync - Empty principal names found for users in cloud collection. Some users were not enabled for cloud services. Please refer to cloudusersync.log for further details.</Description> </Message> <Message> <MessageID>10007</MessageID> <Description>The program for deployment "%1" failed ("%4" - "%5"). The failure description was "%3%7%8%9". User context: %2%12</Description> </Message> <Message> <MessageID>10008</MessageID> <Description>The program for deployment "%1" completed successfully ("%4" - "%5"). User context: %9%12 Configuration Manager determines status for each program it executes. If Configuration Manager cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. This program returned an exit code that indicates it completed successfully.</Description> </Message> <Message> <MessageID>10009</MessageID> <Description>The program for deployment "%1" completed successfully ("%4" - "%5"). The success description was "%3%7%8%9". User context: %2%12 The program generated an installation status Management Information Format (MIF) file with a status value of Success. For more information, see the documentation for the program you are distributing.</Description> </Message> <Message> <MessageID>10010</MessageID> <Description>An error occurred while preparing to run the uninstall program for deployment "%1" ("%4" - "%5").%12 Additional program properties: Command line: %2 Working directory: %3 Drive letter (? = any): %6</Description> </Message> <Message> <MessageID>10018</MessageID> <Description>Deployment "%1" from site "%2" was rejected because the client's platform is not supported.%12</Description> </Message> <Message> <MessageID>10019</MessageID> <Description>Deployment "%1" from site "%2" was rejected because the deployment has expired.%12</Description> </Message> <Message> <MessageID>10021</MessageID> <Description>The program for deployment "%1" failed ("%4" - "%5"). The program was able to be executed but the system was restarted unexpectedly before the program could be completed or before status could be recorded. No installation status MIF was found after the system restarted.%12</Description> </Message> <Message> <MessageID>10022</MessageID> <Description>The program for deployment "%1" ("%4" - "%5") returned an exit code of "%2"("%12"), which indicates the operation was successful but a restart of the system is required for the operation to be complete. A restart might be pending because there is no maintenance window open. The restart will occur at the next available maintenance window. A status message indicating final success will be sent after the system has been restarted. Configuration Manager determines status for each program it executes. Any program dependencies will not be executed until after the restart occurs. If Configuration Manager cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status.</Description> </Message> <Message> <MessageID>10025</MessageID> <Description>Download of the content "%4" - "%2" has failed.%12.</Description> </Message> <Message> <MessageID>10026</MessageID> <Description>The content for "%4" - "%2" has been removed from the cache. This content has been deleted because either the cache has been automatically cleaned or the cache was deleted manually. The current cache size is %8 MB, and %7 MB of cache space is available.</Description> </Message> <Message> <MessageID>10027</MessageID> <Description>The cache size has been modified from %6 MB to %7 MB. The cache is located at %3.</Description> </Message> <Message> <MessageID>10029</MessageID> <Description>The cache location has been modified. The cache was previously located at %2. The cache is now located at %3. The current cache size is %7 MB. The contents of the cache have been cleared as a result of this change.</Description> </Message> <Message> <MessageID>10030</MessageID> <Description>Download of the content "%4" - "%2" has failed. The download failed because the content downloaded to the client does not match the content specified in the source.</Description> </Message> <Message> <MessageID>10034</MessageID> <Description>The program for the deployment "%1" ("%4" - "%5") has been cancelled due to a user request.</Description> </Message> <Message> <MessageID>10035</MessageID> <Description>The program for deployment "%1 has not yet started because the content for the package "%4" - "%5" (version %2) has not been acquired.</Description> </Message> <Message> <MessageID>10036</MessageID> <Description>The program for deployment "%1" has not be run yet ("%4" - "%5"). The program settings indicate that this program has a user logon condition that must be satisfied before it can be run, and this condition has not yet been satisfied. This program will run once the user logon condition is satisfied.</Description> </Message> <Message> <MessageID>10037</MessageID> <Description>The program for deployment "%1" has not been run yet ("%4" - "%5"). ConfigMgr is currently running another program ("%2" - "%3") on this computer, and that program must complete before this one can begin.</Description> </Message> <Message> <MessageID>10040</MessageID> <Description>The program for deployment "%1" will not be run ("%4" - "%5"). The program settings indicate that this program should only be run on computers where the previous attempt to run this program was not successful. The previous attempt to run this program was successful. This program was previously run successfully at %6.</Description> </Message> <Message> <MessageID>10041</MessageID> <Description>The program for deployment "%1" will not be run ("%4" - "%5"). The program settings indicate that this program should only be run on computers where the previous attempt to run this program was successful. The previous attempt to run this program was not successful. This program attempted to run unsuccessfully at %6.</Description> </Message> <Message> <MessageID>10042</MessageID> <Description>The program for deployment "%1" will not be run ("%4" - "%5"). The program settings indicate that this program should never be run on computers where a previous attempt to run this program has occurred. This program has been attempted on this computer. The program was previously attempted at %6.</Description> </Message> <Message> <MessageID>10043</MessageID> <Description>The program for deployment "%1" will not be run ("%4" - "%5"). The program settings indicate that this program should only be run on computers where a previous attempt to run this program has occurred. This program has never before been attempted on this computer.</Description> </Message> <Message> <MessageID>10045</MessageID> <Description>The program for the deployment "%1" ("%4" - "%5") requires content to be downloaded, but the cache does not have enough space. The current cache size is %8 MB, of which %7 MB is available. The current amount of free disk space on the cache volume is %9 MB. This program requires %6 MB to be available in the cache.</Description> </Message> <Message> <MessageID>10046</MessageID> <Description>Windows Installer per-user elevation of this program ("%4" - "%5") failed for deployment "%1".%12This program was started. Please check the status of this program to determine whether or not it was completed successfully.</Description> </Message> <Message> <MessageID>10050</MessageID> <Description>The program for the deployment "%1" ("%4" - "%5") requires content to be downloaded, but the total cache size is smaller than the size of the content. The current cache size is %8 MB, and %7 MB of cache space is available. This program requires %6 MB to be available in the cache.</Description> </Message> <Message> <MessageID>10051</MessageID> <Description>The content for "%4" - "%2" could not be located. This client will no longer attempt to locate this content.</Description> </Message> <Message> <MessageID>10052</MessageID> <Description>The program for the deployment "%1" ("%4" - "%5") could not be run because the policy contains an invalid combination of requirements: %2.</Description> </Message> <Message> <MessageID>10053</MessageID> <Description>The program for deployment "%1 has failed because download of the content "%4" - "%2" has failed.</Description> </Message> <Message> <MessageID>10054</MessageID> <Description>The program for the deployment "%1" ("%4" - "%5") requires content to be downloaded, but the cache does not have enough space. The current cache size is %8 MB, of which %7 MB is available. The current amount of free disk space on the cache volume is %9 MB. This program requires %6 MB to be available in the cache.</Description> </Message> <Message> <MessageID>10055</MessageID> <Description>An error occurred while preparing to run the program for deployment "%1" ("%4" - "%5").%12Additional program properties: Command line: %2 Working directory: %3 Drive letter (? = any): %6</Description> </Message> <Message> <MessageID>10056</MessageID> <Description>The program for deployment "%1" could not be executed ("%4" - "%5").%12Additional program properties: Command line: %2 Working directory: %3 The command line for the program cannot be executed successfully.</Description> </Message> <Message> <MessageID>10057</MessageID> <Description>The program for deployment "%1 has failed because download of the content "%4" - "%5" has failed. The download failed because the content downloaded to the client does not match the content specified in the content source.</Description> </Message> <Message> <MessageID>10058</MessageID> <Description>The program for deployment "%1 has failed because download of the content "%4" - "%2" has failed.</Description> </Message> <Message> <MessageID>10060</MessageID> <Description>The content for "%4" - "%2" can not be located. This client will attempt to locate this content again.</Description> </Message> <Message> <MessageID>10061</MessageID> <Description>The program for deployment "%1 has failed because download of the content "%4" - "%2" has failed.</Description> </Message> <Message> <MessageID>10062</MessageID> <Description>The program for deployment "%1 has failed because download of the content "%4" - "%2" has failed.</Description> </Message> <Message> <MessageID>10070</MessageID> <Description>The program for deployment "%1" ("%4" - "%5") exceeded the maximum allowed run time of %2 minute(s). Configuration Manager has stopped monitoring the program, and is unable to determine the status of the program. ConfigMgr will not automatically attempt to run this program again.</Description> </Message> <Message> <MessageID>10071</MessageID> <Description>The program for deployment "%1" ("%4" - "%5") could not be monitored. Configuration Manager has assumed this program failed and will attempt to run the program again.</Description> </Message> <Message> <MessageID>10072</MessageID> <Description>The program for deployment "%1" failed ("%4" - "%5"). A failure exit code of %2 was returned. User context: %9%12</Description> </Message> <Message> <MessageID>10073</MessageID> <Description>The program for deployment "%1" ("%4" - "%5") has not yet started because no maintenance window is currently available. The Program will be retried when a maintenance window becomes available.</Description> </Message> <Message> <MessageID>10074</MessageID> <Description>The program for deployment "%1" failed ("%4" - "%5"). There is no maintenance window with a duration at least as large as the program's defined maximum runtime. Consequently, the program may never run on the client.</Description> </Message> <Message> <MessageID>10075</MessageID> <Description>A deployment has completed and requires the machine to restart but the restart cannot be performed due to maintenance window restrictions. The restart is waiting for the next available maintenance window.</Description> </Message> <Message> <MessageID>10076</MessageID> <Description>A deployment has completed and requires the machine to restart. The machine will restart now, and will not adhere to any maintenance window restrictions.</Description> </Message> <Message> <MessageID>10077</MessageID> <Description>The deployment "%1" ("%4" - "%5") is waiting for package content from an Intranet-based Distribution Point. The system is Internet based and cannot run the program directly from a UNC location over the internet.</Description> </Message> <Message> <MessageID>10078</MessageID> <Description>The deployment "%1" ("%4" - "%5") failed to locate the package content on a distribution point that is not on the internet. The system is internet based and was unable to locate an intranet based distribution point before the retry limit was reached.</Description> </Message> <Message> <MessageID>10079</MessageID> <Description>A restart is pending for a deployment. There is no maintenance window available for this computer that will allow the restart to occur.</Description> </Message> <Message> <MessageID>10080</MessageID> <Description>The program for deployment "%1" failed ("%4" - "%5"). Operating System Deployment task sequences cannot run when the computer is on the Internet.</Description> </Message> <Message> <MessageID>10081</MessageID> <Description>The client failed to verify the BranchCache contentinfo file for content %1, downloaded from the server "%2". The error return was %3. Try redistributing the content to this server to resolve this issue.%12</Description> </Message> <Message> <MessageID>10090</MessageID> <Description>The Windows Installer source paths have been successfully updated on this computer.</Description> </Message> <Message> <MessageID>10091</MessageID> <Description>The Windows Installer source paths on this computer failed to update. The failure was caused by error %12. The update will be retried.</Description> </Message> <Message> <MessageID>10092</MessageID> <Description>The Windows Installer source paths on this computer failed to update. The failure was caused by error %12. The update will not be retried.</Description> </Message> <Message> <MessageID>10093</MessageID> <Description>The Windows Installer source paths on this computer failed to update. The client was unable to determine the correct locations for the Windows Installer program.</Description> </Message> <Message> <MessageID>10094</MessageID> <Description>The Windows Installer source paths on this computer failed to update. The client was unable to determine the correct locations for the Windows Installer program.</Description> </Message> <Message> <MessageID>10100</MessageID> <Description>The APNs account cert has expired, follow the Request Apple Notification Service CSR process to request a new APNs account cert.</Description> </Message> <Message> <MessageID>10101</MessageID> <Description>An update is required for Windows Intune integration with Configuration Manager. More information on the update can be found here: %1.</Description> </Message> <Message> <MessageID>10201</MessageID> <Description>Certificate Registration Point is responding to HTTP requests.%12</Description> </Message> <Message> <MessageID>10202</MessageID> <Description>Certificate Registration Point is not responding to HTTP requests. The error encountered was %1. Please refer to crpctrl.log for further details.%12</Description> </Message> <Message> <MessageID>10203</MessageID> <Description>Network Device Enrollment Service %1 is responding to HTTPS requests.%12</Description> </Message> <Message> <MessageID>10204</MessageID> <Description>Network Device Enrollment Service %1 is not responding to HTTPS requests. The error encountered was %1. Please refer to crpctrl.log for further details.%12</Description> </Message> <Message> <MessageID>10205</MessageID> <Description>Certificate is issued to machine/device %1 (GUID:%2) for user %3 with thumbprint %4. This certificate was issued against CI Id %5. Certificate is valid till %6.%12</Description> </Message> <Message> <MessageID>10206</MessageID> <Description>Certificate deployed to machine/device %1 (GUID:%2) for user %3 with thumbprint %4 has expired. This certificate was issued against CI Id %5.%12</Description> </Message> <Message> <MessageID>10207</MessageID> <Description>Certificate issued to machine/device %1 (GUID:%2) for user %3 with thumbprint %4 was revoked successfully. This certificate was issued against CI Id %5.%12</Description> </Message> <Message> <MessageID>10208</MessageID> <Description>Certificate Registration Point failed to revoke certificate issued to machine/device %1 (GUID:%2) for user %3 with thumbprint %4. This certificate was issued against CI Id %5. The error encountered was %6.%12</Description> </Message> <Message> <MessageID>10209</MessageID> <Description>Certificate is renewed for machine/device %1 (GUID:%2) for user %3. Old thumbprint of the certificate is %4. New thumbprint of the certificate is %5. This certificate was issued against CI Id %6. New certificate is valid till %7.%12</Description> </Message> <Message> <MessageID>10210</MessageID> <Description>Certificate Registration Point failed to renew certificate issued to machine/device %1 (GUID:%2) for user %3 with thumbprint %4. This certificate was issued against CI Id %5. The error encountered was %6.%12</Description> </Message> <Message> <MessageID>10301</MessageID> <Description>The Certificate Manager failed to revoke the certificate (Cert Serial Number: %1) issued to the device/requester %2/%3 on the Certification Authority %4.%12</Description> </Message> <Message> <MessageID>10500</MessageID> <Description>Hardware Inventory Agent successfully collected hardware inventory from this computer.</Description> </Message> <Message> <MessageID>10501</MessageID> <Description>Hardware Inventory Agent cannot connect to the Common Information Model Object Manager (CIM Object Manager).%12</Description> </Message> <Message> <MessageID>10502</MessageID> <Description>Hardware Inventory Agent cannot open the "%1" namespace.%12</Description> </Message> <Message> <MessageID>10503</MessageID> <Description>The "%1" namespace has been removed or has become corrupted.%12</Description> </Message> <Message> <MessageID>10504</MessageID> <Description>Hardware Inventory Agent has insufficient virtual memory or disk space to proceed. The inventory cycle will be delayed by as much as 8 hours.%12</Description> </Message> <Message> <MessageID>10505</MessageID> <Description>The Hardware Inventory schema has been updated successfully with a new Managed Object Format (MOF) file from site "%1". The Hardware Inventory Agent will use this updated MOF file in all subsequent inventory cycles.%12</Description> </Message> <Message> <MessageID>10506</MessageID> <Description>Hardware Inventory Agent cannot update the Hardware Inventory Schema.%12</Description> </Message> <Message> <MessageID>10507</MessageID> <Description>SMS Hardware Inventory Agent cannot update the SMS Hardware Inventory Schema. The new Managed Object Format (MOF) file from site "%1" cannot be compiled. The agent will continue attempting to recompile this MOF file and will use the default file sms_def.mof until it is successful.%12</Description> </Message> <Message> <MessageID>10508</MessageID> <Description>Hardware Inventory Agent cannot process Management Information Format (MIF) file "%1" and has moved it to "%2".%12</Description> </Message> <Message> <MessageID>10509</MessageID> <Description>Hardware Inventory Agent cannot process Management Information Format (MIF) file "%1" and has moved it to "%2".%12</Description> </Message> <Message> <MessageID>10510</MessageID> <Description>Hardware Inventory Agent cannot process Management Information Format (MIF) file "%1" and has moved it to "%2".%12</Description> </Message> <Message> <MessageID>10511</MessageID> <Description>Hardware Inventory Agent is unable to locate the Windows Management Instrumentation (WinMgmt) service.%12</Description> </Message> <Message> <MessageID>10600</MessageID> <Description>Software Inventory Agent successfully collected software inventory from this computer.%12</Description> </Message> <Message> <MessageID>10601</MessageID> <Description>Software Inventory Agent has insufficient virtual memory or disk space to proceed. The inventory cycle will be delayed by as much as 8 hours.%12</Description> </Message> <Message> <MessageID>10602</MessageID> <Description>Software Inventory Agent could not collect one or more files.%12</Description> </Message> <Message> <MessageID>10603</MessageID> <Description>Software Inventory Agent was unable to collect one or more files because the maximum size for collected files of %1 MB has been reached.%12</Description> </Message> <Message> <MessageID>10604</MessageID> <Description>Software Inventory Agent raised an exception while attempting to extract file version information from file "%1".%12</Description> </Message> <Message> <MessageID>10605</MessageID> <Description>Software Inventory Agent successfully collected %1 files, totally %2 KB of data, from this computer. These files will be transfered to the Site Server as part of the Software Inventory (SINV) file.%12</Description> </Message> <Message> <MessageID>10650</MessageID> <Description>File collection has successfully run on this computer. A total of %1 files (%2 KB) were collected that match the following path and file name: %3 %12</Description> </Message> <Message> <MessageID>10651</MessageID> <Description>The agent has not collected files matching the file name "%1" or the path "%2" from this computer because the files exceed the maximum size limit of %3 KB. You may need to reconfigure the maximum size limit to allow file collection at the next scheduled agent interval.%12</Description> </Message> <Message> <MessageID>10700</MessageID> <Description>Inventory was collected successfully on this computer. The agent completed in %1 minutes, %2 seconds.%12</Description> </Message> <Message> <MessageID>10701</MessageID> <Description>Inventory was collected successfully on this computer. The agent completed in %1 minutes, %2 seconds and generated inventory data report %3. %12</Description> </Message> <Message> <MessageID>10702</MessageID> <Description>The agent encountered an error while querying WMI to collect data from this computer. The first query to fail was "%1".%12</Description> </Message> <Message> <MessageID>10703</MessageID> <Description>The agent encountered an error while collecting data from this computer.</Description> </Message> <Message> <MessageID>10704</MessageID> <Description>The agent encountered an error while generating the inventory report (%1) for this computer.%12</Description> </Message> <Message> <MessageID>10800</MessageID> <Description>The ConfigMgr client was installed. The current version is %1.%12</Description> </Message> <Message> <MessageID>10801</MessageID> <Description>The ConfigMgr client was uninstalled.%12</Description> </Message> <Message> <MessageID>10802</MessageID> <Description>The ConfigMgr client was upgraded. The current version is %1.%12</Description> </Message> <Message> <MessageID>10803</MessageID> <Description>The client failed to download policy. The data transfer service returned "%2" (%1).%12</Description> </Message> <Message> <MessageID>10804</MessageID> <Description>The ConfigMgr client was reassigned. The previous site code was "%1". The new site code is "%2".%12</Description> </Message> <Message> <MessageID>10805</MessageID> <Description>The ConfigMgr Client has determined that its policy is incorrect. A full policy update will be requested to correct the issue. For more information see PolicyAgent.log on the client machine.%12</Description> </Message> <Message> <MessageID>10806</MessageID> <Description>An attempt to assign the ConfigMgr client to site "%1" failed. The site code could not be verified.%12</Description> </Message> <Message> <MessageID>10807</MessageID> <Description>The ConfigMgr client is already assigned to site "%1". The client site assignment was not changed.%12</Description> </Message> <Message> <MessageID>10808</MessageID> <Description>The client failed to compile one or more policies. For more information see PolicyAgentEvaluator.log on the client machine. Policy ID: %1 Policy Version: %2 Policy Source: %3 Error: %4 Object: %5 Lines: %6 - %7 %12</Description> </Message> <Message> <MessageID>10809</MessageID> <Description>The ConfigMgr client was repaired. The current version is %1.%12</Description> </Message> <Message> <MessageID>10810</MessageID> <Description>The SMS Service Host (CCMEXEC) has entered Low Memory Mode. The machine has %2 meg(s) available RAM + pagefile, which falls below the threshold of %1 meg(s). Some functionality will be disabled until more memory becomes available.%12</Description> </Message> <Message> <MessageID>10811</MessageID> <Description>The SMS Service Host (CCMEXEC) has recovered from Low Memory Mode. The machine has %2 meg(s) available RAM + pagefile, which exceeds the recovery threshold of %1 meg(s). All functionality will now be enabled.%12</Description> </Message> <Message> <MessageID>10812</MessageID> <Description>The SMS Service Host (CCMEXEC) was unable to update certificate information in the Active Directory.%12</Description> </Message> <Message> <MessageID>10813</MessageID> <Description>The SMS Service Host (CCMEXEC) successfuly updated certificate information in the Active Directory. %12</Description> </Message> <Message> <MessageID>10814</MessageID> <Description>The ConfigMgr client was installed but may require a reboot for the installation to complete.%12</Description> </Message> <Message> <MessageID>10815</MessageID> <Description>The SMS Service Host (CCMEXEC) encountered a failure (%1) when performing Certificate operations.%12</Description> </Message> <Message> <MessageID>10816</MessageID> <Description>The ConfigMgr Client generated a new SMS Unique Identifier. The old SMS Unique ID was %2. The new SMS Unique ID is %1.%12</Description> </Message> <Message> <MessageID>10817</MessageID> <Description>The ConfigMgr Client rejected the site server signing certificate due to a revocation-related failure (%1).%12</Description> </Message> <Message> <MessageID>10818</MessageID> <Description>The ConfigMgr Client rejected the site server signing certificate due to an expiration-related failure (%1).%12</Description> </Message> <Message> <MessageID>10819</MessageID> <Description>The ConfigMgr Client rejected the site server signing certificate due to a trust-related failure (%1).%12</Description> </Message> <Message> <MessageID>10820</MessageID> <Description>The ConfigMgr Client encounted an SSL-related failure (%1) when using BITS to access location %2.%12</Description> </Message> <Message> <MessageID>10821</MessageID> <Description>The ConfigMgr Client received policy that could not be verified. For more information see PolicyAgent.log on the client machine.%12</Description> </Message> <Message> <MessageID>10822</MessageID> <Description>The ConfigMgr Client encountered a certificate for Management Point %1 that could not be verified.%12</Description> </Message> <Message> <MessageID>10900</MessageID> <Description>Software Metering Agent encountered an error while collecting %1 data from WMI, error code %2. The Agent will not be able to generate the usage report in this cycle.%12</Description> </Message> <Message> <MessageID>10901</MessageID> <Description>Software Metering Agent failed to create %1 usage data file, error code %2.%12</Description> </Message> <Message> <MessageID>10902</MessageID> <Description>Software Metering Agent failed to upload %1 usage data file, error code %2. The agent will retry later to upload this file.%12</Description> </Message> <Message> <MessageID>10903</MessageID> <Description>Software Metering Agent successfully processed %1 usage data files.%12</Description> </Message> <Message> <MessageID>10904</MessageID> <Description>Software Metering Agent failed to download %1 rule file, error code %2. The agent will retry later to download this file.%12</Description> </Message> <Message> <MessageID>10905</MessageID> <Description>Software Metering Agent unable to open %1 rule file, error code %2.%12</Description> </Message> <Message> <MessageID>10906</MessageID> <Description>Software Metering Agent successfully processed %1 rule file.%12</Description> </Message> <Message> <MessageID>10907</MessageID> <Description>Software Metering Agent successfully received rule %1 for program %2, version %3.%12</Description> </Message> <Message> <MessageID>11000</MessageID> <Description>Client agent settings policy received.%12</Description> </Message> <Message> <MessageID>11001</MessageID> <Description>Invalid client agent settings policy received.%12</Description> </Message> <Message> <MessageID>11002</MessageID> <Description>Client agent settings policy is not trusted.%12</Description> </Message> <Message> <MessageID>11010</MessageID> <Description>Software Distribution Policy received for Deployment %1 (Package %2).%12</Description> </Message> <Message> <MessageID>11011</MessageID> <Description>Invalid Software Distribution Policy received for Deployment %1 (Package %2).%12</Description> </Message> <Message> <MessageID>11012</MessageID> <Description>Software Distribution Policy received for Deployment %1 (Package %2) is not trusted.%12</Description> </Message> <Message> <MessageID>11020</MessageID> <Description>Package Location response received for Deployment %1 (Package %2).%12</Description> </Message> <Message> <MessageID>11021</MessageID> <Description>Invalid Package Location response received for Deployment %1 (Package %2).%12</Description> </Message> <Message> <MessageID>11030</MessageID> <Description>Starting content download for package %1 (Deployment %2).%12</Description> </Message> <Message> <MessageID>11031</MessageID> <Description>Successfully downloaded content for package %1 (Deployment %2).%12</Description> </Message> <Message> <MessageID>11032</MessageID> <Description>Content download failed for package %1 (Deployment %2).%12</Description> </Message> <Message> <MessageID>11033</MessageID> <Description>Download aborted due to poor connectivity.%12</Description> </Message> <Message> <MessageID>11034</MessageID> <Description>Attempting to execute command line %1.%12</Description> </Message> <Message> <MessageID>11035</MessageID> <Description>The program for Deployment %1 (Package %2) executed successfully.%12</Description> </Message> <Message> <MessageID>11036</MessageID> <Description>The program for Deployment %1 (Package %2) failed. A non zero exit code of %3 was returned.%12</Description> </Message> <Message> <MessageID>11037</MessageID> <Description>Downloaded content for package %1 (Deployment %2) but the package content's hash verification failed.%12</Description> </Message> <Message> <MessageID>11070</MessageID> <Description>Hardware inventory initiated.%12</Description> </Message> <Message> <MessageID>11071</MessageID> <Description>Hardware inventory failed.%12</Description> </Message> <Message> <MessageID>11072</MessageID> <Description>Hardware inventory succeeded.%12</Description> </Message> <Message> <MessageID>11073</MessageID> <Description>Device Client failed to refresh site server signing certificate (SSSC).%12</Description> </Message> <Message> <MessageID>11074</MessageID> <Description>Device Client successfully refreshed site server signing certificate (SSSC).%12</Description> </Message> <Message> <MessageID>11080</MessageID> <Description>Software inventory initiated.%12</Description> </Message> <Message> <MessageID>11081</MessageID> <Description>Software inventory failed.%12</Description> </Message> <Message> <MessageID>11082</MessageID> <Description>Software inventory succeeded.%12</Description> </Message> <Message> <MessageID>11083</MessageID> <Description>Device Client is about to be upgraded.%12</Description> </Message> <Message> <MessageID>11084</MessageID> <Description>Device Client is about to be uninstalled.%12</Description> </Message> <Message> <MessageID>11090</MessageID> <Description>File collection initiated.%12</Description> </Message> <Message> <MessageID>11091</MessageID> <Description>File collection succeeded.%12</Description> </Message> <Message> <MessageID>11095</MessageID> <Description>File collection failed.%12</Description> </Message> <Message> <MessageID>11096</MessageID> <Description>Registration of Device Client in Native Security Mode succeeded.%12</Description> </Message> <Message> <MessageID>11100</MessageID> <Description>The OS Deployment agent successfully started the action %1.%12</Description> </Message> <Message> <MessageID>11101</MessageID> <Description>The OS installation failed action %1 with exit code %2.%12</Description> </Message> <Message> <MessageID>11102</MessageID> <Description>The OS installation has been completed successfully.%12</Description> </Message> <Message> <MessageID>11103</MessageID> <Description>The OS installation failed to request distribution points from management point %1.%12</Description> </Message> <Message> <MessageID>11104</MessageID> <Description>The OS installation failed because there are no distribution points available at this location.%12</Description> </Message> <Message> <MessageID>11105</MessageID> <Description>The OS installation failed to connect to the distribution point %1.%12</Description> </Message> <Message> <MessageID>11106</MessageID> <Description>The OS installation successfully started the Validation phase.%12</Description> </Message> <Message> <MessageID>11107</MessageID> <Description>The OS installation successfully started the State Capture phase.%12</Description> </Message> <Message> <MessageID>11108</MessageID> <Description>The OS installation successfully started the Preinstall phase.%12</Description> </Message> <Message> <MessageID>11109</MessageID> <Description>The OS installation successfully started the Install phase.%12</Description> </Message> <Message> <MessageID>11110</MessageID> <Description>The OS installation successfully started the Postinstall phase.%12</Description> </Message> <Message> <MessageID>11111</MessageID> <Description>The OS installation successfully started the State Restore phase.%12</Description> </Message> <Message> <MessageID>11112</MessageID> <Description>Package was succesfully downloaded from Multicast enabled DP.%12</Description> </Message> <Message> <MessageID>11113</MessageID> <Description>Package failed to download from Multicast enabled DP. Error %1. Will try another DP. %12</Description> </Message> <Message> <MessageID>11120</MessageID> <Description>The task sequence execution engine skipped the disabled group (%3).%12</Description> </Message> <Message> <MessageID>11121</MessageID> <Description>The task sequence execution engine failed evaluating the condition for the group (%3). Error code %4.%12</Description> </Message> <Message> <MessageID>11122</MessageID> <Description>The task sequence execution engine skipped the group (%3) because the condition was evaluated to be false.%12</Description> </Message> <Message> <MessageID>11123</MessageID> <Description>The task sequence execution engine evaluated TRUE for the condition of the group (%3).%12</Description> </Message> <Message> <MessageID>11124</MessageID> <Description>The task sequence execution engine started the group (%3).%12</Description> </Message> <Message> <MessageID>11125</MessageID> <Description>The task sequence execution engine ignored execution failure in the group (%3).%12</Description> </Message> <Message> <MessageID>11126</MessageID> <Description>The task sequence execution engine aborted execution for a failure in the group (%3).%12</Description> </Message> <Message> <MessageID>11127</MessageID> <Description>The task sequence execution engine successfully completed the group (%3).%12</Description> </Message> <Message> <MessageID>11128</MessageID> <Description>The task sequence execution engine skipped the disabled action (%2) in the group (%3).%12</Description> </Message> <Message> <MessageID>11129</MessageID> <Description>The task sequence execution engine failed evaluating the condition for the action (%2) in the group (%3). Error code %4.%12</Description> </Message> <Message> <MessageID>11130</MessageID> <Description>The task sequence execution engine skipped the action (%2) in the group (%3) because the condition was evaluated to be false.%12</Description> </Message> <Message> <MessageID>11131</MessageID> <Description>The task sequence execution engine evaluated TRUE for the condition of the action (%2) in the group (%3).%12</Description> </Message> <Message> <MessageID>11132</MessageID> <Description>The task sequence execution engine failed to start the action (%2) in the group (%3) with the win32 error code %4.%12</Description> </Message> <Message> <MessageID>11133</MessageID> <Description>The task sequence execution engine successfully started the action (%2) in the group (%3).%12</Description> </Message> <Message> <MessageID>11134</MessageID> <Description>The task sequence execution engine successfully completed the action (%2) in the group (%3) with exit code %4 Action output: %5%6%7%8.%12</Description> </Message> <Message> <MessageID>11135</MessageID> <Description>The task sequence execution engine failed executing the action (%2) in the group (%3) with the error code %4 Action output: %5%6%7%8.%12</Description> </Message> <Message> <MessageID>11136</MessageID> <Description>The task sequence execution engine received an external shutdown request during execution of the action (%2) in the group (%3) Partial action output: %5%6%7%8.%12</Description> </Message> <Message> <MessageID>11137</MessageID> <Description>The task sequence execution engine timeout in executing the action (%2) in the group (%3) Partial action output: %5%6%7%8.%12</Description> </Message> <Message> <MessageID>11138</MessageID> <Description>The task sequence execution engine ignored execution failure of the action (%2) in the group (%3).%12</Description> </Message> <Message> <MessageID>11139</MessageID> <Description>The task sequence execution engine aborted execution for a failure of the action (%2) in the group (%3).%12</Description> </Message> <Message> <MessageID>11140</MessageID> <Description>The task sequence execution engine started execution of a task sequence.%12</Description> </Message> <Message> <MessageID>11141</MessageID> <Description>The task sequence execution engine failed execution of a task sequence.%12</Description> </Message> <Message> <MessageID>11142</MessageID> <Description>The task sequence execution engine performed a system reboot initiated by the action (%2) in the group (%3).%12</Description> </Message> <Message> <MessageID>11143</MessageID> <Description>The task sequence execution engine successfully completed a task sequence.%12</Description> </Message> <Message> <MessageID>11144</MessageID> <Description>The task sequence execution engine from a non-client started execution of a task sequence.%12</Description> </Message> <Message> <MessageID>11169</MessageID> <Description>Task sequence version is not supported.%12</Description> </Message> <Message> <MessageID>11170</MessageID> <Description>The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of %1 was returned.%12</Description> </Message> <Message> <MessageID>11171</MessageID> <Description>The task sequence manager successfully completed execution of the task sequence.%12</Description> </Message> <Message> <MessageID>11200</MessageID> <Description>Software updates evaluation failed: invalid syntax or value for the specified scheduled installation window (/l).</Description> </Message> <Message> <MessageID>11201</MessageID> <Description>Software updates evaluation failed: could not determine the deployment assignment schedule. This is needed to calculate the correct begin and end times for the specified scheduled installation window (/l).</Description> </Message> <Message> <MessageID>11202</MessageID> <Description>Software updates evaluation failed: could not load software updates authorization list %1.</Description> </Message> <Message> <MessageID>11203</MessageID> <Description>Software updates evaluation failed: could not locate the scan component of the specified software update inventory tool. The scan component deployment might not have run on the client computer.</Description> </Message> <Message> <MessageID>11204</MessageID> <Description>Software updates evaluation failed: could not run the scan component of the specified software update inventory tool on the client computer. The scan component program could not be found in the client cache or it returned failure status.</Description> </Message> <Message> <MessageID>11205</MessageID> <Description>Software updates evaluation failed: error loading Win32_PatchState class from WMI.</Description> </Message> <Message> <MessageID>11206</MessageID> <Description>Software updates evaluation failed: error storing Win32_PatchState class into WMI.</Description> </Message> <Message> <MessageID>11207</MessageID> <Description>Software updates evaluation failed: unable to load resource file.</Description> </Message> <Message> <MessageID>11250</MessageID> <Description>Software updates evaluation was ended due to a scheduled installation window violation (installation started too early.)</Description> </Message> <Message> <MessageID>11251</MessageID> <Description>Software updates evaluation was ended due to a scheduled installation window violation (installation started too late.)</Description> </Message> <Message> <MessageID>11252</MessageID> <Description>Software updates installation was rescheduled by the user.%12</Description> </Message> <Message> <MessageID>11253</MessageID> <Description>Software updates installation was postponed by the user.%12</Description> </Message> <Message> <MessageID>11254</MessageID> <Description>Software updates installation was automatically postponed: the user did not choose to install the updates and the grace period has not expired.%12</Description> </Message> <Message> <MessageID>11255</MessageID> <Description>The software updates installation evaluation returned the following results: %1 Authorized, %2 attempted, %3 failed. Review the previous status message for further details about the actions taken during this update cycle. Refer to the associated detail messages from this client for each of the software update installations that were attempted for status on each update.%12</Description> </Message> <Message> <MessageID>11256</MessageID> <Description>Software update installation failed: the scheduled installation window expired while software update installation was not complete.</Description> </Message> <Message> <MessageID>11257</MessageID> <Description>Software updates installation was postponed: the user rescheduled the required system restart.</Description> </Message> <Message> <MessageID>11258</MessageID> <Description>Software updates installation was postponed: The user postponed the required pre-installation restart.</Description> </Message> <Message> <MessageID>11259</MessageID> <Description>Software updates installation was automatically postponed: a pre-installation restart was required, but the user did not choose to restart and the grace period has not expired.</Description> </Message> <Message> <MessageID>11261</MessageID> <Description>Software updates installation completed but the required restart was rescheduled by the user.%12</Description> </Message> <Message> <MessageID>11262</MessageID> <Description>Software updates installation completed but the required restart was postponed by the user.%12</Description> </Message> <Message> <MessageID>11263</MessageID> <Description>Software updates installation completed but the required restart was postponed automatically.%12</Description> </Message> <Message> <MessageID>11264</MessageID> <Description>The Software Updates Installation Agent initiated a system restart because one or more software updates required a restart in order for the installation to take effect.%12</Description> </Message> <Message> <MessageID>11266</MessageID> <Description>Software Updates Installation Agent completed successfully and suppressed the required system restart because the program was configured to suppress restarts for workstations.%12</Description> </Message> <Message> <MessageID>11267</MessageID> <Description>Software Updates Installation Agent completed successfully and suppressed the required system restart because the program was configured to suppress restarts for servers. Note: to avoid this, use the scheduled installation feature (/l) to enable automated restarts within a defined time window.%12</Description> </Message> <Message> <MessageID>11268</MessageID> <Description>Software Updates Installation Agent completed successfully and no restart was required.%12</Description> </Message> <Message> <MessageID>11269</MessageID> <Description>Software update installation was postponed: awaiting system restart.</Description> </Message> <Message> <MessageID>11270</MessageID> <Description>Restart of the computer is required in order for newly installed updates to take effect.%12</Description> </Message> <Message> <MessageID>11300</MessageID> <Description>The software update was installed and a restart of the computer was not required for the changes to take effect. The run-time returned was %7 minute(s). Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </Message> <Message> <MessageID>11301</MessageID> <Description>The software update was installed and a restart of the computer is required in order for the changes to take effect. Refer to the deployment status to determine the restart status of the computer. The run-time returned was %7 minute(s). Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </Message> <Message> <MessageID>11302</MessageID> <Description>The software update failed to install.</Description> </Message> <Message> <MessageID>11303</MessageID> <Description>The software update installation did not complete within the allocated time and was stopped by the agent.</Description> </Message> <Message> <MessageID>11304</MessageID> <Description>The software update was started, but was cancelled during installation by the user of the computer.</Description> </Message> <Message> <MessageID>11306</MessageID> <Description>The software update installation was not attempted due to a low disk space condition.</Description> </Message> <Message> <MessageID>11307</MessageID> <Description>The software update was installed and a restart of the computer was not required for the changes to take effect. The run-time returned was %7 minute(s). Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </Message> <Message> <MessageID>11308</MessageID> <Description>The software update was installed and a restart of the computer is required in order for the changes to take effect. Refer to the deployment status to determine the restart status of the computer. The run-time returned was %7 minute(s). Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </Message> <Message> <MessageID>11309</MessageID> <Description>The software update was installed due to an administrator defined enforcement date being met. A restart of the computer was not required for the changes to take effect. The run-time returned was %7 minute(s). Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </Message> <Message> <MessageID>11310</MessageID> <Description>The software update was installed due to an administrator defined enforcement date being met. A restart of the computer is required in order for the changes to take effect. Refer to the deployment status to determine the restart status of the computer. The run-time returned was %7 minute(s). Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </Message> <Message> <MessageID>11415</MessageID> <Description>Scan started by Software Updates Scan Agent.%12</Description> </Message> <Message> <MessageID>11416</MessageID> <Description>Failed to start Windows Update Agent on the client.%12</Description> </Message> <Message> <MessageID>11417</MessageID> <Description>Scan completed successfully by Software Updates Scan Agent.%12</Description> </Message> <Message> <MessageID>11418</MessageID> <Description>Software Updates Scan Agent has forcibly terminated the scan as it did not finish in the expected duration.%12</Description> </Message> <Message> <MessageID>11423</MessageID> <Description>Software Updates Scan failed.%12</Description> </Message> <Message> <MessageID>11424</MessageID> <Description>Software Update Scan - Update Source registration failed.%12</Description> </Message> <Message> <MessageID>11426</MessageID> <Description>Software Updates Scan Agent completed the scan successfully. However, scan reported error(s) %2 that might result in some updates not being detected as required or installed. Refer to the product documentation to see how these errors affect your enterprise and what steps you can take to correct possible configuration issues.%12</Description> </Message> <Message> <MessageID>11450</MessageID> <Description>Synchronization component failed: Site Code is not specified. Type = %1.%12</Description> </Message> <Message> <MessageID>11451</MessageID> <Description>Synchronization component failed: Package ID is not specified. Type = %1.%12</Description> </Message> <Message> <MessageID>11452</MessageID> <Description>Synchronization component failed: ConfigMgr Site Name is not specified. Type = %1.%12</Description> </Message> <Message> <MessageID>11453</MessageID> <Description>Synchronization component failed: package source folder is not specified. Type = %1.%12</Description> </Message> <Message> <MessageID>11454</MessageID> <Description>Synchronization component failed: Unable to write to %2. Type = %1.</Description> </Message> <Message> <MessageID>11455</MessageID> <Description>Synchronization component failed: Unable to read from %2. Type = %1.</Description> </Message> <Message> <MessageID>11456</MessageID> <Description>Synchronization component failed: the synchronization component (type = %1) failed to download %2, error code: %3.</Description> </Message> <Message> <MessageID>11457</MessageID> <Description>Software update catalog (type = %1) sync operation completed successfully. Newer version of catalog was downloaded and updated on distribution points.%12</Description> </Message> <Message> <MessageID>11458</MessageID> <Description>Synchronization component failed: the synchronization component failed to update the Distribution Points for the catalog (type = %1). Error code: %2.</Description> </Message> <Message> <MessageID>11459</MessageID> <Description>Synchronization component failed: the synchronization component failed to update the Site Database for the catalog (type = %1). See the log file for details.%12</Description> </Message> <Message> <MessageID>11460</MessageID> <Description>Software update catalog (type = %1) sync operation completed successfully. Newer version of catalog was not available.%12</Description> </Message> <Message> <MessageID>11461</MessageID> <Description> The content downloaded can't be trusted as unable to verify the certificate attached to the content, or no certificate was attached to the content therefore it can't be trusted.%12</Description> </Message> <Message> <MessageID>11462</MessageID> <Description> An existing or higher version of a scan tool is already installed at a parent site in the hierarchy. You are not allowed to have multiple instances of same scan tool in a hierarchy. You should only install a scan tool at the central site in the hierarchy.%12</Description> </Message> <Message> <MessageID>11500</MessageID> <Description>Version of device client on attached device is newer. No action taken.%12</Description> </Message> <Message> <MessageID>11501</MessageID> <Description>No device client action specified. No action taken.%12</Description> </Message> <Message> <MessageID>11502</MessageID> <Description>Device client installation completed successfully.%12</Description> </Message> <Message> <MessageID>11503</MessageID> <Description>Device client upgrade completed successfully.%12</Description> </Message> <Message> <MessageID>11504</MessageID> <Description>Installed device client state verified and settings enforced.%12</Description> </Message> <Message> <MessageID>11505</MessageID> <Description>Device client uninstallation completed successfully.%12</Description> </Message> <Message> <MessageID>11506</MessageID> <Description>Device client installation completed successfully and certificate enrollment was not required.%12</Description> </Message> <Message> <MessageID>11507</MessageID> <Description>Device client upgrade completed successfully and certificate enrollment was not required.%12</Description> </Message> <Message> <MessageID>11508</MessageID> <Description>Installed Device client state verified, settings enforced and certificate enrollment was not required.%12</Description> </Message> <Message> <MessageID>11510</MessageID> <Description>Device client installation completed successfully. Certificate installation and/or enrollment failed. Check DmInstaller.log on the Device Client for detailed error information.%12</Description> </Message> <Message> <MessageID>11511</MessageID> <Description>Device client upgrade completed successfully. Certificate installation and/or enrollment failed. Check DmInstaller.log on the Device Client for detailed error information.%12</Description> </Message> <Message> <MessageID>11512</MessageID> <Description>Installed device client state verified and settings enforced. Certificate installation and/or enrollment failed. Check DmInstaller.log on the Device Client for detailed error information.%12</Description> </Message> <Message> <MessageID>11520</MessageID> <Description>Device client deployment action failed. Failed to establish ActiveSync connection to device.%12</Description> </Message> <Message> <MessageID>11521</MessageID> <Description>Device client deployment action failed. Invalid client settings file.%12</Description> </Message> <Message> <MessageID>11522</MessageID> <Description>Device client deployment action failed. Error determining running directory for DmClientXfer.exe.%12</Description> </Message> <Message> <MessageID>11523</MessageID> <Description>Device client deployment action failed. Required ActiveSync libraries missing.%12</Description> </Message> <Message> <MessageID>11524</MessageID> <Description>Device client deployment action failed. Could not determine processor type of attached device.%12</Description> </Message> <Message> <MessageID>11525</MessageID> <Description>Device client deployment action failed. Could not determine base operating system version of attached device.%12</Description> </Message> <Message> <MessageID>11526</MessageID> <Description>Device client deployment action failed. Error determining client version for attached device.%12</Description> </Message> <Message> <MessageID>11527</MessageID> <Description>Device client deployment action failed. Error creating client settings .ini file.%12</Description> </Message> <Message> <MessageID>11528</MessageID> <Description>Device client deployment action failed. Failed copying files to attached device.%12</Description> </Message> <Message> <MessageID>11529</MessageID> <Description>Device client deployment action failed. Failed executing client installer program on attached device.%12</Description> </Message> <Message> <MessageID>11530</MessageID> <Description>Device client deployment action may have failed. Failed reading status information from device.%12</Description> </Message> <Message> <MessageID>11540</MessageID> <Description>Device client deployment action failed. Error determining running directory for client installer program.%12</Description> </Message> <Message> <MessageID>11541</MessageID> <Description>Device client deployment action failed. Error executing pre-install command line.%12</Description> </Message> <Message> <MessageID>11542</MessageID> <Description>Device client deployment action failed. Error executing post-install command line.%12</Description> </Message> <Message> <MessageID>11550</MessageID> <Description>Device client installation or upgrade failed. Error during uninstallation of previous client.%12</Description> </Message> <Message> <MessageID>11551</MessageID> <Description>Device client installation or upgrade failed. Invalid client settings file.%12</Description> </Message> <Message> <MessageID>11552</MessageID> <Description>Device client installation or upgrade failed. Error installing client CAB file.%12</Description> </Message> <Message> <MessageID>11553</MessageID> <Description>Device client installation or upgrade failed. Error starting client service.%12</Description> </Message> <Message> <MessageID>11554</MessageID> <Description>Device client installation or upgrade failed. Error updating client settings.%12</Description> </Message> <Message> <MessageID>11555</MessageID> <Description>Device Client Deployment failed with unknown error.%12</Description> </Message> <Message> <MessageID>11560</MessageID> <Description>Device client verification or repair failed. Error during uninstallation of previous client.%12</Description> </Message> <Message> <MessageID>11561</MessageID> <Description>Device client verification or repair failed. Invalid client settings file.%12</Description> </Message> <Message> <MessageID>11562</MessageID> <Description>Device client verification or repair failed. Error installing client CAB file.%12</Description> </Message> <Message> <MessageID>11563</MessageID> <Description>Device client verification or repair failed. Error starting client service.%12</Description> </Message> <Message> <MessageID>11564</MessageID> <Description>Device client verification or repair failed. Error updating client settings.%12</Description> </Message> <Message> <MessageID>11565</MessageID> <Description>Device client verification or repair failed. Error restoring required files.%12</Description> </Message> <Message> <MessageID>11566</MessageID> <Description>Device client privileged certificate installation failed. Device may have a security policy which prevents the client installer from installing certificates into the privileged and SPC certificate stores.%12</Description> </Message> <Message> <MessageID>11567</MessageID> <Description>Encountered unknown error installing the device client.%12</Description> </Message> <Message> <MessageID>11568</MessageID> <Description>Device client setup failed to launch during install.%12</Description> </Message> <Message> <MessageID>11570</MessageID> <Description>Device client uninstallation failed. Error using unload.exe to uninstall the existing client.%12</Description> </Message> <Message> <MessageID>11571</MessageID> <Description>Device client install/upgrade failed. Error enforcing new client. Device rolled back to old client (if existed before).%12</Description> </Message> <Message> <MessageID>11572</MessageID> <Description>Device client rollback failed during unsuccessful upgrade. Error enforcing old client. Need to freshly install the client.%12</Description> </Message> <Message> <MessageID>11573</MessageID> <Description>Device client failed to perform post cab install actions. Device client installation failed.%12</Description> </Message> <Message> <MessageID>11600</MessageID> <Description>The Component "%1" encountered an error %2 of category "%3" at %4.%12</Description> </Message> <Message> <MessageID>11700</MessageID> <Description>Scan tool %2 for the update %1 not available.</Description> </Message> <Message> <MessageID>11701</MessageID> <Description>Scan tool %2 for the update %1 failed.%12</Description> </Message> <Message> <MessageID>11702</MessageID> <Description>The contents hash for the update %1 provided in policy does not match with the contents downloaded.</Description> </Message> <Message> <MessageID>11703</MessageID> <Description>The contents for update %1 could not be located.%12</Description> </Message> <Message> <MessageID>11704</MessageID> <Description>Contents size for update %1 exceed free cache size available. The current cache size is %2 MB, of which %3 MB is available. The current amount of free disk space on the cache volume is %4 MB. This update requires %5 MB to be available in the cache.</Description> </Message> <Message> <MessageID>11705</MessageID> <Description>Contents size for the update %1 exceed total cache size available.%12 The current cache size is %2 MB, and %3 MB of cache space is available. This update requires %4 MB to be available in the cache.</Description> </Message> <Message> <MessageID>11706</MessageID> <Description>Failed to download contents for update %1.%12</Description> </Message> <Message> <MessageID>11707</MessageID> <Description>Update %1 cannot be attempted due to invalid commandline = %2.</Description> </Message> <Message> <MessageID>11708</MessageID> <Description>Update %1 application failed with returned exit code = %2.</Description> </Message> <Message> <MessageID>11709</MessageID> <Description>Update %1 did not finish in allocated time %2 seconds.</Description> </Message> <Message> <MessageID>11710</MessageID> <Description>Creation of process failed for update %1.%12 Commandline = %2</Description> </Message> <Message> <MessageID>11711</MessageID> <Description>Failed to get installer path for the update %1.%12</Description> </Message> <Message> <MessageID>11712</MessageID> <Description>Failed to monitor process for update %1 after service restart.%12</Description> </Message> <Message> <MessageID>11713</MessageID> <Description>SMS internal error occurred for the update %1.%12</Description> </Message> <Message> <MessageID>11714</MessageID> <Description>Bundle update "%1" failed to get content for update "%2". Please check the enforcement status of update "%2" to get further details.%12</Description> </Message> <Message> <MessageID>11715</MessageID> <Description>Bundle update "%1" failed to install update "%2". Please check the enforcement status of update "%2" to get further details.%12</Description> </Message> <Message> <MessageID>11716</MessageID> <Description>Bundle update "%1" failed to evaluate the applicability of its leaf updates.%12</Description> </Message> <Message> <MessageID>11717</MessageID> <Description>Update "%1" failed to install as no current or future maintenance window is available to accomodate this update with max runtime = %2.%12</Description> </Message> <Message> <MessageID>11750</MessageID> <Description>Updates enforcement job failed for assignment %1.%12</Description> </Message> <Message> <MessageID>11751</MessageID> <Description>Updates failures occured during enforcement for assignment %1.%12</Description> </Message> <Message> <MessageID>11752</MessageID> <Description>Some updates are still non-compliant after enforcement completion of the assignment %1.</Description> </Message> <Message> <MessageID>11753</MessageID> <Description>Post restart updates compliance checking failed.%12</Description> </Message> <Message> <MessageID>11754</MessageID> <Description>Failed to initiate enforcement of assignment %1.%12</Description> </Message> <Message> <MessageID>11755</MessageID> <Description>Failed to initiate updates evaluation for assignment %1.%12</Description> </Message> <Message> <MessageID>11756</MessageID> <Description>Updates evaluation job completed with failure for assignment %1.%12</Description> </Message> <Message> <MessageID>11757</MessageID> <Description>Invalid policy received for assignment %1.</Description> </Message> <Message> <MessageID>11758</MessageID> <Description>Failed to initiate updates advance download for assignment %1.%12</Description> </Message> <Message> <MessageID>11759</MessageID> <Description>Updates advance download job completed with failure for assignment %1.%12</Description> </Message> <Message> <MessageID>11760</MessageID> <Description>No maintenance window is defined to accommodate at least one update in the deployment %1.</Description> </Message> <Message> <MessageID>11800</MessageID> <Description>Failed to download baseline CI Id %1, version %2.</Description> </Message> <Message> <MessageID>11801</MessageID> <Description>The contents hash for baseline CI Id %1, version %2 provided in policy does not match with the contents downloaded.</Description> </Message> <Message> <MessageID>11802</MessageID> <Description>Cannot further process baseline CI Id %1, version %2. Managed client does not have the .Net framework version 2.0 installed.</Description> </Message> <Message> <MessageID>11850</MessageID> <Description>Failed to download baseline content %4 (%3), version %5.</Description> </Message> <Message> <MessageID>11851</MessageID> <Description>The contents hash for baseline content %4 (%3), version %5 provided in policy does not match with the contents downloaded.</Description> </Message> <Message> <MessageID>11852</MessageID> <Description>Failed to evaluate baseline content %4 (%3), version %5. %6.%12</Description> </Message> <Message> <MessageID>11853</MessageID> <Description>Failed to report compliance state for baseline content %4 (%3), version %5.%12</Description> </Message> <Message> <MessageID>11854</MessageID> <Description>Baseline content %4 (%3), version %5 which was previously non-compliant or had no prior discovery information is now compliant.</Description> </Message> <Message> <MessageID>11855</MessageID> <Description>Baseline content %4 (%3), version %5 which was previously compliant, had no prior discovery information, or a different non-compliance severity is now non-compliant with 'Informational' severity.</Description> </Message> <Message> <MessageID>11856</MessageID> <Description>Baseline content %4 (%3), version %5 which was previously compliant, had no prior discovery information, or a different non-compliance severity is now non-compliant with 'Warning' severity</Description> </Message> <Message> <MessageID>11857</MessageID> <Description>Baseline content %4 (%3), version %5 which was previously compliant, had no prior discovery information, or a different non-compliance severity is now non-compliant with 'Critical' severity.</Description> </Message> <Message> <MessageID>11858</MessageID> <Description>Baseline CI Id %1, version %2 could not be decompressed.</Description> </Message> <Message> <MessageID>11859</MessageID> <Description>Baseline content %4 (%3), version %5 could not be decompressed.</Description> </Message> <Message> <MessageID>11860</MessageID> <Description>Internal error - cannot further process baseline CI Id %1, version %2.</Description> </Message> <Message> <MessageID>11861</MessageID> <Description>Internal error - cannot further process baseline content %4 (%3), version %5.</Description> </Message> <Message> <MessageID>11862</MessageID> <Description>Failed to launch discovery process for baseline content %4 (%3), version %5.</Description> </Message> <Message> <MessageID>11863</MessageID> <Description>Discovery process crashed for baseline content %4 (%3), version %5.</Description> </Message> <Message> <MessageID>11864</MessageID> <Description>Baseline content %4, version %5 has model violations.</Description> </Message> <Message> <MessageID>11865</MessageID> <Description>Baseline content %4, version %5 encountered one or more errors during discovery.</Description> </Message> <Message> <MessageID>11866</MessageID> <Description>Download of baseline CI Id %1, version %2 timed out.</Description> </Message> <Message> <MessageID>11867</MessageID> <Description>Download of baseline content %4 (%3), version %5 timed out.</Description> </Message> <Message> <MessageID>11900</MessageID> <Description>The task sequence execution engine successfully installed (%6) package (%5) for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11901</MessageID> <Description>The task sequence execution engine failed to install (%6) package (%5) for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11902</MessageID> <Description>The task sequence successfully installed application %5(%6) for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11903</MessageID> <Description>The task sequence failed to install application %5(%6) for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11904</MessageID> <Description>The task sequence successfully installed application %5(%6) that was specified through TS variable for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11905</MessageID> <Description>The task sequence execution engine failed to install application %5(%6) that was specified through TS variable for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11906</MessageID> <Description>The task sequence has attempted to set UDA for users: %5 with assignment mode: %6 for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11907</MessageID> <Description>The task sequence has failed to set UDA for users: %5 with assignment mode: %6 for action (%2) in the group (%3) with exit code %4.%12</Description> </Message> <Message> <MessageID>11908</MessageID> <Description>The task sequence failed to install application %5(%6) for action (%2) in the group (%3). Please update maximum run time for this task sequence and run it again.%12</Description> </Message> <Message> <MessageID>11909</MessageID> <Description>The task sequence failed to install application %5(%6) for action (%2) in the group (%3) because a 'requirement was not met' warning and per user instruction warning was treated as error with exit code %4.%12</Description> </Message> <Message> <MessageID>11910</MessageID> <Description>The execution policy for running the powershell script is specified not to verify the signature of the scripts. This is unsafe and can potentially risk running malicious scripts.%12</Description> </Message> <Message> <MessageID>12000</MessageID> <Description>The out of band management agent successfully started the configuration at (%4).%12</Description> </Message> <Message> <MessageID>12001</MessageID> <Description>The out of band management agent failed to start the configuration in action (%1) with error code %2(%3).%12</Description> </Message> <Message> <MessageID>12108</MessageID> <Description>Application "%1" failed with failure exit code of %3. User name: %2.</Description> </Message> <Message> <MessageID>12109</MessageID> <Description>Application "%1" failed to download content with error code of %3. User name: %2.</Description> </Message> <Message> <MessageID>12110</MessageID> <Description>Application "%1" failed to be evaluated with error code of %3. User name: %2.</Description> </Message> <Message> <MessageID>12111</MessageID> <Description>Application "%1" failed to launch on the client with error code of %3. Additional error message is: %4. User name: %2.</Description> </Message> <Message> <MessageID>12112</MessageID> <Description>The system failed to suspend Bitlocker before a required system restart. The error returned from the suspend operation was: %1.</Description> </Message> <Message> <MessageID>12113</MessageID> <Description>The agent failed to resume Bitlocker after a require system restart. The error returned from the resume operation was: %1.</Description> </Message> <Message> <MessageID>12114</MessageID> <Description>The computer requires a restart, and the client policy requires that Bitlocker be suspended prior to the restart.</Description> </Message> <Message> <MessageID>12115</MessageID> <Description>The computer required a restart, and Bitlocker was suspended prior to the restart. Bitlocker has been resumed after %1 attempts.</Description> </Message> <Message> <MessageID>12116</MessageID> <Description>Configuration Manager restarted the computer to complete installation of software or software updates.</Description> </Message> <Message> <MessageID>13100</MessageID> <Description>Power settings failed to apply for the following reasons:%1 For more details please refer to powermgmt.log on client.</Description> </Message> <Message> <MessageID>13101</MessageID> <Description>The power schema %1 failed to apply on the client. The error code is: [%2]. [Power Schema GUID is = %3]</Description> </Message> <Message> <MessageID>13102</MessageID> <Description>The power agent detected that there is more than one power policy applied to the machine.</Description> </Message> <Message> <MessageID>13200</MessageID> <Description> Failed to verify certificate for webservice %1</Description> </Message> <Message> <MessageID>30000</MessageID> <Description>User "%1" created a package named "%5 %3 %4 %6" (%2).%12</Description> </Message> <Message> <MessageID>30001</MessageID> <Description>User "%1" modified the Package Properties of a package named "%5 %3 %4 %6" (%2).%12</Description> </Message> <Message> <MessageID>30002</MessageID> <Description>User "%1" deleted a package named "%5 %3 %4 %6" (%2).%12</Description> </Message> <Message> <MessageID>30003</MessageID> <Description>User "%1" created a program named "%2" that belongs to a package with package ID %3.%12</Description> </Message> <Message> <MessageID>30004</MessageID> <Description>User "%1" modified a program named "%2" that belongs to a package with package ID %3.%12</Description> </Message> <Message> <MessageID>30005</MessageID> <Description>User "%1" deleted a program named "%2" that belongs to a package with package ID %3.%12</Description> </Message> <Message> <MessageID>30006</MessageID> <Description>User "%1" created a deployment named "%3" (%2) deploying program "%4".%12</Description> </Message> <Message> <MessageID>30007</MessageID> <Description>User "%1" modified the deployment properties of a deployment named "%3" (%2) deploying program "%4".%12</Description> </Message> <Message> <MessageID>30008</MessageID> <Description>User "%1" deleted a deployment named "%3" (%2) deploying program "%4".%12</Description> </Message> <Message> <MessageID>30009</MessageID> <Description>User "%1" targeted a package with package ID %2 to a distribution point on %5 at site "%4 - %6".%12</Description> </Message> <Message> <MessageID>30010</MessageID> <Description>User "%1" modified a distribution point on %5 at site "%4 - %6" for a package with package ID %2.%12</Description> </Message> <Message> <MessageID>30011</MessageID> <Description>User "%1" removed a package with package ID %2 from a distribution point on %5 at site "%4 - %6".%12</Description> </Message> <Message> <MessageID>30012</MessageID> <Description>User "%1" created secondary site "%3 - %2".%12</Description> </Message> <Message> <MessageID>30013</MessageID> <Description>User "%1" upgraded or removed secondary site "%3 - %2".%12</Description> </Message> <Message> <MessageID>30014</MessageID> <Description>User "%1" deleted (removed all records from the site database) secondary site "%3 - %2".%12</Description> </Message> <Message> <MessageID>30015</MessageID> <Description>User "%1" created a collection named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30016</MessageID> <Description>User "%1" modified the Collection Properties for a collection named "%3" (%2). This collection is currently assigned to the following ConfigMgr Administrators: %4 %12</Description> </Message> <Message> <MessageID>30017</MessageID> <Description>User "%1" deleted a collection named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30018</MessageID> <Description>User "%1" created address of type "%6" connecting site %3 to %7 on %8 with priority %9.%12</Description> </Message> <Message> <MessageID>30019</MessageID> <Description>User "%1" modified the address properties for an address of type "%6" connecting site %3 to %7 on %8 with priority %9.%12</Description> </Message> <Message> <MessageID>30020</MessageID> <Description>User "%1" deleted address of type "%6" connecting site %3 to %7 on %8 with priority %9.%12</Description> </Message> <Message> <MessageID>30021</MessageID> <Description>User "%1" created file definition "%5" at secondary site %3.%12</Description> </Message> <Message> <MessageID>30022</MessageID> <Description>User "%1" modified file definition "%5" at secondary site %3.%12</Description> </Message> <Message> <MessageID>30023</MessageID> <Description>User "%1" deleted file definition "%5" at secondary site %3.%12</Description> </Message> <Message> <MessageID>30024</MessageID> <Description>User "%1" created the property "%5" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30025</MessageID> <Description>User "%1" modified the property "%5" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30026</MessageID> <Description>User "%1" deleted the property "%5" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30027</MessageID> <Description>User "%1" created the property list "%5" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30028</MessageID> <Description>User "%1" modified the property list "%5" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30029</MessageID> <Description>User "%1" deleted the property list "%5" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30030</MessageID> <Description>User "%1" created site definition information in the site control file for site "%3 - %6" (Parent Site Code="%7").%12</Description> </Message> <Message> <MessageID>30031</MessageID> <Description>User "%1" modified site definition information in the site control file for site "%3 - %6" (Parent Site Code="%7").%12</Description> </Message> <Message> <MessageID>30032</MessageID> <Description>User "%1" deleted site definition information in the site control file for site "%3 - %6" (Parent Site Code="%7").%12</Description> </Message> <Message> <MessageID>30033</MessageID> <Description>User "%1" created component "%7" on %6 in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30034</MessageID> <Description>User "%1" modified component "%7" on %6 in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30035</MessageID> <Description>User "%1" deleted component "%7" on %6 in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30036</MessageID> <Description>User "%1" added the role of %7 to the %6 "%8" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30037</MessageID> <Description>User "%1" modified the role of the %6 "%8" as a %7 in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30038</MessageID> <Description>User "%1" deleted the role of the %6 "%8" as a %7 in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30039</MessageID> <Description>User "%1" created a configuration for the "%4" component in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30040</MessageID> <Description>User "%1" modified the configuration of the "%4" component in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30041</MessageID> <Description>User "%1" deleted the configuration of the "%4" component in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30042</MessageID> <Description>User "%1" created client component "%4" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30043</MessageID> <Description>User "%1" modified client component "%4" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30044</MessageID> <Description>User "%1" deleted client component "%4" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30045</MessageID> <Description>User "%1" created client configuration "%4" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30046</MessageID> <Description>User "%1" modified client configuration "%4" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30047</MessageID> <Description>User "%1" deleted client configuration "%4" in the site control file at site %3.%12</Description> </Message> <Message> <MessageID>30048</MessageID> <Description>User "%1" created SQL command "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30049</MessageID> <Description>User "%1" modified SQL command "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30050</MessageID> <Description>User "%1" deleted SQL command "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30051</MessageID> <Description>User "%1" created SQL Task "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30052</MessageID> <Description>User "%1" modified SQL Task "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30053</MessageID> <Description>User "%1" deleted SQL Task "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30054</MessageID> <Description>User "%1" added the site boundaries record to the site control file of site %3.%12</Description> </Message> <Message> <MessageID>30055</MessageID> <Description>User "%1" modified the site boundaries of site %3.%12</Description> </Message> <Message> <MessageID>30056</MessageID> <Description>User "%1" deleted the site boundaries record in the site control file of site %3.%12</Description> </Message> <Message> <MessageID>30057</MessageID> <Description>User "%1" created class security rights for user "%3" on object "%2". Object types: 1=Collection, 2=Package, 3=Advertisement, 4=Status Messages, 6=Site, 7=Query, 8=Report, 9=Metering Rule, 10=Software Update.%12</Description> </Message> <Message> <MessageID>30058</MessageID> <Description>User "%1" modified class security rights for user "%3" on object "%2". Object types: 1=Collection, 2=Package, 3=Advertisement, 4=Status Messages, 6=Site, 7=Query, 8=Report, 9=Metering Rule, 10=Software Update.%12</Description> </Message> <Message> <MessageID>30059</MessageID> <Description>User "%1" deleted class security rights for user "%3" on object "%2". Object types: 1=Collection, 2=Package, 3=Advertisement, 4=Status Messages, 6=Site, 7=Query, 8=Report, 9=Metering Rule, 10=Software Update.%12</Description> </Message> <Message> <MessageID>30060</MessageID> <Description>User "%1" created instance security rights for user "%3" on instance "%4" of object type "%2". Object types: 1=Collection, 2=Package, 3=Advertisement, 4=Status Messages, 6=Site, 7=Query, 8=Report, 9=Metering Rule, 10=Software Update.%12</Description> </Message> <Message> <MessageID>30061</MessageID> <Description>User "%1" modified instance security rights for user "%3" on instance "%4" of object type "%2". Object types: 1=Collection, 2=Package, 3=Advertisement, 4=Status Messages, 6=Site, 7=Query, 8=Report, 9=Metering Rule, 10=Software Update.%12</Description> </Message> <Message> <MessageID>30062</MessageID> <Description>User "%1" deleted instance security rights for user "%3" on instance "%4" of object type "%2". Object types: 1=Collection, 2=Package, 3=Advertisement, 4=Status Messages, 6=Site, 7=Query, 8=Report, 9=Metering Rule, 10=Software Update.%12</Description> </Message> <Message> <MessageID>30063</MessageID> <Description>User "%1" created a query named "%3" (%2) targeting the "%4" class.%12</Description> </Message> <Message> <MessageID>30064</MessageID> <Description>User "%1" modified a query named "%3" (%2) targeting the "%4" class.%12</Description> </Message> <Message> <MessageID>30065</MessageID> <Description>User "%1" deleted a query named "%3" (%2) targeting the "%4" class.%12</Description> </Message> <Message> <MessageID>30066</MessageID> <Description>User "%1" deleted a discovered resource named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30067</MessageID> <Description>User "%1" deleted all of the resources that belong to collection "%3" (%2).%12</Description> </Message> <Message> <MessageID>30068</MessageID> <Description>User "%1" updated a package named "%5 %3 %4 %6" (%2) to the site distribution points.%12</Description> </Message> <Message> <MessageID>30069</MessageID> <Description>User "%1" at "%2" initiated a Remote Control session with "%3".%12</Description> </Message> <Message> <MessageID>30070</MessageID> <Description>User "%1" at "%2" ended a Remote Control session with "%3".%12</Description> </Message> <Message> <MessageID>30076</MessageID> <Description>User "%1" at "%2" initiated Remote Control with "%3".%12</Description> </Message> <Message> <MessageID>30077</MessageID> <Description>User "%1" at "%2" ended Remote Control with "%3".%12</Description> </Message> <Message> <MessageID>30085</MessageID> <Description>User "%1" at "%2" failed to start a Remote Control session with "%3".%12</Description> </Message> <Message> <MessageID>30086</MessageID> <Description>User "%1" at "%2" failed to start a Remote Control session with "%3" due to insufficient security credentials.%12</Description> </Message> <Message> <MessageID>30091</MessageID> <Description>User "%1" created a report named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30092</MessageID> <Description>User "%1" modified a report named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30093</MessageID> <Description>User "%1" deleted a report named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30094</MessageID> <Description>User "%1" created a meter rule named "%7" (%3) for file "%4" with a product version of "%6" and Language ID of "%5".%12</Description> </Message> <Message> <MessageID>30095</MessageID> <Description>User "%1" modified a meter rule named "%7" (%3) for file "%4" with a product version of "%6" and Language ID of "%5".%12</Description> </Message> <Message> <MessageID>30099</MessageID> <Description>User "%1" created Maintenance Task "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30100</MessageID> <Description>User "%1" modified Maintenance Task "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30101</MessageID> <Description>User "%1" deleted Maintenance Task "%5" at site %3.%12</Description> </Message> <Message> <MessageID>30102</MessageID> <Description>User "%2" from computer "%3" created a session using application [%4] version [%5].%12</Description> </Message> <Message> <MessageID>30103</MessageID> <Description>User "%2" from computer "%3" released its session using application [%4] version [%5].%12</Description> </Message> <Message> <MessageID>30104</MessageID> <Description>User "%1" requested that the membership be refreshed for collection "%3" (%2).%12</Description> </Message> <Message> <MessageID>30105</MessageID> <Description>User "%1" deleted a meter rule named "%7" (%3) for file "%4" with a product version of "%6" and Language ID of "%5".%12</Description> </Message> <Message> <MessageID>30106</MessageID> <Description>User "%1" requested that the CCRs be generated for query named "%3" (%2) targeting the "%4" class.%12</Description> </Message> <Message> <MessageID>30107</MessageID> <Description>User "%1" requested that the CCRs be generated for collection "%3" (%2).%12</Description> </Message> <Message> <MessageID>30108</MessageID> <Description>User "%1" requested that the CCR be generated for Machine "%2" (%3).%12</Description> </Message> <Message> <MessageID>30109</MessageID> <Description>User "%1" requested that the CCRs be generated for query named "%3" (%2) targeting the "%4" class. The SMS Provider did not generate CCRs for all the system resources returned by this query.</Description> </Message> <Message> <MessageID>30110</MessageID> <Description>User "%1" requested that the CCRs be generated for collection "%3" (%2). The SMS Provider did not generate CCRs for all the system resources in this collection.</Description> </Message> <Message> <MessageID>30111</MessageID> <Description>User "%1" requested that the CCR be generated for resource "%3". But no CCR is generated.</Description> </Message> <Message> <MessageID>30112</MessageID> <Description>User "%1" has authorized a software update. Details: ID = %2, QNumbers = %3, Product = %4, Title = %5, Locale = %6.%12</Description> </Message> <Message> <MessageID>30113</MessageID> <Description>User "%1" created a folder named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30114</MessageID> <Description>User "%1" modified a folder named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30115</MessageID> <Description>User "%1" deleted a folder named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30116</MessageID> <Description>User "%1" added %3 of %4 to folder "%2".%12</Description> </Message> <Message> <MessageID>30117</MessageID> <Description>User "%1" moved %3 of %4 out of folder "%2".%12</Description> </Message> <Message> <MessageID>30118</MessageID> <Description>User "%1" added software update "%2" to program "%4" in package "%3", package version "%5".%12</Description> </Message> <Message> <MessageID>30119</MessageID> <Description>User "%1" changed the link information for software update "%2" in program "%4" and package "%3", package version "%5".%12</Description> </Message> <Message> <MessageID>30120</MessageID> <Description>User "%1" removed software update "%2" from program "%4" in package "%3", package version "%5".%12</Description> </Message> <Message> <MessageID>30121</MessageID> <Description>User "%1" created software update with CI_ID "%2". Details: ID = "%3", QNumbers = "%4", CI_UniqueID = %5, CIVersion = %6 ".%12</Description> </Message> <Message> <MessageID>30122</MessageID> <Description>User "%1" modified software update with CI_ID "%2". Details: ID = "%3", QNumbers = "%4", CI_UniqueID = %5, CIVersion = %6 ".%12</Description> </Message> <Message> <MessageID>30123</MessageID> <Description>User "%1" deleted software update with CI_ID "%2". Details: ID = "%3", QNumbers = "%4", CI_UniqueID = %5, CIVersion = %6 ".%12</Description> </Message> <Message> <MessageID>30124</MessageID> <Description>User "%1" has authorized software update "%2". Details: ID = "%3", QNumbers = "%5", Product = "%6", Title = "%4", Locale = "%7".%12</Description> </Message> <Message> <MessageID>30125</MessageID> <Description>User "%1" added new distribution points to a package named "%5 %3 %4 %6" (%2).%12</Description> </Message> <Message> <MessageID>30129</MessageID> <Description>User "%1" created device discovery translation "%2".%12</Description> </Message> <Message> <MessageID>30130</MessageID> <Description>User "%1" modified device discovery translation "%2".%12</Description> </Message> <Message> <MessageID>30131</MessageID> <Description>User "%1" deleted device discovery translation "%2".%12</Description> </Message> <Message> <MessageID>30132</MessageID> <Description>User "%1" created an instance of SMS_DeviceFQDN "%2".%12</Description> </Message> <Message> <MessageID>30133</MessageID> <Description>User "%1" modified an instance of SMS_DeviceFQDN "%2".%12</Description> </Message> <Message> <MessageID>30134</MessageID> <Description>User "%1" deleted an instance of SMS_DeviceFQDN "%2".%12</Description> </Message> <Message> <MessageID>30135</MessageID> <Description>User "%1" created relation "%3" between software update "%2" and software update "%4".%12</Description> </Message> <Message> <MessageID>30136</MessageID> <Description>User "%1" changed relation "%3" between software update "%2" and software update "%4".%12</Description> </Message> <Message> <MessageID>30137</MessageID> <Description>User "%1" removed relation "%3" between software update "%2" and software update "%4".%12</Description> </Message> <Message> <MessageID>30138</MessageID> <Description>User "%1" has created an instance of SMS_ScanTool. SMSScanToolID =%2 ToolName=%3.%12</Description> </Message> <Message> <MessageID>30139</MessageID> <Description>User "%1" has modified an instance of SMS_ScanTool. SMSScanToolID =%2 ToolName=%3.%12</Description> </Message> <Message> <MessageID>30140</MessageID> <Description>User "%1" has deleted an instance of SMS_ScanTool. SMSScanToolID =%2 ToolName=%3.%12</Description> </Message> <Message> <MessageID>30152</MessageID> <Description>User "%1" created configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30153</MessageID> <Description>User "%1" modified configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30154</MessageID> <Description>User "%1" deleted configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30155</MessageID> <Description>User "%1" enforced configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30156</MessageID> <Description>User "%1" unenforced configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30157</MessageID> <Description>User "%1" accepted the license terms for configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30158</MessageID> <Description>User "%1" declined the license terms for configuration item "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30159</MessageID> <Description>User "%1" created a CategoryInstance "%2" (LocalizedCategoryInstanceName=%3, CategoryTypeName=%4). .%12</Description> </Message> <Message> <MessageID>30160</MessageID> <Description>User "%1" modified a CategoryInstance "%2" (LocalizedCategoryInstanceName=%3, CategoryTypeName=%4). .%12</Description> </Message> <Message> <MessageID>30161</MessageID> <Description>User "%1" deleted CategoryInstance "%2" (LocalizedCategoryInstanceName=%3, CategoryTypeName=%4). .%12</Description> </Message> <Message> <MessageID>30162</MessageID> <Description>User "%1" created a CategoryInstance Membership (CategoryInstanceID(%2),ObjectType(%3),ObjectKey(%4)). .%12</Description> </Message> <Message> <MessageID>30163</MessageID> <Description>User "%1" delete a CategoryInstance Membership (CategoryName(%2), ObjectType(%3), ObjectName(%4)). .%12</Description> </Message> <Message> <MessageID>30165</MessageID> <Description>User "%1" created a license terms Content "%2" (license terms ContentUniqueID=%3). .%12</Description> </Message> <Message> <MessageID>30166</MessageID> <Description>User "%1" modified a license terms Content "%2" (license terms ContentUniqueID=%3). .%12</Description> </Message> <Message> <MessageID>30167</MessageID> <Description>User "%1" deleted license terms Content "%2" (license terms ContentUniqueID=%3). .%12</Description> </Message> <Message> <MessageID>30168</MessageID> <Description>User "%1" resend configuration item "%2" (CI_UniqueID=%3, CIVersion=%4) to all child sites. .%12</Description> </Message> <Message> <MessageID>30169</MessageID> <Description>User "%1" resend a CategoryInstance "%2" (CategoryInstance_UniqueID=%3, CategoryTypeName=%4) to all child sites. .%12</Description> </Message> <Message> <MessageID>30170</MessageID> <Description>User "%1" resend a SDMPackage "%2" (SDMPackageName=%3, SDMPackageVersion=%4) to all child sites. .%12</Description> </Message> <Message> <MessageID>30171</MessageID> <Description>User "%1" resend a license terms Content "%2" (license terms ContentUniqueID=%3) to all child sites. .%12</Description> </Message> <Message> <MessageID>30172</MessageID> <Description>User "%1" resend software update with CI_ID "%2" to all child sites. Update Details: ID = "%3", QNumbers = "%4", CI_UniqueID = %5, CIVersion = %6 ".%12</Description> </Message> <Message> <MessageID>30173</MessageID> <Description>User "%1" has resend an instance of SMS_ScanTool to all child sites. SMSScanToolID =%2 ToolName=%3.%12</Description> </Message> <Message> <MessageID>30180</MessageID> <Description>User "%1" created a state association between sourceclient (%2) and restoreclient (%3).%12</Description> </Message> <Message> <MessageID>30181</MessageID> <Description>User "%1" deleted a state association between sourceclient (%2) and restoreclient (%3).%12</Description> </Message> <Message> <MessageID>30183</MessageID> <Description>User "%1" attempted to download the content for software update with CI_ID "%2". Update Details: ID = "%3", QNumbers = "%4", CI_UniqueID = %5, CIVersion = %6 ".%12</Description> </Message> <Message> <MessageID>30185</MessageID> <Description>User "%1" attempted to import the content for software update with CI_ID "%2". Update Details: ID = "%3", QNumbers = "%4", CI_UniqueID = %5, CIVersion = %6 ".%12</Description> </Message> <Message> <MessageID>30186</MessageID> <Description>User "%1" created the SUM deployment template with TemplateUniqueID "%2" (Name = "%3"). .%12</Description> </Message> <Message> <MessageID>30187</MessageID> <Description>User "%1" modified the SUM deployment template with TemplateUniqueID "%2" (Name = "%3"). .%12</Description> </Message> <Message> <MessageID>30188</MessageID> <Description>User "%1" deleted the SUM deployment template with TemplateUniqueID "%2" (Name = "%3"). .%12</Description> </Message> <Message> <MessageID>30189</MessageID> <Description>User "%1" added content with ContentID %2 to PackageID "%3" (ContentVersionInPkg = %4). .%12</Description> </Message> <Message> <MessageID>30190</MessageID> <Description>User "%1" modified content with ContentID %2 in PackageID "%3 (ContentVersionInPkg = %4)". .%12</Description> </Message> <Message> <MessageID>30191</MessageID> <Description>User "%1" removed content with ContentID %2 from PackageID "%3". .%12</Description> </Message> <Message> <MessageID>30192</MessageID> <Description>User "%1" initiated a package change notification for Package named "%5 %3 %4 %6" (%2).%12</Description> </Message> <Message> <MessageID>30193</MessageID> <Description>User "%1" created CI assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30194</MessageID> <Description>User "%1" modified CI assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30195</MessageID> <Description>User "%1" deleted CI assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30196</MessageID> <Description>User "%1" created updates assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30197</MessageID> <Description>User "%1" modified updates assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30198</MessageID> <Description>User "%1" deleted updates assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30199</MessageID> <Description>User "%1" created an instance of SMS_DeviceSettingItem %2 (Name = %3, Type = %4, Version = %5). .%12</Description> </Message> <Message> <MessageID>30200</MessageID> <Description>User "%1" modified an instance of SMS_DeviceSettingItem %2 (Name = %3, Type = %4, Version = %5). .%12</Description> </Message> <Message> <MessageID>30201</MessageID> <Description>User "%1" deleted an instance of SMS_DeviceSettingItem %2 (Name = %3, Type = %4, Version = %5). .%12</Description> </Message> <Message> <MessageID>30202</MessageID> <Description>User "%1" created an instance of SMS_DeviceSettingPackage %2 (Name = %3, PlatformType = %4, Version = %5). .%12</Description> </Message> <Message> <MessageID>30203</MessageID> <Description>User "%1" modified an instance of SMS_DeviceSettingPackage %2 (Name = %3, PlatformType = %4, Version = %5). .%12</Description> </Message> <Message> <MessageID>30204</MessageID> <Description>User "%1" deleted an instance of SMS_DeviceSettingPackage %2 (Name = %3, PlatformType = %4, Version = %5). .%12</Description> </Message> <Message> <MessageID>30205</MessageID> <Description>User "%1" created an instance of SMS_DeviceSettingPackageItem (DeviceSettingPkgID = %2, DeviceSettingItemID = %3). .%12</Description> </Message> <Message> <MessageID>30206</MessageID> <Description>User "%1" modified an instance of SMS_DeviceSettingPackageItem (DeviceSettingPkgID = %2, DeviceSettingItemID = %3). .%12</Description> </Message> <Message> <MessageID>30207</MessageID> <Description>User "%1" deleted an instance of SMS_DeviceSettingPackageItem (DeviceSettingPkgID = %2, DeviceSettingItemID = %3). .%12</Description> </Message> <Message> <MessageID>30208</MessageID> <Description>User "%1" modified summary task (%2) (RunInterval=%3 Enabled=%4 TaskParameter=%5). .%12</Description> </Message> <Message> <MessageID>30209</MessageID> <Description>User "%1" requested to execute summary task (%2). .%12</Description> </Message> <Message> <MessageID>30210</MessageID> <Description>User "%1" created user account %6. .%12</Description> </Message> <Message> <MessageID>30211</MessageID> <Description>User "%1" modified user account %6. .%12</Description> </Message> <Message> <MessageID>30212</MessageID> <Description>User "%1" deleted user account %6. .%12</Description> </Message> <Message> <MessageID>30213</MessageID> <Description>User "%1" imported machine at site "%3 - %2" (NetbiosName=%4, MACAddress=%5, SMBIOSGUID=%6).%12</Description> </Message> <Message> <MessageID>30214</MessageID> <Description>User "%1" submitted a registration record at site "%3 - %2" (SMSID=%4).%12</Description> </Message> <Message> <MessageID>30215</MessageID> <Description>User "%1" received policies for Task Sequence %3 using Deployment "%2".%12</Description> </Message> <Message> <MessageID>30216</MessageID> <Description>User "%1" received client configuration policies.%12</Description> </Message> <Message> <MessageID>30217</MessageID> <Description>User "%1" changed the Approved Status to %2 for %3 clients. ResourceIDs (%4).%12</Description> </Message> <Message> <MessageID>30218</MessageID> <Description>User "%1" changed the Allowed Status to %2 for %3 clients. ResourceIDs (%4).%12</Description> </Message> <Message> <MessageID>30219</MessageID> <Description>User "%1" created authorization list "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30220</MessageID> <Description>User "%1" modified authorization list "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30221</MessageID> <Description>User "%1" deleted authorization list "%2" (CI_UniqueID=%3, CIVersion=%4). .%12</Description> </Message> <Message> <MessageID>30222</MessageID> <Description>User "%1" created per-computer settings for %3 (ResourceID %2).%12</Description> </Message> <Message> <MessageID>30223</MessageID> <Description>User "%1" modified per-computer settings for %3 (ResourceID %2).%12</Description> </Message> <Message> <MessageID>30224</MessageID> <Description>User "%1" changed the Block Status to %2 for Certificate (SMSID=%3).%12</Description> </Message> <Message> <MessageID>30225</MessageID> <Description>User "%1" resolved the pending registration record (SMSID=%2, FQDN=%3, ConflictSMSID=%4, Action=%5).%12</Description> </Message> <Message> <MessageID>30226</MessageID> <Description>User "%1" created a deployment of application "%3" to collection "%4".%12</Description> </Message> <Message> <MessageID>30227</MessageID> <Description>User "%1" modified the deployment of application "%3" to collection "%4".%12</Description> </Message> <Message> <MessageID>30228</MessageID> <Description>User "%1" deleted the deployment of application "%3" to collection "%4".%12</Description> </Message> <Message> <MessageID>30229</MessageID> <Description>User "%1" created update group assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30230</MessageID> <Description>User "%1" modified update group assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30231</MessageID> <Description>User "%1" deleted update group assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>30232</MessageID> <Description>User "%1" created per-user settings for %3 (ResourceID %2).%12</Description> </Message> <Message> <MessageID>30233</MessageID> <Description>User "%1" modified per-user settings for %3 (ResourceID %2).%12</Description> </Message> <Message> <MessageID>30234</MessageID> <Description>User "%1" changed the Ownership Type to %2 for %3 clients. ResourceIDs (%4).%12</Description> </Message> <Message> <MessageID>30235</MessageID> <Description>User "%1" changed the site to %2 for %3 clients. ResourceIDs (%4).%12</Description> </Message> <Message> <MessageID>30240</MessageID> <Description>User "%1" created alert (ID=%2, Type=%3, Instance=%4, Enabled=%5, SkipUntil=%6).%12</Description> </Message> <Message> <MessageID>30241</MessageID> <Description>User "%1" modified alert (ID=%2, Type=%3, Instance=%4, Enabled=%5, SkipUntil=%6).%12</Description> </Message> <Message> <MessageID>30242</MessageID> <Description>User "%1" deleted alert (ID=%2, Type=%3, Instance=%4).%12</Description> </Message> <Message> <MessageID>30243</MessageID> <Description>User "%1" set SkipUntil of alert (ID=%2, Type=%3, Instance=%4).%12</Description> </Message> <Message> <MessageID>30244</MessageID> <Description>User "%1" closed alert (ID=%2, Type=%3, Instance=%4).%12</Description> </Message> <Message> <MessageID>30300</MessageID> <Description>User "%1" at "%2" started an OOB Console session to "%3".%12</Description> </Message> <Message> <MessageID>30301</MessageID> <Description>User "%1" at "%2" attempt to disconnect from "%3". Success.%12</Description> </Message> <Message> <MessageID>30302</MessageID> <Description>User "%1" at "%2" attempt to perform a status information query from "%3". Success.%12</Description> </Message> <Message> <MessageID>30303</MessageID> <Description>User "%1" at "%2" attempt to perform a system inventory query from "%3". Success.%12</Description> </Message> <Message> <MessageID>30304</MessageID> <Description>User "%1" at "%2" attempt to perform a power control command to "%3". Success.%12</Description> </Message> <Message> <MessageID>30305</MessageID> <Description>User "%1" at "%2" attempt to perform a serial over lan session to "%3". Success.%12</Description> </Message> <Message> <MessageID>30306</MessageID> <Description>User "%1" at "%2" attempt to perform a IDE-R session to "%3". Success.%12</Description> </Message> <Message> <MessageID>30307</MessageID> <Description>User "%1" at "%2" attempt to unprovision "%3". Success.%12</Description> </Message> <Message> <MessageID>30308</MessageID> <Description>User "%1" at "%2" has no permission to connect "%3". Success.%12</Description> </Message> <Message> <MessageID>30309</MessageID> <Description>User "%1" at "%2" attempt to connect to "%3".%12</Description> </Message> <Message> <MessageID>30310</MessageID> <Description>User "%1" at "%2" attempt to perform a IDE-R session to "%3", but IDE-R session to this device has already been opened .%12</Description> </Message> <Message> <MessageID>30311</MessageID> <Description>User "%1" at "%2" failed to perform a status information query from "%3". WinRM error code: "%4"; PT error code: "%5"; IMR error code: "%6".%12</Description> </Message> <Message> <MessageID>30312</MessageID> <Description>User "%1" at "%2" failed to perform a system inventory query from "%3". WinRM error code: "%4"; PT error code: "%5"; IMR error code: "%6".%12</Description> </Message> <Message> <MessageID>30313</MessageID> <Description>User "%1" at "%2" failed to perform a power control command to "%3". WinRM error code: "%4"; PT error code: "%5"; IMR error code: "%6".%12</Description> </Message> <Message> <MessageID>30314</MessageID> <Description>User "%1" at "%2" failed to perform a serial over lan session to "%3". WinRM error code: "%4"; PT error code: "%5"; IMR error code: "%6".%12</Description> </Message> <Message> <MessageID>30315</MessageID> <Description>User "%1" at "%2" failed to perform a IDE-R session to "%3". WinRM error code: "%4"; PT error code: "%5"; IMR error code: "%6".%12</Description> </Message> <Message> <MessageID>30316</MessageID> <Description>User "%1" at "%2" failed to unprovision "%3". WinRM error code: "%4"; PT error code: "%5"; IMR error code: "%6".%12</Description> </Message> <Message> <MessageID>30317</MessageID> <Description>User "%1" at "%2" failed to disconnect from "%3".%12</Description> </Message> <Message> <MessageID>30318</MessageID> <Description>User "%1" at "%2" failed to connect to "%3".%12</Description> </Message> <Message> <MessageID>30319</MessageID> <Description>User "%1" at "%2" failed to connect to special resource %3 in this site.%12</Description> </Message> <Message> <MessageID>30320</MessageID> <Description>User "%1" at "%2" failed to perform a status information query from "%3". Internal exception occurs.%12</Description> </Message> <Message> <MessageID>30321</MessageID> <Description>User "%1" at "%2" failed to perform a system inventory query from "%3". Internal exception occurs.%12</Description> </Message> <Message> <MessageID>30322</MessageID> <Description>User "%1" at "%2" failed to perform a power control command to "%3". Internal exception occurs.%12</Description> </Message> <Message> <MessageID>30323</MessageID> <Description>User "%1" at "%2" failed to perform a serial over lan session to "%3". Internal exception occurs.%12</Description> </Message> <Message> <MessageID>30324</MessageID> <Description>User "%1" at "%2" failed to perform a IDE-R session to "%3". Internal exception occurs.%12</Description> </Message> <Message> <MessageID>30325</MessageID> <Description>User "%1" at "%2" failed to unprovision "%3". Internal exception occurs.%12</Description> </Message> <Message> <MessageID>30326</MessageID> <Description>User "%1" created a remote application subscription ID (%2).%12</Description> </Message> <Message> <MessageID>30327</MessageID> <Description>User "%1" modified a remote application subscription ID (%2).%12</Description> </Message> <Message> <MessageID>30328</MessageID> <Description>User "%1" deleted a remote application subscription ID (%2).%12</Description> </Message> <Message> <MessageID>30330</MessageID> <Description>User "%1" created a virtual App named %4 (VirtualAppID = %2) for the Package(%3).%12</Description> </Message> <Message> <MessageID>30331</MessageID> <Description>User "%1" modified a virtual App named %4 (VirtualAppID = %2) for the Package(%3).%12</Description> </Message> <Message> <MessageID>30332</MessageID> <Description>User "%1" deleted a virtual App named %4 (VirtualAppID = %2) for the Package(%3).%12</Description> </Message> <Message> <MessageID>30400</MessageID> <Description>User "%1" changed the AMT Status to %2 for AMT Certificate (CertID=%3).%12</Description> </Message> <Message> <MessageID>30401</MessageID> <Description>User "%1" initiated "Power on" command on "%3" (%2) .%12</Description> </Message> <Message> <MessageID>30402</MessageID> <Description>User "%1" initiated "Restart" command on "%3" (%2).%12</Description> </Message> <Message> <MessageID>30403</MessageID> <Description>User "%1" initiated "Shut down" command on "%3" (%2).%12</Description> </Message> <Message> <MessageID>30404</MessageID> <Description>User "%1" enabled Audit Log on "%3" (%2).%12</Description> </Message> <Message> <MessageID>30405</MessageID> <Description>User "%1" disabled Audit Log on "%3" (%2).%12</Description> </Message> <Message> <MessageID>30406</MessageID> <Description>User "%1" cleared Audit Log on "%3" (%2).%12</Description> </Message> <Message> <MessageID>30407</MessageID> <Description>User "%1" updates the provision data on machine "%3" (%2).%12</Description> </Message> <Message> <MessageID>30408</MessageID> <Description>User "%1" unprovisioned machine "%3" (%2).%12</Description> </Message> <Message> <MessageID>30409</MessageID> <Description>User "%1" initiated "Discover" command on "%3" (%2).%12</Description> </Message> <Message> <MessageID>30500</MessageID> <Description>User added the following distribution points to a package (Package ID=%1): %2</Description> </Message> <Message> <MessageID>30501</MessageID> <Description>User removed the distribution point (NALPATH=%2) from package (Package ID=%1).</Description> </Message> <Message> <MessageID>30502</MessageID> <Description>User Refreshed the distribution point (NALPATH=%2) of package (Package ID=%1).</Description> </Message> <Message> <MessageID>30503</MessageID> <Description>User updated the following distribution points of package (Package ID=%1): %2</Description> </Message> <Message> <MessageID>30504</MessageID> <Description>User updated the schedule of Deployment (ID=%1), PresentTime and ExpirationTime were changed from %2 to %3, mandatory schedule and offer flags changed from %4 to %5.</Description> </Message> <Message> <MessageID>30505</MessageID> <Description>User updated the target collection of Deployment (ID=%1), Collection ID was changed from %2 to %3.</Description> </Message> <Message> <MessageID>30506</MessageID> <Description>User updated the schedule of SUM (ID=%1), PresentTime and ExpirationTime were changed from %2 to %3.</Description> </Message> <Message> <MessageID>30507</MessageID> <Description>User updated the target collection of SUM (ID=%1), Collection ID was changed from %2 to %3.</Description> </Message> <Message> <MessageID>30600</MessageID> <Description>User "%1" created relationship (ID=%2) between machine %3 and user %4.%12</Description> </Message> <Message> <MessageID>30601</MessageID> <Description>User "%1" modified relationship (ID=%2) between machine %3 and user %4.%12</Description> </Message> <Message> <MessageID>30602</MessageID> <Description>User "%1" deleted relationship (ID=%2) between machine %3 and user %4.%12</Description> </Message> <Message> <MessageID>30603</MessageID> <Description>User "%1" added a source (SourceID=%2) for relationship (ID=%3) between machine %4 and user %5.%12</Description> </Message> <Message> <MessageID>30604</MessageID> <Description>User "%1" removed a source (SourceID=%2) for relationship (ID=%3) between machine %4 and user %5.%12</Description> </Message> <Message> <MessageID>30605</MessageID> <Description>User "%1" added a type (TypeID=%2) for relationship (ID=%3) between machine %4 and user %5.%12</Description> </Message> <Message> <MessageID>30606</MessageID> <Description>User "%1" removed a type (TypeID=%2) for relationship (ID=%3) between machine %4 and user %5.%12</Description> </Message> <Message> <MessageID>30700</MessageID> <Description>User "%1" created a search folder named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30701</MessageID> <Description>User "%1" modified a search folder named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30702</MessageID> <Description>User "%1" deleted a search folder named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30800</MessageID> <Description>Administrative user %1 approved request of application %2 for user %3.%12</Description> </Message> <Message> <MessageID>30801</MessageID> <Description>Administrative user %1 denied request of application %2 for user %3.%12</Description> </Message> <Message> <MessageID>30900</MessageID> <Description>User "%1" created a migration job named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30901</MessageID> <Description>User "%1" modified a migration job named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30902</MessageID> <Description>User "%1" deleted a migration job named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30903</MessageID> <Description>User "%1" started a migration job named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30904</MessageID> <Description>User "%1" stopped a migration job named "%3" (%2).%12</Description> </Message> <Message> <MessageID>30905</MessageID> <Description>User "%1" created a migration site mapping with ID "%3" (%2).%12</Description> </Message> <Message> <MessageID>30906</MessageID> <Description>User "%1" modified a migration site mapping with ID "%3" (%2).%12</Description> </Message> <Message> <MessageID>30907</MessageID> <Description>User "%1" deleted a migration site mapping with ID "%3" (%2).%12</Description> </Message> <Message> <MessageID>31000</MessageID> <Description>User "%1" created an inventory report with ID "%2".%12</Description> </Message> <Message> <MessageID>31001</MessageID> <Description>User "%1" modified an inventory report with ID "%2".%12</Description> </Message> <Message> <MessageID>31002</MessageID> <Description>User "%1" deleted an inventory report with ID "%2".%12</Description> </Message> <Message> <MessageID>31200</MessageID> <Description>Administrative user %1 successfully created a custom security role %3.%12</Description> </Message> <Message> <MessageID>31201</MessageID> <Description>Administrative user %1 successfully modified security role %2.%12</Description> </Message> <Message> <MessageID>31202</MessageID> <Description>Administrative user %1 successfully deleted a custom security role %2.%12</Description> </Message> <Message> <MessageID>31203</MessageID> <Description>Administrative user %1 tried to create a custom security role but does not have sufficient permissions. User %1 requires at least "Create role" permissions.%12</Description> </Message> <Message> <MessageID>31204</MessageID> <Description>Administrative user %1 tried to modify a custom security role but does not have sufficient permissions. User %1 requires at least "Modify role" permissions.%12</Description> </Message> <Message> <MessageID>31205</MessageID> <Description>Administrative user %1 tried to delete a custom role but does not have sufficient permissions. User %1 requires at least "Delete role" permissions.%12</Description> </Message> <Message> <MessageID>31206</MessageID> <Description>Administrative user %1 was not allowed to import a security role, due to insufficient permissions. User %1 requires at least "Create role" permission.%12</Description> </Message> <Message> <MessageID>31207</MessageID> <Description>Administrative user %1 has successfully imported custom security role %2.%12</Description> </Message> <Message> <MessageID>31208</MessageID> <Description>Administrative user %1 successfully exported security role %2.%12</Description> </Message> <Message> <MessageID>31209</MessageID> <Description>Administrative user %1 tried to export security role %2 but has insufficient rights. User %1 requires at least "read role" permission.%12</Description> </Message> <Message> <MessageID>31220</MessageID> <Description>Administrative user %1 successfully created the new security scope %2.%12</Description> </Message> <Message> <MessageID>31221</MessageID> <Description>Administrative user %1 successfully modified security scope %2.%12</Description> </Message> <Message> <MessageID>31222</MessageID> <Description>Administrative user %1 successfully deleted security scope %2.%12</Description> </Message> <Message> <MessageID>31223</MessageID> <Description>Administrative user %1 was not allowed to create a new security scope due to insufficient permissions. User %1 requires at least "Create security scope" permission.%12</Description> </Message> <Message> <MessageID>31224</MessageID> <Description>Administrative user %1 was not allowed to modify security scope %2 due to insufficient permission. User %1 requires at least "Modify security scope" permission.%12</Description> </Message> <Message> <MessageID>31225</MessageID> <Description>Administrative user %1 was not allowed to delete security scope %2 due to insufficient permissions. User %1 requires at least "Delete security scope" permission.%12</Description> </Message> <Message> <MessageID>31226</MessageID> <Description>User %1 associated securable object %4 (Type: %3) with the following security scope: %2.%12</Description> </Message> <Message> <MessageID>31227</MessageID> <Description>User %1 deassociated securable object %4 (Type: %3) with the following security scope: %2.%12</Description> </Message> <Message> <MessageID>31240</MessageID> <Description>Administrative user %1 has successfully added and associated %3 with the roles %4 and security scopes %5 and collections %6 to the Configuration Manager environment.%12</Description> </Message> <Message> <MessageID>31241</MessageID> <Description>User "%1" modified and associated %3 with the roles %4 and security scopes %5 and collections %6 to the Configuration Manager environment.%12</Description> </Message> <Message> <MessageID>31242</MessageID> <Description>Administrative user %1 has successfully removed %3 from the Configuration Manager environment.%12</Description> </Message> <Message> <MessageID>31243</MessageID> <Description>The Configuration Manager provider on server "%1" was unable to connect to Active Directory domain controller "%2" (result code: "%3"), as a result user %4 was unable to add a Configuration Manager administrator user or group to the Configuration Manager environment. Please check the Windows event log on the Configuration Manager provider machine and Active Directory domain controllers.%12</Description> </Message> <Message> <MessageID>31244</MessageID> <Description>Administrative user %1 failed to add a new Configuration Manager administrator user or security group in the Configuration Manager environment due to insufficient rights. User %1 requires at least "Add administrator" and "Read role" permissions.%12</Description> </Message> <Message> <MessageID>31245</MessageID> <Description>Administrative user %1 failed to modify a new Configuration Manager administrator user or security group in the Configuration Manager environment due to insufficient rights. User %1 requires at least "Modify administrator" and "Read role" permissions.%12</Description> </Message> <Message> <MessageID>31246</MessageID> <Description>Administrative user %1 failed to remove a Configuration Manager administrator user or security group from the Configuration Manager environment, due to insufficient rights. User %1 requires at least "Remove administrator" permissions.%12</Description> </Message> <Message> <MessageID>31247</MessageID> <Description>Administrative user %1 tried to remove his or her own account from Configuration Manager. An administrator cannot remove his or her own account from Configuration Manager.%12</Description> </Message> <Message> <MessageID>31248</MessageID> <Description>Administrative user %1 tried to remove Configuration Manager administrator %2 which is the last Configuration Manager administrator associated with the "ConfigMgr Administrator" security role. The Configuration Manager environment requires at least 1 user or security group associated with the "ConfigMgr Administrator" security role.%12</Description> </Message> <Message> <MessageID>31249</MessageID> <Description>The Configuration Manager provider on server "%1" was unable to add user or group "%2", to the "SMS Admins" security group on server "%1". Please manually add user or group "%2" to the "SMS Admins" security group on server "%1", to enable user or group "%2" to administer the Configuration Manager environment.%12</Description> </Message> <Message> <MessageID>39997</MessageID> <Description>%1%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>39998</MessageID> <Description>%1%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>39999</MessageID> <Description>%1%12%2%3%4%5%6%7%8%9%10</Description> </Message> <Message> <MessageID>40100</MessageID> <Description>User "%1" modified Client Health Settings.%12</Description> </Message> <Message> <MessageID>40200</MessageID> <Description>User "%1" created enrollment record (Device Name=%2) for owner %3.%12</Description> </Message> <Message> <MessageID>40201</MessageID> <Description>User "%1" modified enrollment record (Device Name=%2, Owner=%3).%12</Description> </Message> <Message> <MessageID>40202</MessageID> <Description>User "%1" deleted enrollment record (Device Name=%2, Owner=%3).%12</Description> </Message> <Message> <MessageID>40203</MessageID> <Description>User "%1" regenerated pin for enrollment record (Device Name=%2, Owner=%3).%12</Description> </Message> <Message> <MessageID>40204</MessageID> <Description>User "%1" created enrollment profile (ProfileID=%2, Description=%3) for owner %3.%12</Description> </Message> <Message> <MessageID>40205</MessageID> <Description>User "%1" modified enrollment profile (ProfileID=%2, Description=%3).%12</Description> </Message> <Message> <MessageID>40206</MessageID> <Description>User "%1" deleted enrollment profile (ProfileID=%2, Description=%3).%12</Description> </Message> <Message> <MessageID>40300</MessageID> <Description>User "%1" created client settings object (ID=%2).%12</Description> </Message> <Message> <MessageID>40301</MessageID> <Description>User "%1" modified client settings object (ID=%2).%12</Description> </Message> <Message> <MessageID>40302</MessageID> <Description>User "%1" deleted client settings object (ID=%2).%12</Description> </Message> <Message> <MessageID>40303</MessageID> <Description>User "%1" created client settings assignment (SettingsID=%2, CollectionID=%3).%12</Description> </Message> <Message> <MessageID>40304</MessageID> <Description>User "%1" modified client settings assignment (SettingsID=%2, CollectionID=%3).%12</Description> </Message> <Message> <MessageID>40305</MessageID> <Description>User "%1" deleted client settings assignment (SettingsID=%2, CollectionID=%3).%12</Description> </Message> <Message> <MessageID>40400</MessageID> <Description>User "%1" created Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40401</MessageID> <Description>User "%1" modified Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40402</MessageID> <Description>User "%1" deleted Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40403</MessageID> <Description>User "%1" added one or more packages or applications to the Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40404</MessageID> <Description>User "%1" removed one or more packages or applications from the Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40405</MessageID> <Description>User "%1" added one or more distribution points to the Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40406</MessageID> <Description>User "%1" removed one or more distribution points from the Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40407</MessageID> <Description>User "%1" associated one or more collections to the Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40408</MessageID> <Description>User "%1" removed one or more collections associated with the Distribution Point Group "%3".%12</Description> </Message> <Message> <MessageID>40409</MessageID> <Description>User "%1" cancelled distribution of package "%2" to distribution point "%3".</Description> </Message> <Message> <MessageID>40500</MessageID> <Description>User "%1" created Boundary Group "%3".%12</Description> </Message> <Message> <MessageID>40501</MessageID> <Description>User "%1" modified Boundary Group "%3".%12</Description> </Message> <Message> <MessageID>40502</MessageID> <Description>User "%1" deleted Boundary Group "%3".%12</Description> </Message> <Message> <MessageID>40600</MessageID> <Description>User "%1" created Boundary "%3".%12</Description> </Message> <Message> <MessageID>40601</MessageID> <Description>User "%1" modified Boundary "%3".%12</Description> </Message> <Message> <MessageID>40602</MessageID> <Description>User "%1" deleted Boundary "%3".%12</Description> </Message> <Message> <MessageID>40700</MessageID> <Description>User "%1" created configuration policy assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>40701</MessageID> <Description>User "%1" modified configuration policy assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>40702</MessageID> <Description>User "%1" deleted configuration policy assignment %2 (%3). .%12</Description> </Message> <Message> <MessageID>40800</MessageID> <Description>User %1 initiated client operation %3 to collection %2.%12</Description> </Message> <Message> <MessageID>40801</MessageID> <Description>User %1 initiated client operation %3 to %4 members of collection %2.%12</Description> </Message> <Message> <MessageID>40802</MessageID> <Description>User %1 initiated client operation %3 to %4 resources.%12</Description> </Message> <Message> <MessageID>40803</MessageID> <Description>User %1 cancelled client operation %2.%12</Description> </Message> <Message> <MessageID>40804</MessageID> <Description>User %1 deleted client operation %2.%12</Description> </Message> <Message> <MessageID>40850</MessageID> <Description>User %1 invoked action (Name=%2) for device (ResourceId=%3, ResourceType=%4).%12</Description> </Message> <Message> <MessageID>40900</MessageID> <Description>User %1 modified Site [%2] RCM SQL Control Property for DVIEW %3.%12</Description> </Message> <Message> <MessageID>41000</MessageID> <Description>User "%1" created side loading key %2 (%3) . .%12</Description> </Message> <Message> <MessageID>41001</MessageID> <Description>User "%1" modified side loading key %2 (%3) . .%12</Description> </Message> <Message> <MessageID>41002</MessageID> <Description>User "%1" deleted side loading key %2 (%3). .%12</Description> </Message> <Message> <MessageID>42000</MessageID> <Description>User %1 requested retire for a device. ResourceId: %2.%12</Description> </Message> <Message> <MessageID>42001</MessageID> <Description>User %1 requested wipe for a device. ResourceId: %2.%12</Description> </Message> <Message> <MessageID>42010</MessageID> <Description>Administrative user %1 clicked Enable action for the extension Feature %2 %3.%12</Description> </Message> <Message> <MessageID>42011</MessageID> <Description>Administrative user %1 clicked Disable action for the extension Feature %2 %3.%12</Description> </Message> <MessageSolution> <MessageID>-2147012894</MessageID> <Description>The request has timed out.</Description> </MessageSolution> <MessageSolution> <MessageID>2554</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>2600</MessageID> <Description>Possible cause: SQL Server problem on this site or one or more secondary sites. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2601</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2605</MessageID> <Description>Possible cause: Low disk space on the disk drive of the Data Loader inbox. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2606</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2608</MessageID> <Description>Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2609</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2610</MessageID> <Description>Possible cause: Low memory. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2612</MessageID> <Description>Possible cause: Refer to the previous SMS Discovery Data Manager message.</Description> </MessageSolution> <MessageSolution> <MessageID>2613</MessageID> <Description>Possible cause: The file "%1" is corrupt. Solution: Delete file "%1". Possible cause: Low memory. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2614</MessageID> <Description>Possible cause: The file "%1" is corrupt. Solution: Delete file "%1". Possible cause: Low memory. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2615</MessageID> <Description>Possible cause: The file "%1" is corrupt. Solution: Delete file "%1". Possible cause: Low memory. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2616</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2617</MessageID> <Description>Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2618</MessageID> <Description>Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2619</MessageID> <Description>Possible cause: Low disk space on the disk drive of the destination site server. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2620</MessageID> <Description>Possible cause: Low memory. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2621</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2622</MessageID> <Description>Possible cause: an SMS Discovery Data Manager bug. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. Possible cause: Something other than SMS created the DDR, and no value was specified as the Name. Solution: Every discovery item needs to have some value that can be identified as the name of the resource. In System DDRs, for example, one of the following values is used as the Name: NetBIOS Name, Resource Names, IP Addresses, IPX Addresses, or MAC Addresses. If none of these are available, or if you have created a DDR of a new architecture, then pick a property and flag it as the Name by ORing decimal 64 in the property's Flags column.</Description> </MessageSolution> <MessageSolution> <MessageID>2623</MessageID> <Description>Solution: Increase the number of client access licenses. You can purchase more from your Microsoft sales representative.</Description> </MessageSolution> <MessageSolution> <MessageID>2624</MessageID> <Description>Possible cause: The file is corrupt. Solution: See if an .ncf file exists in the directory Inboxes\Ddm.box\Data.col. If so, delete it. The site control file will recreate it. If there is no .ncf file in that directory, stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2625</MessageID> <Description>Possible cause: The file is corrupt. Solution: See if an .ncf file exists in the directory Inboxes\Ddm.box\Data.col. If so, delete it. The site control file will recreate it. If there is no .ncf file in that directory, stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2626</MessageID> <Description>Possible cause: The file is corrupt. Solution: See if an .ncf file exists in the directory Inboxes\Ddm.box\Data.col. If so, delete it. The site control file will recreate it. If there is no .ncf file in that directory, stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2627</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2628</MessageID> <Description>Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2629</MessageID> <Description>Possible cause: Low disk space on the disk drive containing Asstdata.box. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2631</MessageID> <Description>Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2632</MessageID> <Description>Possible cause: Because these notifications are done by a file, there is probably low disk space on one or more destination disk drives. Solution: Make more space available on those disks.%12</Description> </MessageSolution> <MessageSolution> <MessageID>2633</MessageID> <Description>Possible cause: Low disk space on site "%2". Solution: Make more space available on the disk drive containing \Sms\inboxes on site "%2".</Description> </MessageSolution> <MessageSolution> <MessageID>2635</MessageID> <Description>Possible cause: Something other than SMS created the DDR, and no value was specified as the Architecture. Solution: Re-create the DDR, specifying an architecture as part of the discovery item format. Possible cause: an SMS Discovery Data Manager bug. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2636</MessageID> <Description>Possible cause: On a Primary site, it is probably a SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. Possible cause: On a secondary site, SMS Discovery Data Manager probably cannot write to a file on the site server, so check for low disk space on the site server. Solution: Make more space available on the site server.</Description> </MessageSolution> <MessageSolution> <MessageID>2639</MessageID> <Description>Possible cause: The operating system and SMS client have been reinstalled on this computer.%12</Description> </MessageSolution> <MessageSolution> <MessageID>2640</MessageID> <Description>Possible cause: The hardware properties of this client have changed substantially, and the client has generated a new SMS identifier.%12</Description> </MessageSolution> <MessageSolution> <MessageID>2642</MessageID> <Description>Possible cause: %1 has been imaged, recovered from backup, or migrated to a new computer. Solution: In the ConfigMgr console, under Computer Management, in the Conflicting Records node, right click %1 and then choose one of the following options: Merge to match the conflicting record with the existing record, New to create a new client record, or Block to block this record from being a client.</Description> </MessageSolution> <MessageSolution> <MessageID>2700</MessageID> <Description>Possible cause: The file is invalid or corrupt. Solution: Do nothing. The file will be moved to the BADMIFs directory where it will be checked for corruption. Any formatting errors will be logged in Dataldr.log. If there are no formatting errors, there might have been a memory error, in which case the MIF will be retried.</Description> </MessageSolution> <MessageSolution> <MessageID>2701</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2702</MessageID> <Description>Possible cause: The delta MIF file came from an SMS 1.2 site, and these sites do not have discovery agents. Solution: Verify that the delta MIF file is from a 1.2 site. If so, do nothing. Possible cause: Discovery Data Manager is not running. Solution: Stop and restart Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2703</MessageID> <Description>Possible cause: The file attempted to update inventory information in the SMS site database that does not already exist, or the file contains invalid syntax. Solution: The client inventory needs to be resynchronized, which will be done automatically. Look for the status messages 2714 and 2715, which indicate the resynchronization has begun.</Description> </MessageSolution> <MessageSolution> <MessageID>2706</MessageID> <Description> Solution: Review the immediately preceding status messages from this component for more details. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2712</MessageID> <Description>Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2719</MessageID> <Description>Solution: Increase the maximum allowable size, which is defined in the registry key HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Max MIF Size (the default is 5 MB), and wait for SMS Inventory Data Loader to retry the operation.</Description> </MessageSolution> <MessageSolution> <MessageID>2720</MessageID> <Description>Possible cause: SMS Inventory Data Loader detected a MIF file (from the resource with GUID %1) that contains an update request for data that is not in the SMS site database. Therefore, SMS Inventory Data Loader wants to request a resynchronization, or full MIF file, from that resource. Solution: On the resource with GUID %1, set the registry key HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Resynchronize Clients to 1 (true).</Description> </MessageSolution> <MessageSolution> <MessageID>2721</MessageID> <Description>Possible cause: The file has been edited with changes that are not valid for MOF file syntax. Solution: Review the last set of changes to the file for adherence to MOF file syntax.</Description> </MessageSolution> <MessageSolution> <MessageID>2802</MessageID> <Description>Possible cause: Some site configuration change requests contained in the file might not have been applied to the actual site control file; consequently, the site might not be fully reconfigured. Solution: SMS Site Control Manager will try to process the file again the next time a new delta site control file arrives at "%2" or the next time SMS Site Control Manager is restarted, whichever comes first. You can force SMS Site Control Manager to try to process the file again by stopping and restarting SMS Site Control Manager using the SMS Service Manager application.</Description> </MessageSolution> <MessageSolution> <MessageID>2803</MessageID> <Description>Possible cause: The file could be unnecessarily processed again, or it might temporarily seem that the site has not been fully reconfigured. Solution: Both of these problems will be resolved the next time a new delta site control file arrives at "%2" for processing, or the next time SMS Site Control Manager is restarted, whichever comes first. You can force this to occur immediately by stopping and restarting SMS Site Control Manager using the SMS Service Manager application.</Description> </MessageSolution> <MessageSolution> <MessageID>2804</MessageID> <Description>Possible cause: The delta site control file contained a corrupt or invalid site configuration change request. Any successfully processed site configuration change requests in this file will remain in effect (i.e., those changes will not be "undone" from the actual site control file). However, the corrupt site configuration change request and all subsequent site configuration change requests in this file, were not made to the site configuration. Solution: If the file was submitted by an SMS server component, the component will detect that the change was not made and will submit a new delta site control file, usually within a few minutes. If the file was submitted by the SMS Provider on behalf of one of its clients (such as the SMS Administrator console), SMS Hierarchy Manager will eventually detect that the change was not made and submit a new delta site control file. If the file was submitted by the SMS Provider at the current site, SMS Hierarchy Manager should submit a new file within 24 hours. If the file was submitted by the SMS Provider at a parent site, it could take longer than 24 hours. You can cause a new file to be submitted immediately by stopping and restarting SMS Hierarchy Manager at the site that submitted the file using the SMS Service Manager application. SMS Hierarchy Manager will continue to submit new delta site control files until all outstanding site configuration change requests have been made.</Description> </MessageSolution> <MessageSolution> <MessageID>2805</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2806</MessageID> <Description>Possible cause: This site configuration change request and the remaining change requests in the file are unusable. Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2816</MessageID> <Description>Solution: The SMS server components cannot function without this file. SMS Site Control Manager will shut down SMS Executive immediately. Contact Microsoft for help in restoring the actual site control file.</Description> </MessageSolution> <MessageSolution> <MessageID>2817</MessageID> <Description>Solution: SMS Site Control Manager can run only on the site server. SMS Site Control Manager will shut down immediately. Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2818</MessageID> <Description>Solution: The SMS server components cannot run without this item. Site Component Manager will shut down SMS Executive immediately. Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2821</MessageID> <Description>Solution: SMS Site Control Manager will submit a new copy of the actual site control file to SMS Hierarchy Manager the next time a new delta site control file is processed at "%3", or the next time SMS Site Control Manager is restarted, whichever comes first. You can force this to occur immediately by stopping and restarting SMS Site Control Manager using the SMS Service Manager application.</Description> </MessageSolution> <MessageSolution> <MessageID>2822</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2823</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2824</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2825</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2826</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2827</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2828</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2829</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2830</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2831</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2832</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2833</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2834</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2835</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.%12</Description> </MessageSolution> <MessageSolution> <MessageID>2836</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2837</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2838</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2839</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2840</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2841</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2842</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2843</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2844</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2845</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2846</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2847</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2848</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2849</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2850</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2851</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2852</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2853</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2854</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2855</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2856</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2857</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur from time to time, depending on the performance of your network. If this happens repeatedly again, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2858</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur from time to time, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>5805</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>5806</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>5807</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>5808</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>6003</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>6004</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>6005</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>6006</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>6007</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>6100</MessageID> <Description>Possible cause: The registry information is not available yet. Solution: The State System is waiting for the information to become available and will retry obtaining the registry information at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>6200</MessageID> <Description>Possible cause: The registry information is not available yet. Solution: The State System is waiting for the information to become available and will retry obtaining the registry information at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>6201</MessageID> <Description>Possible cause: Restoring Clients haven't restored the state yet or store deletion wait time has not been reached. Solution: Wait for periodic store deletion time and retry or free up some disk space on SMP drives.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6202</MessageID> <Description>Possible cause: Restoring clients have not restored the state yet or state retention time has not expired. Solution: Wait for store retention time to expire.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6206</MessageID> <Description>Possible cause: Client machine is not part of the domain or access account presented by client is not found.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6207</MessageID> <Description>Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base.</Description> </MessageSolution> <MessageSolution> <MessageID>6208</MessageID> <Description>Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the SMP. For more information, refer to Microsoft Knowledge Base article 838891.</Description> </MessageSolution> <MessageSolution> <MessageID>6300</MessageID> <Description>Possible cause: The registry information is not available yet. Solution: Restart the WDS Service.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6318</MessageID> <Description>Possible cause: PXE may be overloaded. Solution: Reapply the setting at a later time.</Description> </MessageSolution> <MessageSolution> <MessageID>6319</MessageID> <Description>Possible cause: PXE service point is not started or not responding. Solution: Manually restart the PXE service point. Possible cause: WDS service is not responding. Solution: Manually restart the WDS service.</Description> </MessageSolution> <MessageSolution> <MessageID>6320</MessageID> <Description>Possible cause: PXE service point encountered an error when connecting to SQL Server. Solution: Verify that the SQL server is properly configured to allow PXE Service Point access. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the PXE Service Point to use an NT integrated security account, with appropriate access. If using integrated security, verify the account used by the PXE service point to connect to the SQL server is a member of the SMS_SiteSystemToSQLConnection_<sitecode> group on the SQL server, that the account is not locked out, and that the account password is not expired. (In standard security, the default account is SMS_SQL_RX_<sitecode>.) Possible cause: The SQL server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL server SPNs are correctly registered.</Description> </MessageSolution> <MessageSolution> <MessageID>6400</MessageID> <Description>Possible cause: Site server "%4" is under heavy load and is either CPU or I/O constrained. Solution: Use Task Manager to check for processes causing high CPU or I/O utilization. Possible cause: Site server "%4" has a high backlog of files in its inboxes. Solution: Give the system time to work through the current backlog. Do not create any additional tasks that would load the system further.</Description> </MessageSolution> <MessageSolution> <MessageID>6500</MessageID> <Description>Possible cause: The information is not yet available. Solution: The component is waiting for the information to become available and will retry obtaining the information at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>6507</MessageID> <Description>Possible cause:Client data was unavailable. Possible cause:Error occurred while reading client data. Possible cause:A network error occurred.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6508</MessageID> <Description>Possible cause:Client data was unavailable. Possible cause:Error occurred while reading client data. Possible cause:A network error occurred. Solution: Sending will be retried on the next retry time.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6509</MessageID> <Description>Possible cause:Client data was unavailable. Possible cause: Solution:%12</Description> </MessageSolution> <MessageSolution> <MessageID>6511</MessageID> <Description>Possible cause:An error occured accessing the information. Solution:%12</Description> </MessageSolution> <MessageSolution> <MessageID>6600</MessageID> <Description>Possible cause: WSUS Server version 3.0 SP1 and above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP1 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.</Description> </MessageSolution> <MessageSolution> <MessageID>6602</MessageID> <Description>Possible cause: WSUS Server version 3.0 SP1 and above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP1 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.</Description> </MessageSolution> <MessageSolution> <MessageID>6603</MessageID> <Description>Possible cause: WSUS Server version 3.0 SP1 and above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP1 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.</Description> </MessageSolution> <MessageSolution> <MessageID>6607</MessageID> <Description>Solution: WSUS Server configuration on the WSUS Site System requires WSUS Server remoting API of version 3.0 SP1 or greater to be installed on the site server. To install the remoting API for version 3.0 SP1 run "WSUSSetup.exe console_install=1" on the site server or refer to the documentation.</Description> </MessageSolution> <MessageSolution> <MessageID>6707</MessageID> <Description>Possible cause: Server %1 synchronization is disabled. Solution: Enable upstream synchronization for server %1 or manually import data from upstream server %2.</Description> </MessageSolution> <MessageSolution> <MessageID>6800</MessageID> <Description>Possible cause: Wrong name specified or permissions to "%1" are incorrect. Solution: Verify that a readable backup control file named "%1" exists.</Description> </MessageSolution> <MessageSolution> <MessageID>6802</MessageID> <Description>Possible cause: "%1" is an interactive Windows application and is waiting for user confirmation of the stop request. Solution: Manually stop this application.</Description> </MessageSolution> <MessageSolution> <MessageID>6804</MessageID> <Description>Possible cause: "%1" does not exist in the specified location on the local computer. Solution: Verify that an executable "%1" exists on the local computer. Also specify its full path in the backup control file.</Description> </MessageSolution> <MessageSolution> <MessageID>6806</MessageID> <Description>Possible cause: SMS Writer does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. If this problem persists, refer to the SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>10209</MessageID> <Description>Solution: Verify that the client currently has a reliable connection with its assigned client access point (CAP). If the problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>10210</MessageID> <Description>Solution: Verify that the client currently has a reliable connection with its assigned client access point (CAP). If the problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>10211</MessageID> <Description>Solution: Verify that the client currently has a reliable connection with its assigned client access point (CAP). If the problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>10212</MessageID> <Description>Solution: Verify that the client currently has a reliable connection with its assigned client access point (CAP). If the problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>10213</MessageID> <Description>Possible cause: Low disk space. Solution: If this computer is running the Windows NT, 95, or 98 operating system, repair the installation by using the Systems Management tool in Control Panel. Select the Components tab, highlight "SMS Client Base Components," and then click "Repair Installation."</Description> </MessageSolution> <MessageSolution> <MessageID>10214</MessageID> <Description>Possible cause: Low disk space. Solution: Free up some disk space on the client computer.</Description> </MessageSolution> <MessageSolution> <MessageID>10215</MessageID> <Description>Solution: Verify that SMS_Executive is running on the SMS site server. Then, check the client account permissions to verify that the client has read permission to the Clicomp.box directory.</Description> </MessageSolution> <MessageSolution> <MessageID>10216</MessageID> <Description>Solution: Check the client account permissions to verify that the client has read permission to the Clifiles.box directory.</Description> </MessageSolution> <MessageSolution> <MessageID>10217</MessageID> <Description>Solution: Check the client account permissions to verify that the client has read permission to the Clicomp.box directory.</Description> </MessageSolution> <MessageSolution> <MessageID>10218</MessageID> <Description>Possible cause: Either APM is not running or the inter-process communication (IPC) mechanism might not be working. Solution: If this computer is running the Windows NT, 95, or 98 operating system, repair the installation by using the Systems Management tool in Control Panel. Select the Components tab, highlight "SMS Client Base Components," and then click "Repair Installation."</Description> </MessageSolution> <MessageSolution> <MessageID>10219</MessageID> <Description>Possible cause: Either APM is not running or the inter-process communication (IPC) mechanism might not be working. Solution: If this computer is running the Windows NT, 95, or 98 operating system, repair the installation by using the Systems Management tool in Control Panel. Select the Components tab, highlight "SMS Client Base Components," and then click "Repair Installation."</Description> </MessageSolution> <MessageSolution> <MessageID>10220</MessageID> <Description>Solution: See SMS Available Programs Manager (APM) status messages for specific information.</Description> </MessageSolution> <MessageSolution> <MessageID>10221</MessageID> <Description>Solution: See APM status messages for specific information.</Description> </MessageSolution> <MessageSolution> <MessageID>10223</MessageID> <Description>Solution: Before deploying SMS 2003 in your organization, uninstall the files for earlier versions of the SMS client.</Description> </MessageSolution> <MessageSolution> <MessageID>10501</MessageID> <Description>Possible cause: Windows Management Instrumentation (Winmgmt) may not be running properly on the client. Solution: Verify that the WinMgmt service is installed and running on the client.</Description> </MessageSolution> <MessageSolution> <MessageID>10502</MessageID> <Description>Possible cause: Windows Management Instrumentation (Winmgmt) might not be running properly on the client. Solution: Verify that the WinMgmt service is installed and running on the client.</Description> </MessageSolution> <MessageSolution> <MessageID>10503</MessageID> <Description>Possible cause: The SMS Hardware Inventory Agent cannot continue to function in this state and might need to be reinstalled. Solution: Reinstall the Hardware Inventory Agent on this client.</Description> </MessageSolution> <MessageSolution> <MessageID>10504</MessageID> <Description>Possible cause: The Hardware Inventory Agent requires at least 3 MB of virtual memory and 500 KB of disk space to begin the inventory cycle. Solution: Add additional memory or disk space to the client.</Description> </MessageSolution> <MessageSolution> <MessageID>10506</MessageID> <Description>Possible cause: The Hardware Inventory Agent cannot compile either the new Managed Object Format (MOF) file from site "%1" or the default MOF file. The agent cannot continue to function in this state. A request to verify the installation of the agent has been issued. Solution: Reinstall the Hardware Inventory Agent.</Description> </MessageSolution> <MessageSolution> <MessageID>10507</MessageID> <Description>Possible cause: If the file sms_def.mof was updated to change the SMS Inventory Schema, a syntax error might have been introduced. Solution: Verify the syntax of the MOF file by using Mofcomp tool with the -check flag parameter enabled.</Description> </MessageSolution> <MessageSolution> <MessageID>10508</MessageID> <Description>Possible cause: This MIF file exceeds the maximum third-party MIF size. Solution: The maximum MIF file size is configurable and is provided to allow greater control over third-party MIF files. Decrease the size of your MIF file.</Description> </MessageSolution> <MessageSolution> <MessageID>10509</MessageID> <Description>Possible cause: There might be an error in the MIF file. Solution: During parsing, the following error was reported - "%3". Fix the error on the reported line.</Description> </MessageSolution> <MessageSolution> <MessageID>10510</MessageID> <Description>Possible cause: This MIF file is attempting to update the "System" or "Personal Computer" architectures, which are restricted to SMS. For security reasons, third-party MIF files are not permitted to update the "System" or "Personal Computer" architectures. Solution: Reconfigure the MIF file so that it will not attempt to update the "System" or "Personal Computer" architectures.</Description> </MessageSolution> <MessageSolution> <MessageID>10511</MessageID> <Description>Solution: Verify that the WinMgmt service is installed and running on the client.</Description> </MessageSolution> <MessageSolution> <MessageID>10601</MessageID> <Description>Possible cause: The Software Inventory Agent requires at least 3 MB of virtual memory and 500 KB of disk space to begin the inventory cycle. Solution: Add additional memory or disk space to the client.</Description> </MessageSolution> <MessageSolution> <MessageID>10602</MessageID> <Description>Possible cause: Software Inventory Agent needs to make a copy of each collected file before the files can be collected. There is insufficient disk space to allow this second copy to be made. As a result, some files that match the file collection criteria might not be collected on this inventory cycle. Either this client has insufficient disk space, or the file collection criteria specifies the collection of too many files. Solution: Increase disk space on the client, or specify that fewer files be collected.</Description> </MessageSolution> <MessageSolution> <MessageID>10603</MessageID> <Description>Possible cause: Software Inventory Agent is limited in the total collected file size. This limit has been reached. As a result, some files that match the file collection criteria might not be collected on this inventory cycle. Solution: Use the "Reconfigure the maximum data collected per client (MB)" option on the File Collection tab of the Software Inventory Client Agent Properties dialog box in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>10604</MessageID> <Description>Possible cause: The exception was non-fatal, and the agent will continue processing. The file that caused the exception may be corrupt. Solution: Remove the file from this client to prevent further problems.</Description> </MessageSolution> <MessageSolution> <MessageID>10815</MessageID> <Description>Possible cause: The ACLs on the Certificate store are incorrect. Solution: Verify that the ACLs on the Certificate store are correct. If not, fix the ACLs appropriately. Possible cause: Encryption is not supported on this version of the Operating System. Solution: Refer to the SMS Documentation on supported Operating Systems. Possible cause: The Certificate Store is corrupted. Solution: Refer to the Windows Documentation on troubleshooting this.</Description> </MessageSolution> <MessageSolution> <MessageID>11200</MessageID> <Description>Possible cause: Incorrect command line settings. Solution: Review the program command line settings. The valid range, in minutes, is from 5 minutes greater than the value of the timeout for unresponsive updates (/t) to a maximum of 8 hours.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11201</MessageID> <Description>Possible cause: Incorrect advertisement settings. Solution: Verify that the advertisement assignment schedule is correct and that users are not allowed to run the program independently of assignments.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11202</MessageID> <Description>Possible cause: authorization list not present or not valid. Solution: Verify that the authorization list, %1, is present in the package source folder and is a valid authorization list.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11203</MessageID> <Description>Possible cause: Incorrect package and program name in the Scan.ini file. Solution: Verify that the package and program name specified in the scan.ini file are correct. Possible cause: Scan component was never run on client. Solution: Specify that the scan component is run in a program dependency of the software updates package. This will ensure that new client computers always run the scan component before software update installation is attempted.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11204</MessageID> <Description>Possible cause: The scan component was removed from the client cache. Solution: Re-run the advertisement for the scan component on the client computer. This will update the cache and might fix the problem. Possible cause: Unknown scan component failure. Solution: Review the status of the scan component of the specified software update inventory tool on this client.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11205</MessageID> <Description>Possible cause: This is most likely a transitory problem. Solution: None.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11206</MessageID> <Description>Possible cause: This is most likely a transitory problem. Solution: None.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11207</MessageID> <Description>Possible cause: file not present. Solution: Verify that all files are present in the package and that distribution points have been successfully updated.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11250</MessageID> <Description>Solution: Do nothing. The Software Updates Installation Agent will try again at the next advertisement recurrence.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11251</MessageID> <Description>Solution: Do nothing. The Software Updates Installation Agent will try again at the next advertisement recurrence.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11256</MessageID> <Description>Possible cause: The scheduled installation window is not long enough. Solution: Verify that the specified scheduled installation window is long enough to accommodate the run times of all required updates in the package.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11257</MessageID> <Description>Possible cause: Previous installations might have replaced in-use files and are awaiting a system restart to complete installation. This restart was requested but the user of the computer has rescheduled it. Solution: Do nothing. Software update installation will be retried on the next scheduled cycle if the required restart has occurred.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11258</MessageID> <Description>Possible cause: Previous installations might have replaced in-use files and are awaiting a system restart to complete installation. This restart was requested but the user of the computer has postponed it. Solution: Restart the client computer or do nothing. Software update installation will be retried on the next scheduled cycle if the required restart has occurred.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11259</MessageID> <Description>Possible cause: Previous installations might have replaced in-use files and are awaiting a system restart to complete installation. This restart was requested but the user of the computer did not allow it. Because the software updates in the current package were not yet required, the installation was postponed.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11269</MessageID> <Description>Possible cause: Previous installations might have replaced in-use files and are awaiting a system restart to complete installation. Solution: Restart the client computer or do nothing. Software update installation will be retried on the next scheduled cycle if the required restart has occurred.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11302</MessageID> <Description>Possible cause: Typically such failures are the result of internal errors within the software update itself. Solution: Review the log files generated by the software update on the client computer for additional details. Possible cause: The Software Updates Installation Agent was unable to start the software update installation program. Solution: Verify that the software update file is included in the package. Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </MessageSolution> <MessageSolution> <MessageID>11303</MessageID> <Description>Possible cause: The Software Update Installation Agent timeout settings for this package/program do not allow sufficient time for the installation. Solution: Check the command-line settings for the program and ensure that the timeout setting (/t) is sufficient. Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </MessageSolution> <MessageSolution> <MessageID>11304</MessageID> <Description> Solution: To prevent this, software updates can be configured with enforcement options. Consult the product documentation for details on the enforcement feature. Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </MessageSolution> <MessageSolution> <MessageID>11306</MessageID> <Description>Possible cause: This software update was estimated to require %7MB, however only %8MB was available. Solution: Verify that enough disk space is available to install the updates. Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5, Executable = %6%12</Description> </MessageSolution> <MessageSolution> <MessageID>HTTP12007</MessageID> <Description>Possible cause: The content can not be found on the network, or the content could not be accessed. Solution: Investigate and correct any problems with your network. Possible cause: Network problems are preventing the management point from working properly. Solution: Investigate and correct any problems with your network.</Description> </MessageSolution> <MessageSolution> <MessageID>2421</MessageID> <Description> Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2422</MessageID> <Description> Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>5447</MessageID> <Description>Possible cause: Client is not approved Solution: Approve client</Description> </MessageSolution> <MessageSolution> <MessageID>5615</MessageID> <Description> Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information. See the previous and following error status messages for more details.</Description> </MessageSolution> <MessageSolution> <MessageID>615</MessageID> <Description> Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>616</MessageID> <Description> Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>617</MessageID> <Description> Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>618</MessageID> <Description> Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>619</MessageID> <Description> Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>620</MessageID> <Description> Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>30085</MessageID> <Description>Solution: Verify that the Remote Tools Client Agent is installed on the client. If the agent is installed and you cannot start a Remote Tools session, use the "Show Status" command on Control Panel, Remote Tools on the client to verify that the Remote Control Agent is listening on the right protocol.</Description> </MessageSolution> <MessageSolution> <MessageID>30086</MessageID> <Description>Solution: Verify that the logged on user is a member of a group that is listed in the Permitted viewers list on the Security tab of the Remote Tools Client Agent Properties dialog box.</Description> </MessageSolution> <MessageSolution> <MessageID>30087</MessageID> <Description>Solution: Confirm that another Remote Tools session is not already in progress on the client.%12</Description> </MessageSolution> <MessageSolution> <MessageID>30088</MessageID> <Description>Possible cause: When Remote.exe has an open connection to a client, it background polls the connection to verify that the client is still connected. The connection can fail because the network cable is unplugged, the client machine is turned off, or the client stops responding. Solution: Check the security credentials of logged on user "%1". Verify that the client is turned on and is still plugged into the network. If the client is a Windows NT client, verify that the SMS Remote Control Agent service is still running on the client. Then, retry the Remote Tools operation.%12</Description> </MessageSolution> <MessageSolution> <MessageID>30089</MessageID> <Description>Possible cause: When Remote.exe has an open connection to a client, it background polls the connection to verify that the client is still connected. The connection can fail because the network cable is unplugged, the client machine is turned off, or the client quits responding. Solution: Check the security credentials of logged on user "%1". Verify that the client is turned on and is still plugged into the network. If the client is a Windows NT client, verify that the SMS Remote Control Agent service is still running on the client. Then, retry the Remote Tools operation.%12</Description> </MessageSolution> <MessageSolution> <MessageID>30109</MessageID> <Description>Possible cause: Some system resources are not assigned to the current site, And you chose to install clients only on system resources that are assigned to current site. Another possible cause: some system resources do not have Microsoft Windows NT operating system or above installed. %12</Description> </MessageSolution> <MessageSolution> <MessageID>30110</MessageID> <Description>Possible cause: some system resources are not assigned to the current site, and you chose to install clients only on system resources that are assigned to current site. Another possible cause: Some system resources do not have Microsoft Windows NT operating system or above installed. %12</Description> </MessageSolution> <MessageSolution> <MessageID>30111</MessageID> <Description>Possible cause: this is not a system resource, this is not assigned to current site if you choose to install client on system resource that are assigned to current site, or the system resource does not have Microsoft Windows NT operating system or above installed.%12</Description> </MessageSolution> <MessageSolution> <MessageID>10000</MessageID> <Description>Possible cause: The advertisement (.ofr) file on this Client Access Point (CAP) is missing, corrupt, or lacking data. The advertisement will not be run or displayed to users. Solution: Modify the specified advertisement in the SMS Administrator console to force Offer Manager to update (rewrite) the advertisement files. Wait for Inbox Manager to replicate the change to the CAPs throughout the site before refreshing the list of advertised programs on the client (press F5 in the Advertised Programs Monitor). If the problem persists, check for disk problems on the CAP or for other external causes of file corruption.</Description> </MessageSolution> <MessageSolution> <MessageID>10001</MessageID> <Description>Possible cause: The package (.pkg) or network location (.nal) file on this Client Access Point (CAP) is missing, corrupt, or lacking data. Advertisements for the package's programs will not be run or displayed to users until the file can be read successfully. Solution: Modify the specified package or one of its programs to force SMS Distribution Manager to update (rewrite) the package files. Wait for SMS Inbox Manager to replicate the change to the CAPs throughout the site before refreshing the list of advertised programs on the client (press F5 in the Advertised Programs Monitor). If the problem persists, check for disk problems on the CAP or for other external causes of file corruption.</Description> </MessageSolution> <MessageSolution> <MessageID>10003</MessageID> <Description>Possible cause: This message most commonly occurs when the program's command-line executable file could not be found, when a required drive letter connection to a distribution point could not be established, or when the program is configured to use the SMS Software Installation Account but the account is not specified, could not be found, or does not have the appropriate permissions. Solution: Check each of the items listed above.</Description> </MessageSolution> <MessageSolution> <MessageID>10004</MessageID> <Description>Possible cause: This error can be caused by an invalid executable file specified in the command line (such as an Alpha-based executable file on an x86-based computer) or by a corrupt executable file. This error can also be caused if the program is executed from a remote session. Solution: Make sure that the executable file specified in the program's command line is valid for the computer it is attempting to run on. Also, manually verify that the specified command line can be executed from within the original content source directory. If necessary, modify the program properties, the content source files, or both. If changes to the content source files are required, use the Manage Distribution Points wizard to update all of the content's distribution points with the new version of the content source files before retrying execution on the client.</Description> </MessageSolution> <MessageSolution> <MessageID>10006</MessageID> <Description>Possible cause: Systems Management Server (SMS) determines status for each program it executes. If SMS cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. An exit code of %2 is considered a failure. Solution: For more information on the exit code, refer to the documentation for the program you are distributing.</Description> </MessageSolution> <MessageSolution> <MessageID>10007</MessageID> <Description>Possible cause: The program generated an installation status Management Information Format (MIF) file with a status value of Failed. Solution: For more information about the failure, refer to the documentation for the program you are distributing.</Description> </MessageSolution> <MessageSolution> <MessageID>10010</MessageID> <Description>Possible cause: SMS Advertised Program Manager is unable to find the uninstall command line executable file specified in the program's uninstall registry key. Solution: Verify that the uninstall command registered by the program's setup routines is valid for the client.</Description> </MessageSolution> <MessageSolution> <MessageID>10011</MessageID> <Description>Possible cause: The uninstall command line for the program cannot be executed successfully. This error can be caused by an invalid executable file specified in the uninstall command line (such as an Alpha executable file on an Intel computer) or by a corrupt executable file. Solution: Make sure that the executable file specified in the program's uninstall command line is valid for the computer running the advertisement.</Description> </MessageSolution> <MessageSolution> <MessageID>10013</MessageID> <Description>Possible cause: SMS Advertised Program Manager (APM) determines status for each program it executes. If APM cannot find or correlate any install status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. A non-zero exit code is considered a failure. Solution: For more information about the exit code, refer to the documentation for the program you are distributing.</Description> </MessageSolution> <MessageSolution> <MessageID>10014</MessageID> <Description>Possible cause: The uninstall program generated an install status Management Information Format (MIF) file with a status value of Failed. Solution: For more information about the failure, refer to the documentation for the program you are distributing.</Description> </MessageSolution> <MessageSolution> <MessageID>10017</MessageID> <Description>Possible cause: The removal key specified (%2) for the program in the advertisement ("%4" - "%5") cannot be found in the client registry or was found but did not contain either of the required uninstall command line entries (a UninstallString or a QuietUninstallString value). Solution: Verify that the removal key specified on the Advanced tab of the Program's Properties dialog box exists in the client's registry under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Current Version\Uninstall and that it contains one of the required uninstall command-line entries. If necessary, adjust the key specified in the program's properties. APM will retry the uninstall operation the next time the client's list of advertised programs is refreshed and a change in the program's properties is detected.</Description> </MessageSolution> <MessageSolution> <MessageID>10018</MessageID> <Description>Possible cause: The client received the advertisement but rejected it because the client's platform was not included in the list of supported platforms specified for the program. Solution: If the client should actually accept the advertisement, either disable supported platform checking or modify the list of supported platforms specified on the Requirements tab of the Program's Properties dialog box. Changes to the program properties will not be detected until the list of advertised programs is refreshed on the client.</Description> </MessageSolution> <MessageSolution> <MessageID>10019</MessageID> <Description>Possible cause: The client received the advertisement but rejected it because the advertisement expiration date is past. Solution: If the client should accept the advertisement, you can extend the life of the advertisement by changing the expiration date and time or disabling expiration on the Schedule tab of the advertisement's properties. Changes to the Advertisement's Properties dialog box will not be detected until the list of advertised programs is refreshed on the client.</Description> </MessageSolution> <MessageSolution> <MessageID>10020</MessageID> <Description>Possible cause: The advertisement specified has the "Assignments are not mandatory over slow links" checkbox selected on its Schedule tab and the performance of the connection to the Client Access Point (CAP) has either been detected as below the configured threshold, could not be determined, or is a Remote Access Service (RAS) connection. Solution: The advertisement will be scheduled for execution when the client next attaches to the site with a fast network connection.</Description> </MessageSolution> <MessageSolution> <MessageID>10021</MessageID> <Description>Possible cause: The program performs a restart of the client computer when it completes, but the 'After running' setting in the program's properties is not set to Program restarts computer, or the client machine was restarted while the program was running. Solution: Verify the above. If the program does a restart when it completes, even if it only requires a restart in some cases, modify the program's properties and set 'After running' to 'Program restarts computer'.</Description> </MessageSolution> <MessageSolution> <MessageID>10025</MessageID> <Description>Possible cause: The content can not be found on the network, or the content could not be accessed. Solution: Check to ensure this content has been made available on a distribution point. Check to ensure the access control list allows this program to be accessed. Check to make sure that the file system path for the content, including the path to the cache directory, is not greater than 255 characters.</Description> </MessageSolution> <MessageSolution> <MessageID>10030</MessageID> <Description>Possible causes: The content on the distribution point has been manually modified, or a local administrator on the computer has modified the content in the computer's hash. Solution: Refresh the content on the distribution point and retry the download.</Description> </MessageSolution> <MessageSolution> <MessageID>10035</MessageID> <Description>Possible cause: The content for this program must be downloaded into the computer's cache, or the content could not be located. Solution: If the program is being downloaded, no action is required. The program will start once the download has been successfully completed. If the content can not be located, ensure that a distribution point with this content is available for this computer. Distribution point availability can be affected by roaming boundary configuration which is used to determine whether distribution points are classified as local or remote, or by enabling distribution points as protected distribution points. Distribution point availability can also be affected if you are using branch distribution points and the advertisement is configured with the option Run program from distribution point instead of Download content from distribution point and run locally. This is because branch distribution points do not support advertisements that are configured to run directly from a distribution point.</Description> </MessageSolution> <MessageSolution> <MessageID>10045</MessageID> <Description>Solution: Increase the size of the cache, or remove other content from the cache, or increase the amount of free disk space. This program will be retried.</Description> </MessageSolution> <MessageSolution> <MessageID>10046</MessageID> <Description>Possible causes: The version of Windows Installer on the computer is less than version 2.0, or the setup program does not support Windows Installer per-user elevated rights installations. Possible solutions: Update the version of Windows Installer on the computer to version 2.0 or later, or contact the software vendor that supplied the install program to determine if a version of setup that supports per-user elevated rights is available.</Description> </MessageSolution> <MessageSolution> <MessageID>10050</MessageID> <Description>Solution: Increase the size of the cache.</Description> </MessageSolution> <MessageSolution> <MessageID>10051</MessageID> <Description>Possible cause: The content source might not be available on any distribution servers, or the advertisement may have been marked not to run program when no local Distribution Point is available and this SMS client is in remote roaming boundaries of the site. Content source might not be available because the advertisement is configured with the option Run program from distribution point on one or more branch distribution points and is not available on a standard distribution point. Branch distribution points do not support advertisements that are configured with the option Run program from distribution point. Solution: Use the Manage Distribution Points wizard to distribute the content to a distribution point. If this SMS client is expected to stay in remote roaming binderies then change the advertisement to allow running program from remote Distribution Point. Use the Manage Distribution Points wizard to distribute the content to a standard distribution point if you want to use the option Run program from distribution point.</Description> </MessageSolution> <MessageSolution> <MessageID>10052</MessageID> <Description>Possible cause: The program is set to run when no user is logged on, but is being advertised to a user. Solution: Examine the properties of the program to resolve the conflicting requirements. Possible cause: The program is set to require user input, but does not require that a user be logged on in order to run. Solution: Examine the properties of the program to resolve the conflicting requirements. Possible cause: The program requires content download, but no supported hash is available because the package was previously created by a version of SMS that did not support the required hash algorithms. Solution: Perform a package update to recalculate the hash and send policy to clients with the updated hash value.</Description> </MessageSolution> <MessageSolution> <MessageID>10053</MessageID> <Description>Possible cause: The content can not be found on the network, or the content could not be accessed, or the advertisement may have been marked not to run program when no local Distribution Point is available and this SMS client is in remote roaming boundaries of the site. Solution: Check to ensure this content has been made available on a distribution point. Check to ensure the access control list allows this program to be accessed. Check to make sure that the file system path for the content, including the path to the cache directory, is not greater than 255 characters. If this SMS client is expected to stay in remote roaming binderies then change the advertisement to allow running program from remote Distribution Point.</Description> </MessageSolution> <MessageSolution> <MessageID>10054</MessageID> <Description>Solution: Increase the size of the cache, or remove other content from the cache, or increase the amount of free disk space. This program will not be retried.</Description> </MessageSolution> <MessageSolution> <MessageID>10055</MessageID> <Description>Possible cause: This message most commonly occurs when the program's command-line executable file could not be found, when a required drive letter connection to a distribution point could not be established, or when the program is configured to use the SMS Software Installation Account but the account is not specified, could not be found, or does not have the appropriate permissions. Solution: Check each of the items listed above. This program will be retried.</Description> </MessageSolution> <MessageSolution> <MessageID>10056</MessageID> <Description>Possible cause: This error can be caused by an invalid executable file specified in the command line (such as an Alpha-based executable file on an x86-based computer) or by a corrupt executable file. This error can also be caused if the program is executed from a remote session. Solution: Make sure that the executable file specified in the program's command line is valid for the computer on which it is attempting to run. Also, manually verify that the specified command line can be executed from within the original content source directory. If necessary, modify the program properties, the content source files, or both. If changes to the content source files are required, use the Manage Distribution Points wizard to update all of the content's distribution points with the new version of the content source files before retrying execution on the client. This program will be retried.</Description> </MessageSolution> <MessageSolution> <MessageID>10057</MessageID> <Description>Possible causes: The content on the distribution point has been manually modified, or a local administrator on the computer has modified the content in the computer's hash. Solution: Refresh the content on the distribution point and retry the download.</Description> </MessageSolution> <MessageSolution> <MessageID>10058</MessageID> <Description>Possible cause: The content can not be found on the network, or the content could not be accessed, or the advertisement may have been marked not to run program when no local Distribution Point is available and this SMS client is in remote roaming boundaries of the site. Content source might not be available because the advertisement is configured with the option Run program from distribution point on one or more branch distribution points and is not available on a standard distribution point. Branch distribution points do not support advertisements that are configured with the option Run program from distribution point. Solution: Check to ensure this content has been made available on a distribution point. Check to ensure the access control list allows this program to be accessed. Check to make sure that the file system path for the content, including the path to the cache directory, is not greater than 255 characters. If this SMS client is expected to stay in remote roaming binderies then change the advertisement to allow running program from remote Distribution Point. Use the Manage Distribution Points wizard to distribute the content to a standard distribution point if you want to use the option Run program from distribution point.</Description> </MessageSolution> <MessageSolution> <MessageID>10060</MessageID> <Description>Possible cause: The content source might not be available on any distribution servers, or the advertisement may have been marked not to run program when no local Distribution Point is available and this SMS client is in remote roaming boundaries of the site. Content source might not be available because the advertisement is configured with the option Run program from distribution point on one or more branch distribution points and is not available on a standard distribution point. Branch distribution points do not support advertisements that are configured with the option Run program from distribution point. Solution: Use the Manage Distribution Points wizard to distribute the content to a distribution point. If this SMS client is expected to stay in remote roaming binderies then change the advertisement to allow running program from remote Distribution Point. Use the Manage Distribution Points wizard to distribute the content to a standard distribution point if you want to use the option Run program from distribution point.</Description> </MessageSolution> <MessageSolution> <MessageID>10061</MessageID> <Description>Possible cause: The content can not be found on the network, or the content could not be accessed, or the advertisement may have been marked not to run program when no local Distribution Point is available and this SMS client is in remote roaming boundaries of the site. Solution: Check to ensure this content has been made available on a distribution point. Check to ensure the access control list allows this program to be accessed. Check to make sure that the file system path for the content, including the path to the cache directory, is not greater than 255 characters. This operation will be retried. If this SMS client is expected to stay in remote roaming binderies then change the advertisement to allow running program from remote Distribution Point.</Description> </MessageSolution> <MessageSolution> <MessageID>10062</MessageID> <Description>Possible cause: The content can not be found on the network, or the content could not be accessed, or the advertisement may have been marked not to run program when no local Distribution Point is available and this SMS client is in remote roaming boundaries of the site. Content source might not be available because the advertisement is configured with the option Run program from distribution point on one or more branch distribution points and is not available on a standard distribution point. Branch distribution points do not support advertisements that are configured with the option Run program from distribution point. Solution: Check to ensure this content has been made available on a distribution point. Check to ensure the access control list allows this program to be accessed. Check to make sure that the file system path for the content, including the path to the cache directory, is not greater than 255 characters. This operation will be retried. If this SMS client is expected to stay in remote roaming binderies then change the advertisement to allow running program from remote Distribution Point. Use the Manage Distribution Points wizard to distribute the content to a standard distribution point if you want to use the option Run program from distribution point.</Description> </MessageSolution> <MessageSolution> <MessageID>10070</MessageID> <Description>Possible causes: The program might have taken longer to run than expected, or the program might have experienced problems while running. Possible solution: Make sure the maximum allowed run time specified for the program allows enough time for the program to finish running. If the program requires user input, ensure the program properties allow the user to interact with the program.</Description> </MessageSolution> <MessageSolution> <MessageID>10071</MessageID> <Description>Possible cause: There is not enough memory available on the client to monitor this program.</Description> </MessageSolution> <MessageSolution> <MessageID>10072</MessageID> <Description>Possible cause: Systems Management Server (SMS) determines status for each program it executes. If SMS cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. An exit code of %2 is considered a failure. Solution: For more information on the exit code, refer to the documentation for the program you are distributing. This program will be retried.</Description> </MessageSolution> <MessageSolution> <MessageID>10073</MessageID> <Description>Possible cause: The duration for the maintenance window is shorter than the maximum runtime specified for this program. Solution: modify the duration of the maintenance window or add another maintenance window that is long enough in duration to accomodate the maximum runtime of this program. Possible cause: The advertisement is not set to override maintenance window. Solution: Update the advertisement to override maintenance windows. Note: setting the override flag will cause the system to install the program at the mandatory assignment scheduled time and may cause the system to restart if required.</Description> </MessageSolution> <MessageSolution> <MessageID>10074</MessageID> <Description>Possible cause: The duration for the maintenance window is shorter than the maximum runtime specified for this program. Solution: modify the duration of the maintenance window or add another maintenance window that is long enough in duration to accomodate the maximum runtime of this program. Possible cause:There is only one maintenance window defined for this computer, and it is a one-time maintenance window that occurs in the past. Solution: You can delete the maintenance window if it is no longer applicable, or you can disable the maintenance window. You can also add another maintenance window for this computer, and allow the program to run according to the new maintenance window schedule. Possible cause: The advertisement is not set to override maintenance window. Solution: Update the advertisement to override maintenance windows. Note: setting the override flag will cause the system to install the program at the mandatory assignment scheduled time and may cause the system to restart if required.</Description> </MessageSolution> <MessageSolution> <MessageID>10079</MessageID> <Description>Possible cause: the duration of the reboot countdown is longer than the duration of any maintenance windows defined for this computer. Solution: Increase the duration of the maintenance window available to this computer, add another maintenance window for that exceeds the duration of the restart countdown notfication length or reduce the duration of the restart countdown notification.</Description> </MessageSolution> <MessageSolution> <MessageID>10093</MessageID> <Description>Possible causes: The computer is unable to contact a Management Point to locate the program content; the content location request to the Management Point timed out. Solutions: Wait until the computer is connected to the network and able to contact the Management Point. The update will be retried.</Description> </MessageSolution> <MessageSolution> <MessageID>10094</MessageID> <Description>Possible causes: The computer is unable to contact a Management Point to locate the program content; the content location request to the Management Point timed out. Solutions: Wait until the computer is connected to the network and able to contact the Management Point. The update will not be retried.</Description> </MessageSolution> <MessageSolution> <MessageID>10100</MessageID> <Description>Solution: Check for low disk space. Then, if this computer is running the Windows NT, 95, or 98 operating system, repair the installation by using the Systems Management tool in Control Panel. Select the Components tab, highlight "SMS Client Base Components," and then click "Repair Installation."</Description> </MessageSolution> <MessageSolution> <MessageID>10101</MessageID> <Description>Possible cause: Low disk space. Solution: Free up some disk space.</Description> </MessageSolution> <MessageSolution> <MessageID>10102</MessageID> <Description>Solution: Verify that SMS_Executive is running on the SMS site server. Then, check the client account permissions to verify that the client has Read permission to the Clicomp.box directory.</Description> </MessageSolution> <MessageSolution> <MessageID>10103</MessageID> <Description>Solution: Check the client account permissions to verify that the client has read permission to the Clifiles.box directory.</Description> </MessageSolution> <MessageSolution> <MessageID>10104</MessageID> <Description>Solution: Check the client account permissions to verify that the client has read permission to the Clifiles.box directory.</Description> </MessageSolution> <MessageSolution> <MessageID>10105</MessageID> <Description>Possible cause: Either APM is not running or the inter-process communication (IPC) mechanism might not be working. Solution: If this computer is running the Windows NT, 95, or 98 operating system, repair the installation by using the Systems Management tool in Control Panel. Select the Components tab, highlight "SMS Client Base Components" and then click "Repair Installation."</Description> </MessageSolution> <MessageSolution> <MessageID>10106</MessageID> <Description>Possible cause: Either APM is not running or the inter-process communication (IPC) mechanism might not be working. Solution: If this computer is running the Windows NT, 95, or 98 operating system, repair the installation by using the Systems Management tool in Control Panel. Select the Components tab, highlight "SMS Client Base Components," and then click "Repair Installation."</Description> </MessageSolution> <MessageSolution> <MessageID>10107</MessageID> <Description>Solution: See the SMS Available Programs Manager (APM) status messages for specific information.</Description> </MessageSolution> <MessageSolution> <MessageID>10108</MessageID> <Description>Solution: See the APM status messages for specific information.</Description> </MessageSolution> <MessageSolution> <MessageID>11402</MessageID> <Description>Possible cause: The scanprogram may have been run without administrative rights or it cannot write to the folder %2. Solution: Verify the scan program is set torun with administrative rights using the program properties defined for this package%12</Description> </MessageSolution> <MessageSolution> <MessageID>11405</MessageID> <Description>Solution: Review the relevant log files for this client computer.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11408</MessageID> <Description>Possible cause: This can happen when a pending restart condition was resolved, but it can also occur if the user installed the software update independently. Solution: To determine the reason for this message, review other status messages for this software update from this client computer. Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5%12</Description> </MessageSolution> <MessageSolution> <MessageID>11409</MessageID> <Description>Possible cause: This can happen when an update has been removed, or if the update has been re-issued and new detection rules show the old version of the update as not present. Details: ID = %1, QNumbers = %2, Product = %3, Title = %4, Locale = %5%12</Description> </MessageSolution> <MessageSolution> <MessageID>11419</MessageID> <Description>Possible cause: The content must be downloaded into the computer's cache, or the content could not be located. Solution: If the content is being downloaded, no action is required. Scanning will start once the download has been successfully completed. If the content can not be located, ensure that a distribution point with this content is available for this computer.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11420</MessageID> <Description>Possible cause: The content can not be found on the network, or the content could not be accessed. Solution: Check to ensure this content has been made available on a distribution point. Check to ensure the access control list allows this program to be accessed. Check to make sure that the file system path for the content, including the path to the cache directory, is not greater than 255 characters.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11421</MessageID> <Description>Solution: Increase the size of the cache.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11422</MessageID> <Description>Solution: Increase the size of the cache, or remove other content from the cache, or increase the amount of free disk space.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11454</MessageID> <Description>Possible cause: Typically, this error results when the software update inventory tool synchronization component does not have network access to the package source folder for package ID %3. Solution: To prevent this, keep the package source folder on the same computer as the synchronization component.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11455</MessageID> <Description>Possible cause: Typically, this error results when the software update inventory tool synchronization component does not have network access to the package source folder for package ID %3. Solution: To prevent this, keep the package source folder on the same computer as the synchronization component.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11456</MessageID> <Description>Possible cause: Typically, this error results when the user account running the synchronization component does not have access to the Internet. Solution: Consider changing the proxy configuration to allow anonymous connections or specific IP addresses, or consult the product documentation on the use of the SMSPatchDownloader.ini file to configure specific proxy settings on the client computer that runs the catalog download.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11458</MessageID> <Description>Solution: Consider the use of the /unattend command line option and a separate update schedule for this package.%12</Description> </MessageSolution> <MessageSolution> <MessageID>11717</MessageID> <Description>Possible cause: The duration for the maintenance window is shorter than the maximum runtime specified for this update. Solution: modify the duration of the maintenance window or add another maintenance window that is long enough in duration to accomodate the maximum runtime of this update. Possible cause:There is only one maintenance window defined for this computer, and it is a one-time maintenance window that occurs in the past. Solution: You can delete the maintenance window if it is no longer applicable, or you can disable the maintenance window. You can also add another maintenance window for this computer, and allow the update to run according to the new maintenance window schedule. Possible cause: The deployment is not set to override maintenance window. Solution: Update the deployment to override maintenance windows. Note: setting the override flag will cause the system to install the update at the deadline and may cause the system to restart if required.</Description> </MessageSolution> <MessageSolution> <MessageID>11760</MessageID> <Description>Possible cause:There is only one maintenance window defined for this computer, and it is a one-time maintenance window that occurs in the past. Solution: You can delete the maintenance window if it is no longer applicable, or you can disable the maintenance window. You can also add another maintenance window for this computer, and allow the update to run according to the new maintenance window schedule. Possible cause: The deployment is not set to override maintenance window. Solution: Update the deployment to override maintenance windows. Note: setting the override flag will cause the system to install the update at the deadline and may cause the system to restart if required. %12</Description> </MessageSolution> <MessageSolution> <MessageID>1001</MessageID> <Description>Solution: Either extend the schema for the currently designated Active Directory forest, or configure Network Access Protection to store the health state references in a different Active Directory forest that has the Configuration Manager 2007 schema extensions. For more information about extending the schema, see the Help topic How to Extend the Active Directory Schema for Configuration Manager. For more information on configuring the location of the health state references, see the Help topic How to Specify the Location of the Health State Reference.</Description> </MessageSolution> <MessageSolution> <MessageID>1016</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry the installation in %1 minutes. To force SMS Site Component Manager to immediately retry the installation, stop and restart SMS Site Component Manager using the SMS Service Manager.</Description> </MessageSolution> <MessageSolution> <MessageID>1020</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry the reinstallation in %1 minutes. To force SMS Site Component Manager to immediately retry the reinstallation, stop and restart SMS Site Component Manager using the SMS Service Manager.</Description> </MessageSolution> <MessageSolution> <MessageID>1024</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry the deinstallation in %1 minutes. To force SMS Site Component Manager to immediately retry the deinstallation, stop and restart SMS Site Component Manager using the SMS Service Manager.</Description> </MessageSolution> <MessageSolution> <MessageID>1025</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure. The deinstallation has repeatedly failed for %1 minutes and will probably never succeed, therefore SMS Site Component Manager not retry the deinstallation. You might ignore this message and do nothing if the site system is no longer in service or the operating system has been reinstalled on the site system. Otherwise the component may still be installed on this site system, and you will have to manually deinstall it. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>1028</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager cannot install any SMS server components on this site system until the site system is configured successfully. SMS Site Component Manager will automatically retry this operation in %2 minutes. To force SMS Site Component Manager to immediately retry this operation, stop and restart SMS Site Component Manager using the SMS Service Manager.</Description> </MessageSolution> <MessageSolution> <MessageID>1031</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager cannot reinstall any SMS server components on this site system until the site system is reconfigured successfully. SMS Site Component Manager will automatically retry this operation in %2 minutes. To force SMS Site Component Manager to immediately retry this operation, stop and restart SMS Site Component Manager using the SMS Service Manager.</Description> </MessageSolution> <MessageSolution> <MessageID>1034</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry this operation in %2 minutes. To force SMS Site Component Manager to immediately retry this operation, stop and restart SMS Site Component Manager using the SMS Service Manager.</Description> </MessageSolution> <MessageSolution> <MessageID>1035</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure. This operation has repeatedly failed for %2 minutes and will probably never succeed, therefore SMS Site Component Manager not retry this operation again. You might ignore this message and do nothing if the site system is no longer in service or the operating system has been reinstalled on the site system. Otherwise some remnants of the SMS server components might still be installed on this site system, and you will have to manually remove them. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>1036</MessageID> <Description>Solution: To examine the exact failure, turn on logging for SMS Site Component Manager using the SMS Service Manager, wait for SMS Site Component Manager to retry this operation, and review the log messages for SMS Site Component Manager. Please refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1037</MessageID> <Description>Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to connect to the site system. Solution: Verify that the Site Server's computer$ account has administrator rights on the remote site system. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. Possible cause: You took the site system out of service and do not intend on using it as a site system any more. Solution: Remove this site system from the list of site systems for this site. The list appears in the Site Systems node of the Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>1038</MessageID> <Description>Possible cause: You have not installed the required version of Windows NT Server on the site system. Solution: Install the required version of Windows NT Server on the site system. Refer to your SMS documentation to determine the required version. Possible cause: You accidentally configured SMS to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>1039</MessageID> <Description>Possible cause: When installing this site, you did not specify that the binary files for this site system's platform should be installed on the site server. Solution: Use SMS Setup to modify the configuration of this site. When asked to select the server platforms for this site, select this site system's platform. Possible cause: You accidently configured SMS to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the SMS Administrator console. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from properly accessing to the site system. Solution: Investigate and correct any problems on your network.</Description> </MessageSolution> <MessageSolution> <MessageID>1042</MessageID> <Description>Possible cause: You have not installed the required version of Windows NT Server on the site system. Solution: Install the required version of Windows NT Server on the site system. Refer to your SMS documentation to determine the required version. Possible cause: You accidentally configured SMS to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the SMS Administrator console. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network.</Description> </MessageSolution> <MessageSolution> <MessageID>1043</MessageID> <Description>Possible cause: You have not installed the required version of Windows NT Server on the site system. Solution: Install the required version of Windows NT Server on the site system. Refer to your SMS documentation to determine the required version. Possible cause: You accidentally configured SMS to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>1044</MessageID> <Description>Possible cause: You have not installed the required version of Windows NT Server on the site system. Solution: Install the required version of Windows NT Server on the site system. Refer to your SMS documentation to determine the required version. Possible cause: You accidentally configured SMS to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>1045</MessageID> <Description>Possible cause: You have not installed the required version of Windows NT Server on the site system. Solution: Install the required version of Windows NT Server on the site system. Refer to your SMS documentation to determine the required version. Possible cause: You accidentally configured SMS to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>1048</MessageID> <Description>Possible cause: You accidentally configured SMS to use this site system as part of this site and as part of site %2. Solution: Remove this site system from the list of site systems for this site or for site %2. The list appears in the Site Systems node of the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>1049</MessageID> <Description>Possible cause: The site system does not contain an NTFS partition. Solution: Using the Windows NT Disk Administrator, create an NTFS partition on the site system, or convert an existing FAT partition to NTFS. Possible cause: The site system is not exporting the default drive letter shares, such as "%1\C$", "%1\D$", and so on. Solution: You might have disabled the default drive letter shares for security purposes. SMS requires these shares. Please re-enable these shares using the Windows NT Disk Administrator. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network.</Description> </MessageSolution> <MessageSolution> <MessageID>1050</MessageID> <Description>Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The site system is not exporting the default drive letter shares, such as "%1\C$", "%1\D$", and so on. Solution: You might have disabled the default drive letter shares for security purposes. SMS requires these shares. Please re-enable these shares using the Windows NT Disk Administrator. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network.</Description> </MessageSolution> <MessageSolution> <MessageID>1052</MessageID> <Description>Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. When SMS Site Component Manager installs SMS services on the site system, it will configure them to log in using this account. If the site system is a stand-alone server, the account is a local machine account with full administrative rights. If the site system is a domain controller, the account is a domain account with domain user rights and full administrative rights only to the site system.</Description> </MessageSolution> <MessageSolution> <MessageID>1054</MessageID> <Description>Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. When SMS Site Component Manager installs SMS services on the site system, it will configure them to log in using this account. If the site system is a stand-alone server, the account is a local machine account with full administrative rights. If the site system is a domain controller, the account is a domain account with domain user rights and full administrative rights only to the site system.</Description> </MessageSolution> <MessageSolution> <MessageID>1055</MessageID> <Description>Possible cause: The SMS Service account no longer has sufficient access rights to read the data. Solution: Verify that the SMS Service account has full administrative rights to the site server, and that the SMS_SITE_COMPONENT_MANAGER service is configured to log in as the SMS Service account. Possible cause: The data is corrupt. Possible cause: Please refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1056</MessageID> <Description>Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The site system is not exporting the default drive letter shares, such as "%1\C$", "%1\D$", and so on. Solution: You might have disabled the default drive letter shares for security purposes. SMS requires these shares. Please re-enable these shares using the Windows NT Disk Administrator. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network.</Description> </MessageSolution> <MessageSolution> <MessageID>1058</MessageID> <Description>Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. When SMS Site Component Manager installed SMS services on the site system, it configured them to log in using this account. If the site system is a stand-alone server, the account is a local machine account with full administrative rights. If the site system is a domain controller, the account is a domain account with domain user rights and full administrative rights only to the site system.</Description> </MessageSolution> <MessageSolution> <MessageID>1060</MessageID> <Description>Possible cause: The site system is not exporting the default drive letter shares, such as "%1\C$", "%1\D$", and so on. Solution: You might have disabled the default drive letter shares for security purposes. SMS requires these shares. Please re-enable these shares using the Windows NT Disk Administrator. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network.</Description> </MessageSolution> <MessageSolution> <MessageID>1067</MessageID> <Description>Solution: Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1072</MessageID> <Description>Solution: Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1073</MessageID> <Description>Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to connect to the site system. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network.</Description> </MessageSolution> <MessageSolution> <MessageID>1074</MessageID> <Description>Solution: Make at least %1 available on the drive containing the "%2" directory.</Description> </MessageSolution> <MessageSolution> <MessageID>1076</MessageID> <Description>Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network.</Description> </MessageSolution> <MessageSolution> <MessageID>1077</MessageID> <Description>Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network.</Description> </MessageSolution> <MessageSolution> <MessageID>1080</MessageID> <Description>Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. SMS Site Component Manager uses the %1 service to install SMS server components, and cannot install component %3 until the existing %1 service can be deinstalled. If this problem persists and you cannot fix it, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1081</MessageID> <Description>Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. Possible cause: Something other than SMS deleted account "%3" or changed its password. Solution: Reset the site using SMS Setup. SMS Site Component Manager will recreate the account as part of the reset process. SMS Site Component Manager uses the %1 service to install SMS server components, and cannot install component %4 until the %1 service can be installed. If this problem persists and you cannot fix it, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1082</MessageID> <Description>Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the SMS Service or Site System Connection accounts are properly configured to allow SMS to administer the site system. If advanced security verify the site server machine account are properly configured to allow SMS to administer the site system. Possible cause: The service account on the site system is disabled due to password expiration policy. Solution: Re-enable the service account. Possible cause: Something other than SMS deleted account "%3" or changed its password. Solution: Reset the site using SMS Setup. SMS Site Component Manager will recreate the account as part of the reset process. Possible cause: The account "%3" is disabled. Solution: Enable the account. SMS Site Component Manager uses the %1 service to install SMS server components, and cannot install component %4 until the %1 service can be started. If this problem persists and you cannot fix it, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1083</MessageID> <Description>Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. SMS Site Component Manager cannot install component %7 until the program runs successfully. If this problem persists and you cannot fix it, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1084</MessageID> <Description>Possible cause: You deleted account "%3" or changed its password, but forgot to notify SMS. Solution: Use SMS Setup to modify the installation of the site. Specify the correct account and password in SMS Setup. Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system.</Description> </MessageSolution> <MessageSolution> <MessageID>1085</MessageID> <Description>Possible cause: You deleted account "%3" or changed its password, but forgot to notify SMS. Solution: Use SMS Setup to modify the installation of the site. Specify the correct account and password in SMS Setup. Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. Possible cause: The account "%3" is disabled. Solution: Enable the account.</Description> </MessageSolution> <MessageSolution> <MessageID>1086</MessageID> <Description>Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. If this problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1087</MessageID> <Description>Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the SMS Service or Site System Connection accounts are properly configured to allow SMS to administer the site system. If advanced security verify the site server machine account is properly configured to allow SMS to administer the site system. Possible cause: The account "%3" is disabled. Solution: Enable the account. If this problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1090</MessageID> <Description>Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. If this problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1091</MessageID> <Description>Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. If this problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1098</MessageID> <Description>Solution: Review the status messages reported by SMS Executive on this site system, and fix any problems it is experiencing.</Description> </MessageSolution> <MessageSolution> <MessageID>1104</MessageID> <Description>Possible cause: The component is experiencing a severe problem that caused it to stop unexpectedly. Solution: Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1107</MessageID> <Description>Possible cause: The component is scheduled to run so frequently that it cannot complete its work before the next scheduled run time. Solution: Adjust the component's schedule in the SMS Administrator console so that it will not run so frequently. Possible cause: The component is running for an abnormally long time. Solution: Examine the other status messages reported by the component. If the component is experiencing a problem, correct it.</Description> </MessageSolution> <MessageSolution> <MessageID>1108</MessageID> <Description>Possible cause: The DLL was somehow corrupted or deleted. Solution: Restore the DLL by manually copying it from your SMS CD to \"%1\". Possible cause: The file "%1" exists, but something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS component can access the file. Possible cause: The DLL depends on another DLL, which does not exist or cannot be found via the PATH environment variable. Solution: Determine all of the DLLs that this DLL depends on (using Depends.exe from the Win32 SDK) and insure they exist and can be found via the PATH environment variable for the user account that the SMS_EXECUTIVE service runs under.</Description> </MessageSolution> <MessageSolution> <MessageID>1109</MessageID> <Description>Possible cause: The DLL was somehow corrupted or deleted. Solution: Restore the DLL by manually copying it from your SMS CD to \"%1\". Possible cause: This is a defective DLL that is part of an add-on product to Microsoft Systems Management Server. The DLL is defective because it does not export a ThreadMain() function. Solution: Contact the manufacturer of this product for more information.</Description> </MessageSolution> <MessageSolution> <MessageID>1210</MessageID> <Description>Possible cause: The program and command-line arguments are blank or contain an invalid escape sequence. Solution: Correct the value of the Program box on the Actions tab of the Status Filter Rule Properties page in the SMS Administrator console. (Note that you are not limited to %2 characters in the Program box.).</Description> </MessageSolution> <MessageSolution> <MessageID>1211</MessageID> <Description>Possible cause: The Status Filter Rule specifies a program that is invalid or does not exist. Solution: Correct the value of the Program box on the Actions tab of the Status Filter Rule Properties page in the SMS Administrator console. (Note that you are not limited to %3 characters in the Program box.) Be sure to explicitly specify the path to the program. For example, specify "c:\winnt\system32\net.exe" instead of just "net.exe"..</Description> </MessageSolution> <MessageSolution> <MessageID>1212</MessageID> <Description>Possible cause: The Status Filter Rule specifies a program that runs interactively and the program will not exit until it receives user input. This would happen, for example, if you specified "notepad.exe" as the program. Solution: First correct the Status Filter Rule to specify a program that runs to completion without requiring user input; this is done by editing the Program box on the Actions tab of the Status Filter Rule Properties page in the SMS Administrator console. (Note that you are not limited to %3 characters in the Program box.) Then verify that the old program is not still running on the site server using the Windows NT Task Manager. If the old program is still running, use End Process in Task Manager to stop it. Possible cause: The Status Filter Rule specifies a program that takes a long time to run. Solution: Ignore this message, but consider changing the Status Filter Rule to specify a program that runs quickly. Slow programs, when executed frequently, will slow down the rate at which SMS Status Manager can process status messages, and might cause a large number of running processes to build up on your site server. If too many processes build up, the general performance of the site server might be affected..</Description> </MessageSolution> <MessageSolution> <MessageID>1214</MessageID> <Description>Possible cause: The system clock on computer "%2" is not synchronized with the site server's system clock. Most likely, the system clock on computer "%2" is set to some date greater than 2035 or less than 1970. Solution: Synchronize the system clock of computer "%2" with the site server's system clock. Please refer to your Windows NT Server documentation or the Microsoft Knowledge Base for further information. When SMS Status Manager receives status messages with invalid time stamps, it will stamp these messages with the current system time on the site server. The messages will then be processed successfully, but their time and date might not be truly representative of when they were reported in real time. SMS Status Manager will continue to report this problem every 24 hours until you fix it.</Description> </MessageSolution> <MessageSolution> <MessageID>1215</MessageID> <Description>Possible cause: The system clock on computer "%2" is %3 or more seconds ahead of the site server's system clock. Solution: Synchronize the system clock of computer "%2" with the site server's system clock. Please refer to your Windows NT Server documentation or the Microsoft Knowledge Base for further information. SMS Status Manager will process status messages with improper time stamps when the site server's system clock surpasses the improper time stamps. For example, this status message will not be processed for %3 seconds. SMS Status Manager will continue to report this problem every 24 hours until you fix it. SMS Status Manager will not report this problem if the system clock of computer "%2" is less than %4 seconds ahead of the site server's system clock. This interval is configurable in the SMS site control file. Please refer to the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>1309</MessageID> <Description>Possible cause: the DHCP server is running in a domain in which the SMS Service account is not available. (Network Discovery runs under the SMS Service account as part of SMS Executive.) Solution: Create an account on the DHCP server's domain with the same name and password as the SMS Service account.</Description> </MessageSolution> <MessageSolution> <MessageID>1310</MessageID> <Description>Solution: If you are using Microsoft DHCP servers, then refer to the specific error string for details. This error message means that fewer clients and networks will be found than otherwise. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs.</Description> </MessageSolution> <MessageSolution> <MessageID>1311</MessageID> <Description>Solution: Ensure that the TCP/IP stack is installed and running. Also, verify that you are using Windows NT version 4.0 or later. This error message means that fewer clients and networks will be found than otherwise. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs.</Description> </MessageSolution> <MessageSolution> <MessageID>1312</MessageID> <Description>Possible cause: Some other network software on the server is preventing Network Discovery from joining the OSPF multicast group. Solution: Ensure that the TCP/IP stack is installed and running. Also, verify that you are using Windows NT version 4.0 or later. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs.</Description> </MessageSolution> <MessageSolution> <MessageID>1313</MessageID> <Description>Solution: Increase the duration of the discovery. In the Network Discovery Properties dialog box, on the Schedule tab, select a schedule and open the Schedule dialog box. Note that the duration of the discovery is the amount of time spent performing protocol transactions, not the overall time Network Discovery performs processing.</Description> </MessageSolution> <MessageSolution> <MessageID>1314</MessageID> <Description>Possible cause: CIM Object Manager is not installed on this computer. Solution: Install CIM Object Manager by running Sms\bin\i386\wmicore.exe.</Description> </MessageSolution> <MessageSolution> <MessageID>1315</MessageID> <Description>Possible cause: This computer has an incompatible version of CIM Object Manager, or there was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe.</Description> </MessageSolution> <MessageSolution> <MessageID>1316</MessageID> <Description>Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running "Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF". Possible cause: There was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe.</Description> </MessageSolution> <MessageSolution> <MessageID>1317</MessageID> <Description>Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running "Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF". Possible cause: There was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe.</Description> </MessageSolution> <MessageSolution> <MessageID>1318</MessageID> <Description>Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running "Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF". Possible cause: There was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe.</Description> </MessageSolution> <MessageSolution> <MessageID>1319</MessageID> <Description>Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running "Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF". Possible cause: There was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe.</Description> </MessageSolution> <MessageSolution> <MessageID>1320</MessageID> <Description>Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF. Possible cause: There was an internal error within CIM Object Manager. Solution: Re-install CIM Object Manager by running Sms\bin\i386\wmicore.exe.</Description> </MessageSolution> <MessageSolution> <MessageID>1321</MessageID> <Description>Possible cause: Too many SNMP-related applications are running on this computer. Solution: Close some SNMP-related applications. Possible cause: An internal error. Solution: Re-run Network Discovery. If that does not work, reboot. If that does not work, contact your network administrator.</Description> </MessageSolution> <MessageSolution> <MessageID>1322</MessageID> <Description>Possible cause: There is not enough free disk space on the SMS site server. Solution: Free some disk space and re-run Network Discovery.</Description> </MessageSolution> <MessageSolution> <MessageID>1323</MessageID> <Description>Possible cause: There is not enough free disk space on the SMS site server. Solution: Free some disk space and re-run Network Discovery.</Description> </MessageSolution> <MessageSolution> <MessageID>1324</MessageID> <Description>Possible cause: The specified domains do not exist. Solution: Re-specify domains; go to the Network Discovery Properties dialog box, Domains tab. Possible cause: Domain access problems exist. Solution: Contact your network administrator.%12</Description> </MessageSolution> <MessageSolution> <MessageID>1405</MessageID> <Description>Solution: Review the status messages previously reported by SMS NT Logon Server Manager to determine the exact reasons for this failure.</Description> </MessageSolution> <MessageSolution> <MessageID>1406</MessageID> <Description>Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has.</Description> </MessageSolution> <MessageSolution> <MessageID>1407</MessageID> <Description>Possible cause: Domain "%1" does not exist. Solution: Using the SMS Administrator console, remove domain "%1" from the lists of domains in the Windows Networking Logon Discovery and/or Client Installation methods. Add the correct domain to the lists. Possible cause: The all of the domain controllers are turned off, not connected to the network, or not functioning properly. Solution: Verify that the domain controllers are turned on, connected to the network, and functioning properly. Possible cause: SMS NT Logon Server Manager does not have sufficient access rights to remotely administer the domain controllers. Solution: Verify that the Site System Connection Accounts are properly configured to allow SMS to remotely administer the domain controllers. Possible cause: Network problems are preventing SMS NT Logon Server Manager from properly accessing the domain controllers. Solution: Investigate and correct any problems with your network.</Description> </MessageSolution> <MessageSolution> <MessageID>1412</MessageID> <Description>Possible cause: Every NTFS drive on the domain controller has less than 50 MB of free disk space. Solution: Either free up enough space on an NTFS drive or manually create the "SMSLOGON" directory on the root directory of an NTFS drive and share it out as "SMSLOGON". If you manually create the directory, it might have less than 50 MB of free disk space.</Description> </MessageSolution> <MessageSolution> <MessageID>1413</MessageID> <Description>Possible cause: The domain controller is turned off, not connected to the network, or not functioning properly. Solution: Verify that the domain controller is turned on, connected to the network, and functioning properly. Possible cause: SMS NT Logon Server Manager does not have sufficient access rights to remotely administer the domain controller. Solution: Verify that the Site System Connection Accounts are properly configured to allow SMS to remotely administer the domain controller. Possible cause: Network problems are preventing SMS NT Logon Server Manager from properly accessing the domain controller. Solution: Investigate and correct any problems with your network.</Description> </MessageSolution> <MessageSolution> <MessageID>1415</MessageID> <Description>Possible cause: Site "%1" is temporarily out of service. Solution: Ignore this message, but bring site "%1" back into service soon. Possible cause: Site "%1" was deinstalled. Solution: Ignore this message. Eventually the SMS NT Logon Server Manager will remove site "%1" from the list of sites that use this domain for Windows Networking Logon Discovery and Client Installation.</Description> </MessageSolution> <MessageSolution> <MessageID>1416</MessageID> <Description>Possible cause: Site "%1" is temporarily out of service. Solution: Bring site "%1" back into service. Possible cause: Site "%1" was deinstalled. Solution: Ignore this message.</Description> </MessageSolution> <MessageSolution> <MessageID>1419</MessageID> <Description>Possible cause: Low disk space on the drive containing the site control file. Solution: Make more space available on that drive. Possible cause: The file is being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS Setup and reset the current installation. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1420</MessageID> <Description>Possible cause: The file exists, but it is corrupt. Solution: Restore the site control file from a backup copy, or run SMS Setup and reset the current installation. Possible cause: The file is being read from a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1500</MessageID> <Description>Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has.</Description> </MessageSolution> <MessageSolution> <MessageID>1503</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure.</Description> </MessageSolution> <MessageSolution> <MessageID>1504</MessageID> <Description>Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1505</MessageID> <Description>Possible cause: Low disk space on the drive containing the file "%1". Solution: Make disk space is available on that drive. Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1600</MessageID> <Description>Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has.</Description> </MessageSolution> <MessageSolution> <MessageID>1603</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure.</Description> </MessageSolution> <MessageSolution> <MessageID>1604</MessageID> <Description>Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1605</MessageID> <Description>Possible cause: Low disk space on the drive containing the file "%1". Solution: Make disk space is available on that drive. Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1701</MessageID> <Description>Possible cause: The server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the server is turned on, connected to the network, and functioning properly. Possible cause: SMS NW Logon Server Manager does not have sufficient access rights to remotely administer the server. Solution: Verify that the Site System Connection Accounts are properly configured to allow SMS to remotely administer the server. Possible cause: Network problems are preventing SMS NW Logon Server Manager from properly accessing the server. Solution: Investigate and correct any problems with your network.</Description> </MessageSolution> <MessageSolution> <MessageID>1706</MessageID> <Description>Solution: Review the status messages previously reported by SMS NW Logon Server Manager to determine the exact reasons for this failure.</Description> </MessageSolution> <MessageSolution> <MessageID>1707</MessageID> <Description>Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has.</Description> </MessageSolution> <MessageSolution> <MessageID>1708</MessageID> <Description>Possible cause: Server "%1" does not exist. Solution: Using the SMS Administrator console, remove server "%1" from the lists of servers in the Windows Networking Logon Discovery and/or Client Installation methods. Add the correct server to the lists. Possible cause: The server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the server is turned on, connected to the network, and functioning properly. Possible cause: SMS NW Logon Server Manager does not have sufficient access rights to remotely administer the server. Solution: Verify that the Site System Connection Accounts are properly configured to allow SMS to remotely administer the server. Possible cause: Network problems are preventing SMS NW Logon Server Manager from properly accessing the server. Solution: Investigate and correct any problems with your network.</Description> </MessageSolution> <MessageSolution> <MessageID>1713</MessageID> <Description>Possible cause: Every volume on the server has less than 50 MB of free space. Solution: Either free up enough space on a volume or manually create the "SMSLOGON" directory on the root directory of a volume. If you manually create the directory, it might have less than 50 MB of free space.</Description> </MessageSolution> <MessageSolution> <MessageID>1714</MessageID> <Description>Possible cause: The server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the server is turned on, connected to the network, and functioning properly. Possible cause: SMS NW Logon Server Manager does not have sufficient access rights to remotely administer the server. Solution: Verify that the Site System Connection Accounts are properly configured to allow SMS to remotely administer the server. Possible cause: Network problems are preventing SMS NW Logon Server Manager from properly accessing the server. Solution: Investigate and correct any problems with your network.</Description> </MessageSolution> <MessageSolution> <MessageID>1716</MessageID> <Description>Possible cause: Site "%1" is temporarily out of service. Solution: Ignore this message, but bring site "%1" back into service soon. Possible cause: Site "%1" was deinstalled. Solution: Ignore this message. Eventually the SMS NW Logon Server Manager will remove site "%1" from the list of sites that use this server for NetWare Bindery Logon Discovery and Client Installation.</Description> </MessageSolution> <MessageSolution> <MessageID>1717</MessageID> <Description>Possible cause: Site "%1" is temporarily out of service. Solution: Bring site "%1" back into service. Possible cause: Site "%1" was deinstalled. Solution: Ignore this message.</Description> </MessageSolution> <MessageSolution> <MessageID>1720</MessageID> <Description>Possible cause: Low disk space on the drive containing the site control file. Solution: Make more space available on that drive. Possible cause: The file is being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS Setup and reset the current installation. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1721</MessageID> <Description>Possible cause: The file exists, but it is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS Setup and reset the current installation. Possible cause: The file is being read from a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1723</MessageID> <Description>Solution: Install an appropriate NetWare bindery redirector on the site server. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>1724</MessageID> <Description>Solution: SMS NW Logon Server Manager will automatically recreate the directory now.</Description> </MessageSolution> <MessageSolution> <MessageID>1725</MessageID> <Description>Solution: Only one SMS site should be configured to use server "%1" as an SMS Logon Point. Using the SMS Administrator console, remove this server from the list of Logon Points used for the SMS NetWare Bindery Logon Discovery and Installation methods, either for this site or the site that is currently using this server as an SMS Logon Point.</Description> </MessageSolution> <MessageSolution> <MessageID>1800</MessageID> <Description>Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has.</Description> </MessageSolution> <MessageSolution> <MessageID>1803</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure.</Description> </MessageSolution> <MessageSolution> <MessageID>1804</MessageID> <Description>Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1805</MessageID> <Description>Possible cause: Low disk space on the drive containing the file "%1". Solution: Make disk space is available on that drive. Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1808</MessageID> <Description>Solution: Install an appropriate NetWare bindery redirector on the site server. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>1900</MessageID> <Description>Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has.</Description> </MessageSolution> <MessageSolution> <MessageID>1903</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure.</Description> </MessageSolution> <MessageSolution> <MessageID>1904</MessageID> <Description>Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>1905</MessageID> <Description>Possible cause: Low disk space on the drive containing the file "%1". Solution: Make disk space is available on that drive. Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2001</MessageID> <Description>Possible cause: SMS NDS Logon Server Manager does not have sufficient access rights to remotely administer the container. Solution: Verify that the Site System Connection Accounts are properly configured to allow SMS to remotely administer container. Possible cause: Network problems are preventing SMS NDS Logon Server Manager from properly accessing the container. Solution: Investigate and correct any problems with your network.</Description> </MessageSolution> <MessageSolution> <MessageID>2006</MessageID> <Description>Possible cause: SMS NDS Logon Server Manager does not have sufficient access rights to remotely administer the container or volume. Solution: Verify that the Site System Connection Accounts are properly configured to allow SMS to remotely administer container or volume. Possible cause: Network problems are preventing SMS NDS Logon Server Manager from properly accessing the container or volume. Solution: Investigate and correct any problems with your network.</Description> </MessageSolution> <MessageSolution> <MessageID>2007</MessageID> <Description>Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct and problems it is experiencing.</Description> </MessageSolution> <MessageSolution> <MessageID>2008</MessageID> <Description>Possible cause: The site server is low on virtual memory or not functioning properly. Solution: Verify that the site server is functioning properly. Stop any processes that are using up all of the virtual memory. If necessary, reboot the site server to free up virtual memory.</Description> </MessageSolution> <MessageSolution> <MessageID>2016</MessageID> <Description>Possible cause: Site "%1" is temporarily out of service. Solution: Ignore this message, but bring site "%1" back into service soon. Possible cause: Site "%1" was deinstalled. Solution: Ignore this message. Eventually the SMS NDS Logon Server Manager will remove site "%1" from the list of sites that use this container and volume for NetWare NDS Logon Discovery and Client Installation.</Description> </MessageSolution> <MessageSolution> <MessageID>2017</MessageID> <Description>Possible cause: Site "%1" is temporarily out of service. Solution: Bring site "%1" back into service. Possible cause: Site "%1" was deinstalled. Solution: Ignore this message.</Description> </MessageSolution> <MessageSolution> <MessageID>2020</MessageID> <Description>Possible cause: Low disk space on the drive containing the site control file. Solution: Make more space available on that drive. Possible cause: The file is being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the site control file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The site control file exists, but it is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS Setup and reset the current installation. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2021</MessageID> <Description>Possible cause: Low disk space on the drive containing the site control file. Solution: Make more space available on that drive. Possible cause: The file is being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS Setup and reset the current installation. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2023</MessageID> <Description>Solution: Install an appropriate NetWare NDS redirector on the site server. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>2024</MessageID> <Description>Solution: Only one SMS site should be configured to use context "%1" as an SMS Logon Point. Using the SMS Administrator console, remove this context from the list of Logon Points used for the NetWare NDS Logon Discovery and Installation methods, either for this site or the site that is currently using this context as an SMS Logon Point.</Description> </MessageSolution> <MessageSolution> <MessageID>2100</MessageID> <Description>Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct and problems it is experiencing.</Description> </MessageSolution> <MessageSolution> <MessageID>2103</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure.</Description> </MessageSolution> <MessageSolution> <MessageID>2104</MessageID> <Description>Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2105</MessageID> <Description>Possible cause: Low disk space on the drive containing the file "%1". Solution: Make disk space is available on that drive. Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2108</MessageID> <Description>Solution: Install an appropriate NetWare NDS redirector on the site server. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>2200</MessageID> <Description>Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct and problems it is experiencing.</Description> </MessageSolution> <MessageSolution> <MessageID>2203</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure.</Description> </MessageSolution> <MessageSolution> <MessageID>2204</MessageID> <Description>Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2205</MessageID> <Description>Possible cause: Low disk space on the drive containing the file "%1". Solution: Make disk space is available on that drive. Possible cause: The file "%1" exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2302</MessageID> <Description>Possible cause: Distribution manager does not have access to either the package source directory or the distribution point. Solution: Verify that distribution manager can access the package source directory/distribution point. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility. Possible cause: There is not enough disk space available on the site server computer or the distribution point. Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point. Possible cause: The package source directory contains files that might be in use by an active process. Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.</Description> </MessageSolution> <MessageSolution> <MessageID>2305</MessageID> <Description>Possible cause: The Source directory is not specified. Solution: Verify that you have specified the package source directory on the Data Source tab in the Package Properties dialog box in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>2306</MessageID> <Description>Solution: Make sure you have specified a valid package source directory on the Data Source tab in the Package Properties dialog box in the SMS Administrator console. If you specify a local path, it must be a local path on the site server. If you specify a path on a network drive, verify that the path exists and that the path is typed correctly.</Description> </MessageSolution> <MessageSolution> <MessageID>2307</MessageID> <Description>Possible cause: SMS Distribution Manager does not have sufficient rights to the package source directory. Solution: Verify that the SMS Service account has at least Read access to the directory you specify as the package source directory. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.</Description> </MessageSolution> <MessageSolution> <MessageID>2308</MessageID> <Description>Possible cause: The SMS Service account does not have sufficient access rights to delete file "%2". Solution: Verify that the file's permissions will permit the SMS Service account to delete it.</Description> </MessageSolution> <MessageSolution> <MessageID>2309</MessageID> <Description>Possible cause: The drive containing file "%4" does not have enough free disk space. Solution: Verify that there is enough free disk space. Possible cause: If the package source directory "%2" is on a remote machine, that machine is turned off, not connected to the network, or not functioning properly. Solution: Verify that the machine containing the package source directory is turned on, connected to the network, and functioning properly. Verify that the network itself is functioning properly. Possible cause: The SMS Service account does not have sufficient access rights to the package source directory "%2" or the file "%3". Solution: Verify that the SMS Service account has read access to the package source directory and the problem file.</Description> </MessageSolution> <MessageSolution> <MessageID>2312</MessageID> <Description>Possible cause: SMS Distribution Manager cannot update the package data in the SMS site database. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. Possible cause: Low disk space on the drive containing the package source files. Solution: Make more space available on that drive. Possible cause: The package source files are being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: The package source files exist, but something other than SMS has changed the permissions or attributes of the files or the directory containing them. Solution: Restore the files' permissions or attributes so that this SMS service can access the files. Possible cause: The package source files exist, but they are corrupt. Solution: Delete the files and replace them with backup copies. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2313</MessageID> <Description>Possible cause: The share type or the share name have been changed since the package was created. Solution: Verify that the share defined for this package is accessible to SMS Distribution Manager running on the site server and that the name of the share has not been changed. If users are currently accessing the share, disconnect them before making any changes to the share. If the package distribution point is located on a Windows computer, you can force users to disconnect by clicking on the "Disconnect users from distribution points" box in the Data Access tab of the Package Properties dialog box.</Description> </MessageSolution> <MessageSolution> <MessageID>2316</MessageID> <Description>Possible cause: The SMS Service account does not have sufficient access rights to file "%2". Solution: Verify that the SMS Service account has delete access to the file.</Description> </MessageSolution> <MessageSolution> <MessageID>2318</MessageID> <Description>Possible cause: The specified share is a hidden Windows NT drive share or a hidden Windows NT admin share. Solution: Specify a different share name on the Data Access tab of the Package Properties dialog box in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>2319</MessageID> <Description>Possible cause: The compressed image "%2" is either missing or corrupt. SMS Distribution Manager will attempt to recover the package by requesting a new compressed package image from the site that sent it.</Description> </MessageSolution> <MessageSolution> <MessageID>2320</MessageID> <Description>Possible cause: At least %2 megabytes of free disk space are required. Solution: Allocate more free disk space for the site server.</Description> </MessageSolution> <MessageSolution> <MessageID>2321</MessageID> <Description>Possible cause: The drive containing directory "%3" does not have enough free disk space. Solution: Verify that there is enough free disk space.</Description> </MessageSolution> <MessageSolution> <MessageID>2323</MessageID> <Description>Possible cause: SMS Distribution Manager cannot access the NAL. Solution: Use the SMS Service Manager to enable logging for SMS Distribution Manager. Then, investigate the log file for specific NAL errors. Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2324</MessageID> <Description>Possible cause: Windows NT distribution points might not have at least one available NTFS drive. Solution: Verify that there is at least one NTFS drive with enough free disk space to store the package. Then, verify that the distribution point directory exists, has the proper permissions, and is accessible.</Description> </MessageSolution> <MessageSolution> <MessageID>2325</MessageID> <Description>Possible cause: SMS Distribution Manager does not have sufficient rights to create subdirectories on the distribution point. Solution: In the SMS Administrator console, create a new site system connection account or verify that an existing account has sufficient privileges.</Description> </MessageSolution> <MessageSolution> <MessageID>2326</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2327</MessageID> <Description>Solution: Verify that there is enough free disk space on the site server to update the package.</Description> </MessageSolution> <MessageSolution> <MessageID>2328</MessageID> <Description>Possible cause: SMS Distribution Manager does not have sufficient rights to read from the package source directory or to write to the destination directory on the distribution point. Solution: In the SMS Administrator console, verify that the site system connection accounts have sufficient privileges to the source and destination directories. Possible cause: The distribution point might not be accessible to SMS Distribution Manager running on the site server. Solution: If users are currently accessing the package files on the distribution point, disconnect the users first. If the package distribution point is located on a Windows NT computer, you can force users to disconnect by clicking on the "Disconnect users from distribution points" box in the Data Access tab of the Package Properties dialog box. Possible cause: The distribution point does not have enough free disk space to store the package. Solution: Verify that there is enough free disk space. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.</Description> </MessageSolution> <MessageSolution> <MessageID>2332</MessageID> <Description>Possible cause: The distribution point might not be accessible to SMS Distribution Manager running on the site server. Solution: If users are currently accessing the package files on the distribution point, disconnect the users first.</Description> </MessageSolution> <MessageSolution> <MessageID>2336</MessageID> <Description>Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file.</Description> </MessageSolution> <MessageSolution> <MessageID>2337</MessageID> <Description>Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file.</Description> </MessageSolution> <MessageSolution> <MessageID>2340</MessageID> <Description>Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file.</Description> </MessageSolution> <MessageSolution> <MessageID>2341</MessageID> <Description>Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file.</Description> </MessageSolution> <MessageSolution> <MessageID>2343</MessageID> <Description>Solution: Verify that "%2" has at least %3 kbytes of free disk.%12</Description> </MessageSolution> <MessageSolution> <MessageID>2344</MessageID> <Description>Possible cause: Distribution Manager requires that IIS base components be installed on the local SMS Site Server in order to create the virtual directory. Distribution Manager also requires that IIS Web Services be installed on the Distribution Point Server that needs to support Background Intelligent Transfer Service (BITS). Solution: Verify that IIS base components are installed on the local SMS Site Server, and IIS Web Services are installed on the Distribution Point Server.</Description> </MessageSolution> <MessageSolution> <MessageID>2345</MessageID> <Description>Possible cause: The IIS base components may not be installed on the local SMS Site Server or IIS Web Services may not be installed on the Distribution Point Server. Solution: Verify that IIS base components are installed on the local SMS Site Server, and IIS Web Services are installed on the Distribution Point Server.</Description> </MessageSolution> <MessageSolution> <MessageID>2346</MessageID> <Description>Possible cause: The specified share is a hidden SMS share. Solution: Specify a different share name on the Data Access tab of the Package Properties dialog box in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>2348</MessageID> <Description>Possible cause: The compressed image "%2" is either missing or corrupt. SMS Distribution Manager will not attempt to recover the package. Please update the package to repair the compressed image</Description> </MessageSolution> <MessageSolution> <MessageID>2351</MessageID> <Description>Possible cause: A package update has recently been triggered. The package source site has been recently recovered. Possible workaround: If the package has been recently updated, verify that sites "%2" receive the package directly from package source site. If package source site has been recently recovered, verify that all recovery steps for this package have been followed.</Description> </MessageSolution> <MessageSolution> <MessageID>2352</MessageID> <Description>Possible cause: A package update has recently been triggered. This site "%5" has been recently recovered. Possible workaround: If the package has been recently updated, verify that sites "%2" receive the package directly from package source site. If this site has been recently recovered, verify that all recovery steps for this package have been followed.</Description> </MessageSolution> <MessageSolution> <MessageID>2353</MessageID> <Description>Possible cause: Distribution Manager requires that IIS base components be installed on the local SMS Site Server in order to configure the ports. Distribution Manager also requires that IIS Web Services be installed on the Distribution Point Server that needs to support Background Intelligent Transfer Service (BITS). Solution: Verify that IIS base components are installed on the local SMS Site Server, and IIS Web Services are installed on the Distribution Point Server.</Description> </MessageSolution> <MessageSolution> <MessageID>2354</MessageID> <Description>Possible cause: The package status file is signed by the BDP client and then matched with the public key of the client on the site server. This signature verification failure will cause this error. This error can also happen if the BDP client is not in the boundaries of the site where the BDP Site System belongs to. Solution: Verify that the correct Branch Distribution Point is reporting this message. Make sure that the BDP client is assigned to and is in the boundaries of the site where the BDP Site System was created.</Description> </MessageSolution> <MessageSolution> <MessageID>2400</MessageID> <Description>Possible cause: The file "%1" exists, but it is corrupt. Solution: Delete the file, and then stop and restart SMS SQL Monitor. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. Possible cause: The file is being read from a remote computer (the site server) that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: The file smsxp.dll exists, but something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2401</MessageID> <Description>Possible cause: A SQL Server problem prevented this task from running. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. Most database maintenance tasks are designed to optimize database performance. If a task fails once, the effect on the system will be small and you can ignore the failure. But if a task fails repeatedly you should investigate and fix the problem.</Description> </MessageSolution> <MessageSolution> <MessageID>2402</MessageID> <Description>Possible cause: The SQL command contains syntax errors. Solution: Manually execute the command using the Microsoft SQL Server ISQL/w application, and fix any problems you discover. When you are satisfied the command runs successfully in ISQL/w, correct in the SMS Administrator console. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the Smsdbmon.log for SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2407</MessageID> <Description>Possible cause: Either table "%2" or column "%3" of table "%2" does not exist in the SMS site database. Solution: If you modified table "%2", restore it to its original, unmodified state. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2416</MessageID> <Description>Possible cause: You changed the service setting for the SMS Backup service, but forgot to notify SMS. Solution: Use SMS Setup to modify the installation of the site. Possible cause: SMS SQL Monitor does not have sufficient access rights to administer the site server. Solution: Verify that the server connection accounts are properly configured to allow the SMS SQL Monitor to administer the site server.</Description> </MessageSolution> <MessageSolution> <MessageID>2420</MessageID> <Description>Possible cause: The task has been enabled recently or updated to run today, but this occurred after the end of the scheduled time. Or, other tasks that were scheduled to run today did not complete before the end of the scheduled time, preventing this task from starting. Solution: Allow more time for this task to run, or schedule this task to run at another day or time. You can configure the schedule for this SQL command or task in the Configuration Manager console under Site Database / Site Management / <site code> - <site name> / Site Settings / Site Maintenance -> SQL Commands or Tasks.</Description> </MessageSolution> <MessageSolution> <MessageID>2500</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2501</MessageID> <Description>Possible cause: The SMS SQL Monitor service is not running. Solution: Restart SMS SQL Monitor. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. Possible cause: The collection was created before SMS SQL Monitor had time to install the trigger. Solution: Look in the registry for HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Triggers\<site_code>\Coll_Add. If that key exists, the trigger was installed (make sure Active is set to 0x1). If not, SMS Collection Evaluator was unable to write to the registry. In that case, check for low disk space on the site server, or an SMS Service account that lacks privileges to write to the registry.</Description> </MessageSolution> <MessageSolution> <MessageID>2502</MessageID> <Description>Possible cause: The SMS SQL Monitor service is not running. Solution: Restart SMS SQL Monitor. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. Possible cause: The collection was created before SMS SQL Monitor had time to install the trigger. Solution: Look in the registry for HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Triggers\<site_code>\Coll_Upd. If that key exists, the trigger was installed (make sure Active is set to 0x1). If not, SMS Collection Evaluator was unable to write to the registry. In that case, check for low disk space on the site server, or an SMS Service account that lacks privileges to write to the registry.</Description> </MessageSolution> <MessageSolution> <MessageID>2504</MessageID> <Description>Possible cause: The collection was deleted shortly after being created or updated, but SMS SQL Monitor and SMS Collection Evaluator processed the create or update file out of sequence. Solution: None needed. The create or update file will simply not be processed for the nonexistent collection.</Description> </MessageSolution> <MessageSolution> <MessageID>2505</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2507</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2509</MessageID> <Description>Solution: Update the collection manually using the SMS Administrator console. Right-click the collection, point to All Tasks, then choose Update Collection Membership. Alternatively, you can specify an update schedule for the collection using the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>2511</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2512</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2514</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2517</MessageID> <Description>Possible cause: Low disk space on the disk drive containing \Sms\inboxes\colleval.box. Solution: Make more space available on that drive. Otherwise, look for other status messages before this one; they will give you clues about what is happening.</Description> </MessageSolution> <MessageSolution> <MessageID>2518</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2519</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2520</MessageID> <Description>Possible cause: low disk space on the drive containing the file "%1". Solution: Make more space available on that drive. Possible cause: The file "%1" is read-only. Solution: Clear the Read-only attribute from the file's properties dialog box. Possible cause: Another process has the file "%1" locked. Solution: Wait for the other process to finish, then retry the operation. Possible cause: The file "%1" is corrupt. Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2521</MessageID> <Description>Possible cause on primary sites: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. Possible cause on secondary sites: The file in \Sms\inboxes\colleval.box is corrupt. Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2522</MessageID> <Description>Possible cause: low disk space on the drive containing the file "%1". Solution: Make more space available on that drive. Possible cause: The file "%1" is read-only. Solution: Clear the Read-only attribute from the file's properties dialog box. Possible cause: Another process has the file "%1" locked. Solution: Wait for the other process to finish, then retry the operation. Possible cause: The file "%1" is corrupt. Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2523</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2524</MessageID> <Description>Possible cause: low disk space on the drive containing the file "%1". Solution: Make more space available on that drive. Possible cause: The file "%1" is read-only. Solution: Clear the Read-only attribute from the file's properties dialog box. Possible cause: Another process has the file "%1" locked. Solution: Wait for the other process to finish, then retry the operation. Possible cause: The file "%1" is corrupt. Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2525</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2526</MessageID> <Description>Possible cause: low disk space on the drive containing the file "%1". Solution: Make more space available on that drive. Possible cause: The file "%1" is read-only. Solution: Clear the Read-only attribute from the file's properties dialog box. Possible cause: Another process has the file "%1" locked. Solution: Wait for the other process to finish, then retry the operation. Possible cause: The file "%1" is corrupt. Solution: Delete the file, and then stop and restart SMS Collection Evaluator. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2527</MessageID> <Description>Possible cause: The file "%1" is corrupt. Solution: Delete the file, stop and restart SMS Collection Evaluator (You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components), and then update all collection memberships; in the SMS Administrator console, right-click Collections, point to All Tasks, and then choose Update Collection Membership.</Description> </MessageSolution> <MessageSolution> <MessageID>2528</MessageID> <Description>Solution: Manually update the subcollection's membership at the parent site; in the SMS Administrator console, right-click the collection, point to All Tasks, then choose Update Collection Membership.</Description> </MessageSolution> <MessageSolution> <MessageID>2529</MessageID> <Description>Possible cause: Low disk space on the drive containing \Sms\inboxes\colleval.box. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2530</MessageID> <Description>Possible cause: Low disk space on the disk drive of the site server inbox. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2531</MessageID> <Description>Possible cause: An SMS Provider failure occurred while inserting the WBEM Query Language (WQL) string into the SQL Server database, or the rule was added improperly. Solution: Recreate the rule in the SMS Administrator console and save it. If the WQL string had been stored correctly, it should remain after it was resaved, and the proper SQL string should be stored in the database.</Description> </MessageSolution> <MessageSolution> <MessageID>2532</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2533</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2535</MessageID> <Description>Solution: Add a name by editing the collection in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>2542</MessageID> <Description>Possible cause: Inventory or Resource classes referenced in the query do not exist at this site, resulting in a SQL error. Solution: Enable the collection of the missing Inventory or Resource information at this site.n Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2543</MessageID> <Description>Possible cause: Inventory or Resource classes referenced in the query do not exist at this site, resulting in a SQL error. Solution: Review the immediately preceding status messages from this component about query rule failures. Enable the collection of the missing Inventory or Resource information at this site. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>2548</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>2549</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>2550</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>2551</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>2552</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>2553</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>2859</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2860</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2861</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2862</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2863</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2864</MessageID> <Description>Solution: Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2868</MessageID> <Description>Possible cause: If SMS is functioning properly, this configuration will not produce any problems. However, if inter-site communication problems interrupt the proper replication of site control files and replicated site control files are lost, the site hierarchy might take a long time to recover or might not recover at all. During this time, parent sites might not have the most up-to-date configuration of this site. Solution: If this happens, you can either reconfigure SMS Site Control Manager to submit heartbeat site control files again, or you can cause it to immediately submit a heartbeat site control file by stopping and restarting SMS Site Control Manager using the SMS Service Manager application.</Description> </MessageSolution> <MessageSolution> <MessageID>2870</MessageID> <Description>Possible cause: Most likely, the file was corrupted during network transmission, which might occur periodically, depending on the performance of your network. If this happens repeatedly, it could be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2900</MessageID> <Description>Solution: Do nothing. CIDM will retry in the next interval. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2901</MessageID> <Description>Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2902</MessageID> <Description>Possible cause: The computer is low on memory or other resources. Solution: Reboot.</Description> </MessageSolution> <MessageSolution> <MessageID>2903</MessageID> <Description>Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: Insufficient permissions on the SMS Service account. Solution: See the SMS documentation for the necessary privileges of the Site Server account, then ensure that the SMS Service account has such privileges. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2904</MessageID> <Description>Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2905</MessageID> <Description>Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: The file is on a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The file is corrupt. Solution: Delete the file, and then stop and restart SMS Client Installation Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2906</MessageID> <Description>Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: The file is on a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The file is corrupt. Solution: Delete the file, and then stop and restart SMS Client Installation Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2907</MessageID> <Description>Possible cause: The registry is full. Solution: Allocate more space for the registry. Possible cause: The computer is low on memory or other resources. Solution: Reboot. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2910</MessageID> <Description>Possible cause: The file %1 was locked by another process. Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>2912</MessageID> <Description>Possible cause: The files were locked by another process. Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The files are corrupt. Solution: Delete the files, and then stop and restart SMS Client Installation Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2916</MessageID> <Description>Possible cause: The files were locked by another process. Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The files are corrupt. Solution: Delete the files, and then stop and restart SMS Client Installation Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>2917</MessageID> <Description>Possible cause: The registry is full. Solution: Allocate more space for the registry. Possible cause: The computer is low on memory or other resources. Solution: Reboot. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>2918</MessageID> <Description>Possible cause: A package definition file for the component does not exist in Clicfg.src or Clicomp.src. Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. Possible cause: Low disk space on the drive containing Clicfg.src or Clicomp.src. Solution: Make more space available on that drive. Possible cause: Something other than SMS has changed the permissions or attributes of Clicfg.src or Clicomp.src or the directory containing them. Solution: Restore the permissions or attributes of Clicfg.src and Clicomp.src so that this SMS service can access them.</Description> </MessageSolution> <MessageSolution> <MessageID>2919</MessageID> <Description>Possible cause: This computer is low on virtual memory. Solution: Do nothing. SMS Client Installation Data Manager will retry in the next interval. Solution: Shut down some applications. Solution: Stop and restart the SMS Executive. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>3000</MessageID> <Description>Possible cause: Low disk space on the drive containing the site control file. Solution: Make more space available on that drive. Possible cause: The file is being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS and reset the current installation. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>3001</MessageID> <Description>Solution: Reboot. If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>3002</MessageID> <Description>Solution: Reboot. If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>3003</MessageID> <Description>Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS and reset the current installation. If you ignore this problem, CCM will continue using any SMS Client Remote Installation account that is available (if specified), but client installations might not be successful.</Description> </MessageSolution> <MessageSolution> <MessageID>3004</MessageID> <Description>Possible cause: The file is being read from a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file's permissions or attributes so that this SMS service can access the file. Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\inboxes\sitectrl.box\history directory on the site server), or run SMS and reset the current installation. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. If you ignore this problem, CCM will continue using previously read information, but client installations might not be successful.</Description> </MessageSolution> <MessageSolution> <MessageID>3005</MessageID> <Description>Possible cause: The computer is low on memory or other resources. Solution: Reboot.</Description> </MessageSolution> <MessageSolution> <MessageID>3006</MessageID> <Description>Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: Insufficient permissions on the SMS Service account. Solution: See the SMS documentation for the necessary privileges of the SMS Service account, then ensure that the SMS Service account has such privileges. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>3007</MessageID> <Description>Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: Insufficient permissions on the SMS Service account. Solution: See the SMS documentation for the necessary privileges of the SMS Service account, then ensure that the SMS Service account has such privileges. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>3008</MessageID> <Description>Possible cause: The registry is full. Solution: Allocate more space for the registry. Possible cause: The computer is low on memory or other resources. Solution: Reboot, or stop and restart the SMS Executive. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>3009</MessageID> <Description>Possible cause: If the Incoming queue threshold (default 100) or the Processing queue threshold (default 150) is being exceeded, there might suddenly be many clients needing installation, in which case simply be aware that it will take a while to get them all installed. However, it is more likely that this error means SMS Client Configuration Manager is not processing CCRs properly. Solution: Stop and restart SMS Client Configuration Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components. Possible cause: If the Retry queue's threshold (default 150) is being exceeded, there is probably a client access problem. Solution: Verify that the SMS Service account or (if specified) the SMS Client Remote Installation account have the required privileges, as specified in the SMS documentation.</Description> </MessageSolution> <MessageSolution> <MessageID>3010</MessageID> <Description>Possible cause: The client is not accessible. Solution: Verify that the client is connected to the network and that the SMS Service account or (if specified) the SMS Client Remote Installation account have the required privileges, as specified in the SMS documentation.</Description> </MessageSolution> <MessageSolution> <MessageID>3011</MessageID> <Description>Possible cause: The client is not accessible. Solution: Verify that the client is connected to the network and that the SMS Service account or (if specified) the SMS Client Remote Installation account have the required privileges, as specified in the SMS documentation.</Description> </MessageSolution> <MessageSolution> <MessageID>3012</MessageID> <Description>Possible cause: Network problems. Solution: Do nothing. SMS Client Configuration Manager will retry in the next interval (the default is 30 days). This error will not cause problems with the operation of SMS. The account maintenance cycle merely deletes obsolete domain accounts.</Description> </MessageSolution> <MessageSolution> <MessageID>3013</MessageID> <Description>Possible cause: A version of the SMS Administrator console earlier than SMS 2.0 SP2 was used to modify the list. These earlier versions recognize and retain only the first account in the list. Solution: To maintain multiple SMS Client Remote Installation accounts for this site, use the latest version of the SMS Administrator console to manage the account list.</Description> </MessageSolution> <MessageSolution> <MessageID>3014</MessageID> <Description>Possible cause: The client is not accessible. Solution: Verify that the client is connected to the network and that the SMS Service account or (if specified) the SMS Client Remote Installation account has the required privileges, as specified in the SMS documentation. Possible cause: A remote client installation account was not specified in the SMS Admin console, the account is not valid, is disabled, or has an expired password. Solution: Ensure one or more valid and active remote client installation accounts are specified in the SMS Admin console, that the account names and passwords are correct, and that the account has the required administrator rights on the target machines.</Description> </MessageSolution> <MessageSolution> <MessageID>3015</MessageID> <Description>Possible cause: The client is offline. Solution: Verify that the client is connected to the network.</Description> </MessageSolution> <MessageSolution> <MessageID>3100</MessageID> <Description>Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has.</Description> </MessageSolution> <MessageSolution> <MessageID>3101</MessageID> <Description>Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has.</Description> </MessageSolution> <MessageSolution> <MessageID>3102</MessageID> <Description>Possible cause: The specified directory, %3, does not exist. Solution: Create it. Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive. Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct any problems it has.</Description> </MessageSolution> <MessageSolution> <MessageID>3200</MessageID> <Description>Possible cause: The MIF file is not formatted correctly. Solution: Check the inboxes\invproc\BADMIFs directory for the MIF. Determine what the error is, correct it, and resubmit the file.</Description> </MessageSolution> <MessageSolution> <MessageID>3201</MessageID> <Description>Possible cause: The file might be corrupt. Solution: The file will be moved to the inboxes\invproc.box\BADRAWs directory. Regenerate the RAW file by reinstalling the client. Possible cause: low disk space on the drive containing the file "%1". Solution: Make more space available on that drive. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>3300</MessageID> <Description>Solution: Configure the site hierarchy properly; it must not contain loops. See the SMS documentation for information on how to create a proper site hierarchy.</Description> </MessageSolution> <MessageSolution> <MessageID>3301</MessageID> <Description>Possible cause: SMS Hierarchy Manager has detected that a child site has the same site code as this site or another child site. Solution: Each site must have a unique site code. Deinstall the child site and reinstall it using a unique site code.</Description> </MessageSolution> <MessageSolution> <MessageID>3302</MessageID> <Description>Possible cause: You attempted to configure this site to report to a different parent site, but you attempted this using an SMS Administrator console that was not connected to this site's database. Solution: To change configure this site to report to a different parent site, use an SMS Administrator console that is connected to the this site's database. If this site is a secondary site, use SMS Setup to configure this site to report to a different parent site.</Description> </MessageSolution> <MessageSolution> <MessageID>3303</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>3304</MessageID> <Description>Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>3305</MessageID> <Description>Possible cause: Site "%3" is using the same site code as another site. Solution: Each site must have a unique site code. Deinstall one of these sites and reinstall it using a unique site code.</Description> </MessageSolution> <MessageSolution> <MessageID>3308</MessageID> <Description>Possible cause: The service account and password are not valid. Solution: Specify a valid service account and password using the SMS Administrator console. Possible cause: The account does not have Administrator permissions and "Log on as a service" rights. Solution: Ensure that the service account is directly or indirectly in the administrator's group on the site server and has 'Logon as a service' rights. Possible cause: The new service account is disabled. Solution: Enable the account. Possible cause: Due to an OS error, the SMS Site Component Manager is marked for deletion. Solution: Perform a site reset and then reboot the site server to recover from this error.</Description> </MessageSolution> <MessageSolution> <MessageID>3313</MessageID> <Description>Possible cause: Service containing the maintenance task, %1, is not installed or in not running. Solution: Check the status of the service containing the maintenance task.</Description> </MessageSolution> <MessageSolution> <MessageID>3319</MessageID> <Description> Solution: Apply Windows QFE 325804 on the site server. This QFE is included on the SMS 2003 CD under the WinQFE directory. Solution: Install Windows 2000 service pack 4 or above on the site server. Solution: Upgrade the site server to Windows Server 2003 or above.</Description> </MessageSolution> <MessageSolution> <MessageID>3400</MessageID> <Description>Solution: Define a valid address at site "%2" for site "%1" in the SMS Administrator console under Site Hierarchy -> %2 -> Site Settings -> Addresses.</Description> </MessageSolution> <MessageSolution> <MessageID>3401</MessageID> <Description>Solution: If you purposefully configured the addresses this way, ignore this message. Otherwise, modify the addresses' scheduling in the SMS Administrator console under Site Hierarchy -> %2 -> Site Settings -> Addresses.</Description> </MessageSolution> <MessageSolution> <MessageID>3500</MessageID> <Description>Possible cause: Remote site server "%2" might not be connected to the LAN. Solution: Verify that site server "%2" is connected to the LAN and functioning properly. Possible cause: Share "%3" might not be accessible. Solution: Verify that share "%3" is visible and that the address connection account has the necessary permissions to access the share. Possible cause: Network load might be too high. Solution: Verify that the network is not saturated. Verify that you can move large amounts of data across the network.</Description> </MessageSolution> <MessageSolution> <MessageID>3501</MessageID> <Description>Possible cause: Remote site server "%2" might be down. Solution: Verify that remote site server "%2" is connected to the network and functioning properly. Possible cause: Remote site server "%2" might not be running RAS Server Service. Solution: Verify that remote site server "%2" is running RAS Server Service. Possible cause: The phone book entry "%3" in the default phone book might not contain the correct information. Solution: Verify that the phone book entry "%3" contains valid information. Possible cause: Share "%4" might not be accessible. Solution: Verify that share "%4" is visible and that the address connection account has the necessary permissions to access the share. For a detailed explanation of the RAS error code, see the Windows NT documentation.</Description> </MessageSolution> <MessageSolution> <MessageID>3502</MessageID> <Description>Possible cause: The destination site server name is missing. Solution: Define a valid address in the SMS Administrator console under Site Hierarchy -> site code - site name -> Site Settings -> Addresses.</Description> </MessageSolution> <MessageSolution> <MessageID>3503</MessageID> <Description>Possible cause: The destination share name is missing. Solution: Define a valid address in the SMS Administrator console under Site Hierarchy -> site code - site name -> Site Settings -> Addresses.</Description> </MessageSolution> <MessageSolution> <MessageID>3504</MessageID> <Description>Possible cause: The targeted installation directory "%3" does not reside on an NTFS partition. Solution: Select an NTFS partition for the installation directory or convert the current partition to NTFS.</Description> </MessageSolution> <MessageSolution> <MessageID>3505</MessageID> <Description>Possible cause: The SMS Service account for site "%1" might not have the appropriate privileges to create the initialization file Solution: Verify that the account has Administrator privileges to server "%2". Possible cause: There is not enough free disk space on server "%2". Solution: Make more space available on the destination drive.</Description> </MessageSolution> <MessageSolution> <MessageID>3507</MessageID> <Description>Possible cause: The SMS Service account for site "%1" might not have the appropriate privileges to server "%2". Solution: Make sure the service account has Administrator privileges to server "%2".</Description> </MessageSolution> <MessageSolution> <MessageID>3508</MessageID> <Description>Possible cause: The SMS Service account for site "%1" might not have the appropriate privileges to server "%2". Solution: Make sure the service account has Administrator privileges to server "%2".</Description> </MessageSolution> <MessageSolution> <MessageID>3509</MessageID> <Description>Possible cause: The server is running Windows NT %3 %4, but this does not meet the minimum installation requirements for an SMS site server. Solution: Install a version of Windows NT that meets the installation requirements. Please refer to your SMS documentation for more information.</Description> </MessageSolution> <MessageSolution> <MessageID>3510</MessageID> <Description>Possible cause: The server is already in use as a site system for another SMS site. Solution: Install secondary site "%1" on a different server.</Description> </MessageSolution> <MessageSolution> <MessageID>3511</MessageID> <Description>Possible cause: The SMS Service account for site "%1" might not have the appropriate privileges to create the destination file. Solution: Verify that the account has Administrator privileges to server "%2". Possible cause: There is not enough free disk space on server "%2". Solution: Make more space available on the destination drive.</Description> </MessageSolution> <MessageSolution> <MessageID>3512</MessageID> <Description>Possible cause: The SMS Service account for site "%1" might not be valid. Solution: Verify that the service account is valid. Possible cause: The service account might not have the appropriate privileges. Solution: Ensure that the account has Administrator privileges and the "Log on as a service" right on server "%2".%12</Description> </MessageSolution> <MessageSolution> <MessageID>3513</MessageID> <Description>Possible cause: The SMS Service account for site "%1" might not be valid. Solution: Verify that the service account is valid. Possible cause: The service account might not have the appropriate privileges. Solution: Ensure that the account has Administrator privileges and the "Log on as a service" right on server "%2".%12</Description> </MessageSolution> <MessageSolution> <MessageID>3518</MessageID> <Description>Possible cause: Server "%2" might not be running RAS Server Service. Solution: Verify that server "%2" is running RAS Server Service.</Description> </MessageSolution> <MessageSolution> <MessageID>3519</MessageID> <Description>Possible cause: Remote site server "%2" might not be connected to the network. Solution: Verify that site server "%2" is connected to the network and functioning properly. Possible cause: The specified server name "%2" is unrecognizable. Solution: Verify that server name "%2" is recognizable by DNS server. Possible cause: The Winsock Sender/Receiver compononents are not started on the remote server. Solution: Verify that the Winsock Sender has been created on the remote server "%2". Possible cause: Network load might be too high. Solution: Verify that the network is not saturated. Verify that you can move large amounts of data across the network.</Description> </MessageSolution> <MessageSolution> <MessageID>3520</MessageID> <Description>Possible cause: The Winsock DLL or the TCP/IP is mising on server "%1". Solution: Verify that TCP/IP is installed properly.</Description> </MessageSolution> <MessageSolution> <MessageID>3521</MessageID> <Description>Possible cause: Winsock Receiver can not get enough resoures(memorry) to handle a new connection. Solution: Verify that system resources are not exhausted.</Description> </MessageSolution> <MessageSolution> <MessageID>3529</MessageID> <Description>Possible cause: Either connection to the parent site is unavailable or the sender address provided is not correct. Solution: If the secondary site does not show up even if the connection is there, please reinstall the site with correct sender address.</Description> </MessageSolution> <MessageSolution> <MessageID>3530</MessageID> <Description>Possible cause: Remote site server "%2" might not be connected to the LAN. Solution: Verify that site server "%2" is connected to the LAN and functioning properly. Possible cause: Share "%3" might not be accessible. Solution: Verify that share "%3" is visible and that the site server machine account has the necessary permissions to access the share. Possible cause: Network load might be too high. Solution: Verify that the network is not saturated. Verify that you can move large amounts of data across the network.</Description> </MessageSolution> <MessageSolution> <MessageID>3600</MessageID> <Description>Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The destination site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Inbox Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Inbox Manager from properly accessing the site system. Solution: Investigate and correct any problems with your network.</Description> </MessageSolution> <MessageSolution> <MessageID>3601</MessageID> <Description>Possible cause: The destination drive is full. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>3602</MessageID> <Description>Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The destination site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Inbox Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Inbox Manager from properly accessing the site system. Solution: Investigate and correct any problems with your network.</Description> </MessageSolution> <MessageSolution> <MessageID>3603</MessageID> <Description>Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The destination site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Inbox Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing SMS Inbox Manager from properly accessing the site system. Solution: Investigate and correct any problems with your network.</Description> </MessageSolution> <MessageSolution> <MessageID>3604</MessageID> <Description>Possible cause: The site server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site server is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing SMS Inbox Manager Assistant from properly accessing the site server. Solution: Investigate and correct any problems with your network.</Description> </MessageSolution> <MessageSolution> <MessageID>3605</MessageID> <Description>Possible cause: Site system "%1" does not have any drives or volumes that support file and directory permissions. For example, the FAT file system does not support permissions, but the NTFS file system does. Solution: Choose a site system that supports file and directory permissions.</Description> </MessageSolution> <MessageSolution> <MessageID>3606</MessageID> <Description>Possible cause: Site server "%4" is under heavy load and is either CPU or I/O constrained. Solution: Use Task Manager to check for processes causing high CPU or I/O utilization. Possible cause: Site server "%4" has a high backlog of files in its inboxes. Solution: Give the system time to work through the current backlog. Do not create any additional tasks that would load the system further.</Description> </MessageSolution> <MessageSolution> <MessageID>3607</MessageID> <Description>Possible cause: Site system "%4" is under heavy load and is either CPU or I/O constrained. Solution: Use Task Manager to check for processes causing high CPU or I/O utilization. Possible cause: Site system "%4" has a high backlog of files in its outboxes. Solution: Give the system time to work through the current backlog. Do not create any additional tasks that would load the system further.</Description> </MessageSolution> <MessageSolution> <MessageID>3701</MessageID> <Description>Possible cause: The file attempted to update inventory information in the SMS site database that does not already exist, or the file contains invalid syntax. Solution: The client inventory needs to be resynchronized, which will be done automatically. Look for the subsequent message 3703, which indicates the resynchronization has begun.</Description> </MessageSolution> <MessageSolution> <MessageID>3702</MessageID> <Description> Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>3706</MessageID> <Description>Possible cause: Low disk space on the destination disk drive. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>3707</MessageID> <Description>Possible cause: SMS Discovery Data Manager is not running. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.</Description> </MessageSolution> <MessageSolution> <MessageID>3708</MessageID> <Description>Solution: Increase the maximum allowable size, which is defined in the registry key HKLM\Software\Microsoft\SMS\Components\SMS_SOFTWARE_INVENTORY_PROCESSOR\Max File Size (the default is 5 MB), and wait for SMS Software Inventory Processor to retry the operation.</Description> </MessageSolution> <MessageSolution> <MessageID>4001</MessageID> <Description>Solution: Either enable component "%1" at the current site, or reconfigure it at all child sites to not replicate to the current site.</Description> </MessageSolution> <MessageSolution> <MessageID>4101</MessageID> <Description>Solution: Do nothing. SMS NT User Group Discovery Agent will retry at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>4103</MessageID> <Description>Possible cause: The primary domain controller is not accessible. Solution: Verify that the primary domain controller is running and accessible. Possible cause: The domain %1 does not exist. Solution: Verify that the domain name was specified correctly. In SMS Administrator console, under Site Settings, Discovery Methods, open the Windows NT User Group Discovery dialog box. Possible cause: The SMS Service account lacks sufficient rights in the domain %1. Solution: See the SMS documentation for the necessary rights of the SMS Service account, then ensure that the SMS Service account has such rights.</Description> </MessageSolution> <MessageSolution> <MessageID>4104</MessageID> <Description>Possible cause: The SMS Service account lacks sufficient rights in the domain %1. Solution: See the SMS documentation for the necessary rights of the SMS Service account, then ensure that the SMS Service account has such rights.</Description> </MessageSolution> <MessageSolution> <MessageID>4105</MessageID> <Description>Possible cause: The primary domain controller is not accessible. Solution: Verify that the primary domain controller is running and accessible. Possible cause: The domain %1 does not exist. Solution: Verify that the domain name was specified correctly. In SMS Administrator console, under Site Settings, Discovery Methods, open the Windows NT User Group Discovery dialog box. Possible cause: The SMS Service account lacks sufficient rights in the domain %1. Solution: See the SMS documentation for the necessary rights of the SMS Service account, then ensure that the SMS Service account has such rights.</Description> </MessageSolution> <MessageSolution> <MessageID>4200</MessageID> <Description>Possible cause: The registry information is not available yet. Solution: SMS Windows NT Server Discovery Agent is waiting for the information to become available and will retry obtaining the registry information at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>4201</MessageID> <Description>Possible cause: The information necessary to complete the initialization is not available now. Solution: Windows NT Server Discovery Agent is waiting for the information to become available and will retry at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>4301</MessageID> <Description>Solution: Do nothing. SMS NT User Group Discovery Agent will retry at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>4303</MessageID> <Description>Possible cause: The primary domain controller is not accessible. Solution: Verify that the primary domain controller is running and accessible. Possible cause: The domain %1 does not exist. Solution: Verify that the domain name was specified correctly. In SMS Administrator console, under Site Settings, Discovery Methods, open the Windows NT User Group Discovery dialog box. Possible cause: The SMS Service account lacks sufficient rights in the domain %1. Solution: See the SMS documentation for the necessary rights of the SMS Service account, then ensure that the SMS Service account has such rights.</Description> </MessageSolution> <MessageSolution> <MessageID>4304</MessageID> <Description>Possible cause: The SMS Service account lacks sufficient rights in the domain %1. Solution: See the SMS documentation for the necessary rights of the SMS Service account, then ensure that the SMS Service account has such rights.</Description> </MessageSolution> <MessageSolution> <MessageID>4305</MessageID> <Description>Possible cause: The primary domain controller is not accessible. Solution: Verify that the primary domain controller is running and accessible. Possible cause: The domain %1 does not exist. Solution: Verify that the domain name was specified correctly. In SMS Administrator console, under Site Settings, Discovery Methods, open the Windows NT User Group Discovery dialog box. Possible cause: The SMS Service account lacks sufficient rights in the domain %1. Solution: See the SMS documentation for the necessary rights of the SMS Service account, then ensure that the SMS Service account has such rights.</Description> </MessageSolution> <MessageSolution> <MessageID>4401</MessageID> <Description>Possible cause: The compressed image "%2" is either missing or corrupt. Solution: SMS Distribution Manager will attempt to recover the package by requesting a new compressed package image from the site that sent it.</Description> </MessageSolution> <MessageSolution> <MessageID>4402</MessageID> <Description>Possible cause: The destination drive is full. Solution: Make more space available on that drive. SMS Despooler will attempt to merge the delta again during its next retry interval</Description> </MessageSolution> <MessageSolution> <MessageID>4403</MessageID> <Description>Solution: Upgrade the 2.0 child site to SMS 2.0 SP5 or above, or upgrade the 2.0 child site to SMS 2003, or change the site property site connection setting in the Administrator UI to allow child sites that are SMS 2.0 SP4 or earlier.</Description> </MessageSolution> <MessageSolution> <MessageID>4404</MessageID> <Description>Solution: Extend the Active Directory schema to allow SMS sites to publish their public keys into AD, or use the preinst.exe tool to manually replicate the public keys, or change the site property site connection setting in the Administrator UI to allow unsigned key exchange between sites.</Description> </MessageSolution> <MessageSolution> <MessageID>4405</MessageID> <Description>Solution: Extend the Active Directory schema to allow sites to publish their public keys into AD, or use the preinst.exe tool to manually replicate the public keys.</Description> </MessageSolution> <MessageSolution> <MessageID>4601</MessageID> <Description>Possible cause: The site control file entry does not contain a component name. Solution: SMS Component Status Summarizer will ignore this entry, which might result in the Status column of the Component Status display in the SMS Administrator console being improperly set for a particular component. This problem might be the result of a code defect. If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>4602</MessageID> <Description>Possible cause: SMS Component Status Summarizer will now begin tracking the status of this component as if it were properly listed in the site control file. If this component is an SMS component, it could mean the component should have been deinstalled sometime in the past by Site Component Manager. Solution: Investigate whether or not the component should really be installed and running on this computer. If it should not be installed, the problem might be the result of defective code. If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>4603</MessageID> <Description>Possible cause: The count equals or exceeds the Component Status Critical Threshold (%5 status messages) for Informational status messages for the component. Solution: SMS Component Status Summarizer will set the component's status to Critical in the Component Status summary in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>4604</MessageID> <Description>Possible cause: The count equals or exceeds the Component Status Critical Threshold (%5 status messages) for Warning status messages for the component. Solution: SMS Component Status Summarizer will set the component's status to Critical in the Component Status summary in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>4605</MessageID> <Description>Possible cause: The count equals or exceeds the Component Status Critical Threshold (%5 status messages) for Error status messages for the component. Solution: SMS Component Status Summarizer will set the component's status to Critical in the Component Status summary in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>4606</MessageID> <Description>Possible cause: The count equals or exceeds the Component Status Warning Threshold (%5 status messages) for Informational status messages for the component. Solution: If the component's status is not already set to Warning, SMS Component Status Summarizer will set the component's status to Warning in the Component Status summary in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>4607</MessageID> <Description>Possible cause: The count equals or exceeds the Component Status Warning Threshold (%5 status messages) for Warning status messages for the component. If the component's status is not already set to Warning, SMS Component Status Summarizer will set the component's status to Warning in the Component Status summary in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>4608</MessageID> <Description>Possible cause: The count equals or exceeds the Component Status Warning Threshold (%5 status messages) for Error status messages for the component. Solution: If the component's status is not already set to Warning, SMS Component Status Summarizer will set the component's status to Warning in the Component Status summary in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>4609</MessageID> <Description>Possible cause: The component is experiencing a problem. Solution: Diagnose and fix the problem by: 1. Examining the status messages that the component reports. 2. Correcting the problem. 3. Instructing SMS Component Status Summarizer to reset the counts of Error, Warning, and/or Informational status messages reported by the component. To reset the counts, right-click Reset Counts on the component in the Component Status summary in the SMS Administrator console. When the counts are reset, SMS Component Status Summarizer will change the status of the component to OK. This might take some time if site "%3" is a child site. 4. Delete any unwanted status messages from the SMS site database, if necessary. 5. Monitor the component occasionally to verify that the problem does not reoccur. Possible cause: The component is OK and you were unnecessarily alerted because the Component Status Thresholds are set too low for the component. Solution: Increase the Component Status Thresholds for the component using the Thresholds tab of the Component Status Summarizer Properties dialog box in the SMS Administrator console. Possible cause: The component is flooding the status system by rapidly reporting the same message repeatedly. Solution: Diagnose and control the flood of status messages by: 1. Verifying that the component is actually flooding the status system. View the status messages reported by the component and verify that the same message is continually reported every several minutes or seconds. 2. Noting the Message ID of the flooded status message. 3. Creating a Status Filter Rule for site "%3" that instructs Status Manager to discard the flooded status message when component "%1" on computer "%2" reports it. 4. Verifying that your sites' databases were not filled up by the flooded status message. Delete anyduplicate status messages from the site database, if necessary. 5. Refer to the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>4610</MessageID> <Description>Possible cause: The component is experiencing a problem. Solution: Diagnose and fix the problem by: 1. Examine the status messages that the component reports. 2. Correcting the problem. 3. Instructing SMS Component Status Summarizer to reset the counts of Error, Warning, and/or Informational status messages reported by the component. To reset the counts, right-click Reset Counts on the component in the Component Status summary in the SMS Administrator console. When the counts are reset, SMS Component Status Summarizer will change the status of the component to OK. This might take some time if site "%3" is a child site. 4. Deleting any unwanted status messages from the site database, if necessary. 5. Monitor the component occasionally to verify the problem does not reoccur. Possible cause: The component is OK and you were unnecessarily alerted because the Component Status Thresholds are set too low for the component. Solution: Increase the Component Status Thresholds for the component using the Thresholds tab of the Component Status Summarizer Properties dialog box in the SMS Administrator console. Possible cause: The component is "flooding" the status system by rapidly reporting the same message repeatedly. Solution: Diagnose and control the flood of status messages by: 1. Verifying that the component is actually flooding the status system. View the status messages reported by the component, and verify that the same message is continually reported every several minutes or seconds. 2. Noting the Message ID of the flooded status message. 3. Creating a Status Filter Rule for site "%3" that instructs Status Manager to discard the flooded status message when component "%1" on computer "%2" reports it. 4. Verifying that your sites' databases were not filled up by the flooded status message. Delete any duplicate status messages from the site database, if necessary. 5. Refer to the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>4611</MessageID> <Description> Solution: SMS Component Status Summarizer will also reset a component's status to OK when an administrator manually resets the counts of status messages reported by the component for the Threshold Period. Solution: SMS Component Status Summarizer will also reset a component's status to OK when an administrator adjusts the Component Status Thresholds to be higher than the current counts of status messages reported by the component.</Description> </MessageSolution> <MessageSolution> <MessageID>4612</MessageID> <Description>Possible cause: There is no record of this component in the site control file. Solution: The SMS Component Status Summarizer will assume the component was deinstalled and will remove it from the Component Status summary.%12</Description> </MessageSolution> <MessageSolution> <MessageID>4613</MessageID> <Description>Possible cause: SMS Component Status Summarizer is designed to process only status messages reported by components at the site where SMS Component Status Summarizer is running. Solution: SMS Component Status Summarizer will ignore this status message. Possible cause: This problem might be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>4618</MessageID> <Description>Possible cause: "%9" is a custom Display Interval you have configured the SMS Component Status Summarizer to use. SMS Component Status Summarizer cannot display a an unencrypted version of "%9" in a status message. Solution: If you wish to decode "%9" into something more readable, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>4630</MessageID> <Description>Possible cause: This component has failed to generate a heartbeat within its heartbeat interval or has reported with its heartbeat that it is in a failure state. Solution: Verify that the condition persists by examining compmon.log and then check the component's log file.</Description> </MessageSolution> <MessageSolution> <MessageID>4631</MessageID> <Description>Possible cause: This component has with its heartbeat that it is in a degraded state. Solution: Verify that the condition persists by examining the component's log file and performance counters.</Description> </MessageSolution> <MessageSolution> <MessageID>4632</MessageID> <Description>Possible cause: This component is under maintenance or shutdown. Solution: Verify that maintenance is not being performed at this time and the component is running. If the component is not running, restart it using SMS Service Manager.</Description> </MessageSolution> <MessageSolution> <MessageID>4633</MessageID> <Description>Possible cause: This component does not have an Availability State, it could not be accessed or it has not been updated. Solution: Verify that the Site Server can connect to the registry of the server on which this component resides.</Description> </MessageSolution> <MessageSolution> <MessageID>4700</MessageID> <Description>Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site System Status Summarizer does not have sufficient access rights to connect to the site system and access the storage object. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to connect to the site system and access the storage object. Possible cause: Network problems are preventing SMS Site System Status Summarizer from connecting to the site system. Solution: Investigate and correct any problems on your network. Possible cause: You took the site system out of service and do not intend to use it as a site system any more. Solution: Remove the site system from the list of site systems used by this site; this list appears in the Site Systems node of the SMS Administrator console. Possible cause: You accidentally deleted the storage object or took the storage object out of service. Solution: The SMS components will eventually detect that the storage object no longer exists on the site system and will either recreate it or choose a new storage object. Monitor the status messages reported by other SMS components to verify that this occurs properly. SMS Site System Status Summarizer will now set the storage object's status to Critical in the Site System Status summary in the SMS Administrator console. When you correct the problem and SMS Site System Status Summarizer successfully accesses the storage object, SMS Site System Status Summarizer will set the storage object's status to OK, providing that the storage object has sufficient free space.</Description> </MessageSolution> <MessageSolution> <MessageID>4701</MessageID> <Description>Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Site System Status Summarizer does not have sufficient access rights to connect to the site system and access the storage object. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to connect to the site system and access the storage object. Possible cause: Network problems are preventing SMS Site System Status Summarizer from connecting to the site system. Solution: Investigate and correct any problems on your network. Possible cause: You took the site system out of service and do not intend on using it as a site system any more. Solution: Remove the site system from the list of site systems used by this site; this list appears under Site Systems in the SMS Administrator console. Possible cause: You accidentally deleted the storage object or took the storage object out of service. Solution: The SMS components will eventually detect that the storage object no longer exists on the site system and will either recreate it or choose a new storage object. Monitor the status messages reported by other SMS components to verify that this occurs properly. The storage object has been inaccessible since "%3". When you correct the problem and SMS Site System Status Summarizer successfully accesses the storage object, SMS Site System Status Summarizer will set the storage object's status to OK, providing that the storage object has sufficient free space.</Description> </MessageSolution> <MessageSolution> <MessageID>4702</MessageID> <Description>Possible cause: The storage object had been inaccessible since "%3". Solution: If the storage object has sufficient free storage space, SMS Site System Status Summarizer will now restore the status of the storage object to OK in the Site System Status summary in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>4703</MessageID> <Description>Possible cause: The SMS Site Database Server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the SMS Site Database Server is turned on, connected to the network, and functioning properly. Possible cause: The SQL Server account is misconfigured in the SMS Administrator console. Solution: Verify that the SQL Server account in the SMS Administrator console contains the correct user name and password, and that the account has sufficient access rights to the SMS Site Database Server. Possible cause: Network problems are preventing SMS Site System Status Summarizer from connecting to the SMS Site Database Server. Solution: Investigate and correct any problems on your network. Possible cause: The database no longer exists. Solution: Reinstall your SMS site. SMS Site System Status Summarizer will now set the status of the "%1" database to Critical in the Site System Status summary in the SMS Administrator console. When you correct the problem and SMS Site System Status Summarizer successfully accesses the database, SMS Site System Status Summarizer will set the status of the "%1" database to OK, providing that the database has sufficient free space.</Description> </MessageSolution> <MessageSolution> <MessageID>4704</MessageID> <Description>Possible cause: The SMS Site Database Server is turned off, not connected to the network, or not functioning properly. Solution: verify that the SMS Site Database Server is turned on, connected to the network, and functioning properly. Possible cause: The SQL Server account is misconfigured in the SMS Administrator console. Solution: Verify that the SQL Server account in the SMS Administrator console contains the correct user name and password, and that the account has sufficient access rights to the SMS Site Database Server. Possible cause: Network problems are preventing SMS Site System Status Summarizer from connecting to the SMS Site Database Server. Solution: Investigate and correct any problems on your network. Possible cause: The database no longer exists. Solution: Reinstall your SMS site. The database has been inaccessible since "%3". When you correct the problem and SMS Site System Status Summarizer successfully accesses the database, SMS Site System Status Summarizer will set the status of the database to OK, providing that the database has sufficient free space.</Description> </MessageSolution> <MessageSolution> <MessageID>4705</MessageID> <Description>Possible cause: The database had been inaccessible since "%3". Solution: If the database has sufficient free space, SMS Site System Status Summarizer will now restore the status of the database to OK in the Site System Status summary in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>4706</MessageID> <Description>Possible cause: The SMS Site Database Server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the SMS Site Database Server is turned on, connected to the network, and functioning properly. Possible cause: The SQL Server account is misconfigured in the SMS Administrator console. Solution: Verify that the SQL Server account in the SMS Administrator console contains the correct user name and password, and that the account has sufficient access rights to the SMS Site Database Server. Possible cause: Network problems are preventing SMS Site System Status Summarizer from connecting to the SMS Site Database Server. Solution: Investigate and correct any problems on your network. Possible cause: The database no longer exists. Solution: Reinstall your SMS site. SMS Site System Status Summarizer will now set the status of the transaction log to Critical in the Site System Status summary in the SMS Administrator console. When you correct the problem and SMS Site System Status Summarizer successfully accesses the transaction log, SMS Site System Status Summarizer will set the status of the transaction log to OK, providing that the transaction log has sufficient free space.</Description> </MessageSolution> <MessageSolution> <MessageID>4707</MessageID> <Description>Possible cause: The SQL server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the SQL server computer is turned on, connected to the network, and functioning properly. Possible cause: The SQL server account is misconfigured in the SMS Administrator console. Solution: Verify that the SQL server account in the SMS Administrator console contains the correct user name and password, and that the account has sufficient access rights to the SQL server computer. Possible cause: Network problems are preventing SMS Site System Status Summarizer from connecting to the SQL server computer. Solution: Investigate and correct any problems on your network. Possible cause: The database no longer exists. Solution: Reinstall your SMS site. The transaction log has been inaccessible since "%3". When you correct the problem and SMS Site System Status Summarizer successfully accesses the transaction log, SMS Site System Status Summarizer will set the status of the transaction log to OK, providing that the transaction log has sufficient free space.</Description> </MessageSolution> <MessageSolution> <MessageID>4710</MessageID> <Description>Possible cause: The storage object is almost full. Solution: Make more space available on the storage object by deleting unneeded files. Possible cause: The Warning Free Space Threshold is set too high for this storage object. Solution: Decrease the Warning Free Space Threshold in the SMS Administrator console by navigating to the Site Hierarchy --> %5 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for this storage object. SMS Site System Status Summarizer will now set the status of the storage object to Warning in the Site System Status summary in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>4711</MessageID> <Description>Possible cause: The storage object is almost full. Solution: Make more space available on the storage object by deleting unneeded files. Possible cause: The Critical Free Space Threshold is set too high for this storage object. Solution: Decrease the Critical Free Space Threshold in the SMS Administrator console by navigating to the Site Hierarchy --> %5 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for this storage object. SMS Site System Status Summarizer will now set the status of the storage object to Critical in the Site System Status summary in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>4713</MessageID> <Description>Possible cause: The database is almost full. Solution: Make more space available in the database by deleting unneeded data. Possible cause: The database is too small. Solution: Increase the size of the database using SQL Enterprise Manager. Possible cause: The Warning Free Space Threshold is set too high for the database. Solution: Decrease the Warning Free Space Threshold in the SMS Administrator console by navigating to the Site Hierarchy --> %5 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for the database. SMS Site System Status Summarizer will now set the status of the database to Warning in the Site System Status summary in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>4714</MessageID> <Description>Possible cause: The database is almost full. Solution: Make more space available in the database by deleting unneeded data. Possible cause: The database is too small. Solution: Increase the size of the database using SQL Enterprise Manager. Possible cause: The Critical Free Space Threshold is set too high for the database. Solution: Decrease the Critical Free Space Threshold in the SMS Administrator console by navigating to the Site Hierarchy --> %5 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for the database. SMS Site System Status Summarizer will now set the status of the database to Critical in the Site System Status summary in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>4716</MessageID> <Description>Possible cause: The transaction log is too small. Solution: Increase the size of the transaction log using SQL Enterprise Manager. Possible cause: The Warning Free Space Threshold is set too high for the transaction log. Solution: Decrease the Warning Free Space Threshold in the SMS Administrator console by navigating to the Site Hierarchy --> %5 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for the transaction log. SMS Site System Status Summarizer will now set the status of the transaction log to Warning in the Site System Status summary in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>4717</MessageID> <Description>Possible cause: The transaction log is too small. Solution: Increase the size of the transaction log using SQL Enterprise Manager. Possible cause: The Critical Free Space Threshold is set too high for the transaction log. Solution: Decrease the Critical Free Space Threshold in the SMS Administrator console by navigating to the Site Hierarchy --> %5 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for the transaction log. Possible cause: A software defect caused the transaction log to fill up completely. Solution: investigate why the transaction log is full (see the SQL Server documentation for details). If you suspect a software defect, contact Microsoft for more information. Stop and start SQL Server to empty the transaction log. SMS Site System Status Summarizer will now set the status of the database to Critical in the Site System Status summary in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>4719</MessageID> <Description>Possible cause: The storage object is almost full or the storage status has not yet been received from the Branch Distribution Point. Solution: Verify that the messages from the Branch Distribution Point are successfully received. Make more space available on the storage object by deleting unneeded files. Possible cause: The Critical Free Space Threshold is set too high for this storage object. Solution: Decrease the Critical Free Space Threshold in the SMS Administrator console by navigating to the Site Hierarchy --> %5 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for this storage object. SMS Site System Status Summarizer will now set the status of the storage object to Critical in the Site System Status summary in the SMS Administrator console.</Description> </MessageSolution> <MessageSolution> <MessageID>4721</MessageID> <Description>Possible cause: This SMS Server Role is unable to function. Solution: Verify that no security or configuration problems exist and that all related components are running.</Description> </MessageSolution> <MessageSolution> <MessageID>4722</MessageID> <Description>Possible cause: This SMS Server Role is experiencing a severe impact to its performance and or partial loss of functionality. Solution: Check the overall CPU, Memory and Disk performance on this server. Solution: Verify that no security or configuration problems exist that could be impacting availability of this role.</Description> </MessageSolution> <MessageSolution> <MessageID>4723</MessageID> <Description>Possible cause: This SMS Server Role is under maintenance or shutdown. Solution: Verify that maintenance is not being performed at this time and that all related components are running.</Description> </MessageSolution> <MessageSolution> <MessageID>4724</MessageID> <Description>Possible cause: This SMS Server Role does not have an Availability State, it could not be accessed or it has not been updated. Solution: Verify that the Site Server can connect to the registry of the site system.</Description> </MessageSolution> <MessageSolution> <MessageID>4800</MessageID> <Description>Possible cause: The registry information is not available yet. Solution: NetWare Bindery Server Discovery Agent will try to obtain the registry information at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>4801</MessageID> <Description>Possible cause: The information necessary to complete the initialization is not available now. Solution: NetWare Bindery Server Discovery Agent is waiting for the information to become available and will try again at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>4902</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry this operation in %2 minutes. To force SMS Site Component Manager to immediately retry this operation, stop and restart SMS Site Component Manager using the SMS Service Manager.</Description> </MessageSolution> <MessageSolution> <MessageID>4903</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure. This operation has repeatedly failed for %2 minutes and will probably never succeed, therefore SMS Site Component Manager not retry this operation again. You might ignore this message and do nothing if the site system is no longer in service or the operating system has been reinstalled on the site system. Otherwise some remnants of the SMS server components might still be installed on this site system, and you will have to manually remove them. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>4905</MessageID> <Description>Possible cause: The site system's registry is full. Solution: Increase the size of the site system's registry. Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. More information may be available in SMS Site Component Manager's log file "sitecomp.log" and the perfsetup.log on the site system.</Description> </MessageSolution> <MessageSolution> <MessageID>4907</MessageID> <Description>Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. More information may be available in SMS Site Component Manager's log file "sitecomp.log" and the perfsetup.log on the site system.</Description> </MessageSolution> <MessageSolution> <MessageID>4908</MessageID> <Description>Possible cause: This site's SMS Service account or the site server's machine account might not have administrative access to the SQL Server computer. Solution: Manually add the machine account "%1" to the SQL Access Group "%2" on the SQL Server machine "%3".</Description> </MessageSolution> <MessageSolution> <MessageID>4909</MessageID> <Description>Possible cause: This site's SMS Service account or the site server's machine account might not have the correct rights to update active directory. Solution: Either give the Service Account rights to update the domain's System Container, or manually create the "System Management" container in this domain's Active Directory system container, and give the Service Account full rights to that container (and all children objects.)</Description> </MessageSolution> <MessageSolution> <MessageID>4912</MessageID> <Description>Possible cause: This site's SMS Service account or the site server's machine account may not have full control rights for the "System Management" container in Active Directory Solution: Give the site's SMS Service account full control rights to the "System Management" container, and all child objects in Active Directory. Possible cause: The Active Directory object "%1" has been moved to a location outside of the "System Management" container, or has been lost. Solution: Delete the object from its current location, and let SMS create a new object. Possible cause: The Active Directory schema has not been extended with the correct SMS Active Directory classes and attributes. Solution: Turn off Active Directory publishing for each site in the forest, until the schema can be extended. The schema can be extended with the tool "extadsch.exe" from the SMS CD.</Description> </MessageSolution> <MessageSolution> <MessageID>4913</MessageID> <Description>Possible cause: This site's SMS Service account or the site server's machine account may not have full control rights for the "System Management" container in Active Directory Solution: Give the site's SMS Service account full control rights to the "System Management" container, and all child objects in Active Directory. Possible cause: Another Active Directory object named "%1" already exists somewhere outside of the "System Management" container Solution: Locate the other object with the same name, and delete the object from its current location. Then allow SMS create a new object. Possible cause: The Active Directory schema has not been extended with the correct SMS Active Directory classes and attributes. Solution: Turn off Active Directory publishing for each site in the forest, until the schema can be extended. The schema can be extended with the tool "extadsch.exe" from the SMS CD.</Description> </MessageSolution> <MessageSolution> <MessageID>4915</MessageID> <Description>Possible cause: This site's SMS Service account or the site server's machine account may not have full control rights for the "System Management" container in Active Directory Solution: Give the site's SMS Service account full control rights to the "System Management" container, and all child objects in Active Directory. Possible cause: The Active Directory object "%1" has been moved to a location outside of the "System Management" container Solution: Manually delete the object from its current location.</Description> </MessageSolution> <MessageSolution> <MessageID>4916</MessageID> <Description>Possible cause: This site's SMS Service account or the site server's machine account might not have full control rights for the "System Management" container in Active Directory Solution: Manually add the Management Point's machine account to the Active Directory object "%1". Possible cause: The Management Point server is not in a trusted domain, or its machine account has not replicated the domain controllers necessary for completing this action. Solution: Verify that the Management Point's machine account is trusted by the forest, and that it has replicated to the domain controllers. Until the permissions for Active Directory object "%1" are set up correctly, clients for this site will be unable to communicate with that Management Point.</Description> </MessageSolution> <MessageSolution> <MessageID>4917</MessageID> <Description>Possible cause: The SQL server site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the SQL server site system is turned on, connected to the network, and functioning properly. Possible cause: SMS Server Locator Point does not have sufficient access rights to the SQL server site system. Solution: Verify that the SQL server is properly configured to allow Server Locator Point access. Verify that the credentials used by Server Locator Point to connect to the Database have not expired. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the Server Locator Point to use an NT integrated security account, with appropriate access. Possible cause: Network problems are preventing SMS Server Locator Point from properly accessing the SQL server. Solution: Investigate and correct any problems with your network.</Description> </MessageSolution> <MessageSolution> <MessageID>4918</MessageID> <Description>Possible cause: The Active Directory schema has not been extended with latest version of the SMS Active Directory classes and attributes. Solution: Ensure the schema has been extended with the latest version of the SMS Active Directory classes and attributes. The schema can be extended with the tool "extadsch.exe" from the SMS directory on the SMS Site server that reported this message.</Description> </MessageSolution> <MessageSolution> <MessageID>4920</MessageID> <Description>Possible cause: The site system's registry is full. Solution: Increase the size of the site system's registry. Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. More information may be available in SMS Site Component Manager's log file "sitecomp.log" and the comregsetup.log on the site system.</Description> </MessageSolution> <MessageSolution> <MessageID>4922</MessageID> <Description>Possible cause: SMS Site Component Manager does not have administrator rights to this site system. Solution: Verify that the either the site server computer account or the Site System Installation account is a member of the local Administrators group on the site system. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system. Solution: Investigate and correct any problems on your network. More information may be available in SMS Site Component Manager's log file "sitecomp.log" and the comregsetup.log on the site system.</Description> </MessageSolution> <MessageSolution> <MessageID>4950</MessageID> <Description>Possible cause: Microsoft Internet Information Services (IIS) is not installed or running. Solution: Use Add/Remove Programs to install Microsoft Internet Information Services (IIS), and verify that the World Wide Web Service is running. Possible cause: SMS Site Component Manager does not have sufficient access rights to administer and configure Microsoft Internet Information Services (IIS) on this site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. SMS Site Component Manager cannot install component %1 until Microsoft Internet Information Services (IIS) is installed and configured correctly. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>4954</MessageID> <Description>Possible cause: Another SMS site is using this virtual directory name for its reporting. Solution: Use a different virtual directory name. Possible cause: A previous installation of Report Viewer was not completely removed. Solution: Manually delete the directory containing the previous installation of Report Viewer. Refer to the component's installation logs, as well as the SMS documentation and the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>4955</MessageID> <Description>Possible cause: Microsoft Message Queuing Services (MSMQ) is not installed or running. Solution: Use Add/Remove Programs to install Microsoft Message Queuing Services (MSMQ). Possible cause: SMS Site Component Manager does not have sufficient access rights to administer and configure Microsoft Message Queuing Services (MSMQ) on this site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. SMS Site Component Manager cannot install component %1 until Microsoft Message Queuing Services (MSMQ) is installed and configured correctly. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>4956</MessageID> <Description>Possible cause: Some files could not be replaced because they were in use by another process Solution: Reboot the machine to complete the installation. The component %1 may not be fully operational until a reboot. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>4957</MessageID> <Description>Possible cause: Background Intelligent Transfer Service (BITS) is not installed or running. Solution: Use Add/Remove Programs to install Background Intelligent Transfer Service (BITS) . Possible cause: SMS Site Component Manager does not have sufficient access rights to administer and configure Background Intelligent Transfer Service (BITS) on this site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. SMS Site Component Manager cannot install component %1 until Background Intelligent Transfer Service (BITS) is installed and configured correctly. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>4958</MessageID> <Description>Possible cause: The account is not configured correctly in IIS. Solution: Configure the account in IIS. SMS Site Component Manager cannot install component %1 until this account is configured correctly. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>4959</MessageID> <Description>Possible cause: The MSSQL Service is running under a user account, instead of the computer account. In this case, SQL does not publish its own SPN. Solution: Manually publish the SQL SPN in Active Directory. The component %1 will operate correctly. However remote site systems requiring access to SQL Server (i.e., server locator points, or management points) might not be able to access SQL in advanced security mode. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>4960</MessageID> <Description>Possible cause: The designated Web Site is in the Stopped or Paused state. Solution: Start the designated Web Site using the Internet Services Manager. Possible cause: The World Wide Publishing Service is in the Stopped or Paused or Disabled state. Solution: Start the World Wide Publishing Service on the machine. SMS Site Component Manager cannot install component %1 until the designated Web Site is started. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>4963</MessageID> <Description>Possible cause: The IIS IWAM account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IWAM account. (i.e.: "net user IWAMMachineName) Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties. Possible cause: The IIS IUSR account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IUSR account. (i.e.: "net user IWAMMachineName) Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly.</Description> </MessageSolution> <MessageSolution> <MessageID>4964</MessageID> <Description>Possible cause: No Server Certificate is attached to the designated Web Site. Solution: Refer to SMS Documentation regarding how to create and attach a proper Server Certificate to the designated Web Site. Possible cause: The Server Certificate is invalid or expired. Solution: Refer to SMS Documentation regarding how to create and attach a proper Server Certificate to the designated Web Site.</Description> </MessageSolution> <MessageSolution> <MessageID>4965</MessageID> <Description>Possible cause: Microsoft Internet Authentication Service (IAS) is not installed or running. Solution: Use Add/Remove Programs to install Microsoft Internet Authentication Service (IAS). Possible cause: SMS Site Component Manager does not have sufficient access rights to administer and configure Microsoft Internet Authentication Service (IAS) on this site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. SMS Site Component Manager cannot install component %1 until Microsoft Internet Authentication Service (IAS) is installed and configured correctly. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>4966</MessageID> <Description>Possible cause: You have not installed the required version of Windows Server on the site system. Solution: Install the required version of Windows Server on the site system. Refer to the Configuration Manager Documentation Library to determine the required version. Possible cause: You accidentally configured ConfigMgr to use the wrong computer as a site system. Solution: Remove this site system from the list of site systems for this site, and add the correct site system to the list. The list appears in the Site Systems node of the Configuration Manager console.</Description> </MessageSolution> <MessageSolution> <MessageID>4967</MessageID> <Description>Possible cause: Microsoft Windows Deployment Services (WDS) is not installed. Solution: Use Add/Remove Programs to install Windows Deployment Services (WDS). Possible cause: SMS Site Component Manager does not have sufficient access rights to configure Microsoft Windows Deployment Services (WDS) on this site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. SMS Site Component Manager cannot install component %1 until Microsoft Windows Deployment Services (WDS) is installed. Refer to your SMS documentation or the Microsoft Knowledge Base for further information.</Description> </MessageSolution> <MessageSolution> <MessageID>4968</MessageID> <Description>Possible cause: WSUS service is not installed or running. Solution: Use Add/Remove Programs to install WSUS.</Description> </MessageSolution> <MessageSolution> <MessageID>4970</MessageID> <Description>Solution: Make sure WebDAV is installed and enabled. Make sure there is an authoring rule that allow "All users" read access to "All content". Make sure the WebDAV settings "Allow anonymous property queries" and "Allow property queries with infinite depth" are set to "true" and "Allow Custom Properties" is set to false.%12</Description> </MessageSolution> <MessageSolution> <MessageID>5000</MessageID> <Description>Possible cause: Wrong name specified or permissions to "%1" are incorrect. Solution: Verify that a readable backup control file named "%1" exists.</Description> </MessageSolution> <MessageSolution> <MessageID>5002</MessageID> <Description>Possible cause: "%1" is an interactive Windows application and is waiting for user confirmation of the stop request. Solution: Manually stop this application.</Description> </MessageSolution> <MessageSolution> <MessageID>5004</MessageID> <Description>Possible cause: "%1" does not exist in the specified location on the local computer. Solution: Verify that an executable "%1" exists on the local computer. Also specify its full path in the backup control file.</Description> </MessageSolution> <MessageSolution> <MessageID>5006</MessageID> <Description>Possible cause: SMS Site Backup does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. If this problem persists, refer to the SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>5008</MessageID> <Description>Possible cause: SMS Site Backup does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. If this problem persists, refer to the SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>5010</MessageID> <Description>Possible cause: %1 is not readable, or %2 is not writable. Solution: Adjust file attributes and/or permissions of %1 and/or %2. Possible cause: The destination directory %2 did not already exist, and SMS Site Backup was unable to create it. Solution: Verify that a regular file with the same name as %2 or one of its parent directories does not exist, or replace %2 with an existing directory. Possible cause: %1 or %2 are on remote computers that SMS Site Backup does not have sufficient access rights to administer. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the remote computer. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application. Possible cause: Source %1 being copied to %2 may cause a recursive operation Solution: Verify that destination folder does not exist within the source folder.</Description> </MessageSolution> <MessageSolution> <MessageID>5012</MessageID> <Description>Possible cause: SMS Site Backup was unable to connect to or set backup privileges for the source registry. Solution: If %1 is in a remote registry, verify that the Site System Connection accounts are properly configured to allow SMS to administer the remote computer; otherwise, reboot. Possible cause: %1 specifies a registry key relative to a hive other than HKEY_LOCAL_MACHINE. Solution: Change %1 so it is relative to HKEY_LOCAL_MACHINE. Possible cause: %2 or its directory are not writable. Solution: Adjust file attributes and/or permissions on %2 and/or its directory. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application.</Description> </MessageSolution> <MessageSolution> <MessageID>5014</MessageID> <Description>Possible cause: %3 or its directory are not writable. Solution: Adjust file attributes and/or permissions on %3 and its directory. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application.</Description> </MessageSolution> <MessageSolution> <MessageID>5016</MessageID> <Description>Possible cause: "%1" does not exist at the specified location or is not in the system path. Solution: Install "%1" at the specified location, or add its directory to the system path. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application.</Description> </MessageSolution> <MessageSolution> <MessageID>5017</MessageID> <Description>Possible causes: the backup control file was truncated or contains a syntax error. Solution: Verify completeness of the backup control file and fix any errors.</Description> </MessageSolution> <MessageSolution> <MessageID>5018</MessageID> <Description>Possible cause: The backup control file contains a syntax error on line %1. Solution: Fix any errors in the backup control file.</Description> </MessageSolution> <MessageSolution> <MessageID>5019</MessageID> <Description>Possible cause: The backup control file contains an invalid section name on line %1. Solution: Verify that line %1 specifies a valid section name. Possible cause: The section starting at line %1 contains no valid definitions. Solution: If the section contains invalid definitions, correct any errors. If the section contains no definitions, remove the section or add at least one definition. Possible cause: The backup control file contains a syntax error on or before line %1. Solution: Fix any errors in the backup control file.</Description> </MessageSolution> <MessageSolution> <MessageID>5021</MessageID> <Description>Possible cause: %1 is not an SMS client application and so cannot respond to a "close" event. Solution: Stop this application manually or as a standard executable. Possible cause: %1 was not running. Solution: Remove the "clientapp %1" definition from the backup control file.</Description> </MessageSolution> <MessageSolution> <MessageID>5022</MessageID> <Description>Possible cause: %1 does not exist on the local computer. Solution: Verify that there are no errors in the "clientapp %1" definition, or remove the definition from the backup control file.</Description> </MessageSolution> <MessageSolution> <MessageID>5024</MessageID> <Description>Possible causes: %1 is not in the system path or does not exist on the local computer. Solution: Verify that an SMS client application "%1" exists on the local system. Either add its directory to the system path, or specify its full path in the backup control file.</Description> </MessageSolution> <MessageSolution> <MessageID>5025</MessageID> <Description>Possible cause: The current SMS site's "Backup SMS Site Server" Maintenance Task has no value set for its "Backup Destination" field. Solution: Set the "Backup Destination" field using the SMS Administrator Console.</Description> </MessageSolution> <MessageSolution> <MessageID>5026</MessageID> <Description>Possible cause: The current SMS site's "Backup SMS Site Server" Site Maintenance Task has invalid value set for its "Backup destination" field or "Backup destination" exists inside SMS root folder or Backup was unable to create this directory. Solution: Set a valid location to the "Backup destination" field using the SMS Administrator Console Make sure "Backup destination" does not exist inside SMS root folder. Check the privileges for proper rights</Description> </MessageSolution> <MessageSolution> <MessageID>5027</MessageID> <Description>Possible cause: There are syntax errors or unsupported commands that need to be removed. Solution: Edit backup control file and remove syntax errors on the given lines.</Description> </MessageSolution> <MessageSolution> <MessageID>5028</MessageID> <Description>Possible cause: %1 is/are missing from their predefined location. Solution: Please copy the unavailable tools to their designated folder.</Description> </MessageSolution> <MessageSolution> <MessageID>5029</MessageID> <Description>Possible cause: if %1 is a service then it is not installed or cannot be reached. Solution: Check the name and location of the Service and make sure that service is installed and the machine is reachable.</Description> </MessageSolution> <MessageSolution> <MessageID>5031</MessageID> <Description>Possible cause: %1 is either a built-in symbol or already defined in Backup Control file. Solution: If it is a built-in symbol, it cannot be redefined, remove added definition from backup control file otherwise use only a single definition.</Description> </MessageSolution> <MessageSolution> <MessageID>5032</MessageID> <Description>Possible cause: SMS Site Backup was unable to connect to or set backup privileges for the source registry. Solution: If %1 is in a remote registry, verify that the Site System Connection accounts are properly configured to allow SMS to administer the remote computer; otherwise, reboot. Possible cause: %1 specifies a registry key relative to a hive other than HKEY_LOCAL_MACHINE. Solution: Change %1 so it is relative to HKEY_LOCAL_MACHINE. Possible cause: %2 or its directory are not writable. Solution: Adjust file attributes and/or permissions on %2 and/or its directory. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application.</Description> </MessageSolution> <MessageSolution> <MessageID>5033</MessageID> <Description>Possible cause: %3 or its directory are not writable. Solution: Adjust file attributes and/or permissions on %3 and its directory. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application.</Description> </MessageSolution> <MessageSolution> <MessageID>5034</MessageID> <Description>Possible cause: "%1" is not found in the specified location. Solution: Verify that the executable "%1" exists on the local computer. Please specify its full path in the backup control file.</Description> </MessageSolution> <MessageSolution> <MessageID>5041</MessageID> <Description>Possible cause: Unable to find command shell to execute this file. Solution: Install command shell (CMD.EXE) in the system directory. Possible cause: Command shell failed to execute this file. Solution: Verify that CMD.EXE or "%1" are not corrupted.</Description> </MessageSolution> <MessageSolution> <MessageID>5043</MessageID> <Description>Possible cause: %1 is not readable, or %2 is not writable. Solution: Adjust file attributes and/or permissions of %1 and/or %2. Possible cause: The destination directory %2 did not already exist, and SMS Site Backup was unable to create it. Solution: Verify that a regular file with the same name as %2 or one of its parent directories does not exist, or replace %2 with an existing directory. Possible cause: %1 or %2 are on remote computers that SMS Site Backup does not have sufficient access rights to administer. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the remote computer. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application. Possible cause: Source %1 being copied to %2 may cause a recursive operation Solution: Verify that destination folder does not exist within the source folder. Possible cause: Source %1 contains some file(s) that is opened exclusively by some application. Solution: Retry backup again.</Description> </MessageSolution> <MessageSolution> <MessageID>5048</MessageID> <Description>Possible Cause: The Volume Shadow Copy Service may not have sufficient disk space to create the shadow copy of the site backup snapshot information. Check the storage associations for the drives containing Configuration Manager data and ensure that they are configured to use a volume with free space equivalent to at least 50% of the size of the Configuration Manager data. The backup destination should not be on the source volume, and the storage association should refer to a different volume than the source volume.%12</Description> </MessageSolution> <MessageSolution> <MessageID>5200</MessageID> <Description>Possible cause: The registry information is not available yet. Solution: SMS Active Directory System Discovery Agent is waiting for the information to become available and will retry obtaining the registry information at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>5201</MessageID> <Description>Possible cause: The information necessary to complete the initialization is not available now. Solution: SMS Active Directory System Discovery Agent is waiting for the information to become available and will retry at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>5203</MessageID> <Description>Possible cause: The SMS Service might not have access to some properties of this object. The container specified might not have the properties available. Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information. Possible cause: Disjoint namespace configuration Solution: http://support.microsoft.com/kb/258503 Possible cause: Active Directory System Discovery does not resolve the IP address of a computer that is discovered by System Center Configuration Manager 2007 Solution: http://support.microsoft.com/kb/948303 Possible cause: Check Discovery Logs for more information</Description> </MessageSolution> <MessageSolution> <MessageID>5204</MessageID> <Description>Possible cause: The AD container specified earlier might be invalid now. The Domain Controller is inaccessible. Solution: Please verify that the AD container paths specified are valid. Confirm accessibility of the site server to the Domain Controller to be queried.</Description> </MessageSolution> <MessageSolution> <MessageID>5300</MessageID> <Description>Possible cause: The registry information is not available yet. Solution: SMS Active Directory User Discovery Agent is waiting for the information to become available and will retry obtaining the registry information at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>5301</MessageID> <Description>Possible cause: The information necessary to complete the initialization is not available now. Solution: SMS Active Directory User Discovery Agent is waiting for the information to become available and will retry at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>5303</MessageID> <Description>Possible cause: The SMS Service might not have access to some properties of this object. The container specified might not have the properties available. Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information.</Description> </MessageSolution> <MessageSolution> <MessageID>5304</MessageID> <Description>Possible cause: The AD container specified earlier might be invalid now. The Domain Controller is inaccessible. Solution: Please verify that the AD container paths specified are valid. Confirm accessibility of the site server to the Domain Controller to be queried.</Description> </MessageSolution> <MessageSolution> <MessageID>5350</MessageID> <Description>Possible cause: The registry information is not available yet. Solution: SMS Active Directory Security Group Discovery Agent is waiting for the information to become available and will retry obtaining the registry information at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>5351</MessageID> <Description>Possible cause: The information necessary to complete the initialization is not available now. Solution: SMS Active Directory Security Group Discovery Agent is waiting for the information to become available and will retry at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>5353</MessageID> <Description>Possible cause: OU name or Security Group name may contain at least a Unicode character which has conversion problem between Unicode and your system ANSI locale(e.g. Korean characters in English System Locale). The SMS Service might not have access to some properties of this object. The container specified might not have the properties available. Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information.</Description> </MessageSolution> <MessageSolution> <MessageID>5354</MessageID> <Description>Possible cause: The AD container specified earlier might be invalid now. The Domain Controller is inaccessible. Solution: Please verify that the AD container paths specified are valid. Confirm accessibility of the site server to the Domain Controller to be queried.</Description> </MessageSolution> <MessageSolution> <MessageID>5400</MessageID> <Description>Possible cause: The site server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site server is turned on, connected to the network, and functioning properly. Possible cause: Network problems are preventing MP File Dispatch Manager from properly accessing the site server. Solution: Investigate and correct any problems with your network. Possible cause: The account used to connect the MP to the site server may be locked out or may not have needed permissions. Solution: Check that the account is not locked out and that it has needed permissions. Refer to SMS security documentation for more information.</Description> </MessageSolution> <MessageSolution> <MessageID>5401</MessageID> <Description>Possible cause: The destination drive is full. Solution: Make more space available on that drive. Possible cause: The destination site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: MP File Dispatch Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the site system. Possible cause: Network problems are preventing MP File Dispatch Manager from properly accessing the site system. Solution: Investigate and correct any problems with your network.</Description> </MessageSolution> <MessageSolution> <MessageID>5410</MessageID> <Description>Possible cause: The corruption of the registry or an installation problem. Solution: Check the registry entries for MP or reinstall MP.</Description> </MessageSolution> <MessageSolution> <MessageID>5411</MessageID> <Description>Possible cause: Temporary spike in processing requests. Solution: If the condition persists check the logs to identify the cause and if necessary install NLB.</Description> </MessageSolution> <MessageSolution> <MessageID>5412</MessageID> <Description>Possible cause: Unforeseen system error. Solution: Check the logs to pinpoint the source of the problem and the reason for the condition. If unsuccessful raise the issue to Microsoft support.</Description> </MessageSolution> <MessageSolution> <MessageID>5413</MessageID> <Description>Possible cause: Corruption or invalid user definition. Solution: Check the logs to identify the cause. If the problem is persistent raise the issue with Microsoft support</Description> </MessageSolution> <MessageSolution> <MessageID>5414</MessageID> <Description>Possible cause: Out of disk space. Solution: Increase the disk space, remove unprocessable files.</Description> </MessageSolution> <MessageSolution> <MessageID>5415</MessageID> <Description>Possible cause: MP cannot communicate with the SQL data base. Solution: Check the network connection between MP and the machine hosting the SQL data base (likely the PSS). Possible cause: The SQL data base not initialized properly or corrupted. Solution: Check the data for consistency. Recreate the hardware definition tables if necessary.</Description> </MessageSolution> <MessageSolution> <MessageID>5416</MessageID> <Description>Possible cause: Inconsistent way the new definitions have been introduced. Solution: Check that the mapping tables contain the information consistent with the hardware definition tables and that the definitions have been propagated properly. Possible cause: Corruption of the data base. Solution: Check the consistency of the data base.</Description> </MessageSolution> <MessageSolution> <MessageID>5417</MessageID> <Description>Possible cause: Temporary spike in processing requests. Solution: If the condition persists, check the logs to identify the cause and if necessary install NLB.</Description> </MessageSolution> <MessageSolution> <MessageID>5418</MessageID> <Description>Possible cause: This might indicate that the report has become obsolete due to a new HW inventory policy or that a customer's private definitions haven't been properly propagated to the sms_def.mof at the PSS. Solution: See if the missing classes or properties are genuinely missing in the current sms_def.mof and find out why the client put them in the xml report.</Description> </MessageSolution> <MessageSolution> <MessageID>5419</MessageID> <Description>Possible cause: The file was too old to start with due to propagation problems. Solution: Ignore. Possible cause: MP's cache of class definitions could not be reloaded for a long time. Solution: Fix the network connection or SQL data base replication problem for the affected MP.</Description> </MessageSolution> <MessageSolution> <MessageID>5420</MessageID> <Description>Possible cause: The computer running SQL Server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the computer running SQL Server site system is turned on, connected to the network, and functioning properly. Possible cause: Management point does not have sufficient access rights to the SQL server site system. Solution: Verify that management point computer account or the Management Point Database Connection Account is a member of SMS Management Point Role (msdbrole_MP) in the SQL Server database. Possible cause: Network problems are preventing the management point from properly accessing the SQL Server. Solution: Investigate and correct any problems with your network. Possible cause: The management point having problems is at a secondary site, and SQL access account being used was recently reset by the parent site. Solution: This can automatically repair itself after one hour , as long as the account in use is not locked out. Check that the account in use is not locked out. Instead of waiting an hour, you can stop and start the SMS_SITE_COMPONENT_MANAGER service to immediately apply the new configuration. Possible cause: The SQL server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL server SPNs are correctly registered. Review Q829868.</Description> </MessageSolution> <MessageSolution> <MessageID>5430</MessageID> <Description>Possible cause: WINS server is not running. Solution: Make sure that the WINS server on the local network is up and running. Possible cause: MP's IP configuration has an invalid address of the WINS server. Solution: Supply a valid WINS IP address.</Description> </MessageSolution> <MessageSolution> <MessageID>5431</MessageID> <Description>Possible cause: WINS server is not running. Solution: Make sure that the WINS server on the local network is up and running. Manually delete that MP's entry from the WINS server Possible cause: The MP's entry at the WINS server is missing. Solution: Ignore the issue.</Description> </MessageSolution> <MessageSolution> <MessageID>5432</MessageID> <Description>Possible cause: MP didn't get installed properly. Solution: Ensure MP setup succeeded; if not, reinstall MP</Description> </MessageSolution> <MessageSolution> <MessageID>5433</MessageID> <Description>Possible cause: MP may be overloaded. Solution: Reapply the setting at a later time.</Description> </MessageSolution> <MessageSolution> <MessageID>5434</MessageID> <Description>Possible cause:MP didn't get installed properly. Solution: Ensure MP setup succeeded; if not, reinstall MP Possible cause: MP may be overloaded. Solution: Manually start the SMS Agent Host service on the MP.</Description> </MessageSolution> <MessageSolution> <MessageID>5435</MessageID> <Description>Possible cause:MP didn't get installed properly. Solution: Ensure MP setup succeeded; if not, reinstall MP Possible cause: MP may be overloaded. Solution: Manually start the SMS Agent Host service on the MP.</Description> </MessageSolution> <MessageSolution> <MessageID>5436</MessageID> <Description>Possible cause: Management point encountered an error when connecting to SQL Server. Solution: Verify that the SQL server is properly configured to allow Management Point access. Verify that management point computer account or the Management Point Database Connection Account is a member of SMS Management Point Role (msdbrole_MP) in the SQL Server database. Possible cause: The SQL Server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL server SPNs are correctly registered. Review Q829868. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base article 838891. Possible cause: The IIS Service is running under IIS 5.0 isolation mode. Solution: Check the IIS 5.0 isolation mode under Web Sites -> Properties -> Services. Possible cause: ASP.NET registry keys are missing. Solution: Run aspnet_regiis.exe -i and iisreset</Description> </MessageSolution> <MessageSolution> <MessageID>5437</MessageID> <Description>Possible cause: MP encountered an error when connecting to SQL Server. Solution: Verify that the SQL server is properly configured to allow Management Point access. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the Management Point to use an NT integrated security account, with appropriate access. If using integrated security, verify the account used by the MP to connect to the SQL server is a member of the SMS_SiteSystemToSQLConnection_<sitecode> group on the SQL server, that the account is not locked out, and that the account password is not expired. (In standard security, the default account is SMS_SQL_RX_<sitecode>.) Possible cause: The SQL server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL server SPNs are correctly registered. Review Q829868. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base article 838891.</Description> </MessageSolution> <MessageSolution> <MessageID>5438</MessageID> <Description>Possible cause: MP service is not started or not responding. Solution: Manually restart the SMS Agent Host service on the MP. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MP. For more information, refer to Microsoft Knowledge Base article 838891.</Description> </MessageSolution> <MessageSolution> <MessageID>5439</MessageID> <Description>Possible cause: MP service is not started or not responding on all MP physical machines. Solution: Manually restart the SMS Agent Host service on the MP. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MP. For more information, refer to Microsoft Knowledge Base article 838891.</Description> </MessageSolution> <MessageSolution> <MessageID>5440</MessageID> <Description>Possible causes: The client is incorrectly identifying itself, or the client's signing certificate was re-created, resulting in a new public key.</Description> </MessageSolution> <MessageSolution> <MessageID>5443</MessageID> <Description>Possible causes: The client is incorrectly identifying itself, or the client's signing certificate was re-created, resulting in a new public key.</Description> </MessageSolution> <MessageSolution> <MessageID>5480</MessageID> <Description>Possible cause: DMP encountered an error when connecting to SQL Server. Solution: Verify that the SQL server is properly configured to allow Device Management Point access. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the Device Management Point to use an NT integrated security account, with appropriate access. If using integrated security, verify the account used by the DMP to connect to the SQL server is a member of the SMS_SiteSystemToSQLConnection_<sitecode> group on the SQL server, that the account is not locked out, and that the account password is not expired. (In standard security, the default account is SMS_SQL_RX_<sitecode>.) Possible cause: The SQL server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL server SPNs are correctly registered. Review Q829868. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base article 838891.</Description> </MessageSolution> <MessageSolution> <MessageID>5481</MessageID> <Description>Possible cause: DMP service is not started or not responding on all DMP physical machines. Solution: Manually restart the SMS Agent Host service on the DMP. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MP. For more information, refer to Microsoft Knowledge Base article 838891.</Description> </MessageSolution> <MessageSolution> <MessageID>5482</MessageID> <Description>Possible cause: MP encountered an error when connecting to SQL Server. Solution: Verify that the SQL server is properly configured to allow Management Point access. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the Management Point to use an NT integrated security account, with appropriate access. If using integrated security, verify the account used by the MP to connect to the SQL server is a member of the SMS_SiteSystemToSQLConnection_<sitecode> group on the SQL server, that the account is not locked out, and that the account password is not expired. (In standard security, the default account is SMS_SQL_RX_<sitecode>.) Possible cause: The SQL server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL server SPNs are correctly registered. Review Q829868. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base article 838891.</Description> </MessageSolution> <MessageSolution> <MessageID>5483</MessageID> <Description>Possible cause: MP service is not started or not responding on all MP physical machines. Solution: Manually restart the SMS Agent Host service on the MP. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MP. For more information, refer to Microsoft Knowledge Base article 838891.</Description> </MessageSolution> <MessageSolution> <MessageID>5485</MessageID> <Description>Possible cause: The node will be taken offline for maintenance or retired. Solution: Confirm with the system administrator responsible for the cluster.</Description> </MessageSolution> <MessageSolution> <MessageID>5486</MessageID> <Description>Possible cause: The node has been suspended or stopped. Solution: Confirm with the system administrator responsible for the cluster. Possible cause: The node is in the process of converging. Solution: This should resolve itself when the node has completed converging.</Description> </MessageSolution> <MessageSolution> <MessageID>5487</MessageID> <Description>Possible cause: The database is a site database, not a replica, and ConfigMgr setup failed to enable the CLR. Solution: Open the SQL SQL Server Surface Area Configuration tool and select Surface Area Configuration for Feature. Select the Enable CLR Integration checkbox. Possible cause: The Management Point is configured to communicate with a replica database on a SQL Server that does not have CLR enabled. Solution: Open the SQL SQL Server Surface Area Configuration tool and select Surface Area Configuration for Feature. Select the Enable CLR Integration checkbox.</Description> </MessageSolution> <MessageSolution> <MessageID>5500</MessageID> <Description>Possible cause: The registry information is not available yet. Solution: SMS Active Directory System Group Discovery Agent is waiting for the information to become available and will retry obtaining the registry information at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>5501</MessageID> <Description>Possible cause: The information necessary to complete the initialization is not available now. Solution: SMS Active Directory System Group Discovery Agent is waiting for the information to become available and will retry at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>5503</MessageID> <Description>Possible cause: The SMS Service might not have access to some properties of this object. The container specified might not have the properties available. Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information.</Description> </MessageSolution> <MessageSolution> <MessageID>5504</MessageID> <Description>Possible cause: The AD container specified earlier might be invalid now. The Domain Controller is inaccessible. Solution: Please verify that the AD container paths specified are valid. Confirm accessibility of the site server to the Domain Controller to be queried.</Description> </MessageSolution> <MessageSolution> <MessageID>5600</MessageID> <Description>Possible cause: The registry information is not available yet. Solution: SMS Software Metering Processor is waiting for the information to become available and will retry obtaining the registry information at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>5601</MessageID> <Description>Possible cause: The file is corrupt. Solution: If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>5602</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure and fix any problems it is experiencing. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>5603</MessageID> <Description>Possible cause: MSXML 3.0 has not been installed on the system. Solution: Download and install MSXML 3.0 from http://www.microsoft.com/xml. Possible cause: The site server drive is full. Solution: Make more space available on that drive. Possible cause: SQL Server problem. Solution: Review the immediately preceding status messages from this component about SQL Server errors.</Description> </MessageSolution> <MessageSolution> <MessageID>5604</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure and fix any problems it is experiencing. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information..</Description> </MessageSolution> <MessageSolution> <MessageID>5605</MessageID> <Description>Possible cause: SQL Server problem. Solution: Review the immediately preceding status messages from this component about SQL Server errors. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>5606</MessageID> <Description>Possible cause: The site server drive is full. Solution: Make more space available on that drive..</Description> </MessageSolution> <MessageSolution> <MessageID>5607</MessageID> <Description>Possible cause: SQL Server problem. Solution: Review the immediately preceding status messages from this component about SQL Server errors. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>5608</MessageID> <Description>Possible cause: The client that reported the metering data does not exist in the database. Solution: Verify that the client is active and attached to the network. Possible cause: MSXML 3.0 has not been installed on the system. Solution: Download and install MSXML 3.0 from http://www.microsoft.com/xml. Possible cause: SQL Server problem. Solution: Review the immediately preceding status messages from this component about SQL Server errors. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>5612</MessageID> <Description>Possible cause: The destination drive is full. Solution: Make more space available on that drive.</Description> </MessageSolution> <MessageSolution> <MessageID>5613</MessageID> <Description>Solution: Review the previous status messages to determine the exact reason for the failure and fix any problems it is experiencing. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>5614</MessageID> <Description>Possible cause: The clock on the client computer is not accurate or has been recently changed. Solution: Reset the time on the client computer to the current time. Problem: The time on the SMS Site Server is incorrect. Solution: Reset the time on the SMS Site Server to the current time.</Description> </MessageSolution> <MessageSolution> <MessageID>5616</MessageID> <Description>Possible cause: A child site was recently attached and some of the discovery records have not yet been processed by the Discovery Data Manager. Solution: No action is required; the problem will resolve itself once all of the discovery records have been processed.</Description> </MessageSolution> <MessageSolution> <MessageID>5617</MessageID> <Description>Possible cause: A computer has been deleted from the database on the current site but not from the child site. Solution: The summary file has been deleted, no further action is required.</Description> </MessageSolution> <MessageSolution> <MessageID>5804</MessageID> <Description>Solution: Review the previous status messages and logs for further clarification about this problem.</Description> </MessageSolution> <MessageSolution> <MessageID>6808</MessageID> <Description>Possible cause: SMS Writer does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. If this problem persists, refer to the SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.</Description> </MessageSolution> <MessageSolution> <MessageID>6810</MessageID> <Description>Possible cause: %1 is not an SMS client application and so cannot respond to a "close" event. Solution: Stop this application manually or as a standard executable. Possible cause: %1 was not running. Solution: Remove the "clientapp %1" definition from the backup control file.</Description> </MessageSolution> <MessageSolution> <MessageID>6811</MessageID> <Description>Possible cause: %1 does not exist on the local computer. Solution: Verify that there are no errors in the "clientapp %1" definition, or remove the definition from the backup control file.</Description> </MessageSolution> <MessageSolution> <MessageID>6813</MessageID> <Description>Possible causes: %1 is not in the system path or does not exist on the local computer. Solution: Verify that an SMS client application "%1" exists on the local system. Either add its directory to the system path, or specify its full path in the backup control file.</Description> </MessageSolution> <MessageSolution> <MessageID>6814</MessageID> <Description>Possible cause: There are syntax errors or unsupported commands that need to be removed. Solution: Edit backup control file and remove syntax errors on the given lines.</Description> </MessageSolution> <MessageSolution> <MessageID>6815</MessageID> <Description>Possible cause: %1 is/are missing from their predefined location. Solution: Please copy the unavailable tools to their designated folder.</Description> </MessageSolution> <MessageSolution> <MessageID>6816</MessageID> <Description>Possible cause: if %1 is a service then it is not installed or cannot be reached. Solution: Check the name and location of the Service and make sure that service is installed and the machine is reachable.</Description> </MessageSolution> <MessageSolution> <MessageID>6818</MessageID> <Description>Possible cause: %1 is either a built-in symbol or already defined in Backup Control file. Solution: If it is a built-in symbol, it cannot be redefined, remove added definition from backup control file otherwise use only a single definition.</Description> </MessageSolution> <MessageSolution> <MessageID>6819</MessageID> <Description>Possible cause: %1 is not readable. Solution: Adjust file attributes and/or permissions of %1. Possible cause: %1 are on remote computers that SMS Site Backup does not have sufficient access rights to administer. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the remote computer.</Description> </MessageSolution> <MessageSolution> <MessageID>6820</MessageID> <Description>Possible cause: SMS Writer was unable to connect to or set backup privileges for the source registry. Solution: If %1 is in a remote registry, verify that the Site System Connection accounts are properly configured to allow SMS to administer the remote computer; otherwise, reboot. Possible cause: %1 specifies a registry key relative to a hive other than HKEY_LOCAL_MACHINE. Solution: Change %1 so it is relative to HKEY_LOCAL_MACHINE.</Description> </MessageSolution> <MessageSolution> <MessageID>6821</MessageID> <Description>Possible cause: %1 might be locked by another process. Solution: Delete %1 and restart SMS Writer;</Description> </MessageSolution> <MessageSolution> <MessageID>6825</MessageID> <Description>Possible cause: VSS services may not be running.</Description> </MessageSolution> <MessageSolution> <MessageID>6900</MessageID> <Description>Possible cause: The registry information is not available yet. Solution: The State System is waiting for the information to become available and will retry obtaining the registry information at its next interval.</Description> </MessageSolution> <MessageSolution> <MessageID>6901</MessageID> <Description>Possible cause: Client machine is not part of the domain or access account presented by client is not found.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6902</MessageID> <Description>Possible cause: The disk is full.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6903</MessageID> <Description>Possible causes: The registry can not be accessed or the registry is empty.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6904</MessageID> <Description>Possible causes: The registry can not be accessed or the registry is empty or the staging folder can not be accessed.%12</Description> </MessageSolution> <MessageSolution> <MessageID>6905</MessageID> <Description>Possible causes: The outbox is not accessible or is an invalid location.%12</Description> </MessageSolution> <MessageSolution> <MessageID>7000</MessageID> <Description>Possible cause: WSUS Server version 3.0 SP1 and above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP1 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.You can receive failure because proxy is set but proxy name is not specified or proxy server port is invalid.</Description> </MessageSolution> <MessageSolution> <MessageID>7001</MessageID> <Description>Solution: Verify that the failed WSUS components are installed and running.</Description> </MessageSolution> <MessageSolution> <MessageID>7002</MessageID> <Description>Possible cause: SQL Database service is not running or cannot be accessed. Solution: Verify that the SQL Server and SQL Server Agent services are running and can be contacted.</Description> </MessageSolution> <MessageSolution> <MessageID>7003</MessageID> <Description>Possible cause: WSUS Server version 3.0 SP1 and above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP1 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.</Description> </MessageSolution> <MessageSolution> <MessageID>7004</MessageID> <Description>Solution: WSUS Site System requires WSUS Server of version 3.0 SP1 or greater to be installed on the site system. Verify that the correct version is installed</Description> </MessageSolution> <MessageSolution> <MessageID>7100</MessageID> <Description>Possible cause: The WDS Multicast service is not running. Solution: Restart the WDS Service.%12</Description> </MessageSolution> <MessageSolution> <MessageID>7101</MessageID> <Description>Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base.</Description> </MessageSolution> <MessageSolution> <MessageID>7102</MessageID> <Description>Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MCS. For more information, refer to Microsoft Knowledge Base article 838891.</Description> </MessageSolution> <MessageSolution> <MessageID>7200</MessageID> <Description>Possible cause: The out of band service point is not setup successfully. Possible cause: The registry is not accessible. Solution: Wait some time to verify out of band service point is setup successfully. Verify the registry can be accessible.</Description> </MessageSolution> <MessageSolution> <MessageID>7201</MessageID> <Description>Possible cause: The inboxes folder is not accessible. Possible cause: Inbox manager is not running. Solution: Verify the inboxer folder is accessible. Verify inbox manager is running.</Description> </MessageSolution> <MessageSolution> <MessageID>7204</MessageID> <Description>Solutions: Install WinRM out of band service manager and start it in out of band service point site role machine.</Description> </MessageSolution> <MessageSolution> <MessageID>7206</MessageID> <Description>Possible cause: This condition can be caused by transient network connectivity errors. Possible cause: The account used to provision systems is not authorized to provision the management controller. Possible cause: the management controller is not in a state capable of being provisioned or updated. Solution: Verify network connectivity is functional between the out of band service point and the management controller. Verify that the account used to provision the management controller has sufficient permissions to update or provision the management controller. It may be necessary to reset the management controller to factory mode before it can be provisioned.</Description> </MessageSolution> <MessageSolution> <MessageID>7207</MessageID> <Description>Possible cause: This condition can be caused by transient network connectivity errors. The credential used to connect management controller is invalid. The management controllers are in unavailable status. Solution: Verify network connectivity is functional between the out of band service point and the management controller. Verify that the credential used to connect the management controller is valid. It may be necessary to reset the management controller to factory mode and provision it again.</Description> </MessageSolution> <MessageSolution> <MessageID>7208</MessageID> <Description>Possible causes: WinHTTP Proxy is being used between the out of band service point and the AMT-based computer; the AMT-based computer is not on a wired connection; the FQDN of the AMT-based computer exceeds the maximum allowed length of 44 bytes. Solution: Remedy the unsupported scenario by doing one of the following: Reconfigure the proxy configuration or remove the proxy requirement; connect the AMT-based computer to a wired network; reduce the length of the FQDN for the AMT-based computer. Then retry to provision the AMT-based computer.</Description> </MessageSolution> <MessageSolution> <MessageID>7209</MessageID> <Description>Possible cause: This condition is caused when no provisioning certificate is selected or an incorrect certificate is selected. Solution: Create or apply provision certificates from trusted certificates authorities(for example: Verisign, etc). Select the certificates in the Component Configuration settings for the out of band component.</Description> </MessageSolution> <MessageSolution> <MessageID>7212</MessageID> <Description>Possible cause: This error can be caused by network configuration errors or because AMT has the wrong IP address for wired network access . Solution: Ensure that the DHCP scope for AMT is configured correctly with the options 006 (DNS Servers) and 015 (DNS Domain Name). Also check in AMT that the correct IP address is configured for wired network access.</Description> </MessageSolution> <MessageSolution> <MessageID>7213</MessageID> <Description>Possible cause: The remote admin account password of this AMT device is out of sync with SCCM database. This condition might be caused by this device is provisioned by some other provision server, the MEBx password of this device has been changed locally or hasn't been configured as a provision account in the Component Configuration settings for the out of band component. Solution: If this device is provisioned by other provision server, please refer to migration scenario. If the MEBx password is changed, please change it into someone already known by SCCM, or configure this MEBx password as a provision account.</Description> </MessageSolution> <MessageSolution> <MessageID>7214</MessageID> <Description>Possible cause: This condition can be caused when the certificate is revoked by certificate authority. The computer does not have network connectivity to the certification authority. The proxy settings for the CRL checking are not set correctly. Solution: Verify that the certificate is unrevoked by certificate authority. Verify that the the system can connect to the certification authority (it could require internet connectivity for certain certification authorities). Verify the proxy configuration settings for the CRL checking are set correctly.</Description> </MessageSolution> <MessageSolution> <MessageID>7216</MessageID> <Description>Possible cause: This error can occur when the AMT audit log is full and when %1 is set as critical event in the audit log settings. Solution: Verify the audit log settings on %2. Disable and then re-enable the AMT audit log settings on %2 in the Configuration Manager console.</Description> </MessageSolution> <MessageSolution> <MessageID>7217</MessageID> <Description>Solution: You can change the precedence order by typing the following commands in a command prompt: "netsh interface ipv6 delete prefix ::ffff:0:0/96" and then "netsh interface ipv6 add prefix prefix=::ffff:0:0/96 precedence=45 label=4".</Description> </MessageSolution> <MessageSolution> <MessageID>7300</MessageID> <Description>Solution: Verify that the .Net Framework 2.0 or greater is installed.</Description> </MessageSolution> <MessageSolution> <MessageID>7600</MessageID> <Description>Possible cause: This condition may occur when the SMS service account does not have permission to apply the requested certificate from the certification authority to the out of band management controller. Possible cause: This condition may occur if the network connectivity is intermittent or failed during the attempt to update the out of band management controller with the requested certificate. Solution: Verify that the account used by SMS_EXECUTIVE service has permission to update the out of band management controller. For Intel AMT devices, the required permission (realm) is "PT Administer". Additionally, ensure that the network connection between the certification authority, the site server and the out of band management device is operational and required infrastructure components are accessilbe during the update.</Description> </MessageSolution> <MessageSolution> <MessageID>7601</MessageID> <Description>Possible cause: This condition may occur when the root certificate of the CA is not in the store "Trusted Root Certification Authorities" or the root certificate is invalid. Solution: Verify that the root certificate of the CA is in the store "Trusted Root Certification Authorities" and it is valid.</Description> </MessageSolution> <MessageSolution> <MessageID>7602</MessageID> <Description>Possible cause: the SMS service account does not have permission to publish the object in the Active Directory.</Description> </MessageSolution> <MessageSolution> <MessageID>7603</MessageID> <Description>Possible cause: the SMS service account does not have permission to remove the object in the Active Directory.</Description> </MessageSolution> <MessageSolution> <MessageID>7604</MessageID> <Description>Possible cause: the SMS service account does not have permission to remove the object in the Active Directory, or this object doesn't exist.</Description> </MessageSolution> <MessageSolution> <MessageID>7606</MessageID> <Description>Possible cause: The site server does not have sufficient permission to update DNS. Solution: Check that the account used by SMS_EXECUTIVE has permission to publish records for the site server's DNS server.</Description> </MessageSolution> <MessageSolution> <MessageID>7607</MessageID> <Description>Possible cause: The site server does not have sufficient permission to update DNS. Solution: Check that the account used by SMS_EXECUTIVE has permission to publish records for the site server's DNS server.</Description> </MessageSolution> <MessageSolution> <MessageID>7403</MessageID> <Description>Possible cause: SQL Server Reporting Service authentication. Solution: How to: Configure Windows Authentication in Reporting Services (http://technet.microsoft.com/en-us/library/cc281253.aspx). Possible cause: Cummulative update package 4 for SQL Server 2008 R2 has not being installed. Solution: Install Cummulative update package 4 for SQL Server 2008 R2 (http://support.microsoft.com/kb/2345451). Possible cause: SQL Server Reporting Service corrupt. Solution: How to rebuild the report server performance counters (SSRS) (http://social.technet.microsoft.com/wiki/contents/articles/how-to-rebuild-the-report-server-performance-counters-ssrs.aspx).</Description> </MessageSolution> <MessageSolution> <MessageID>0x80070422</MessageID> <Description>Possible cause: Background Intelligent Transfer Service (BITS) is not running. Solution: Confirm that Background Intelligent Transfer Service (BITS) is not disabled by the administrator Possible cause: Error message when you try to install updates by using the Windows Update Web site or the Microsoft Update Web site: "0x80070422" Solution: http://support.microsoft.com/kb/958043</Description> </MessageSolution> <MessageSolution> <MessageID>0x8007f02b</MessageID> <Description>Possible cause: There is not enough disk space for WSUS to create the Uninstall files. Solution: You need to clean up your system drive.</Description> </MessageSolution> <MessageSolution> <MessageID>0x8007f003</MessageID> <Description>Possible cause: There is not enough disk space for WSUS to create the Uninstall files. Solution: You need to clean up your system drive.</Description> </MessageSolution> <MessageSolution> <MessageID>0x80072F8F</MessageID> <Description>Possible cause: WSUS Server is configured with SSL. Solution: Ensure that the server is connecting to a certificate subject name. You can also type the https address into Internet Explorer and look for error messages relating to the certificate- if a certificate error is displayed, clients will not sync.</Description> </MessageSolution> <MessageSolution> <MessageID>0x8007F004</MessageID> <Description>Possible cause: User rights issue. Solution: If a user has administrative rights, but is not listed, or a member of a group listed under the “Manage Auditing and Security Log” right in the security policy- then any patch that writes to the event log will fail with this error code.</Description> </MessageSolution> <MessageSolution> <MessageID>0x80072EFD</MessageID> <Description>Possible cause: WSUS Server is configured with SSL. Solution: Validate the certificate chains on the server and ensure the WSUS server’s certificate is trusted. Also, ensure FIPS-140 compliant algorithms are disabled on the WSUS server, as they do not appear to be supported by the WU clients. Possible cause: Connection Issue. Solution: Verify if there is no firewall blocking any connection with WSUS Server.</Description> </MessageSolution> <MessageSolution> <MessageID>0x8024400D</MessageID> <Description> Solution: Run this command in a command prompt: wuauclt /detectnow /resetauthorizations Possible cause: This may indicate some stored files are out of date. Solution: Stop the Automatic Updates Service. Delete all files in "C:\Windows\SoftwareDistribution\DataStore" and "C:\Windows\SoftwareDistribution\Download" directories. Start the Automatic updates service. Force a Detection Cycle. Possible cause: This may indicate a problem with WMI Solution: See WMI Troubleshooting Tips (http://blogs.technet.com/b/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx)</Description> </MessageSolution> <MessageSolution> <MessageID>0x80244018</MessageID> <Description>Possible cause: Proxy connectivity issue Solution: Check proxy settings</Description> </MessageSolution> <MessageSolution> <MessageID>0x80072AFC</MessageID> <Description>Possible cause: DnldMgr error Solution: Check the log and ensure that the DNS name used by the WU client is the location DnldMgr is attempting to download from. Clients will not download updates, though they will report correctly to the WSUS server. You may have to clear the software distribution folder to remove any cached information or downloads.</Description> </MessageSolution> <MessageSolution> <MessageID>0x80070002</MessageID> <Description>Possible cause: You receive a "0x80070002" or "0x80070003" error code after you download an update from Windows Update, from Microsoft Update, or from Windows Server Update Services Solution: http://support.microsoft.com/kb/910336</Description> </MessageSolution> <MessageSolution> <MessageID>0x80070003</MessageID> <Description>Possible cause: You receive a "0x80070002" or "0x80070003" error code after you download an update from Windows Update, from Microsoft Update, or from Windows Server Update Services Solution: http://support.microsoft.com/kb/910336</Description> </MessageSolution> <MessageSolution> <MessageID>0x80004005</MessageID> <Description>Possible cause: Unspecified error Possible cause: Automatic updates may not be successfully downloaded from a computer that is running Software Update Services Solution: http://support.microsoft.com/kb/842289</Description> </MessageSolution> <MessageSolution> <MessageID>0x80040651</MessageID> <Description> Check WindowsUpdate.log from C:\Windows folder to see if it offers anything additional</Description> </MessageSolution> <MessageSolution> <MessageID>0x80040602</MessageID> <Description>Possible cause: There is not enough disk space for SCCM Client to download Software Update Files Solution: You need to clean up the drive where the SCCM Client keep cache files.</Description> </MessageSolution> <MessageSolution> <MessageID>0x800705B4</MessageID> <Description>Possible cause: Time out Solution: Check your network connectivity.</Description> </MessageSolution> <MessageSolution> <MessageID>0x80040692</MessageID> <Description>Possible cause: This can happen when there is a Group policy set in the domain that is managing updates and patching machines in the domain. Solution 01: Remove the group policy at the domain level Solution 02: Use the same WSUS server as the Software Update Point for the SCCM as well</Description> </MessageSolution> <MessageSolution> <MessageID>0x80072EE2</MessageID> <Description>Possible cause: Time out Solution: Check your network connectivity Possible cause: Connection Aborted error Solution: Check your network connectivity Possible cause: Proxy/Firewall Issue Solution: Check your proxy/firewall settings. Make sure that connectivity with WSUS Server is allowed using ports TCP 80/443 or 8530/8531 Possible cause: Service Issue Solution: Restart Windows Update Service using: net stop wuauserv and net start wuauserv Possible cause: Network bandwidth issue Solution: Make sure there is enough network bandwidth to download files from WSUS Possible cause: Automatic updates may not be successfully downloaded from a computer that is running Software Update Services Solution: http://support.microsoft.com/?kbid=842289 Possible cause: Unspecified error Solution: Check client logs for more information</Description> </MessageSolution> <MessageSolution> <MessageID>0x80004002</MessageID> <Description>Possible cause: FATAL: Failed to get session from datastore, error = 0x80004002 Possible cause: FATAL: Failed to Unserialize from data store, error = 0x80004002 Possible cause: WARNING: Exit code = 0x80004002 Possible cause: WARNING: InitAUComponents Failed, will restart AU in 30 mins, error = 0x80004002 Solution 01: Stop Automatic Update Service - "Net stop wuauserv". Run the following command: "proxycfg.exe -u". Start Automatic Update Service - "Net start wuauserv". Run the following command: "WUAUCLT /detectnow". Solution 02: Stop Automatic Update Service - "Net stop wuauserv". Rename/delete "%Windir%\SoftwareDistribution" folder. Start Automatic Update Service - "Net start wuauserv". Run the following command: "WUAUCLT /detectnow".</Description> </MessageSolution> <MessageSolution> <MessageID>0x80040269</MessageID> <Description>Possible cause: You receive an error code and the copy of Microsoft Windows is not validated when you try to use Windows Genuine Advantage to validate your copy of Windows Solution: http://support.microsoft.com/kb/908440</Description> </MessageSolution> <MessageSolution> <MessageID>0x80040605</MessageID> <Description>Possible cause: Scan Tool has been Removed Solution: http://support.microsoft.com/kb/949104</Description> </MessageSolution> <MessageSolution> <MessageID>0x80041001</MessageID> <Description>Possible cause: WMI Generic Failure Solution: See WMI Troubleshooting Tips (http://blogs.technet.com/b/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx) Possible cause: The Microsoft Windows Server Update Services (WSUS) SelfUpdate service does not send automatic updates Solution: http://support.microsoft.com/kb/920659</Description> </MessageSolution> <MessageSolution> <MessageID>0x8007000E</MessageID> <Description>Possible cause: You may encounter temporary connection-related errors when you use Windows Update or Microsoft Update to install updates Solution: http://support.microsoft.com/kb/836941 Possible cause: There is not enough memory available on the client Solution: Close few programs, reboot client machine or add more RAM memory</Description> </MessageSolution> <MessageSolution> <MessageID>0x80070020</MessageID> <Description>Possible cause: You receive error 0x80070020 when you use the Windows Update Web site or the Microsoft Update Web site to install updates Solution: http://support.microsoft.com/kb/883825</Description> </MessageSolution> <MessageSolution> <MessageID>0x80070005</MessageID> <Description>Possible cause: Error message when you try to install the Windows Genuine Advantage (WGA) Validation Tool from the Windows Update Web site: "0x80070005" Solution: http://support.microsoft.com/kb/917499 Possible cause: Error message when you use Windows Update or Microsoft Update Web sites to install updates on Windows 2000, Windows XP, and Windows Server 2003: 0x80070005 Solution: http://support.microsoft.com/kb/968003</Description> </MessageSolution> <MessageSolution> <MessageID>-2147023838</MessageID> <Description>Possible cause: Error message when you use Windows Update or Microsoft Update Web sites to install updates: 0x80070424 Solution: http://support.microsoft.com/kb/968002 Possible cause: Background Intelligent Transfer Service (BITS) is not running. Solution: Confirm that Background Intelligent Transfer Service (BITS) is not disabled by the administrator</Description> </MessageSolution> <MessageSolution> <MessageID>0x80072EE6</MessageID> <Description>Possible cause: The URL does not use a recognized protocol Solution: Change the Specify intranet Microsoft update service location to use the FQDN WSUS Server name</Description> </MessageSolution> <MessageSolution> <MessageID>0x8024001F</MessageID> <Description>Possible cause: No network connection is available to finish the operation. Solution: Connect to the network</Description> </MessageSolution> <MessageSolution> <MessageID>0x80241003</MessageID> <Description>Possible cause: Windows Installer updating is disabled by policy.</Description> </MessageSolution> <MessageSolution> <MessageID>0x8024400A</MessageID> <Description>Possible cause: You may encounter temporary connection-related errors when you use Windows Update or Microsoft Update to install updates Solution: http://support.microsoft.com/kb/836941</Description> </MessageSolution> <MessageSolution> <MessageID>0x8024400E</MessageID> <Description>Possible cause: You may encounter temporary connection-related errors when you use Windows Update or Microsoft Update to install updates Solution: http://support.microsoft.com/kb/836941</Description> </MessageSolution> <MessageSolution> <MessageID>0x80244016</MessageID> <Description>Possible cause: You may encounter temporary connection-related errors when you use Windows Update or Microsoft Update to install updates Solution: http://support.microsoft.com/kb/836941</Description> </MessageSolution> <MessageSolution> <MessageID>0x80248011</MessageID> <Description>Possible cause: You may receive an error message when you search for available updates on the Windows Update Web site or on the Microsoft Update Web site Solution: http://support.microsoft.com/kb/883821</Description> </MessageSolution> <MessageSolution> <MessageID>0x80070641</MessageID> <Description>Possible cause: How to troubleshoot problems connecting to Windows Update or to Microsoft Update Solution: http://support.microsoft.com/kb/818018/</Description> </MessageSolution> <MessageSolution> <MessageID>0x80070643</MessageID> <Description>Possible cause: Error message when you use Windows Server Update Services Setup: "Error 0x80070643: Fatal error during installation" Solution: http://support.microsoft.com/kb/920660</Description> </MessageSolution> <MessageSolution> <MessageID>0x80070652</MessageID> <Description>Possible cause: Another conflicting operation was in progress. Some operations such as installation cannot be performed twice simultaneously. Solution: Restart client computer Solution: Reinstall the Windows Update Agent - http://support.microsoft.com/kb/946928</Description> </MessageSolution> <MessageSolution> <MessageID>0x80040668</MessageID> <Description>Possible cause: Software update incomplete Solution: http://support.microsoft.com/kb/319585 Solution: http://technet.microsoft.com/en-us/library/bb735894.aspx Solution: Confirm that the client computer has network access and/or have downloaded all updates prior any network disconnection Possible cause: Software update still detected as actionable after apply. Solution: Reinstall .NET Framework 2.0 - http://support.microsoft.com/kb/908077</Description> </MessageSolution> <MessageSolution> <MessageID>0x80244008</MessageID> <Description>Possible cause: You may encounter temporary connection-related errors when you use Windows Update or Microsoft Update to install updates Solution: http://support.microsoft.com/kb/836941</Description> </MessageSolution> <MessageSolution> <MessageID>0x8024402C</MessageID> <Description>Possible cause: You may receive an error message when you search for available updates on the Windows Update Web site or on the Microsoft Update Web site Solution: http://support.microsoft.com/kb/883821</Description> </MessageSolution> <MessageSolution> <MessageID>0x80041002</MessageID> <Description>Possible cause: This may indicate a problem with WMI Solution: See WMI Troubleshooting Tips (http://blogs.technet.com/b/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx)</Description> </MessageSolution> <MessageSolution> <MessageID>6703</MessageID> <Description>Possible cause: Status message ID 6703 contains different error messages depending on the problem that occurs. Solution: Look for the synchronization error message in one of the detailed troubleshooting topics at http://technet.microsoft.com/en-us/library/bb735874.aspx for possible solutions to the issue.</Description> </MessageSolution> <MessageSolution> <MessageID>0x80040154</MessageID> <Description>Possible cause: Class not registered Solution: BITS in Windows 200x is dependent on SENS and EventSystem services. If COM+ catalog is corrupted, one of these errors was seen. Possible cause: This may indicate some stored files are out of date. Solution: Stop the Automatic Updates Service. Delete all files in "C:\Windows\SoftwareDistribution\DataStore" and "C:\Windows\SoftwareDistribution\Download" directories. Start the Automatic updates service. Force a Detection Cycle.</Description> </MessageSolution> <MessageSolution> <MessageID>6301</MessageID> <Description> Solution: Check Previous Messages for more error information.</Description> </MessageSolution> <MessageSolution> <MessageID>11170</MessageID> <Description> Solution: Check Previous Messages for more error information.</Description> </MessageSolution> <MessageSolution> <MessageID>11139</MessageID> <Description> Solution: Check Message for more information.</Description> </MessageSolution> <MessageSolution> <MessageID>11135</MessageID> <Description> Solution: Check Message for more information.</Description> </MessageSolution> <MessageSolution> <MessageID>11141</MessageID> <Description> Solution: Check Message for more information.</Description> </MessageSolution> <MessageSolution> <MessageID>6315</MessageID> <Description>Possible cause: The computer running SQL Server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the computer running SQL Server site system is turned on, connected to the network, and functioning properly. Possible cause: PXE Service point does not have sufficient access rights to the SQL server site system. Solution: Verify that management point computer account or the Management Point Database Connection Account is a member of SMS Management Point Role (msdbrole_MP) in the SQL Server database. Possible cause: Network problems are preventing the pxe service point from properly accessing the SQL Server. Solution: Investigate and correct any problems with your network. Possible cause: The pxe service point having problems is at a secondary site, and SQL access account being used was recently reset by the parent site. Solution: This can automatically repair itself after one hour , as long as the account in use is not locked out. Check that the account in use is not locked out. Instead of waiting an hour, you can stop and start the SMS_SITE_COMPONENT_MANAGER service to immediately apply the new configuration. Possible cause: The SQL server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL server SPNs are correctly registered. Review Q829868.</Description> </MessageSolution> <MessageSolution> <MessageID>600</MessageID> <Description>Possible cause: The computer running SQL Server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the computer running SQL Server site system is turned on, connected to the network, and functioning properly. Possible cause: Site Server does not have sufficient access rights to the SQL server site system. Solution: Verify that management point computer account or the Management Point Database Connection Account is a member of SMS Management Point Role (msdbrole_MP) in the SQL Server database. Possible cause: Network problems are preventing the site server from properly accessing the SQL Server. Solution: Investigate and correct any problems with your network. Possible cause: The site server having problems is at a secondary site, and SQL access account being used was recently reset by the parent site. Solution: This can automatically repair itself after one hour , as long as the account in use is not locked out. Check that the account in use is not locked out. Instead of waiting an hour, you can stop and start the SMS_SITE_COMPONENT_MANAGER service to immediately apply the new configuration. Possible cause: The SQL server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL server SPNs are correctly registered. Review Q829868.</Description> </MessageSolution> <MessageSolution> <MessageID>679</MessageID> <Description>Possible cause: SQL Server problem. Solution 1: Review the immediately preceding status messages from this component about SQL Server errors. Solution 2: Verify that this computer can reach the SQL Server computer. Solution 3: Verify that SQL Server services are running. Solution 4: Verify that SMS can access the SMS site database. Solution 5: Verify that the SMS site database, transaction log, and tempdb are not full. Solution 6: Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. Solution 7: If the problem persists, check the SQL Server error logs.</Description> </MessageSolution> <MessageSolution> <MessageID>11756</MessageID> <Description>Possible cause: Computer does not have the latest Windows Update Agent Solution: http://support.microsoft.com/kb/949104</Description> </MessageSolution> <MessageSolution> <MessageID>11708</MessageID> <Description> Enabling verbose logging for Windows installer may provide more information about the source of the problem. See http://support.microsoft.com/kb/314852 on how to enable Windows Installer logging in Windows XP. </Description> </MessageSolution> <MessageSolution> <MessageID>11751</MessageID> <Description> Enabling verbose logging for Windows installer may provide more information about the source of the problem. See http://support.microsoft.com/kb/314852 on how to enable Windows Installer logging in Windows XP. </Description> </MessageSolution> <MessageSolution> <MessageID>11714</MessageID> <Description> Enabling verbose logging for Windows installer may provide more information about the source of the problem. See http://support.microsoft.com/kb/314852 on how to enable Windows Installer logging in Windows XP. </Description> </MessageSolution> <MessageSolution> <MessageID>11713</MessageID> <Description>Possible cause: Background Intelligent Transfer Service (BITS) is not running. Solution: Start the Background Intelligent Transfer Service (BITS). Extra troubleshooting: Enabling verbose logging for Windows installer may provide more information about the source of the problem. See http://support.microsoft.com/kb/314852 on how to enable Windows Installer logging in Windows XP. </Description> </MessageSolution> <MessageSolution> <MessageID>11753</MessageID> <Description> Enabling verbose logging for Windows installer may provide more information about the source of the problem. See http://support.microsoft.com/kb/314852 on how to enable Windows Installer logging in Windows XP. </Description> </MessageSolution> <MessageSolution> <MessageID>11750</MessageID> <Description> Enabling verbose logging for Windows installer may provide more information about the source of the problem. See http://support.microsoft.com/kb/314852 on how to enable Windows Installer logging in Windows XP. </Description> </MessageSolution> <MessageSolution> <MessageID>11759</MessageID> <Description> Enabling verbose logging for Windows installer may provide more information about the source of the problem. See http://support.microsoft.com/kb/314852 on how to enable Windows Installer logging in Windows XP. </Description> </MessageSolution> <MessageSolution> <MessageID>11701</MessageID> <Description> Enabling verbose logging for Windows installer may provide more information about the source of the problem. See http://support.microsoft.com/kb/314852 on how to enable Windows Installer logging in Windows XP. </Description> </MessageSolution> <MessageSolution> <MessageID>11706</MessageID> <Description> Enabling verbose logging for Windows installer may provide more information about the source of the problem. See http://support.microsoft.com/kb/314852 on how to enable Windows Installer logging in Windows XP. </Description> </MessageSolution> <MessageSolution> <MessageID>11752</MessageID> <Description> Enabling verbose logging for Windows installer may provide more information about the source of the problem. See http://support.microsoft.com/kb/314852 on how to enable Windows Installer logging in Windows XP. </Description> </MessageSolution> <MessageSolution> <MessageID>11755</MessageID> <Description> Enabling verbose logging for Windows installer may provide more information about the source of the problem. See http://support.microsoft.com/kb/314852 on how to enable Windows Installer logging in Windows XP. </Description> </MessageSolution> <MessageSolution> <MessageID>11709</MessageID> <Description> Check WindowsUpdate.log from C:\Windows folder to see if it offers anything additional</Description> </MessageSolution> <MessageSolution> <MessageID>11702</MessageID> <Description> Check WindowsUpdate.log from C:\Windows folder to see if it offers anything additional</Description> </MessageSolution> <MessageSolution> <MessageID>7608</MessageID> <Description> Check http://technet.microsoft.com/en-us/library/cc161803.aspx</Description> </MessageSolution> <MessageSolution> <MessageID>7609</MessageID> <Description> Check http://technet.microsoft.com/en-us/library/cc161803.aspx</Description> </MessageSolution> <MessageSolution> <MessageID>0x80073712</MessageID> <Description>Possible cause: Error Code 0x80073712 when using Windows Update or Microsoft Update to install updates. Solution: http://support.microsoft.com/kb/957310 Possible cause: You receive error code "0x80073712" or the "Windows Features" dialog box is empty when you try to install updates or components in Windows 7 or in Windows Vista Solution: http://support.microsoft.com/kb/931712</Description> </MessageSolution> <MessageSolution> <MessageID>0xC8000247</MessageID> <Description>Possible cause: How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7 Solution: http://support.microsoft.com/kb/929833 Possible cause: How do I reset Windows Update components? Solution: http://support.microsoft.com/kb/971058</Description> </MessageSolution> <MessageSolution> <MessageID>0xC80003F3</MessageID> <Description>Possible cause: hrOutOfMemory: The computer is out of memory Solution: http://windows.microsoft.com/en-US/windows-vista/Change-the-size-of-virtual-memory</Description> </MessageSolution> <MessageSolution> <MessageID>0xC80003FA</MessageID> <Description>Possible cause: Temporary connection-related errors may occur when you use Windows Update or Microsoft Update Solution: http://support.microsoft.com/?kbid=836941</Description> </MessageSolution> <MessageSolution> <MessageID>682</MessageID> <Description>Possible cause: ClientKeyData table gets corrupted on central site server Solution: http://blogs.technet.com/b/dominikheinz/archive/2010/09/29/clientkeydata-gets-corrupted-on-central-site-server.aspx Possible cause: Dynamically fix invalid ClientKeyData issue on central site Solution: http://blog.itminutes.net/?p=867</Description> </MessageSolution> <MessageSolution> <MessageID>6104</MessageID> <Description>Possible cause: Anti-Virus Solution: http://blogs.technet.com/b/configurationmgr/archive/2010/11/30/configmgr-2007-antivirus-scan-and-exclusion-recommendations.aspx.</Description> </MessageSolution> <MessageSolution> <MessageID>6105</MessageID> <Description>Possible cause: Anti-Virus Solution: http://blogs.technet.com/b/configurationmgr/archive/2010/11/30/configmgr-2007-antivirus-scan-and-exclusion-recommendations.aspx.</Description> </MessageSolution> <MessageSolution> <MessageID>6105</MessageID> <Description>Possible cause: A new Volume Shadow Copy Service update is now available that fixes various Volume Shadow Copy Service problems in Windows Server 2003 Solution: http://support.microsoft.com/kb/913648 Possible cause: Error message when you run the "vssadmin list writers" command on a Windows Server 2003-based computer: "Error: 0x8000FFFF" Solution: http://support.microsoft.com/kb/940184 Possible cause: Configuration Manager 2007 : SMS_SITE_BACKUP \ SMS_SITE_VSS_WRITER not starting... whats my locale Solution: http://blogs.technet.com/b/jeevanbisht/archive/2009/02/26/configuration-manager-2007-sms-site-backup-sms-site-vss-writer-not-starting-whats-my-locale.aspx Possible cause: SQL Server Rights Solution: Add the SCCM Site Server computer account as Sysadmin on SQL Server (if SQL Server is remote computer, add it also to the Local Administrators group - http://technet.microsoft.com/en-us/library/bb680595.aspx) Possible cause: The "Backup ConfigMgr Site Server" task fails on a ConfigMgr 2007 site server Solution: http://support.microsoft.com/?kbid=981640 Possible cause: SMS_SITE_VSS_WRITER Stopped Solution: Start/restart the SMS_SITE_VSS_WRITER</Description> </MessageSolution> <MessageSolution> <MessageID>0x80080005</MessageID> <Description>Possible cause: You may receive an "Error code 80080005 -- server execution failed." error message when you start many COM+ applications Solution: http://support.microsoft.com/kb/870655 Possible cause: Server execution failed Solution: Reinstall the Windows Update Agent - http://support.microsoft.com/kb/946928</Description> </MessageSolution> <MessageSolution> <MessageID>0x80072EFE</MessageID> <Description>Possible cause: You may encounter temporary connection-related errors when you use Windows Update or Microsoft Update to install updates Solution: http://support.microsoft.com/kb/836941</Description> </MessageSolution> <MessageSolution> <MessageID>0x8024401B</MessageID> <Description>Possible cause: You cannot download updates when you access the Windows Update Web site from a Windows XP-based computer that is behind a firewall or a proxy server Solution: http://support.microsoft.com/kb/896226</Description> </MessageSolution> <MessageSolution> <MessageID>-2147012894</MessageID> <Description>Possible cause: Windows Update error 80072ee2 Solution: http://windows.microsoft.com/en-hk/windows-vista/windows-update-error-80072ee2 Possible cause: Time out Solution: Check your network connectivity.</Description> </MessageSolution> </dtsHealthCheck> |