Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Maintenance plan jobs suspended due to errors.


Maintenance plan jobs suspended due to errors.

Author
Message
rlondon
rlondon
SSC-Addicted
SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)

Group: General Forum Members
Points: 423 Visits: 1160
Running SQL Server 2005 Enterprise Edition version 9.0.3175.
Windows 2003 SP2.

The SA recently applied some patches to the OS and upgraded to .NET 2.0 service pack 1.

After that upgrade the application was having problems. So the SA uninstalled the .NET service pack.

After the service pack was unistalled all of my maintenance plans and backup jobs failed with the following error.

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.

Errors from the SQLAGENT.OUT are as follows:

2008-02-05 10:25:48 - ! [LOG] Step 1 of job 'System DB Backups.Subplan_1' (0x96F3196477224045B547A213E551C10A) cannot be run because the SSIS subsystem failed to load. The job has been suspended

Any one have any clue as to how to fix this?
rlondon
rlondon
SSC-Addicted
SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)

Group: General Forum Members
Points: 423 Visits: 1160
I am also having problems with Management studio package not loading. This is the error I receive.

sql server management studio package failed to load

I assume the two issues are related, but do not know how to fix it.

Anyone have any suggestions?
Greg Charles
Greg Charles
SSCarpal Tunnel
SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)

Group: General Forum Members
Points: 4089 Visits: 5825
Could SSIS have been accidentally uninstalled? Confirm that the service exists in SQL Server Configuration Manager.

Greg
rlondon
rlondon
SSC-Addicted
SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)

Group: General Forum Members
Points: 423 Visits: 1160
I was able to re-create the problem on a test box. I re-installed .NET and it seemed to fixed the problem.
optradba
optradba
Mr or Mrs. 500
Mr or Mrs. 500 (590 reputation)Mr or Mrs. 500 (590 reputation)Mr or Mrs. 500 (590 reputation)Mr or Mrs. 500 (590 reputation)Mr or Mrs. 500 (590 reputation)Mr or Mrs. 500 (590 reputation)Mr or Mrs. 500 (590 reputation)Mr or Mrs. 500 (590 reputation)

Group: General Forum Members
Points: 590 Visits: 1045
May I know what version of .NET was reinstalled? I ahve both versions 1.0 and 2.0 in our server.
rlondon
rlondon
SSC-Addicted
SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)SSC-Addicted (423 reputation)

Group: General Forum Members
Points: 423 Visits: 1160
.NET 2.0 was reinstalled. The problem was that a patch to .NET 2.0 was uninstalled and it caused problems with SQL Server. We had to reinstall .NET 2.0 (not just the patch) to fix the problem.
DMarvez
DMarvez
SSC Rookie
SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)

Group: General Forum Members
Points: 41 Visits: 313
Hi,

Ran into the same issue. Reinstalled .Net 2.0
but the issue persisted.

Came across this article

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=525809&SiteID=1

which pointed me to

http://support.microsoft.com/?kbid=903205

While the version in the KB didn't matchup, I did check
msdb.dbo.syssubsystems and found that the BINN directory listed in
the paths was missing in action. Somebody else did a reinstall of SQL2K5 on the box and I think the registry or MSDB didn't get updated
with the new path.

As a test, I copied over the BINN directory from mssql.3 to mssql.1 and restarted SQL Agent. The jobs now run without error. Probably a better way to fix this but it's Saturday so this will do for now.
DoubleD
DoubleD
SSC-Enthusiastic
SSC-Enthusiastic (180 reputation)SSC-Enthusiastic (180 reputation)SSC-Enthusiastic (180 reputation)SSC-Enthusiastic (180 reputation)SSC-Enthusiastic (180 reputation)SSC-Enthusiastic (180 reputation)SSC-Enthusiastic (180 reputation)SSC-Enthusiastic (180 reputation)

Group: General Forum Members
Points: 180 Visits: 185
Just to add to the discussion, we had the same issue. We ran: select * from msdb.dbo.syssubsystems and noticed that the subsystem dll path was incorrect. Our path read mssql.7, instead of mssql.1, because this instance had been the second named instance on the server. It is now the only instance on a new server, but the paths were not properly updated.
DMarvez
DMarvez
SSC Rookie
SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)

Group: General Forum Members
Points: 41 Visits: 313
So, were you able to update the path in msdb.dbo.syssubsystems ?

That was my thought when I came across this but didn't pursue it further after copying over the folder.
DoubleD
DoubleD
SSC-Enthusiastic
SSC-Enthusiastic (180 reputation)SSC-Enthusiastic (180 reputation)SSC-Enthusiastic (180 reputation)SSC-Enthusiastic (180 reputation)SSC-Enthusiastic (180 reputation)SSC-Enthusiastic (180 reputation)SSC-Enthusiastic (180 reputation)SSC-Enthusiastic (180 reputation)

Group: General Forum Members
Points: 180 Visits: 185
Yes, that did the trick. Thankfully, it was only 11 rows. Update statements did it. After restarting the SSIS service, the plans worked fine.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search