Monthly Archives: October 2018

Error encountered trying to prepare the existing metaverse configuration.

Import Server Configuration fails:

Oh great, and you’ve also unselected all the connector space attributes in every MA for me, thanks very much MIM. Oh well, it’s only the production environment.

This time the reason turned out to be due to changes to attribute types in the metaverse schema. One of the changes was to “convert” an attribute from a string to a boolean. It turns out that you cannot effect this change by using “Import Server Configuration” to obliterate the old config and replace with the new one, it must be trying to do some sort of delta change instead, and failing. The same probably also happens if you are trying to change an attribute from single-valued to multi-valued (see https://social.technet.microsoft.com/Forums/en-US/31ebeaf5-827a-49b9-b2a2-ebb38e63c223/error-importing-miis-server-configuration?forum=identitylifecyclemanager)

The solution is to delete the attribute(s) that are changing type, and then import the new configuration, which will recreate the attributes with the correct (new) type. Note: you can’t delete attributes until any flow rules that use them are manually removed.

Success, finally.

“Management agent update processing FAILED” when trying to update an ECMA2 MA

Infuriating product…

Export MA from one environment, try to import it to another using “Update Management Agent” and encounter this error:

Nothing in the event log, I sense another wasted day coming up…

The issue turned out to be that I was not only updating the MA configuration, but also the ECMA2 DLL associated with the MA as the same time. The new DLL introduced some new ConfigParameters on the connectivity page. In order to be able to import the new MA config, I had to first do a “refresh Interfaces” on the exisint MA (with the new DLL in place), and then run “Update Management Agent”.

So, if updating a Management Agent at the same time as an ECMA2 DLL, the following order should be observed:

  1. Replace the DLL
  2. Open the existing MA, do “Refresh Interfaces” and save.
  3. Run “Update Management Agent” and provide the new config XML

Hopefully you then get an successfully updated MA: