0
Not a bug

BadImageFormatException on service startup

Matthew Woolnough 2 years ago • updated by anonymous 2 years ago 4

Attempting new install of IdB 5.1 on Windows 2016. Installing Aurion connector 5.0.1 and trying to create the agent. The configuration section of the Agent is missing.

Error below is seen in logs:

20170502,22:32:16,UNIFY Identity Broker,Service Engine,Warning,"An error occurred whilst coordinating the plug-in engine. The error was:
System.BadImageFormatException: Could not load file or assembly 'file:///C:\Program Files\UNIFY Solutions\Identity Broker\Services\Unify.Service.Connect32.exe' or one of its dependencies. An attempt was made to load a program with an incorrect format.
File name: 'file:///C:\Program Files\UNIFY Solutions\Identity Broker\Services\Unify.Service.Connect32.exe'

How can I get the configuration section displayed so I can configure it?

Affected Versions:
Fixed by Version:

Answer

Answer

That gets logged with Verbose logging - there's nothing actually wrong. It may be fixed in v5.2.

To use v5.1 you'll have to install a v5.1.x connector.

Not a bug

Hi Matt,

Please download and install Identity Broker for Aurion v5.1.1 (currently RC1).

Answer

That gets logged with Verbose logging - there's nothing actually wrong. It may be fixed in v5.2.

To use v5.1 you'll have to install a v5.1.x connector.

Perhaps a prompt during install to ask the user if they are sure they want to proceed if there is a version mismatch, might be appropriate?

The Aurion, SP and MIM 5.1 Connectors appear to be in RC state & therefore not appropriate for production deploy. Is this correct?

It's the column "Identity Broker Version" on the download page.

Release Candidate is the stage that has been tested and the candidate for release. They get RTM'd when they are accepted by client(s). It's up to the client whether they'll accept something that hasn't been accepted by another client, some are more cautious than others.