Microsoft KB Archive/903205

= &quot;The specified module could not be found&quot; error messages are logged, and all your SQL Server Agent jobs do not run after you upgrade from SQL Server 2005 Beta 2 to SQL Server 2005 Community Technology Preview =

Article ID: 903205

Article Last Modified on 3/11/2006

-

APPLIES TO


 * Microsoft SQL Server 2005 Beta 2
 * Microsoft SQL Server 2005 Developer Edition Community Technology Preview
 * Microsoft SQL Server 2005 Developer x64 Edition Community Technology Preview
 * Microsoft SQL Server 2005 Enterprise Edition Community Technology Preview
 * Microsoft SQL Server 2005 Express Edition Community Technology Preview
 * Microsoft SQL Server 2005 Standard Edition Community Technology Preview
 * Microsoft SQL Server 2005 Standard x64 Edition Community Technology Preview
 * Microsoft SQL Server 2005 Workgroup Edition Community Technology Preview

-





Beta Information
This article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this Beta product. For information about how to obtain support for a Beta release, see the documentation that is included with the Beta product files, or check the Web location where you downloaded the release.



SYMPTOMS
After you upgrade from Microsoft SQL Server 2005 Beta 2 to Microsoft SQL Server 2005 Community Technology Preview (CTP), all your SQL Server Agent jobs do not run. Additionally, the following error messages are logged in the SQL Server Agent error log:

Subsystem 'ActiveScripting' could not be loaded (reason: The specified module could not be found)

Subsystem 'CmdExec' could not be loaded (reason: The specified module could not be found)

Subsystem 'Snapshot' could not be loaded (reason: The specified module could not be found)

Subsystem 'LogReader' could not be loaded (reason: The specified module could not be found)

Subsystem 'Distribution' could not be loaded (reason: The specified module could not be found)

Subsystem 'Merge' could not be loaded (reason: The specified module could not be found)

Subsystem 'QueueReader' could not be loaded (reason: The specified module could not be found)

Subsystem 'ANALYSISQUERY' could not be loaded (reason: The specified module could not be found)

Subsystem 'ANALYSISCOMMAND' could not be loaded (reason: The specified module could not be found)

Subsystem 'Dts' could not be loaded (reason: The specified module could not be found)

Note This problem only occurs when you perform an installation upgrade that installs the SQL Server 2005 CTP components together with the option to use existing data.



CAUSE
This problem occurs because the location of the binary files was changed in SQL Server 2005 CTP.



RESOLUTION
To resolve this problem, update the subsystem metadata that is contained in the msdb.dbo.syssubsystems system table to point to the correct location of each subsystem.

By default, the subsystem_dll data column and the agent_exe data column should have the following values for each subsystem.

Note After you update the data columns, you must restart the SQL Server Agent service.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about SQL Server 2005 CTP, visit the following Microsoft Web site:

http://www.microsoft.com/sql/default.mspx

Additional query words: SQL2005 CTP BETA2

Keywords: kbtshoot kbprb KB903205

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.