System error: "No Assemblies loaded" (4326320)

System error: "No Assemblies loaded"

After an Identity Manager (1IM) migration, installation, or system upgrade, a system error, "No Assemblies loaded" is constantly displayed on the front-end tools, e.g. JobQueueInfo, Manager, Designer.

The error, "No assemblies loaded" is shown if there is an empty file in the database.  This can be verified using the following query:

select FileName from QBMFileRevision
where FileContent is null
order by 1

All files related to 1IM are saved in the table QBMFileRevision.  A migration/upgrade/installation first creates the entries in this table, but only the FileName is filled, the FileContent is still empty at this point.  The very last step in the migration uploads the files in the database.  That step fills the empty FileContent field.  If the migration/upgrade/installation has been stopped before the files were uploaded, this error will be displayed.

If all files are affected, then the migration/installation/upgrade should be run again.  As mentioned: the last step will upload the missing files.

If only single files are affected, these files can be uploaded manually using Software Loader.

For example, if only the file 'OneIM_ServiceNow_Administration_de-de.html5.zip' has the content missing, the 'OneIM_ServiceNow_Administration_de-de.html5.zip' file is needed, and should be available (if it's not a custom file) in the installer (binaries) provided with Identity Manager and uploaded to the database using Sofware Loader.

To do this, in the example case of 'OneIM_ServiceNow_Administration_de-de.html5.zip' file, it is located under \Modules\SCN\Documentation\de-DE\Subsystems in the installer's folder hierarchy.  In order to load it into the database, before opening Software Loader, the file has to be put in the correct folder hierarchy.

In this case, following the example, on the workstation a temporary folder has to be created if there isn't one yet.  Inside of the folder, the folder "de-DE" has to be created, and the "Subsystems" folder inside the "de-DE" folder, and then the file should be put into the "Subsystems" folder.  This would end up putting the file on the following example path: C:\temp\de-DE\Subsystems\OneIM_ServiceNow_Administration_de-de.html5.zip.

Now the Software Loader has to be started, the option "Import into database" selected, and after login to the database with the necessary credentials, the C:\temp folder has to be selected as the root folder.  After doing this, it is necesary to navigate to the "de-DE" folder and then to the "Subsystems" folder.  This causes Software Loader to treat it as the same folder hierarchy as the one present on the Identity Manager instance.

 

(In the above image the chosen temporary folder is "Downloads", but in the example above, the "Temp" folder would work the same way).

After doing this, and following the next steps with Software Loader, the error message should disappear from the front-ends.