none
Unable to export Task Sequence with dependencies in SCCM 2012 R2 SP1 RRS feed

  • Question

  • Hi all,

    I try to export a task sequence. If I don't select dependencies, the TS is exported fine. However, when I choose "Export all task sequence dependencies", it fails with an error title "Object reference not set to an instance of an object." with details

    System.NullReferenceException
    Object reference not set to an instance of an object.


    Stack Trace:
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.Modeling.PrototypeImpl.TryGetPropertyValue(Object instance, String propertyName, Object& value)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.Modeling.EntityHandle.TryGetValue[T](String propName, T& value)
       at Microsoft.ConfigurationManagement.AdminConsole.MigrationAssistant.ExportPageControl.relatedWoker_DoWork(Object sender, DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

    Before SP1 upgrade this worked perfectly. I am experiencing this in two separate independent systems, so it may be something with the service pack.

    All task sequences work perfectly, and there are no references to unknown objects, packages, applications, whatsoever.

    Anyone else experiencing this? Any suggestions?


    • Edited by VRK13 Tuesday, August 25, 2015 11:23 AM Typo
    Tuesday, August 25, 2015 11:22 AM

Answers

  • Hi,

    yes I am seeing exactly the same thing with MDT intergrated task sequences in Configuration Manager 2012 R2 Sp1. If you remove the Apply OS Image step it should work.

    If I try a standard task sequence without MDT integration it works just fine.

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Tuesday, August 25, 2015 11:30 AM

All replies

  • Hi,

    yes I am seeing exactly the same thing with MDT intergrated task sequences in Configuration Manager 2012 R2 Sp1. If you remove the Apply OS Image step it should work.

    If I try a standard task sequence without MDT integration it works just fine.

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Tuesday, August 25, 2015 11:30 AM
  • Thanks Jörgen,

    With your help I managed to narrow it down. If I remove the checkmark "Use an unattended or Sysprep answer file..." from Apply OS step, the export goes fine.

    One of these systems has MDT installed, the other one does not. I'm guessing your MDT installation TS might have also this checkmark in that step?

    Hopefully this will be fixed, but at least this way I can export and document task sequences.

    Regards, Vesa

    • Proposed as answer by DriesWillemsBE Tuesday, December 15, 2015 1:11 PM
    Tuesday, August 25, 2015 11:42 AM
  • It will only be fixed if they know about the issue (which they may not). Thus you should open a support case with Microsoft Customer Support Services or file a bug on connect.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, August 25, 2015 1:06 PM
  • We are seeing this as well. Did anyone ever open a premier case?

    Will

    Thursday, October 15, 2015 7:13 PM
  • Is this setting in the Task Sequence?

    Friday, October 16, 2015 7:56 PM
  • Is this setting in the Task Sequence?

    Which setting are you talking about?

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

    Friday, October 16, 2015 9:37 PM
  • tanks it's work
    Tuesday, August 13, 2019 5:49 AM