C001f011 ms sql server ошибка

SQL Agent job steps can be of several types: if you choose a T-SQL step type, you should just be able to put your T-SQL script content in the job step detail/content directly. This should be no different for a script involving a cursor, or any other T-SQL.

A Cursor is not a persistent database object like a stored procedure that you just Call once you’ve created it; a cursor is a temporary object that is created, used and destroyed in the context of a single SQL connection. typically something like this:

DECLARE XXX CURSOR 
FOR
SELECT Something
FROM Somewhere

OPEN XXX

FETCH NEXT FROM XXX
INTO @A

WHILE @@FETCH_STATUS = 0
BEGIN

    --Do something here

    FETCH NEXT FROM XXX
    INTO @A
END 

CLOSE XXX
DEALLOCATE XXX

If you have a T-SQL script that uses a cursor, then you can simply copy the entire T-SQL script into a SQL Agent job.

If this is not working, please provide more information as to what you’ve tried, what type of problem you encountered, the detail of any error messages you received, etc.

Update after SSMS Error detail provided:

I have found that in SSMS 2008 R2 (at least on a 64-bit machine), the SQL Agent Job Editing UI sometimes starts throwing errors like the one you just provided. When this happens, you sometimes get an error, or sometimes when you double-click on a job step to be edited, nothing happens.

In my experience, these issues simply go away if you complete close SSMS (close all jobs you had open, close activity monitor, close ssms), start it up again, and go straight to the job you wanted to edit.

Try doing this, and if you still have a problem, please describe the exact steps you are taking, the size of your T-SQL script, and any more information you can think to add.

Reference for this error, with confirmation of the bug from Microsoft: http://connect.microsoft.com/SQLServer/feedback/details/557402/ssms-can-no-longer-create-or-edit-job-steps

The only known workaround at this time is to close ssms completely, open it again, and edit the one job you want to edit (after that, you may start to get errors again and need to close again)

• November 2, 2008 at 11:57 am

  #128229

  This is the following result I found when I try to edit the job step.

  Job -> right click -> Properties -> job step -> edit

  What is the root cause of this error?

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

• Elisabeth Rédei

  Hall of Fame

  Points: 3873

  November 2, 2008 at 1:58 pm

  #892852

  Hi,

  Which version of SQL SErver are you on (SELECT @@version)? There seem to be a bug in earlier builds (http://support.microsoft.com/kb/918222/en-us contains a fix).

  Does it always happen, even if you restart SSMS?

  /Elisabeth

  elisabeth@sqlserverland.com
  MCITP | MCT
  http://sqlblog.com/blogs/elisabeth_redei/
  http://linkedin.com/in/elisabethredei

• ashish.johri

  Mr or Mrs. 500

  Points: 560

  November 2, 2008 at 2:49 pm

  #892853

  This is Yukon

• vmenon

  SSC Veteran

  Points: 274

  November 4, 2008 at 12:00 am

  #893437

  Please can you try out the following:

  RUN AT THE COMMAND PROMPT ON SERVER: REGSVR32.EXE dts.dll

  You can fing the dll file at the location :Program FilesMicrosoft SQL Server90DTSbinn

• SQLQuest29

  SSCrazy Eights

  Points: 8264

  vmenon (11/4/2008)

  ---

  Please can you try out the following:

  RUN AT THE COMMAND PROMPT ON SERVER: REGSVR32.EXE dts.dll

  You can fing the dll file at the location :Program FilesMicrosoft SQL Server90DTSbinn

  Hi,

  I had the same problem after I installed SP3 on my SQL 2005 standard edition, Win 2003 server. Your solution works like a charm.

  Thanks for the solution !!

  K

  ______________________________________________________________________________________________________________________________________________________________________________________
  HTH !
  Kin
  MCTS : 2005, 2008
  Active SQL Server Community Contributor 🙂

• phbianchi

  SSC Journeyman

  Points: 97

  I was having the same problem, and your suggestion solved it! Thanks!!!

• SQLQuest29

  SSCrazy Eights

  Points: 8264

  phbianchi (7/1/2009)

  ---

  I was having the same problem, and your suggestion solved it! Thanks!!!

  Glad it helped you !

  ______________________________________________________________________________________________________________________________________________________________________________________
  HTH !
  Kin
  MCTS : 2005, 2008
  Active SQL Server Community Contributor 🙂

• Johan Bijnens

  SSC Guru

  Points: 135035

  I was having the same issue after installing SSMS SQL2008R2.

  The regsvr fix worked like a charm. 😎

  ( I first changed my current directory in the command prompt to «C:Program FilesMicrosoft SQL Server100DTSBinn» )

  Thanks.

  edited:

  This has only been a temporary solution. I don’t know why, but it started giving these errors again after a couple of days. (btw: I have SQL2K, SQL2K5 and sql2008R2 full installs dev-edtn on my laptop)

• Damon Falconi-345992

  Old Hand

  Points: 359

  Help !!! I’m getting the same type of issue where I can’t edit Job Steps.

  I just installed

  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: ) (Hypervisor)

  On Windows Server 2008 R2 Standard 64-bit OS

  I tried the fix everyone has suggested : Pointed to folder

  C:Program FilesMicrosoft SQL Server100DTSBinn and ran REGSVR32.EXE dts.dll then bounced the

  service.

  But after I create a couple of test jobs and try to edit them a couple of times, the error returns.

• Keith Edwards

  Default port

  Points: 1446

  I am having the same issue after installing SSMS SQL2008R2. Has anybody found a long term fix for this by chance?

• Damon Falconi-345992

  Old Hand

  Points: 359

  There is a fix — Cumulative Update package 3 for SQL Server 2008 R2 —

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

  I applied this and it resolved the issue… If you wade through the KB you’ll see the problem listed.

• Keith Edwards

  Default port

  Points: 1446

  Great, Thanks for the reply

• JasonYousef

  SSCommitted

  Points: 1769

  Cool, Thanks, I was having the same problem while trying to create any maintenance plans on R2.

  the update called «sqlncli.msi»

  41822

• Johan Bijnens

  SSC Guru

  Points: 135035

  Damon Falconi-345992 (9/1/2010)

  ---

  There is a fix — Cumulative Update package 3 for SQL Server 2008 R2 —

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

  I applied this and it resolved the issue… If you wade through the KB you’ll see the problem listed.

  Indeed, after CU3 — for the moment — this jobstep editor issus vanished :w00t:

• casti77

  Grasshopper

  Points: 23

  after you register dts.dll restart your ssms.

Viewing 15 posts — 1 through 15 (of 19 total)

Just came across this peculiar SSMS error while trying to view a Job’s steps

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)

——————————

ADDITIONAL INFORMATION:

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)

——————————

BUTTONS:

OK

——————————

And found a simple solution here: http://connect.microsoft.com/SQLServer/feedback/details/569732/creating-an-instance-of-the-com-component-with-clsid

It only takes to register dts.dll with regsvr32 utility:

This, however, works in a random way – sometimes it does, sometimes it doesn’t. When it doesn’t, the only solution as far as I understand is to restart SSMS. Not comfortable, especially if you need to open several server nodes or multiple categories inside a single node. Let’s hope they will fix it in the next SQL Server version.