Users may encounter the error Could not load file or assembly 'Microsoft.SqlServer.Smo, Version=X.x.x.x 

If this error is encountered, it indicates the machine running the JAMS Client is missing the SQL Shared Management Objects (SMO). JAMS attempts to search for SQL Server SMO versions from the latest version (15) down to the oldest supported version (11). When JAMS finds an SMO version, it will use that version. 

This may be seen when trying to create a Job using the SQLStoredProc, SSISDirect, or SSRS Execution Method. It may also occur when trying to view the External Tab.

It is advised that regardless of the version number of the error, you should install SMO based on the version of SQL being used. Users should read the Software and Hardware Prerequisites article that corresponds to their version of JAMS to understand which SQL versions are supported by their JAMS version.

The following version numbers correspond to the versions of SQL:

• SQL 2019 - 15
• SQL 2017 - 14
• SQL 2016 - 13
• SQL 2014 - 12
• SQL 2012 - 11

To find the appropriate version of Shared Management Objects, search the internet for "Shared Management Objects XXXX Download" where XXXX is the version of SQL that is described in the exception. Download and install the SMO on the machine where the error occurs, and then restart the JAMS Client and attempt the operation again.

NOTE: In later versions of SQL, the Shared Management Objects dependency can be satisfied by installing the Client Tools Backwards Compatibility and Client Tools SDK SQL Shared Features. 

NOTE: If you already have SQL Shared Management Objects installed, users can force JAMS to use a specific version of SQL Server SMO by adding a parameter called JAMSSQLVersion on a Job.

Possible values for the JAMSSQLVersion parameter are:

• 2019
• 2017
• 2016
• 2014
• 2012