This is very strange. I have been able to open steps within a job for several days now. All of a sudden, today, when I open a step in any job, I get the following error message "Creating an instance of the COM component with CLSID {AA40D1D6-CAEF-4A56 ..... failed eu to the following error: ......" What causes this error? This is our production server where the jobs have been running for several days now without issues and I have been able to open the job steps prior to today. Nothing changed on this server since we have very stringent change management procedures in place. Appreciate any help! Jagannathan Santhanam

Does this happen only for Steps that are SSIS steps, or would it bomb out if you had, say, a T-SQL step?Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.

Just checked, it is happening across the board, SSIS, T-SQL jobs etc., Perplexed since it just started happening today (or atleast I saw it just today)Jagannathan Santhanam

Have you tried re-starting the SQL Agent Service? Do the jobs still actually RUN? What happens if you try to CREATE a NEW job with steps. Can you see its steps after creation?Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.

Sigh! I logged out and logged back in and it works fine now. I guess, like in any Microsoft product, the snap-in was confused :)Jagannathan Santhanam

Could it be this issue - FIX: You cannot create, add, or edit steps for an SQL Server Agent job in SQL Server Management Studio 2008 R2 If not... Are you running SSMS on the server or on a remote machine? What happnes if using this same SSMS you connect to another SQL Server? Can you connect to this production server from another machine with SSMS? What I am trying to work our its whether the problem is within the SSMS install, or SQL Agent itself. I suspect the former. Are your SSMS machine and the SQL server running the same SQL versions, SP and updates? Client tools need to be updated as well as the server.http://www.sqlis.com | http://www.konesans.com

Darren - Look at my post prior to yours. Logging off and back on fixed the issue. Strange but true :)Jagannathan Santhanam