Subsystems could not be loaded
Hi, I'm running SQL Server Agent services and SQL Server Integration services under same Domain\User account and the same Domain\User account is also having sysadmin rights in sql server. Andbelow is the SQLAgent.OUT file details which I'm getting while running the SSIS from SQL Agent job. [100] Microsoft SQLServerAgent version 9.00.1399.06 (x86 unicode retail build) : Process ID 4012[101] SQL Server MachineNameXYZ version 9.00.1399 (0 connection limit)[102] SQL Server ODBC driver version 9.00.1399[103] NetLib being used by driver is DBNETLIB.DLL; Local host server is [310] 4 processor(s) and 3072 MB RAM detected[339] Local computer is MachineNameXYZ running Windows NT 5.2 (3790) Service Pack 1[432] There are 11 subsystems in the subsystems cache[125] Subsystem 'ActiveScripting' could not be loaded (reason: The specified module could not be found)[125] Subsystem 'CmdExec' could not be loaded (reason: The specified module could not be found)[125] Subsystem 'Snapshot' could not be loaded (reason: The specified module could not be found)[125] Subsystem 'LogReader' could not be loaded (reason: The specified module could not be found)[125] Subsystem 'Distribution' could not be loaded (reason: The specified module could not be found)[125] Subsystem 'Merge' could not be loaded (reason: The specified module could not be found)[125] Subsystem 'QueueReader' could not be loaded (reason: The specified module could not be found)[125] Subsystem 'ANALYSISQUERY' could not be loaded (reason: The specified module could not be found)[125] Subsystem 'ANALYSISCOMMAND' could not be loaded (reason: The specified module could not be found)[125] Subsystem 'SSIS' could not be loaded (reason: The specified module could not be found)[364] The Messenger service has not been started - NetSend notifications will not be sent[129] SQLSERVERAGENT starting under Windows NT service control[260] Unable to start mail session (reason: No mail profile defined)[396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect[LOG] Step 1 of job 'TestJob' (0x4A197E88EAD5134581A35132A546414C) cannot be run because the SSIS subsystem failed to load. The job has been suspended[LOG] Unable to read local eventlog (reason: The parameter is incorrect)[LOG] Unable to read local eventlog (reason: The parameter is incorrect)[LOG] Step 1 of job 'TestJob' (0xE412C2AB10C7A34B87F5DFC8CFD978CA) cannot be run because the SSIS subsystem failed to load. The job has been suspended[LOG] Unable to read local eventlog (reason: The parameter is incorrect) Any help will be appreciated. Regards, M.S
July 4th, 2006 1:49am

That's nothing to do with SSIS so I would try one of the other forums if I were you. http://forums.microsoft.com/MSDN/default.aspx?ForumGroupID=19&SiteID=1 -Jamie
Free Windows Admin Tool Kit Click here and download it now
July 4th, 2006 3:04am

Hi , I am also getting same error while trying to run a maintenance job for backup. Here is the error from SQLAgent.out file. There are 6 subsystems in the subsystems cache2007-05-04 16:30:55 - ! [125] Subsystem 'ANALYSISCOMMAND' could not be loaded (reason: A dynamic link library (DLL) initialization routine failed)2007-05-04 16:30:55 - ! [125] Subsystem 'ANALYSISQUERY' could not be loaded (reason: A dynamic link library (DLL) initialization routine failed)2007-05-04 16:30:56 - ! [125] Subsystem 'SSIS' could not be loaded (reason: A dynamic link library (DLL) initialization routine failed)2007-05-04 16:30:56 - ! [364] The Messenger service has not been started - NetSend notifications will not be sent2007-05-04 16:30:56 - ? [129] SQLAgent$DEV01 starting under Windows NT service control2007-05-04 16:30:56 - + [260] Unable to start mail session (reason: No mail profile defined)2007-05-04 16:30:56 - + [396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect2007-05-07 09:53:40 - ! [LOG] Step 1 of job 'Full Backup InfraDB' (0xB2E5E769B04D1547B284415B652F5DD2) cannot be run because the SSIS subsystem failed to load. The job has been suspended Any help is appreciated.
May 7th, 2007 10:44am

Mohammed F wrote: Hi , I am also getting same error while trying to run a maintenance job for backup. Here is the error from SQLAgent.out file. There are 6 subsystems in the subsystems cache2007-05-04 16:30:55 - ! [125] Subsystem 'ANALYSISCOMMAND' could not be loaded (reason: A dynamic link library (DLL) initialization routine failed)2007-05-04 16:30:55 - ! [125] Subsystem 'ANALYSISQUERY' could not be loaded (reason: A dynamic link library (DLL) initialization routine failed)2007-05-04 16:30:56 - ! [125] Subsystem 'SSIS' could not be loaded (reason: A dynamic link library (DLL) initialization routine failed)2007-05-04 16:30:56 - ! [364] The Messenger service has not been started - NetSend notifications will not be sent2007-05-04 16:30:56 - ? [129] SQLAgent$DEV01 starting under Windows NT service control2007-05-04 16:30:56 - + [260] Unable to start mail session (reason: No mail profile defined)2007-05-04 16:30:56 - + [396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect2007-05-07 09:53:40 - ! [LOG] Step 1 of job 'Full Backup InfraDB' (0xB2E5E769B04D1547B284415B652F5DD2) cannot be run because the SSIS subsystem failed to load. The job has been suspended Any help is appreciated. Like I said above, this is the wrong forum to ask this question. its nothing to do with SSIS. -Jamie
Free Windows Admin Tool Kit Click here and download it now
May 7th, 2007 11:28am

Has anyone solved this. I don't care which forum its solved in but I can't find a good solution! Can someone help me find it? What subsystem of sql server does the problem lie in? Unable to start execution of step 1 (reason: The CmdExec subsystem failed to load [see the SQLAGENT.OUT file for details]; The job has been suspended). The step failed. Date5/15/2008 12:06:03 PMLogJob History (VSP_EDI) Step ID1ServerULTIPROSQLT-1Job NameVSP_EDIStep NameEDI_SSIS_PACKAGEDuration00:00:00Sql Severity0Sql Message ID0Operator EmailedOperator Net sentOperator PagedRetries Attempted0 MessageUnable 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.
May 15th, 2008 3:10pm

Ran into the same issue when after a server crash, another DBA rebuilt sqlserver to a different directory. We restored msdb from backup prior to crash. As a result subsystem_dll column in msdb.dbo.syssubsystems was out of sync. Here is the fix: sp_configure "allow updates", 1 reconfigure with override update syssubsystems set subsystem_dll= replace(subsystem_dll,'E:\Program Files','c:\Program Files\Microsoft sql server') FROM syssubsystems where subsystem_dll like 'E:\Program Files%' sp_configure "allow updates", 0 reconfigure with override --ensure the change took select * FROM syssubsystems
Free Windows Admin Tool Kit Click here and download it now
September 10th, 2008 3:57pm

Thank you for this information. I definitly helped us to be able to start backing up this server by using agent jobs.
September 11th, 2008 10:44am

Worked like a champ.... THANKS Here is my error and resolution /* MESSAGE FROM SQLAGENT.OUT 2008-09-24 15:14:56 - ! [125] Subsystem 'ActiveScripting' could not be loaded (reason: The specified module could not be found) 2008-09-24 15:14:56 - ! [125] Subsystem 'CmdExec' could not be loaded (reason: The specified module could not be found) 2008-09-24 15:14:56 - ! [125] Subsystem 'Snapshot' could not be loaded (reason: The specified module could not be found) 2008-09-24 15:14:56 - ! [125] Subsystem 'LogReader' could not be loaded (reason: The specified module could not be found) 2008-09-24 15:14:56 - ! [125] Subsystem 'Distribution' could not be loaded (reason: The specified module could not be found) 2008-09-24 15:14:56 - ! [125] Subsystem 'Merge' could not be loaded (reason: The specified module could not be found) 2008-09-24 15:14:56 - ! [125] Subsystem 'QueueReader' could not be loaded (reason: The specified module could not be found) 2008-09-24 15:14:56 - ! [125] Subsystem 'ANALYSISQUERY' could not be loaded (reason: The specified module could not be found) 2008-09-24 15:14:56 - ! [125] Subsystem 'ANALYSISCOMMAND' could not be loaded (reason: The specified module could not be found) 2008-09-24 15:14:56 - ! [125] Subsystem 'SSIS' could not be loaded (reason: The specified module could not be found) 2008-09-24 15:14:56 - ! [364] The Messenger service has not been started - NetSend notifications will not be sent 2008-09-24 15:14:56 - ? [129] SQLSERVERAGENT starting under Windows NT service control 2008-09-24 15:14:56 - + [396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect 2008-09-24 15:15:18 - ! [LOG] Step 1 of job 'SystemDatabasesMaintenancePlan.Back Up Database Task' (0xAEAED6468D57C648AE2555BCDC3CA977) cannot be run because the SSIS subsystem failed to load. The job has been suspended 2008-09-24 15:55:12 - + [000] Request to run job SystemDatabasesMaintenancePlan.Back Up Database Task (from User PROD1\mvarriale) refused because the job has been suspended */ -- -- Here is the fix: EXEC sp_configure 'allow updates', 1 reconfigure with override GO -- update msdb.dbo.syssubsystems set subsystem_dll= replace(subsystem_dll,'D:\Program Files','C:\Program Files') FROM msdb.dbo.syssubsystems where subsystem_dll like 'D:\Program Files%' -- EXEC sp_configure 'allow updates', 0 reconfigure with override GO -- -- ensure the change took -- select subsystem , subsystem_dll , agent_exe from msdb.dbo.syssubsystems where subsystem_dll like 'c:\Program Files%'
Free Windows Admin Tool Kit Click here and download it now
September 24th, 2008 4:11pm

Thanks! I've been looking all over for this as well. It resolved my problem too!.....In regards to the "wrong forum" post...What the heck Jamie? Are you really an MVP or just a cranky engineer...Obviously it does affect SSIS...when trying to run a SSIS package from the Agent the subsystem , the DLLs for SSIS could not be loaded. DBA24x7 should get a medal, Jamie should be demoted..
August 18th, 2009 7:01pm

No need to overreact - you're both right. This is both the right and wrong forum. It's the wrong forum for someone who knows SQL Server already but it's the right forum for someone who doesn't know SQL Server. This same scenario could play on on the SSAS boards, the PowerShell boards, etc (and probably has).I have about 1,000 video tutorials on SQL Server 2008, 2005, and 2000 over at http://www.learnitfirst.com/Database-Professionals.aspx
Free Windows Admin Tool Kit Click here and download it now
September 18th, 2009 11:23am

Be sure to restart your SQL Server Agent after updating the table!
October 24th, 2009 1:36pm

Thank you so much! It works great by using your scropt. Thanks again!I was doing the server migration and moved all system databases to the new server. The drive was changed from D:\ to J:\.
Free Windows Admin Tool Kit Click here and download it now
January 23rd, 2010 12:36pm

Thanks a lot for this solution. This has saved my day too. Ketan Patel.
June 22nd, 2012 10:34am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics