Creating an instance of the COM component with CLSID

Posted by John Saunders on 8/4/2011 at 11:30 AM

Please say exactly which of the hotfix packages I should install to solve this. I'm guessing SQLServer2008R2_RTM_CU6_2489376_10_50_1765_x64, but don't know.

Posted by Jin LV on 5/8/2011 at 1:50 AM

thank you for this

http://support.microsoft.com/kb/2489376

Posted by buddylee17 on 3/18/2011 at 9:41 AM

Same problem. Problem occurs when editing jobs. SQL Server 2008 R2. Very annoying.

Posted by DanEPL on 3/3/2011 at 3:37 PM

With a new BizSpark copy of SQL2008 R2 downloaded from MSDN 17-Feb-2011 after install. Setting up a maintenance plan generates this error repeatedly. Have tried registering C:\Program Files\Microsoft SQL Server\100\DTS\binn directory as suggested but problem still exists - is there another workaround?

TITLE: Maintenance Plan Wizard Progress
------------------------------

Create maintenance plan failed.

------------------------------
ADDITIONAL INFORMATION:

Creating an instance of the COM component with CLSID {17BCA6E8-A95D-497E-B2F9-AF6AA475916F} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)

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

Creating an instance of the COM component with CLSID {17BCA6E8-A95D-497E-B2F9-AF6AA475916F} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)

------------------------------
BUTTONS:

OK
------------------------------

Posted by Chris Powers on 1/31/2011 at 1:13 PM

Also seeing this problem on x64.

Posted by Laurence Davis on 11/13/2010 at 12:27 AM

Hi
I have just installed CU4 and this problem persists.

Posted by Microsoft on 9/5/2010 at 5:58 PM

Hi guys,

We already ported fix of this issue to SQL Server 2008 and SQL Server 2008 R2 next CU. You can get your problem fixed after these CUs are released.

Sorry for the misleading messages and thanks a lot for all your feedbacks. Any concerns, please feel free to let us know.

Regards,
Xiaochen

Posted by Microsoft on 9/5/2010 at 5:58 PM

Posted by Jif128 on 8/18/2010 at 8:43 AM

Hi, what do you mean by next major SQL Server release?
it can get very annoying to have to close and open the management studio every time it happens.

Posted by WolfgangPurrer on 8/16/2010 at 8:23 AM

i have the same problem to => is there a workaround or hot fix available, otherwise i cannot create Maintenance Tasks

Posted by Doclane on 8/13/2010 at 7:09 AM

next major SQL Server release!!! SO you are saying that this will not be fixed in a CU or sp? Every DBA/Developer uses this interface to setup Jobs and it does not work!! PLEASE FIX THIS!!

Posted by Amol Mahajan on 8/12/2010 at 5:13 AM

I do have a same problem, occured when tried to add a new sql job.
Any workgroud from microsoft peoples? Its urgent, I have release on monday :(

Posted by Microsoft on 8/10/2010 at 12:59 AM

Hi Alex,

Thanks a lot for reporting this issue. We already fixed this issue and the fix will be shipped in next major SQL Server release. If you have any concern or suggestion, please feel free to let us know. Thanks a lot!

Regards,
Xiaochen

Posted by sqlGDBA on 7/23/2010 at 11:46 AM

Update: It temporarily resolved the problem on one instance(My server has 3 instances). I then proceeded to find every dts.dll on all disk drives(I found some more because of the multiple instances installed). I then proceeded to register each one of them in every location it existed. Again - works on one instance but not on the others...

Posted by sqlGDBA on 7/23/2010 at 11:18 AM

Same problem - and the fix helped. Thanks JayKusch !!

Posted by akissane on 7/21/2010 at 11:39 AM

Sorry. Should have noted I get this trying to view Job properties.

===================================

Creating an instance of the COM component with CLSID {AA40D1D6-CAEF-4A56-B9BB-D0D3DC976BA2} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)

------------------------------
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Package..ctor()
at Microsoft.DataTransformationServices.DTSExecUI.Controls.LoggingCtrl..ctor(IDTSExecViewManager treePanel)
at Microsoft.SqlServer.Management.SqlManagerUI.DTSJobSubSystemDefinition.InitializeControls()
at Microsoft.SqlServer.Management.SqlManagerUI.DTSJobSubSystemDefinition..ctor(CDataContainer dataContainer, IMessageBoxProvider messageProvider)
at Microsoft.SqlServer.Management.SqlManagerUI.JobStepSubSystems..ctor(CDataContainer dataContainer, JobStepData data, IMessageBoxProvider messageProvider)
at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.get_SubSystems()
at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.InitializeStepCombo()
at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.InitializeData()
at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.OnInitialization()
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.SetView(Int32 index, TreeNode node)
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.SelectCurrentNode()
at Microsoft.SqlServer.Management.SqlMgmt.ViewSwitcherControlsManager.InitializeUI(ViewSwitcherTreeView treeView, ISqlControlCollection viewsHolder, Panel rightPane)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm.InitializeForm(XmlDocument doc, IServiceProvider provider, ISqlControlCollection control)
at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm..ctor(ISqlControlCollection control, IServiceProvider provider)
at Microsoft.SqlServer.Management.SqlManagerUI.JobSteps.editJobStep_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

===================================

Creating an instance of the COM component with CLSID {AA40D1D6-CAEF-4A56-B9BB-D0D3DC976BA2} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)

------------------------------
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Package..ctor()

Posted by akissane on 7/21/2010 at 11:38 AM

I've also got this problem with SQL 2008 R2.
Restarting SSMS resolves--for a [sometimes very short] time.
Registering DLL does not help.

Posted by TatyanaS on 7/15/2010 at 1:39 PM

I have the same problem with creating maintenance plans in SQL 2008 R2, x64.
The fix helped.

1) But you need to register dll from the C:\Program Files (x86)\Microsoft SQL Server\100\DTS\binn folder in case of x64.
2) I got the following error while running regsvr32:

The module "dts.dll" was loaded but the call to DllRegisterServer failed with error code 0x80070005.

But even with this error, I was able to create a maintenance plan after that.

Posted by JJKusch on 7/7/2010 at 9:19 AM

FIXED ...

Traverse to the C:\Program Files\Microsoft SQL Server\100\DTS\binn directory and run the following from the command:

REGSVR32.EXE dts.dll

Posted by JJKusch on 7/7/2010 at 7:56 AM

Add me to the list of users leveraging SQL Server 2008 R2 and having the same error listed above.

Posted by shasta247 on 7/1/2010 at 1:47 PM

I have the same problem with SQL 2008 R2

Posted by Donkalypse on 11/9/2011 at 11:58 PM

The workaround posted by WolfgangPurrer will work. I felt the need to update this thread because it is the top result at Google and it isn't 100% clear.

1. You DO NOT need to install Microsoft's Cumulative Update 6 to fix this particular issue. This bug has nothing to do with the SQL Server, it is specific to the Management Studio application.
2. Close SMSE if it is running.
3. Run "REGSVR32.EXE dts.dll" from command line after changing directories to "%INSTALL DIRECTORY%\90\DTS\binn" folder. NOTE: %INSTALL DIRECTORY% is where SQL server installed. See the "GOTCHA" at the end of this post.
5. Start SSMS and you can now use the maintenance plan features.

GOTCHA: You must execute "REGSVR32.EXE dts.dll" from the SQL server installation directory where SSMS is installed. Look at the shortcut to see where SSMS is running. By default, the SQL Server 2008 R2 installer will drop files in both "C:\Program Files\Microsoft SQL Server\" and "C:\Program Files (x86)\Microsoft SQL Server" directories. Running "REGSVR32.EXE dts.dll" will execute successfully but WILL NOT NECESSARILY fix the problem if executed from the wrong working directory.

Posted by Xkryon on 6/1/2011 at 12:28 AM

REGSVR32.EXE dts.dll

This works like a charm!

Posted by Tjerk Drouen on 5/17/2011 at 1:02 AM

The workaround mentioned by WolfgangPurrer needs to be applied to the client that runs Microsoft SQL Server 2008 R2 Management Studio. Registering the COM DLL (dts.dll) patches the Microsoft SQL Server 2008 R2 Management Studio client not the SQL server.

Posted by Sethu Srinivasan on 3/31/2011 at 6:51 PM

Please update SQL 20008 R2 CU6 http://support.microsoft.com/kb/2489376
Let us know if you still have issues

Thanks
Sethu Srinivasan [MSFT]
SQL Server

Posted by WolfgangPurrer on 8/16/2010 at 8:27 AM

It turns out that the unregistered COM in dts.dll located in C:\Program Files\Microsoft SQL Server\90\DTS\binn. I ran the following from the command line:

REGSVR32.EXE dts.dll

in the aforementioned directory. source http://geekswithblogs.net/NutAndBolts/archive/2008/06/06/sql_server_2005_event_id_208.aspx

Creating an instance of the COM component with CLSID by Alex Chouklin