SSMS : Can no longer create or edit job steps - by AaronBertrand

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 557402 Comments
Status Closed Workarounds
Type Bug Repros 96
Opened 5/6/2010 9:11:13 AM
Duplicates 565461 Access Restriction Public


After the first time I create or edit a job step, I am no longer able to do so.  I get this error, which I have been able to reproduce successfully on two different Win7 x64 machines with RTM 2008 R2 tools:

TITLE: Microsoft SQL Server Management Studio

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)


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)


Sign in to post a comment.
Posted by Sethu Srinivasan on 4/16/2012 at 6:42 PM
Issue: When attempting to add a step to a SQL Server Job,if you see this issue "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)",


SQL Server 2008 R2 SP1 -

SQL Server 2008 SP3

Sethu Srinivasan [MSFT]
SQL Server
Posted by richard75013 on 4/12/2012 at 8:53 PM
Thanks for the update as to resolving the issue. This was really ticking me off having to restart SSMS so often when trying to edit a step on 1 of many servers. I am Running Win7 Professional x64 SP1 and SSMS 2008R2 RTM client tools accessing dedicated SQL 2008R2 SP1 servers. I updated my client tools with SP1 for R2 and all seams to be good.
Posted by tulip05 on 2/23/2012 at 2:41 PM
Hi I am still having the error, we have sql 2008 R2 SP1, i have to restart SSMS every time, please help.
Posted by Jeff Moden on 1/27/2012 at 12:28 PM
I'll ditto Martin's post immediately below. Having the exact same problem that he is using the same tools with a similar mix of SQL Servers.
Posted by Martin Bérubé on 11/25/2011 at 7:29 AM
Is there a fix for SQL Server 2005 ? We have multiple SQL servers, we're using SSMS 2008 R2 to manage them all and we still experience this issue with the 2005 servers ?

Posted by Microsoft on 11/21/2011 at 12:03 PM

This issue was resolved in the following releases

SQL Server 2008 R2 comulative update package 3:
Issue explanation:
Reference to comulative update package:

SQL Server 2008 R2 SP1:
(In the “more information” section you can find the following statement: “In addition to the fixes that are listed in this article, SQL Server 2008 R2 SP1 CTP contains the hotfixes that were included in Cumulative Update 1 through Cumulative Update 6 for SQL Server 2008 R2.”)

Now for SQL Server 2008 SP1, I can see that fix was done in cumulative update package 10
For some reason the cumulative update information page is not referencing this bug:, but I do encorage you to install it.

The SQL Server 2008 SP2 doesn't have this change, if you look into release notes:
you will see that it includes SQL Server SP1 Cumulative update 1 to 8 only

So if you would like to go with SP for SQL Server 2008, you will need to install SP3

Thank you
Alex Grach [MSFT]

Posted by Stephen Bialobok on 10/26/2011 at 9:02 AM
I get this error if I edit a SQL Agent step 5-10+ times in a single SSMS session. Restart of SSMS resolves the issue but is VERY inconvenient

Microsoft SQL Server Management Studio                        10.50.1600.1
Microsoft Analysis Services Client Tools                        10.50.1600.1
Microsoft Data Access Components (MDAC)                        3.86.3959
Microsoft MSXML                        2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer                        8.0.6001.18702
Microsoft .NET Framework                        2.0.50727.3623
Operating System                        5.2.3790
Posted by James Jiao on 10/9/2011 at 2:45 PM
@NishadJadhav Not practical in a corporate environment that's controlled by group policies. UAC is there for a reason and our sys admins wouldn't make exceptions just for this.
Posted by Nishad Jadhav on 8/11/2011 at 12:19 PM
Hi All,
I could fix this problem. Please check 'Workarounds' section.

Nishad Jadhav.
Posted by TheBoyHolty on 8/4/2011 at 2:15 AM
I'm using Microsoft SQL Server 2005 - 9.00.4053.00 (Intel X86) May 26 2009 14:24:20 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

And I got this issue when attempting to add a step to a SQL Server Job, "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)"

Posted by Nishad Jadhav on 8/3/2011 at 3:34 AM
A request to Microsoft- Please release hotfix/CU immediately to fix this bug. It appears many users like me are got stuck because of this issue.
Posted by Nik - Shahriar Nikkhah on 8/2/2011 at 6:56 AM
I am having the same issue
error ....
TITLE: Microsoft SQL Server Management Studio

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


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



We have SQL server: 2008R2 Ent. & OS: 2008R2 Ent.
Posted by RCRacer on 8/2/2011 at 2:29 AM
The really annoying thing about this bug is that it's indicating an error in DTS which is SSIS. But even when I edit a t-SQL job step and go nowhere near SSIS I still get this error. Even more annoying is this error never happens in SSMS 2005, and because of this I initially thought the problem was administering a SQL 2005 instance with SQL 2008 SSMS, as there will be a mismatch in the DTS/SSIS componets, but looking at these comments the problem happens regardlesss of SQL Server instance version.
Posted by Nishad Jadhav on 7/29/2011 at 2:59 AM
As Derek has mentioned, problem is still unresolved. I have installed latest CU (10.50.1797), but it did not work. And 'Workarounds' given here also did not help. Tried re-installing SSIS but no luck. even SSMS restart is not working for me. Error while modifying maintenance plan is -
The action you attempted to perform on a remote instance of SQL Server has failed because the action requires a SQL Server component that is not installed on the remote computer. To proceed, install SQL Server Management Tools on the remote computer, and then try again. For more information, see "How to: Install SQL Server (Setup)" in SQL Server Books Online. (ObjectExplorer)
MarcD has described here error while editing job.

Posted by Derek Robinson on 7/26/2011 at 4:31 AM
It's typical and regrettable that the MS team mark this as unreproducible. I've seen it many times, got it right now on my 2k8 box and everything is patched to date. A pro tester knows that not all factors that lead to a problem can be captured but I'd have serious words and retraining of any of my staff that claimed something as widely reported as this and outstanding for so long was just brushed away. The SSMS restart works but it hardly make me feel this is an industrial strength product after all these years.
Posted by MarcD on 7/19/2011 at 9:34 PM
Fresh Install
TITLE: Maintenance Plan Wizard Progress

Create maintenance plan failed.


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)


Posted by jkmelbs on 6/26/2011 at 7:00 PM
Just got the error

Microsoft SQL Server Management Studio                        10.50.1600.1
Microsoft Analysis Services Client Tools                        10.50.1600.1
Microsoft Data Access Components (MDAC)                        6.1.7600.16385
Microsoft MSXML                        3.0 5.0 6.0
Microsoft Internet Explorer                        8.0.7600.16385
Microsoft .NET Framework                        2.0.50727.4961
Operating System                        6.1.7600
Posted by DBAman8 on 6/23/2011 at 12:20 PM
Fresh install of SQL Server 2008 R2 on 64 bit server. After editing sql agent jobs several times, this displays the error. Come on guys - I can reproduce day after every install of the developer edition on 64 bit hardware. This non-reproduceable shows a serious lack of effort.
Posted by Crakdkorn on 6/3/2011 at 5:23 AM
I was unable to fix using the regsvr32 method but I am able to close and reopen ssms and that allows me to access the jobs twice without repeating the shutdown and startup... Running on VISTA 64 - 4 Gig RAM - R2 Tools only. Under a deadline and seriously slowed down by this issue. Started when I put a job on a 2008 (not R2) server without a lot of RAM that required heavy resources. Did not have this error prior to this push.
Posted by bl8t4nt1 on 5/26/2011 at 9:57 AM
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

Please. Fix. This.
Posted by rathor on 5/19/2011 at 9:33 AM
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

I get the error almost every time I try to view/edit a job step in SSMS.

It's been over a year, since this was opened. This is not a trivial/cosmetic issue.
Where's a SP? I'm a little nervous about applying CU's after reading that they might break database projects in VS2010... which I'm heavily dependent on (read that in regard to suggests to apply CU6 to fix the intellisense that VS2010 SP1 broke... ).

Posted by Elephant76 on 3/24/2011 at 9:47 AM
Hi, the problem is still there i am running on a Server2008R2 (Clustered) with SQL2008R2 CU6 (KB2485376) do we know when a Fix will be available?
Posted by allmhuran on 3/20/2011 at 10:06 PM
Here as well. It doesn't happen every time I edit a job (even if I do so repeatedly), but it does occasionally.

Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 <X64> (Build 3790: Service Pack 2)
Posted by Jaedon Tan on 3/16/2011 at 6:47 PM
I'm having this error on a new instance installed. I've tried almost everything on this page from registering the dll to repairing the shared features. None of these methods work. The only thing I didn't try is to upgrade it with a CU which I'm not comfortable with because they are people who have upgraded and complain it didn't fix the problem. I hope someone from Microsoft fix this permanently or at the very least provide a workaround(without restarting SSMS).
Posted by Kastanjehoeve on 3/10/2011 at 2:51 AM
Same issue. Running SQL on 2008R2 OS, solved the issue by setup/repair (shared features only).
Posted by Sean Shea-Schrier on 2/22/2011 at 9:12 AM

We are also experiencing this bug.

I see that the fix actually resides in CU3.

However, CU6 is now available.

I would feel much more comfortable applying these fixes via a fully tested SP1.

Does anyone know when SQL 2008 R2 SP1 will be released?

Is there a schedule for this?

Posted by Eli Gassert on 2/18/2011 at 6:17 AM
Confirmed as well. I can edit about 3 times then I get that error and have to restart SSMS.
Posted by NYDBA on 2/17/2011 at 10:20 AM
I can confirm that this bug still exists after applying CU5.
Posted by Sandra Mueller on 2/11/2011 at 6:25 AM
After installing CU5 I was able to create 2 jobs, in the middle of the third it blew up again.

Microsoft SQL Server 2008 R2 (RTM) - 10.50.1753.0 (X64)
    Dec 10 2010 22:13:00
    Copyright (c) Microsoft Corporation
    Enterprise Edition (64-bit) on Windows NT 6.0 <X64> (Build 6001: Service Pack 1) (VM)

DTS DLL -- DTS/Binn/dts.dll 2009.100.1753.0

No SSIS Install on this Server - all other services installed
Posted by AaronBertrand on 2/11/2011 at 5:55 AM
I've re-activated this bug because folks are still experiencing the issue after applying CU5.
Posted by Clément on 12/28/2010 at 1:58 AM

I encounter the issue.
The second time I try to edit a job step I get the error message.

a+, =)

Configuration :
Windows Server 2003 x64 SP2
SQL Server 10.50.1734 both 32 and 64 installed
32bits : DTS\Binn\dts.dll 2009.100.1734.0
64bits : DTS\Binn\dts.dll 2009.100.1734.0
Posted by Microsoft on 12/16/2010 at 3:45 AM
If you still encounter this issue with the latest patch, can you reply with the exact version of SQL server? Or can you provide the version of dts.dll (located at DTS\Binn folder)?

Posted by Ben Seaman on 12/7/2010 at 5:01 AM
I still have this problem in SQL 2008 R2 RTM CU4
Posted by Aaron Nelson on 12/1/2010 at 5:39 AM
I'm having the same problem but it's only after I: edit a job step > start a job via right-click > edit job via properties > edit job step > BOOM!

My only fix is to close down SSMS and open it again.
Posted by Dave_Mc on 11/10/2010 at 12:56 PM
Does anyone know whether this problem was fixed in CU4 (made available 10/18)? I quickly skimmed through the list of fixes and didn't find it.

Related question: In the response from Microsoft dated 7/9/10 below, it was said that the fix will be in "the next service release." Would that be the next CU, the next SP, or something else?

Posted by James12314909 on 10/20/2010 at 8:20 AM
I have installed CU3. It does not resolve the problem for me. The only difference I noticed is that when I double click on the job step to open it, then nothing happens. I have to click the edit button to get the error to display.

The only workaround seems to be to close management studio and reopen it. Then it lets me open the job up and edit it. The problem is that as time passes and I need to open a job again, then I get the error again. I then have to close management studio and reopen it again to edit the job.
Posted by lianvh on 10/15/2010 at 5:36 AM
Good Day,
I did restart the SQLS erverAgent, however I was still unable to edit any jobs in SQL Server 2008R2 64 Bit Enterprise Edition .
Posted by Melony.S on 9/16/2010 at 11:00 AM
I have the same problem. I applied a cu and it still doesn't allow me to create new job steps. Does anyone have a solution to this problem? The hotfix did not work. I identified the hotfix associated to my problem and the first job was created however the second received the same error.
Posted by ixy on 9/10/2010 at 11:46 AM
I applied SQL2008R2 Cu3 on 08/19/2010, have not received this error since.
Posted by geraint_e on 8/18/2010 at 7:21 AM
Looks like this may be fixed with a hotfix available from here:
Posted by ob213 on 8/13/2010 at 8:32 AM
When is the next service release?
Posted by Jane2006 on 8/4/2010 at 12:08 PM
When will microsoft release the fix? It seems it happens more frequently every day or maybe it has reached a point that really drive me mad. I have used SQL server since 7 and this is definitely the worst bug that affects the productivity.

Posted by sdgsdgsdfgsdg on 7/21/2010 at 1:54 AM
I'm getting this on and off now, too. It's getting to be a real pain as I can't edit my jobs most of the time.

I'm running Windows 7 on my 64 bit PC, and the DB is SQL Server 2008 R2 (32 bit), but it also did it when I fired up SSMS on the DB server itself over remote desktop.

When is the fix being released please?!
Posted by StormRider01 on 7/14/2010 at 9:07 AM
Any chance of a hotfix?
Does the fix only require an update to SSMS, or will the target SQL Server engines require an update as well?
Posted by Microsoft on 7/9/2010 at 7:38 AM
Here is an update from SSIS team,

a. We have identified the root cause
b. A fix is ready and we are currently testing the fix
c. You can expect the fix in the next service release

We believe the problem affects SQL Server 2005, 2008 and 2008 R2. There is no easy work around.

Wenjin Zhang[MSFT]
SQL Server SSIS team
Posted by on 7/7/2010 at 12:35 PM
I am having the same issue too...Any fix from MICROSOFT
Posted by davidP20090614 on 7/1/2010 at 8:04 AM
Applied hotfix in hopes this was addressed but no improvement in the problem on 32 bit platform.

Microsoft SQL Server Management Studio                        10.50.1720.0
Posted by Robert Heinig II on 7/1/2010 at 2:12 AM
I think x64 has no relevance for this issue. The x86 SSMS 2008 R2 has the same problems, whether connecting to SQL 2008 R2 x64, SQL 2005 x86, or SQL 2008 non-R2 x64. Interestingly, the problem does not occur for a connection to SQL 2000 - even in the same SSMS process that is exhibiting the problem on another connection.

The PC in question is fully patched to company standards (which essentially pushes everything through our WSUS unmonitored), so AndrewTheodore's success case might be a fluke - or there's a fix M$ offers for W7 but not for Server 2008 R2 or Vista.

Let's hope the guys supposed to work on this return from their vacations soon.
Posted by BigErn782 on 6/28/2010 at 9:43 AM
I was having this issue but it has seemed to have gone away. I'm assuming that there was some Windows Update that had been applied to my machine that caused this to get fixed - which update, I'm not sure. My OS - Windows 7 x64 Version 6.7.7600 and I have SQL 2008 R2 SSMS Version 10.50.1600.1. It has been fixed now for about a month.
Posted by Joe Fedak on 6/28/2010 at 6:39 AM
I'm having the same issue. Win7 RTM 64 with SQL 2008 R2.
Posted by Toni2 on 6/28/2010 at 5:29 AM
I started having this problem last week with SSMS 2008 on my 32-bit Win XP sp3 workstation connecting to any SQL instances. I can create jobs but just not edit them.

I uninstalled SSMS 2008, reinstalled but same issue. Then I uninstalled SSMS 2008 and installed SSMS 2008 R2 but that didn't fix the issue either.

Any progress on finding the issue?
Posted by Jane2006 on 6/25/2010 at 11:28 AM
I could report that I have exactly the same issue. I am connecting from SSMS installed on my local 32-bit machines to a SQL2008 R2 64-bit enterprise server. I never had this issue with SQL2008 SP1.
Posted by M. Clark on 6/25/2010 at 9:45 AM
We are experiencing this on a new SQL 2008 R2 Enterprise install on Windows 2008 R2 Datacenter. I am using Windows 7 32-bit to run Management Studio. My original SQL 2008 R2 install had the DB Engine, SSIS, and some of the tools. I then added the SSRS after the fact. I did not notice the errors until after I had added SSRS, but then again I also had not tried to edit job steps very much until after adding SSRS.
Posted by JHeim99 on 6/21/2010 at 1:54 PM
....just aren't cutting it... :)
Posted by JHeim99 on 6/21/2010 at 1:53 PM
For the record, we have the problem too....2008R2 etc....

Any ETA on a fix?! Lots of users having this. Multiple restarts just are cutting it.
Posted by Wenjin Zhang on 6/21/2010 at 9:03 AM
First, did anyone run into this issue on 32 bit Windows?

If you are running 64 bit machine, to register dts.dll for 64 abd 32 bit, you may run the following,

c:\windows\system32\regsvr32 "c:\Program Files\Microsoft SQL Server\100\DTS\Binn\dts.dll"
c:\windows\syswow64\regsvr32 "c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\dts.dll"

The first command registers 64 bit DTS.dll, and the second command registers 32 bit. SSMS is 32-bit.


Posted by Robert Heinig II on 6/17/2010 at 5:21 AM
@richard_deeming - sorry for not searching the forum properly, you were indeed the first to suggest the dll registration here.

To MS: To reproduce, a fresh out-of-the-box install of Server 2008 R2 Standard x64, let it autoupdate until stable, then SQL 2008 R2 Standard x64 including Default Instance, Tools and SSIS should be sufficient. Mine has SSRS and SSAS as well, but I don't think these are relevant. My installation has seen no other software except z-zip, the sysinternals suite, and the postgres ODBC driver x64, again, I think none of these have an influence. The job steps in question do *not* need to be of type SSIS Package, in fact, I have had the issue right after New Job, Steps->New...
Posted by Robert Heinig II on 6/17/2010 at 4:25 AM
@richard_deeming - true. My luck ran out several hours after my post, but after that I was back to 0-1 job step edits per SSMS launch. Creating new job steps felt like having an even lower success chance.

I'm still positive the DLL is involved, as the CLSID displayed belongs to it; and I'm >50% confident it's related to x64/x86 issues. Previous comments did often state x64, but no-one explicitly mentioned having x32 OR or SQL. So, colleagues, can anyone shed some insight on whether the problem occurs on x32 Software? What about SSMS on 32-Bit connecting to 64-bit SQL Server? What about SSMS on x64 connecting to a 32-Bit SQL instance?

In the mean time, I recommend maintining agent jobs as T-SQL scripts. Once you have -and keep- the scripts, then maintaining those and just hitting F5 to update the jobs themselves is easy enough. Mind you - the SSMS generated scripts are defective. You don't need to fix the script bug if you add a job deletion statement, but then you lose history each time. Hint: The step existence test uses a literal GUID where the correct one is available in a variable anyway...
Posted by Richard Deeming on 6/16/2010 at 4:51 AM
Registering the 32-bit DTS.dll with the 64-bit version of regsvr32 didn't make any difference for me; after editing a step, closing the dialog and waiting for a few minutes, attempting to edit the same step results in the same error message.

I already had entries under the win32 and win64 keys of the typelib entry. Re-registering the dll didn't seem to make any difference to the entries.
Posted by Robert Heinig II on 6/16/2010 at 2:44 AM
This seems to be a regression of
I can confirm that SQL 2008 R2 Standard x64 exhibits this on Server 2008 R2 x64, but SQL 2008 x64 SP1 does not (identical OS and hardware).

From comments so far I'd guess this may have a correlation to an x64 host OS.

The CSLID the error names belongs to a "Package Neutral Class" from InprocServer32="C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTS.dll". I think the 32 in InprocServer32 is just a naming thing, and the location means the DLL is x64. SMSS, however, is 32-bit (wooo-hooo, this in 2010! embarrassing!). There's another DTS.dll in ProgramFiles(x86). Registering this (don't forget to turn off UAC before doing so) fixes the problem for me - even while leaving SMSS open. There's several texts out there recommending registering that DLL from the 32-Bit folders, but I don't trust the situation. M$ must have had a reason to deliver a different insallation. Plus, I have been able to execute a wide variety of SQL Agent Jobs - 64-bit dtexec, 32-bit dtexec, using the 32-bit Jet4 engine, both OLEDB and ODBC, some pulling unusual tricks. All successful. I have not yet re-tested all of them to see whether this regsvr32 call breaks any of them.

Start, cmd, Ctrl-Shift-Enter, Yes, regsvr32 "C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\DTS.dll"

So, please, someone confirm my findings and, should this break no other stuff, post it as workaround.

Miscellaneous: The steps where SSMS fails do *not* need to be of type SSIS Package for the bug to hit or for my "fix" to help. Also, the 32-bit DTS.dll will *not* turn up as Server for the CLSID the error shows, but it adds a win32 entry unter the appropriate typelib {FAD11436-A84C-4720-8D20-B07FE84FDE74} - a good omen.

P.S.: M$, You are forgiven, if only for finally making the Report Manager work in serious browsers!
Posted by katie77 on 6/15/2010 at 8:26 AM
Just for record. I am getting this error too. Connecting from Windows 7 64 bit, through SSMS 2008 R2 to SQL server 2008
Posted by David Wimbush on 6/15/2010 at 1:45 AM
For the record, I'mm getting this too. Connecting from Win XP x64, SSMS 2008 R2 Dev Edition RTM (10.50.1600) to SQL 2005 (9.0.4035).
Posted by Sethu [MSFT] on 6/10/2010 at 11:52 AM
Hello Aaron,

Our SSIS dev team is looking at this issue. We shall keep you posted with our investigation

Sethu Srinivasan[MSFT]
SQL Server
Posted by Atilla gunhan on 6/7/2010 at 11:18 PM
if your server is not selected as application server and dcom is not activated (DTS also must be activated) then you get this error i suppose
Posted by CTS_Dba on 6/7/2010 at 4:49 PM
I recently upgraded to SSMS win 2008 R2 and can reproduce this ..happens for both 2005 (9.0.4053) & 2008 (10.0.2531).
can't edit existing jobs, job steps.
here's the error

TITLE: Microsoft SQL Server Management Studio

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)


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)



Posted by rtorrone on 6/4/2010 at 1:13 PM

I get this in SSMS 2008 R2 (not CTP) on Win 2008 R2 and on Win XP SP3.

Hope it helps. What a pain.

Rich Torrone
Posted by sporoy on 5/30/2010 at 3:56 AM
I ca repro this issue like this: Restart SSMS R2, open a job step, close the step, and try to edit another job step immediately after, need a solution, thanks
Posted by Men Peng on 5/27/2010 at 12:40 AM
I am also having this issue with SSMS 2008 R2 running on Windows 7 Enterprise x64 editing job step from SQL Server 2005 Standard x64 SP3 running on VMware. It seems that the first time I can edit the job step but after a while this error comes out.
Posted by GFBaevich on 5/24/2010 at 12:53 PM
I am experiencing the same issue. I have installed 64-bit SQL Server 2008 R2 Enterprise Edition on a 64-bit Windows 2008 standard edition server. When creating a new job or editing an existing job the error described in this connect article occurs. If I restart SSMS I work normally again. After a few minutes of working with jobs in SSMS the problem re-appears.
Posted by PegB on 5/24/2010 at 6:37 AM
Just installed CU1 for SQL 2008 R2 in the vain hope it'd include a fix for this and still getting this error when I edit job steps. Seems to occur after about the 4th or 5th time I open and close the job step properties. Only workaround is to re-start SSMS.

I get the same error on 2 machines - 1 is SQL 2008 R2 RTM on Windows Server 2008 R2, otheris SQL 2008 R2 CU1 on Windows Server 2003.

The job step can be anything - TSQL, SSIS, or Powershell for example.
Posted by Glenn A. Berry on 5/20/2010 at 7:30 PM
I have seen this same error with x64 SQL Server 2008 R2 (Build 1702) SSMS on Windows 2008 Server trying to create Agent job steps against two different SQL Server 2008 SP1 instances and a SQL Server 2005 SP3 instance.
Posted by AaronBertrand on 5/20/2010 at 6:24 PM
Sethu, please try the repro against a 2008 SP1 server.

Also this is in a VMWare Fusion VM (sorry, I'm a Mac guy) so I do not believe I can create a Hyper-V compatible VM for you.
Posted by AaronBertrand on 5/20/2010 at 6:23 PM
Yep, the workaround posted by Ewan1 is only temporary, and only works because of restarting SSMS (which you can also do to have temporary relief without re-registering DTS.dll).
Posted by davidP20090614 on 5/20/2010 at 8:40 AM
I'm getting this, too. Just installed R2.
Posted by Rolf Tesmer (Mr. Fox SQL) on 5/19/2010 at 3:51 AM
I am also getting this issue on Win 2008 Std Ed x64 on SQL 2008 Std Ed x64 (RTM). The suggested fix of running regsvr for the DTS.DLL (x86/x64) does not work. The only fix I have found is to restart SSMS. Not a showstopper but annoying.
Posted by ixy on 5/17/2010 at 3:22 PM
Work around: registering DTS.dll didn't work.

I am only receiving this error when using SSMS R2 editing jobs on SQL Server 2008 sp1 servers.
Posted by ixy on 5/14/2010 at 2:10 PM
I am getting this error randomly but mostly when I am editing an existing SQL Agent jobs in SSMS.

OS: Win7 Ultimate
SQL: SQL 2008 R2 Dev 32 bit.

Posted by Richard Deeming on 5/14/2010 at 6:09 AM
I've just duplicated this on another computer: Windows 2003 Server x64, clean install of SQL 2008 R2 Express, using 2K8R2 SSMS to edit a job on a 2005 Workgroup instance.
Posted by Richard Deeming on 5/14/2010 at 5:46 AM
Exactly the same error here - Win7 Enterprise x64, SQL 2008 R2 Dev (upgraded from 2008 Dev).

Restarting SSMS temporarily fixes the problem, but after a couple of minutes it comes back.

I've tried re-registering both the 32 and 64 bit versions of DTS.dll, which has had no effect.
Posted by Sethu Srinivasan on 5/12/2010 at 10:29 AM
Job step dialog's SSIS package properties editing control references SSIS components. We always had that dependency. Let me check if Job editing dialog has that dependency as well.

There is a tool to capture your system as VHD so that later it can be converted to VM in HyperV.

If it is possible to share your VHD, I can take a look at current state of the VM , it would help us narrow down the rootcause.

Posted by AaronBertrand on 5/12/2010 at 5:32 AM
Sethu, I installed the engine as well (just not other server components like SSIS). Is it possible the job editor now relies on SSIS? Or some of the client components that I didn't install? I'm digging up the log files and will post them shortly.
Posted by Sethu [MSFT] on 5/11/2010 at 4:42 PM
Hello Aaron,
I tried following the repro scenario you had mentioned. I could not reproduce this issue on my test machine
My scenario:
OS: Win7 x64 ENU RTM
SQL: SQL 2008 R2 RTM tools only installation
Launched ssms and connected to SQL 2005 Server (Microsoft SQL Server 2005 - 9.00.4053.00 (Intel X86) )
Created new job, edited new job - I dont see issues like the one in your scenario.

May be I am missing something in repro sequence. please advise

Also, Can we take a look setup logs? We need to check if DTS.dll and related components are registered. Usually COM errors like these occur when COM registration during setup failed for some reason / registry key entries were modified by some other app

Setup logs are available at :\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\...

Posted by Amy [MSFT] on 5/10/2010 at 1:35 PM
Thank you for reporting this issue; we will investigate and get back to you.


Amy Lewis