Cannot edit some task sequences
Hi,
My main production task sequences cannot be edited any more. I keep seeing the two errors listed below. Restarting the WMI service is not helping any more at this point. How can I go about getting these task sequences back to where I am able to edit them?
I already deleted about 20 or more lines but I still cannot edit these. Does anyone have some recommendations how to get past this issue? Increasing WMI memory buffers is not an option for our organization. I am able to edit smaller task sequences without
any problems.
An error occurred while storing the task sequence. Please see log file for more information.
An error occurred when loading the task sequence
Thanks,
Rob
June 20th, 2012 1:44pm
Is it a MDT based Task Sequence? If so then have a look here:
http://blogs.technet.com/b/configurationmgr/archive/2010/12/08/a-system-center-configuration-manager-2007-mdt-task-sequence-fails-with-quot-an-error-occurred-when-loading-the-task-sequence.aspx
Otherwise you might want to take a look at the TaskSequenceProvider.log for more information.My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
Free Windows Admin Tool Kit Click here and download it now
June 20th, 2012 2:43pm
This is an MDT task sequence. If shorter task sequences can be edited even though the larger production one cannot, should we even be considering to remove and reinstall the Configure ConfigMgr Integration feature? Our admins are not in favor of doing things
at random. There has to be a good reason in order for me to sell an operation like that. Their argument is that the smaller task sequences are working fine even when the larger task sequences are failing so why would you want to do anything like work on Configure
ConfigMgr Integration. The issue is the size of the task sequence has exceeded the limitation of the system.
My feeling is that I may need to rebuild these from a blank task sequence and split desktops and laptops into separate task sequences in order to make these shorter. Laptops require a ridiculous number of driver packages to get all of the hardware and features
working.
June 20th, 2012 3:45pm
To be sure you can take a look at the TaskSequenceProvider.log to see more information about the error.My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
Free Windows Admin Tool Kit Click here and download it now
June 20th, 2012 4:42pm
Hi,
Can you post a snippet from the smsprov.log and tasksequenceprovider.log, I'd love to take a look.
And take a look at this KB: http://support.microsoft.com/default.aspx?scid=kb;EN-US;2468097
Also I found some threads maybe help:
http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/8144f211-73f4-46cb-9615-b25bdeec04c0/
http://social.technet.microsoft.com/forums/en-US/configmgrsdk/thread/10622c88-68b9-449a-986c-36019c4eb661/
http://social.technet.microsoft.com/forums/en-US/configmgrosd/thread/7f2801ef-f6c2-4e57-a208-7cefbf89ac64/
Hope this will help.
Thanks
June 26th, 2012 5:39am
It turns out that we went ahead and increased the WMI Memory Buffers and after that, I am able to edit task sequences again.
Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2012 4:45pm