Formula una domandaFormula una domanda
 

Con risposta5413, 55447, 3707, 3701, 2703 warnings

  • giovedì 2 luglio 2009 10.38jorgequesada_wanadoo.es Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     

    Hi,

    We have installed SCCM 2007 in a customer where there were a previous installation of a failed SCCM. From this previous installation there are quite a few SCCM clients already installed on the workstations.

    Once the installation of the new SCCM hierarchy is made everything seems to work fine but there are some warning messages reported by the SMS_MP_CONTROL_MANAGER, SMS_SOFTWARE_INVENTORY_PROCESSOR and SMS_INVENTORY_DATA_LOADER that repeat constantly.

    Severity: Warning
    Source: SMS Server
    Component: SMS_MP_CONTROL_MANAGER
    Message ID: 5413

    Description:
    MP has discarded a report when processing Ddr.

    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


    Severity: Warning
    Source: SMS Server
    Component: SMS_MP_CONTROL_MANAGER
    Message ID: 55447

    Description: MP has rejected a policy request from GUID:CEF95F16-508C-4F6C-A4C0-801C81CBADF5 because it was not approved. The operating system reported error 2147942405: Access is denied.



    Severity: Warning
    Source: SMS Server
    Component: SMS_SOFTWARE_INVENTORY_PROCESSOR
    Message ID: 3707

    Description:
    SMS Software Inventory Processor failed to process software inventory file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\sinv.box\VCYNO885.SID" because the file does not have a corresponding discovery record. SMS Software Inventory Processor has moved this file to the Orphans directory as file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\sinv.box\Orphans\1pqly4we.SID" and will retry processing it later.

    When SMS 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 SMS 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 SMS Software Inventory Processor retries the file every 10 minutes.

    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.


    Severity: Warning
    Source: SMS Server
    Component: SMS_SOFTWARE_INVENTORY_PROCESSOR
    Message ID: 3701

    Description:
    SMS Software Inventory Processor failed to process software inventory file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\sinv.box\Orphans\nqo4ze8x.SID," and has moved it to "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\sinv.box\BADSinv\xv041q56.SID."

    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.


    Severity: Warning
    Source: SMS Server
    Component: SMS_INVENTORY_DATA_LOADER
    Message ID: 2703

    Description:
    SMS Inventory Data Loader failed to process the delta MIF file "XH1X39BZS.MIF" and has moved it to "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\dataldr.box\BADMIFS\tgd7lpy4.MIF."

    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.


    We have enabled Active Directory System Discovery discovery method and configured all needed boundaries. The approval is set to automatically aprove computers in trusted domains. 

    SCCM has discovered the systems that had the SCCM client installed and they appear in All Systems with domain and Site Code blanked, Client: Yes, Blocked: No, Client Type: Advanced, Obsolet: No, Active: Yes

    Are these errors dued to the clients are not approved yet? If so, how can they be approved taking ¡nto account that they all are members of the same domain as the Site Server is? Is there any other explanation?

    Thanks and regards,
    Jorge Q


    Jorge Q

Risposte

Tutte le risposte