none
Configuration Manager 1606 - TS Import Issues RRS feed

  • Question

  • Hi All,  

    Testing out Current Branch 1606, so just did a fresh build out in a lab environment.  Previously I was able to import my 20+ task sequences without issue back into the Environment on 1511/1602, but now when I try and import these task sequences I get the following error:

    POWERSHELL:

    Import-CMTaskSequence : Object reference not set to an instance of an object.
    At line:1 char:5
    +     Import-CMTaskSequence -ImportFilePath "$TSPath" -Verbose
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [Import-CMTaskSequence], NullReferenceException
        + FullyQualifiedErrorId : System.NullReferenceException,Microsoft.ConfigurationManagement.Cmdlets.Osd.Commands.ImportTaskSequenceCommand

    GUI:

    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.WmiUtility.WriteEmbedded(WmiConnection connection, Prototype type, ManagementBaseObject instance, Object obj)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiConnection.AttachEmbedded(Object embedded)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.<>c__DisplayClass1e.<ToWmiObjectValue>b__1c(Object v)
       at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
       at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
       at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.ToWmiObjectValue(WmiConnection connection, Object value, Boolean isArray)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.ToWmiValue(WmiConnection connection, PropertyData item, Object value)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.WriteEmbedded(WmiConnection connection, Prototype type, ManagementBaseObject instance, Object obj)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiConnection.AttachEmbedded(Object embedded)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.<>c__DisplayClass1e.<ToWmiObjectValue>b__1c(Object v)
       at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
       at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
       at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.ToWmiObjectValue(WmiConnection connection, Object value, Boolean isArray)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.ToWmiValue(WmiConnection connection, PropertyData item, Object value)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.WriteEmbedded(WmiConnection connection, Prototype type, ManagementBaseObject instance, Object obj)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiConnection.AttachEmbedded(Object embedded)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.<>c__DisplayClass1e.<ToWmiObjectValue>b__1c(Object v)
       at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
       at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
       at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.ToWmiObjectValue(WmiConnection connection, Object value, Boolean isArray)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.ToWmiValue(WmiConnection connection, PropertyData item, Object value)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.WriteEmbedded(WmiConnection connection, Prototype type, ManagementBaseObject instance, Object obj)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiConnection.AttachEmbedded(Object embedded)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.<>c__DisplayClass1e.<ToWmiObjectValue>b__1c(Object v)
       at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
       at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
       at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.ToWmiObjectValue(WmiConnection connection, Object value, Boolean isArray)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.ToWmiValue(WmiConnection connection, PropertyData item, Object value)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.WriteEmbedded(WmiConnection connection, Prototype type, ManagementBaseObject instance, Object obj)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiConnection.AttachEmbedded(Object embedded)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.ToWmiObjectValue(WmiConnection connection, Object value, Boolean isArray)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.ToWmiValue(WmiConnection connection, PropertyData item, Object value)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiUtility.WriteInputParameters(WmiConnection connection, ManagementBaseObject parameters, Prototype prototype, Object method)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiConnection.TryExecuteMethod(IObjectContext context, Object method, Object target, IObjectSession cache)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.ObjectLibrary`1.ExecuteMethod(IObjectContext context, IObjectSession cache, Object method, Object target)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.ObjectMethod`1.Execute(IObjectContext context, IObjectSession cache)
       at Microsoft.ConfigurationManagement.Migration.ConfigMgr2012.SMS_TaskSequencePackage.SetSequence(IObjectContext context, SMS_TaskSequencePackage TaskSequencePackage, SMS_TaskSequence TaskSequence, String& SavedTaskSequencePackagePath)
       at Microsoft.ConfigurationManagement.Migration.ConfigMgr2012.SoftwareDistribution.TaskSequenceLibrary.PutInstance(ObjectHandle value, ObjectContext context)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.ObjectContext.SaveChanges(IEnumerable`1 values)
       at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.ImportRequest.Submit()
       at Microsoft.ConfigurationManagement.AdminConsole.MigrationAssistant.FileContentPageControl.PostApply(BackgroundWorker worker, DoWorkEventArgs e)
       at Microsoft.ConfigurationManagement.AdminConsole.SmsWizardPage.PostApply(BackgroundWorker worker, DoWorkEventArgs e)
       at Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.PostApply(SmsWizardPage page, BackgroundWorker worker, DoWorkEventArgs e)
       at Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.PostApply(BackgroundWorker worker, DoWorkEventArgs e)
       at Microsoft.ConfigurationManagement.AdminConsole.ProgressPage.backgroundWorkerPostApply_DoWork(Object sender, DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

    -------------------------------


    Is anybody else seeing this error/issue?

    I'm building out a Temporary 1602 CAS/AD Server to test the import to see if its a 1606 issue specifically..

    UPDATE:

    As an update as well, I built up another temp environment to test imports:
    1511 Fresh Install - Import Works, no errors.
    1511 --> 1602 Upgrade - Import Works, no errors.
    1602-->1606 - Import Fails as per First Post in this thread, definitely a 1606 Specific issue...

    1604 CMDLet Library Update had no effect either.  Ruled out Powershell 5 as the cause as well (No v5 in temp environment.


    Hopefully addressed in a new CMDLET Library Update or Hotfix...




    • Edited by aleekoo Tuesday, July 26, 2016 6:43 AM
    Tuesday, July 26, 2016 12:21 AM

Answers

All replies

  • What happens if you import using the console?

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

    Tuesday, July 26, 2016 3:27 AM
  • Hi Jason,

    Cheers for the reply.

    the POWERSHELL Segment was via the Import-TaskSequence CMDLET.

    The GUI Section was when I tried the process through the GUI.

    I also tried both with content and without..

    As an update as well, I built up another temp environment to test imports:
    1511 Fresh Install - Import Works, no errors.
    1511 --> 1602 Upgrade - Import Works, no errors.

    Testing 1602 --> 1606 Now and will test to see if its definitely 1606..

    UPDATE:
    1602-->1606 - Import Fails as per First Post in this thread, definitely a 1606 Specific issue...

    Hopefully addressed in a new CMDLET Library Update or Hotfix...

    • Edited by aleekoo Tuesday, July 26, 2016 6:38 AM
    Tuesday, July 26, 2016 4:15 AM
  • I have exactly the same problem on two diferent labs and one productive environment...
    Tuesday, July 26, 2016 10:49 AM
  • I've just pinged the product group ...

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

    Tuesday, July 26, 2016 12:18 PM
    Moderator
  • Can you please file a bug on Connect (http://connect.microsoft.com/ConfigurationManagervnext) and attach a sample task sequence that you're having problems importing so we can try to reproduce this internally?

    Thanks!


    Check out my Configuration Manager blog at http://aka.ms/ameltzer

    Tuesday, July 26, 2016 5:40 PM
  • Tuesday, July 26, 2016 6:13 PM
  • Can you please share the Admin UI log and the SMSPROV log?

    Also, any details on your task sequence steps?

    Tuesday, July 26, 2016 9:39 PM
  • Hi,

    i added the logs to the Connect Case as attachment.

    Any Details to the Task Sequence Steps you can see in the unzipped TS Zip in the XML Files under "SMS_TaskSequencePackage\TDE00009"

    Nothing Special here. I exported the TS without any dependent packages. I imported this TS under SCCM 1602 without any Problems. Now under 1606 i exported this TS and tried to import it again.

     


    • Proposed as answer by Michael-CM Tuesday, July 26, 2016 10:14 PM
    • Unproposed as answer by Michael-CM Tuesday, July 26, 2016 10:14 PM
    • Edited by Michael-CM Tuesday, July 26, 2016 10:14 PM
    Tuesday, July 26, 2016 10:13 PM
  • Can you please share the Admin UI log and the SMSPROV log?

    Also, any details on your task sequence steps?

    I've Posted the Admin UI Log, the SMSPROV Log and a Task Sequence that is failing.

    I've also attached a CSV that details the entire Task Sequence as well. 

    In the same Connect Case as above.

    I thought this might have been an Answer File Regression (2012 R2 SP1 CU1 had an issue with exporting Task Sequences).  But most of my Build and Capture Task Sequences Import correctly and one of them has an Answer File Set, so don't believe its that issue.
    Tuesday, July 26, 2016 10:47 PM
  • I am having trouble accessing Connect right now. So, for the moment, can you please let me know if you task sequence has a 'Install Software Updates' step? If so, can you please try removing it and see if you can successfully export/import the task sequence?

    We have a suspicion that the 'Install Software Updates' step is the culprit, and I want to verify that that is the case that you are seeing.

    Wednesday, July 27, 2016 12:18 AM
  • I can confirm that every Task Sequence that has an "Install Software Updates" Step Fails and every Task Sequence that doesn't imports Successfully. (This is with a pool of 20 Task Sequences).

    7 Successful, 13 Failed out of that Pool.
    Wednesday, July 27, 2016 12:47 AM
  • Thanks for confirming that.

    We believe we know what the root the issue is. If you urgently need a fix, please contact support.

    Thanks again for reporting the issue and helping us finding the root cause.

    • Proposed as answer by Michael-CM Wednesday, July 27, 2016 6:26 AM
    Wednesday, July 27, 2016 3:28 AM
  • Thanks for confirming that issue.

    The Workarround is to delete the "SMS_TaskSequence_InstallUpdateAction" Step(s) from the object.xml inside the Task Sequence ZIP.

    After that the Import is working.

    Wednesday, July 27, 2016 6:26 AM
  • THANKS!!!

    I had the same problem. Luckily your workaround worked for me as well.

    I hope that there will be a fix for this bug in the next hotfix update for 1606 :-D

    Thanks again.


    Thomas Forsmark Soerensen

    Tuesday, August 30, 2016 12:41 PM