You are currently offline, waiting for your internet to reconnect

Error message when you restore or attach an msdb database or when you change the syssubsystems table in SQL Server 2005: "Subsystem % could not be loaded"

Extended support for SQL Server 2005 ends on April 12, 2016

If you are still running SQL Server 2005 after April 12, 2016, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

Bug #: 425161 (SQBUDT)
SYMPTOMS
Consider the following scenario. You perform one of the following actions in Microsoft SQL Server 2005:
  • You restore an msdb backup.
  • You attach an msdb database.
  • You change the information in the syssubsystems table in the msdb database.
The paths to the SQL Server Agent subsystem DLLs are stored in the msdb.dbo.syssubsystems table in the msdb database. The locations do not correspond to the current locations of the binaries for the instance of SQL Server 2005. In this scenario, an error occurs. The following error message may be logged in the SQL Server Agent log or in the Job step history:
Subsystem %s could not be loaded (reason: The specified module could not be found)
When this error occurs, jobs may fail. Additionally, the following error message may be logged in the Job steps history:
Unable to start execution of step 1 (reason: The %s subsystem failed to load [see the SQLAGENT.OUT file for details]; The job has been suspended). The step failed.
The following error is logged in the SQL Server Agent logs:
2006-01-24 14:02:41 - ! [125] Subsystem %s could not be loaded (reason: The specified module could not be found)
RESOLUTION
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 msdbgodelete from msdb.dbo.syssubsystemsexec msdb.dbo.sp_verify_subsystems 1go
  2. Stop and then restart the SQL Server Agent service.
Subsystem SQLAgent ActivexScripting ANALYSISCOMMAND ANALYSISQUERY QueueReader
Properties

Article ID: 914171 - Last Review: 11/20/2007 17:41:19 - Revision: 1.2

Microsoft SQL Server 2005 Developer Edition, Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems, Microsoft SQL Server 2005 Enterprise X64 Edition, Microsoft SQL Server 2005 Express Edition, Microsoft SQL Server 2005 Standard Edition, Microsoft SQL Server 2005 Standard X64 Edition, Microsoft SQL Server 2005 Workgroup Edition, Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems

  • kbsql2005engine kbexpertiseinter kbexpertiseadvanced kbtshoot kbprb KB914171
Feedback
avaScript" async=""> var varAutoFirePV = 1; var varClickTracking = 1; var varCustomerTracking = 1; var Route = "76500"; var Ctrl = ""; document.write(" -repeat="language in languagesListForLargeScreens track by $index" class="col-sm-6 col-xs-24 ng-scope"> Uruguay - Español
대한민국 - 한국어
España - Español
Paraguay - Español
Venezuela - Español
id=1&t=">I=4050&did=1&t="> var varCustomerTracking = 1; var Route = "76500"; var Ctrl = ""; document.write(" .getElementsByTagName('head')[0].appendChild(m);" onload="var m=document.createElement('meta');m.name='ms.dqp0';m.content='false';document.getElementsByTagName('head')[0].appendChild(m);" src="http://c1.microsoft.com/c.gif?"> dy>