What are the correct procedures to install the Microsoft SQL Server Management (SMO) library on a MID server?

[Tom Rausch]

ServiceNow documentation apparently states that we must install the Microsoft SQL Server Management (SMO) library on the MID server in order to Discover MSSQL servers (https://docs.servicenow.com/bundle/london-it-operations-management/page/product/discovery/reference/mssql-data-collected-pattern.html, https://docs.servicenow.com/bundle/geneva-it-operations-management/page/product/discovery/reference/r_MicrosoftSQLServers.html).

We installed the SMO on one of our MID servers as part of a larger VisualStudio installation (Installed SMO.png). Unfortunately, when we attempt to run a Discovery against a machine that has a MSSQL server, we obtain the error "Unable to load assembly Microsoft.SqlServer.Smo. The SMO library must be installed on the MID Server host" (Discovery - SMO Error.png) .

What is the correct way to install the SMO on the MID server?

[Tom Rausch]

The solution is apparently to download and install these two MSI files on the MID server.

• SQLSysClrTypes.msi
• SharedManagementObjects.msi

The details appear in this link: Full SQL Discovery (Help Required - Eureka)

This solution was found by Atos Discovery Technician Jansi Bhandari.

[Tom Rausch]

The libraries are also available for download at this link: KB #240112: Installing SQL Server Shared Management Objects (SQL-SMO).

This link was provided by ServiceNow Technician Louie Barrameda.

[kostadinof1]

This is definitely helpful, however the MID servers usually sit within customer (private) NW.
The above installer on the other hand requires internet access. 

This presents quite a challenge to install the libraries. 
It would be nice to have these libraries as part of the MID server package. 
Have you faced this or similar situation and do you  see any workaround ?

Regards

[Tom Rausch]

One workaround is to do the following.

• Logon the ServiceNow instance on your local workstation
• Create a ServiceNow Knowledge Base article on the ServiceNow instance related to the libraries
• Check the "Display Attachments" checkbox
• Attach the libraries' source code files to the Knowledge Base article
• Logon the MID Server
• Open a browser
• Logon the same ServiceNow instance. You are guaranteed to have a connection to the ServiceNow instance as it was enabled when the MID Server was initiated
• Access the new Knowledge Base article
• Download the attached files

Here is an example.

Does this help?