Backup job thru maintenance plan is failing in sql 2005

Question

Post reply

Backup job thru maintenance plan is failing in sql 2005

fasiuddin

Valued Member

Points: 52
More actions
May 8, 2007 at 9:07 am

#116791

Hi,
Backup job thru maintenance plan is failing in sql server 2005.
I have created the maint paln after connecting thru SA user.
here is the error message
Message
Unable to start execution of step 1 (reason: The SSIS subsystem failed to load [see the SQLAGENT.OUT file for details]; The job has been suspended). The step failed.

any help is appreciated.

Thx

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

John-79567 SSCommitted Points: 1892 More actions · Answer 1

Is integration services installed and running? 2005 maintenance plans require SSIS.

fasiuddin Valued Member Points: 52 More actions · Answer 2

Hi John,

Thanks for the reply.

SSIS is installed , what do you mean by running , is it the ssis service ?

i think ssis services is not required for running the pkg.

Thx

Robert Davis One Orange Chip Points: 28027 More actions · Answer 3

SSIS has its own service entry. However, it is only needed for the creation of the maintenance plan, not for running it. In fact, starting with SP2, you don't even have to install SSIS to be able to do maintenance plans.

Step 1 is to look in the sqlagent.out log file and see what is in there.

My blog: SQL Soldier[/url]
SQL Server Best Practices: SQL Server Best Practices
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring[/url]
Microsoft Certified Master: SQL Server, Data Platform MVP
Database Engineer at BlueMountain Capital Management[/url]

fasiuddin Valued Member Points: 52 More actions · Answer 4

hi Robert,

Thanks for the reply,

Here is the message in SQLAgent.out file

Step 1 of job 'Full Backup For Test DB.Subplan_1' (0xB318484B455F944EB77480640A47599A) cannot be run because the SSIS subsystem failed to load. The job has been suspended

Thx

Rajib Kundu Grasshopper Points: 22 More actions · Answer 5

if it is showing that job is in suspended condition please follow the step.

To work around this problem, delete the entries from the msdb.dbo.syssubsystems table, and then repopulate the entries. The following steps will update the subsystem DLLs to the correct path based on the current install folder. To do this, follow these steps: 1. In SQL Server Management Studio, run the following script.use msdb

go

delete from msdb.dbo.syssubsystems

exec msdb.dbo.sp_verify_subsystems 1

go

2. Stop and then restart the SQL Server Agent service.

russellgh SSC Enthusiast Points: 141 More actions · Answer 6

I has the same error and the root cause was that SSIS was NOT installed on the cluster node that the SQL instance was running on at the time the job executed. I have an active/passive cluster that someone forgot to install SSIS on both nodes so hence the problem.