December 11, 2013 at 4:39 am
Hi
On this server we are using SQL Server 2005 SP4, with a number of instances and the same issues is experienced over all instances.
The Symantic Enterprise vault was upgraded over the weekend, whilst being upgraded issues were experienced with the .NET framework.
As a result lastnight .NET2 was removed and an MStool to remove all associated DLL's was used.
.NET 3.5 was then installed which re-installed .Net2
When SQL JOBS try to run the backup routine, created in Maintenance Plan we are now getting the following error.
cannot be run because the SSIS subsystem failed to load. The job has been suspended
I have done
SELECT * From msdb.dbo.syssubsystems and checked the location and this is correct.
At the moment I would prefer not to re-install SQL.
Any help would be appriciated.
December 16, 2013 at 4:31 am
In your position I would also not want to re-install SQL Server.
I would want to reformat the system drive and re-install Windows.
Removing and re-installing .Net is a bit like doing a heart transplant without using any anti-rejection drugs. You might eventually be able to fix all the problems, but it will not be easy and success is not guaranteed.
Rebuilding your server from Windows onwards is also not easy, but has a better chance of success and is likely to take less time.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply