locked
Can't Stop Data Gathering to complete Migration RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I get the error in the picture when I try to Stop Gathering Data.  I have no migration jobs running the last gathering process was hours ago.  Am I missing something?  I'm doing a migration from 2007 to 2012.  I am currently sharing Distribution Points. 


    Wednesday, December 12, 2012 1:20 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    What does the logfile tell (mig*.log)?

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, December 12, 2012 6:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    What does the logfile tell (mig*.log)?

    Torsten Meringer | http://www.mssccmfaq.de

    I found this to be interesting-  The logs below keep repeating about every hour

    [MigrationManager]: Start two step scheduling for MIG_Job SMS_MIGRATION_MANAGER 12/13/2012 3:00:50 PM 2104 (0x0838)
    [MigrationManager]:         Step 1. Query the schedule items that was running or requested to start immediately ... SMS_MIGRATION_MANAGER 12/13/2012 3:00:50 PM 2104 (0x0838)
    [MigrationManager]:         Step 2. Query the first item in order of DateNextRun ... SMS_MIGRATION_MANAGER 12/13/2012 3:00:50 PM 2104 (0x0838)
    [MigrationManager]:                 The item MIG_Job 16777221 has finished running. SMS_MIGRATION_MANAGER 12/13/2012 3:00:50 PM 2104 (0x0838)
    [MigrationManager]: End two step scheduling for MIG_Job SMS_MIGRATION_MANAGER 12/13/2012 3:00:50 PM 2104 (0x0838)
    [MigMCtrl]: the workitem queue is full! SMS_MIGRATION_MANAGER 12/13/2012 3:00:50 PM 2104 (0x0838)
    [MigMCtrl]: WAIT 3 event(s) for 60 minute(s) and 0 second(s). SMS_MIGRATION_MANAGER 12/13/2012 3:00:50 PM 2104 (0x0838)


    What is weird is that I looked and MIG_Job 16777221 it is an object migration job of one driver in which the the driver was actually skipped.  It clearly shows in the SCCM Console that the job completed.  There have been several other migration jobs run after this one that completed as well.

    Yet in the mig*.log it just keeps repeating the above section every hour.

    Thursday, December 13, 2012 8:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have the exact same problem and I can't figure it out. Did you find a solution?
    Tuesday, February 12, 2013 7:59 AM