Ask a questionAsk a question
 

Proposed AnswerSCCM errors

  • Friday, October 16, 2009 8:54 PMJepeto46 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    This is a re-install after the previous site was removed.
    the SCCM is running on a 64 bit machine, WSUs and SQL are on two separate machines. Teh install went without any errors, however we see a load of critical errors in the component status:
    SMS_CI_assignment _manager : SMS CI Assignment Manager failed to process CI Assignment changes. These changes will be retried on next processing cycle.
    SMS_collection_evaluator : SMS Collection Evaluator failed to process Collection Settings changes. These changes will be retried on next processing cycle.
    And list goes on.
    SMS_database_notification
    SMS_discovery_data_manager
    SMS_hierarchy_manager
    SMS_inventory-data_loader
    SMS_MP_control_manager
    SMS_object_replication_manager
    SMS_policy_provider
    SMS_software_metering_processor
    SMS_state-system
    SMS_WSUS_SYNC_manager
    SMS_SRs_reporting_point
    SMS_system_health_validator
    SMS_MP_decive_manager

    For many entries the severity level for  the first few are information and the rest are errors. trying to apply hot fixes fails due to hardware platform error, so where would you start? this is a dedicated SCCM machine, so i was thinking, uninstall, wipe out, directory clean up and re-install from scratch. Or are those errors "easy" to fix.

All Replies

  • Saturday, October 17, 2009 12:41 AMJason SandysMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Did you use the same site code as the previous site?
    Did you use the same server name as the previous site server?
    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
  • Tuesday, October 20, 2009 12:42 PMJepeto46 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    Jason, as i mentioned in my duplicate post (sorry, my bad), those were all permission errors. once i fixed the permissions everything started working properly.