Identity Broker for chris21 downgrade stop Identity Broker service from starting

Shane Lim 13 years ago in UNIFYBroker/Frontier ichris/chris21 updated by anonymous 9 years ago 9

Post upgrade of Identity Broker for chris21 from version 3.0.5 to

I ran into the issue that I cannot perform "Synchronisation Import" or "Full Import" on any exist chris21 Connectors. See end of issue IDBCHRS-13 for details of the error.

Since I need my Lab environment for other work for chris21 I downgrade Identity Broker for chris21 back to version 3.0.5. This is done by uninstalling Identity Broker for chris21 v3.0.5.2 and install Identity Broker for chris21 v3.0.5.

I also restore to Connector and Adapter configuration file to the known working ones.

When starting the Identity Broker service I encounter the following error:

Unify.Framework.UnifyServerInitializeException: Could not load file or assembly
'Unify.Framework.LogWorker.Interfaces, Version=, Culture=neutral, PublicK
eyToken=84b9288cb2633de4' or one of its dependencies. The located assembly's man
ifest definition does not match the assembly reference. (Exception from HRESULT:
 0x80131040) ---> System.IO.FileLoadException: Could not load file or assembly '
Unify.Framework.LogWorker.Interfaces, Version=, Culture=neutral, PublicKe
yToken=84b9288cb2633de4' or one of its dependencies. The located assembly's mani
fest definition does not match the assembly reference. (Exception from HRESULT:
File name: 'Unify.Framework.LogWorker.Interfaces, Version=, Culture=neutr
al, PublicKeyToken=84b9288cb2633de4'
   at Unify.Connectors.Chris21GtrConnectorFactoryBase`3.CreateComponent(IMultiKe
yedConnectorFactoryInformation factoryInformation)
   at Unify.Framework.PlugInGeneratorBase`4.CreateComponent(TFactoryInfo factory
   at Unify.Framework.ConnectorEngineConnectorGenerator.CreateComponent(IMultiKe
yedConnectorFactoryInformation factoryInformation)
   at Unify.Framework.ConnectorGenerator.CreateComponent(IConnectorGeneratorInfo
rmation factoryInformation)
   at Unify.Framework.PollingConnectorEngineConfigurationFactory.CreateConnector
ConfigurationBase(XElement xmlConfiguration, IConnectorHelper connectorHelper, I
Timing pollingTiming, INotificationMessageService messageService, ITiming getAll
EntitiesTiming, IConnectorGroup connectorGroup)
   at Unify.Framework.PollingConnectorConfigurationFactoryBase`2.CreateComponent
(IConnectorConfigurationFactoryInformation`1 factoryInformation)
   at Unify.Framework.PlugInGeneratorBase`4.CreateComponent(TFactoryInfo factory
   at Unify.Framework.ConnectorConfigurationGeneratorBase`4.CreateConnectorConfi
gurationFromNode(THelper connectorHelper, XElement connectorNode, TConnectorConf
igurationCollection connectorConfigurationCollection, IConnectorGroup connectorG
   at Unify.Framework.ConnectorConfigurationGeneratorBase`4.CreateConnectorConfi
gurationCollection(XElement xmlCollection, THelper connectorHelper)
   at Unify.Framework.ConnectorEngine.Initialize()
   at Unify.Framework.UnifyEngine.Initialize()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\M
icrosoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure lo
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fus

   --- End of inner exception stack trace ---
   at Unify.Framework.UnifyEngine.Initialize()
   at Unify.Services.Connect.Debug.ProgramProxy.Execute()

I thought that the core files are somehow wrong version thus I uninstall Identity Broker Service v3.0.5.6 and re-install it. The problem persist.

Any advise or assistant on how to resolve this issue would be much appreciated.

Thank you.

This looks like a file version problem.

Uninstall all the Unify components. Ensure the "Program File\UNIFY Solutions" directory is empty, and reinstall all the components.

Make sure you copy your configuration files before uninstalling.

Thanks Rodney.

I was hoping to avoid this level of restoration.

For now I will look at restoring my VMWare image to a particularly snapshot instead. And perform minimal updates.

This is fixed, new UNIFY Identity Broker for Frontier chris21 v3.0.5.2 installer at:


Hi Rodney,

I believe you may have updated the wrong issue for this fix.

Unless I am mistaken this latest release fixed the upgrade issue I encountered in IDBCHRS-13 with the Synchronise Import and Full Import no longer working?

Or does this version now allows downgrading without the binary file version issue?


Re-open and re-assign for clarification.

I can't guarantee any downgrading, but this version will fix all outstanding issues (9, 12, 13, 14).

Thanks Rodney!

I will verify it now.

Much appreciated your time and help!

Not Test this latest build version for downgrading.

However, I have tested with a previous build version of Identity Broker for chris21 v3.0.5.2 downgrading to version 3.0.5 successfully.

Thus will close this issue unless it re-surface at other times.

Issue resolved. Closed.