Cant create task sequence ERROR
When i try and create a TS i get the below error in the AdminUI.log? Has anyone come across this before? [6][10/10/2012 12:30:58] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details: instance of SMS_ExtendedStatus { Description = "Failed to call SMS_TaskSequence::SaveToXml due to error 80041013."; ErrorCode = 1078462229; File = "c:\\qfe\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\ssptspackage.cpp"; Line = 2932; Operation = "ExecMethod"; ParameterInfo = "SMS_TaskSequencePackage"; ProviderName = "WinMgmt"; StatusCode = 2147749889; }; \r\n [6][10/10/2012 12:30:58] :Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe ConfigMgr Provider reported an error.\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters) at Microsoft.ConfigurationManagement.AdminConsole.OsdCommon.OsdUtilities.SetSequence(ConnectionManagerBase connectionManager, IResultObject taskSequencePackage, IResultObject taskSequence)\r\nConfigMgr Error Object: instance of SMS_ExtendedStatus { Description = "Failed to call SMS_TaskSequence::SaveToXml due to error 80041013."; ErrorCode = 1078462229; File = "c:\\qfe\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\ssptspackage.cpp"; Line = 2932; Operation = "ExecMethod"; ParameterInfo = "SMS_TaskSequencePackage"; ProviderName = "WinMgmt"; StatusCode = 2147749889; }; \r\nSystem.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details: instance of SMS_ExtendedStatus { Description = "Failed to call SMS_TaskSequence::SaveToXml due to error 80041013."; ErrorCode = 1078462229; File = "c:\\qfe\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\ssptspackage.cpp"; Line = 2932; Operation = "ExecMethod"; ParameterInfo = "SMS_TaskSequencePackage"; ProviderName = "WinMgmt"; StatusCode = 2147749889; }; \r\nKev :)
October 10th, 2012 7:38am

Hi Kev I have seen this before, in the specific circumstances we were experiencing it due to resource issues on the site servers and the task sequence was a particularly large task sequence. The issue was usually experienced from remote console connections. What we did to resolve the issue was to increase the memoryperhost limit in WMI on the site server, we also addressed resource issues on the site server including migrating the site database to a dedicated SQL server. to increase the memoryperhost setting in WMI refer to following for reference: http://blogs.technet.com/b/askperf/archive/2008/09/16/memory-and-handle-quotas-in-the-wmi-provider-service.aspx Kriss Milne | MCSE *Please click 'Vote As Helpful' or 'Mark as Answer' if a post has helped you or answered your question*
Free Windows Admin Tool Kit Click here and download it now
October 12th, 2012 8:02am

Hi Kriss, I hope you are well. I have already increased the WMI allocation in the past as we were having problems with the provider running out of memory. The Provider and the SQL database are on a dedicated server together. I think it maybe a WMI issue..Kev :)
October 12th, 2012 9:42am

Sorry i am wrong, The provider is on the central server and the SQL database is on another server which has other database instances on. I have increased the WMI memory allocation on the servers in the past I cant just restart WMI on the database server as its has other databases on..Kev :)
Free Windows Admin Tool Kit Click here and download it now
October 12th, 2012 9:51am

Or do you know what affect restarting WMI will have if any on the databases ie will it affect operations? Kev :)
October 12th, 2012 10:04am

Hi Kev If I'm understanding you correctly, the database is on a separate database server. I wouldn't think that you would need to restart the WMI Service on the database server. However restarting the WMI Service on the site server may alleviate the problem you are experiencing with the task sequence if it is WMI causing the problem. a quick FYI, restarting the SCCM Site Server almost always resolved our task sequence errors as an immediate work around.Kriss Milne | MCSE *Please click 'Vote As Helpful' or 'Mark as Answer' if a post has helped you or answered your question*
Free Windows Admin Tool Kit Click here and download it now
October 12th, 2012 8:54pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics