Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Maintenance plan jobs suspended due to errors. Expand / Collapse
Author
Message
Posted Tuesday, February 5, 2008 9:56 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 10:51 AM
Points: 417, Visits: 1,156
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?
Post #451735
Posted Tuesday, February 5, 2008 2:09 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 10:51 AM
Points: 417, Visits: 1,156
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?
Post #451888
Posted Tuesday, February 5, 2008 2:17 PM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Yesterday @ 9:45 AM
Points: 4,064, Visits: 5,341
Could SSIS have been accidentally uninstalled? Confirm that the service exists in SQL Server Configuration Manager.

Greg
Post #451895
Posted Wednesday, February 6, 2008 10:06 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 10:51 AM
Points: 417, Visits: 1,156
I was able to re-create the problem on a test box. I re-installed .NET and it seemed to fixed the problem.
Post #452337
Posted Wednesday, March 26, 2008 8:24 PM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Yesterday @ 3:39 AM
Points: 588, Visits: 977
May I know what version of .NET was reinstalled? I ahve both versions 1.0 and 2.0 in our server.
Post #475181
Posted Thursday, March 27, 2008 6:56 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 10:51 AM
Points: 417, Visits: 1,156
.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.
Post #475358
Posted Saturday, June 28, 2008 8:32 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, September 2, 2014 12:13 PM
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.
Post #525491
Posted Thursday, January 22, 2009 2:25 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, January 31, 2011 8:56 AM
Points: 178, 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.
Post #642080
Posted Thursday, January 22, 2009 2:41 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, September 2, 2014 12:13 PM
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.
Post #642091
Posted Friday, January 23, 2009 8:46 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, January 31, 2011 8:56 AM
Points: 178, 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.
Post #642511
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse