Error while creating a Job

Question

Hi All,

I am getting the below error while creating the New Job. when i clicking on Steps--> New, that time it is showing the below error.

Please help me to create a new job.

Thanks

KRish

Answer 1

sorry forgot to paste screen shot

Answer 2

Hi Krish,

You are missing the error message in this thread. could you please post the exact error message ? without knowing the error message you are getting, we cannot help out much .

---

Sanil Mhatre | Database Developer | MCTS | If you find my reply useful in any way, please vote it as helpful. If it has helped answer your question, please mark it as Answer.

Answer 3

below is the error:

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).

Answer 4

What version of SQL Server are you using ? if its 2008 or 2008R2, this is a know issue documented on connect.

http://connect.microsoft.com/SQLServer/feedback/details/557402/ssms-can-no-longer-create-or-edit-job-steps

http://connect.microsoft.com/SQLServer/feedback/details/569732/creating-an-instance-of-the-com-component-with-clsid

Microsoft support has documented the fix here: 

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

Similar issue was discussed in an earlier thread on the forums : 

http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/d573546e-c54d-4eac-b89c-23aeed739b2b

Hope this helps !

---

Sanil Mhatre | Database Developer | MCTS | If you find my reply useful in any way, please vote it as helpful. If it has helped answer your question, please mark it as Answer.

Answer 5

Please take a look at following blog article http://blogs.msdn.com/b/sqlagent/archive/2012/01/20/fix-ssms-can-no-longer-create-or-edit-job-steps-creating-an-instance-of-the-com-component-with-clsid-aa40d1d6-caef-4a56-b9bb-d0d3dc976ba2-from-the-iclassfactory-failed.aspx

Thanks

Sethu Srinivasan [MSFT]

SQL Server

http://blogs.msdn.com/sqlagent

Answer 6

Hi Krish,

Temporarily solution to your issue is to disable UAC.

UAC can be disabled from control panel -> User settings or security policy console (secpole.msc).

As per Microsoft, this bug was fixed in CU3 however since now sp1 is there , I recommend you to apply sp1 at the earliest to fix this issue.

Hope this helps!!

---

Regards, Vishal Srivastava