Cannot edit job steps in SQL Server 2008 R2 Management Studio on 64 bit windows.

If you’re running SQL Server 2008 R2 and find that when you try to open a job steps for the second time you get the error

"Creating an instance of the OCM component with CLSID {E80*************}" from the IClassFactory failed due to following error:c001f011(Microsoft.sqlserver.ManagedDTS)"

then this is because there is a bug that is addressed by one of Microsoft’s service packs.

However, it does not always work. If like me you are running windows 7 professional 64 bit then you might have to register dts.dll for both 64 and 32 bit

Quit all SQL based applications (SSMS, BIDS etc), you dont have to stop sql service.

Go to Start -> All Programs -> Accessories and then right click on Command Prompt and choose run as administrator.

Now copy and past the following two lines in to the command window to register the DLL’s

This will register 64 bit DTS.dll
c:\windows\system32\regsvr32 "c:\Program Files\Microsoft SQL Server\100\DTS\Binn\dts.dll"

This will register 32 bit which is required as SSMS is a 32-bit application.
c:\windows\syswow64\regsvr32 "c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\dts.dll"

Start SSMS and test that you can open and re-open jobs steps.

Job done!

Dave

Advertisements

About davidbridge

I am a contractor for David Bridge Technology Limited specialising in database design and Web development using Microsoft technologies such as c#, MVC .net and SQL Server (full stack)
This entry was posted in Developer stuff, SQL Stuff and tagged , , , , , , . Bookmark the permalink.

3 Responses to Cannot edit job steps in SQL Server 2008 R2 Management Studio on 64 bit windows.

  1. Pingback: SSMS(SQL Server Management Studio) can not edit SQL Agent Job steps | Li Guoliang

  2. Homepage says:

    I was suggested this blog by my cousin. I am not positive whether
    this publish is written by him as no one else know such specific
    approximately my trouble. You’re incredible! Thank you!

  3. Steve says:

    Thanks – appears to have worked as described – was beginning to bug me 🙂

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s