Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter >
> 
> 
MP Sync Job Pending Association

Unanswered MP Sync Job Pending Association

  • Friday, January 13, 2012 10:24 AM
     
     
    Sign In to Vote
    0

    Hi 

    have (what i think) installed SM MS and DW  successfull but see two  Pending Association in MP Sync Job

    It is batch 36 Microsoft.Systemcenter.Datawarehouse.base and Microsoft.Systemcenter.warehouse.system - all other is imported og Associated - I have no problems with reports etc. 

     

     

All Replies

  • Friday, January 13, 2012 10:30 AM
     
     
    Sign In to Vote
    0

    Have your other jobs run?

    The MPSyncJob runs every 5 minutes, have the other jobs run to completion?

    Do you have up to date information within your reports?

    As long as you learn something new every day, the day is not wasted.
     
  • Friday, January 13, 2012 12:26 PM
     
     
    Sign In to Vote
    0
    1321    MPSyncJob            Running      Synchronization  13-01-2012 10:30:00                               True
    1323    Transform.Common     Running      Transform        13-01-2012 10:30:00                               True
    1324    Load.Common          Running      Load             13-01-2012 10:30:00                               True
    1328    Extract_DW_IT_SM     Running      Extract          13-01-2012 10:29:00                               True
    1329    Extract_IT_SM        Running      Extract          13-01-2012 10:29:00                               True
    an two hours later:
    BatchId Name                 Status       CategoryName     StartTime                EndTime                  IsEnabled
    ------- ----                 ------       ------------     ---------                -------                  ---------
    1390    DWMaintenance        Not Started  Maintenance                                                        True
    1391    MPSyncJob            Not Started  Synchronization                                                    True
    1393    Transform.Common     Not Started  Transform                                                          True
    1394    Load.Common          Not Started  Load                                                               True
    1395    Extract_IT_SM        Not Started  Extract                                                            True
    1396    Extract_DW_IT_SM     Not Started  Extract                                                            True
    about reports (all incidents ) it takes a hour before the new incident is presented (but I think this is ok)
     
  • Friday, January 13, 2012 1:08 PM
     
     
    Sign In to Vote
    0

    Can you please look into the detail of the MPSYncJob, can you see more MPs being imported?

    You can also check this under "management packs" in the "Data Warehouse" Wunderbar.

    As long as you learn something new every day, the day is not wasted.
     
  • Friday, January 13, 2012 1:11 PM
     
     
    Sign In to Vote
    0

    Hi

    All MP under Management Packs have deployed "Completed"

    All aprox. 190 batch job is associated or imported except those two mentioned

     
  • Friday, January 13, 2012 1:15 PM
     
     
    Sign In to Vote
    0

    You can try to restart the System Center Services to "kick it along"

    System Center Data Acess - stop

    Ssytem Center Management Configuration - stop

    System Center Management -  stop

    Ssytem Center Management Configuration - start

    System Center Management - start

    System Center Data Acess - start

    As long as you learn something new every day, the day is not wasted.
     
  • Friday, January 13, 2012 1:29 PM
     
     
    Sign In to Vote
    0
    on the smdw or smms (or both)
     
  • Friday, January 13, 2012 1:47 PM
     
     
    Sign In to Vote
    0

    Sorry, forgot to mention that

    DW

    As long as you learn something new every day, the day is not wasted.
     
  • Friday, January 13, 2012 1:54 PM
     
     
    Sign In to Vote
    0

    Done 

    All jobs is now runing - - now MP sync is done - still the same two Pending associated

    some warnings in Operations Manager event log (don´t know whether this have to Opsmgr agent to do)

    Incorrect user information detected. The domain name, user name or password were not valid. Ignoring the given credentials and proceeding with the default workflow account: 

     

    User information detected: 

    Domain name:  

    User name: 

     

     
  • Friday, January 13, 2012 1:56 PM
     
     
    Sign In to Vote
    0

    OIt might take some time for all the jobs to complete now.

    The error is standard when the Data Access Service restarts.

    As long as you learn something new every day, the day is not wasted.
     
  • Friday, January 13, 2012 2:03 PM
     
     
    Sign In to Vote
    0

    now it is weekend, so next weekend I will se  -

    ok thanks :)

     
  • Sunday, January 15, 2012 10:07 PM
    Moderator
     
     
    Sign In to Vote
    1

    Hi,

    If this hasn't been resolved yet, you should log on to your DW server, start a Powershell prompt and run the following commands:

    Add-PSSnapIn SMCmdletSnapIn
    Get-SCDWJobModule

    Look for any errors, if you see any, run the following:

    Get-SCDWJobModule -jobname <NameOfJob> -moduleid <IdOfModuleWithError> | fl

    Regards
    //Anders

    Anders Asp | Lumagate | www.lumagate.com | Sweden | My blog: www.scsm.se
     
  • Tuesday, January 17, 2012 8:59 AM
     
     
    Sign In to Vote
    0
    will try tommorow - but I have run those cmdlets without errors before
     
  • Wednesday, January 18, 2012 8:14 AM
     
     
    Sign In to Vote
    0
    There are about 637 lines - a mix of completed (48) and "not started" (the rest) - but no errors
     
  • Tuesday, August 07, 2012 1:09 PM
     
     
    Sign In to Vote
    0

    View the Details of the MPSync job. Review each batch ID for the problem management pack in the MPSyncJob dialog box. In the MP Sync Job dialog box, click the Management Pack column name to sort the list according to management pack name. Find any management packs with Pending Association status. In the list of management packs, check to see if, in the later batch, the management pack status is listed as Associated, for example:

    • For Batch ID 136, Management Pack Microsoft.SystemCenter.ConfigurationManager is Pending Association.
    • For Batch ID 207, Management Pack Microsoft.SystemCenter.ConfigurationManager is Associated.

    This indicates the management pack is associated properly in batch 207, even though it ran into an error in batch 136. Because it recovered in batch 207, the management pack is correctly associated and the synchronization completed successfully.

    you can find more details here: http://technet.microsoft.com/en-us/library/hh542403.aspx