
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-31-2017 09:41 AM
Hello all,
We are integrating SCOM 2016 with event management and have the following error:
Connection test failed: Error running SCOM client:
Unhandled Exception: System.BadImageFormatException: Could not load file or assembly 'Microsoft.EnterpriseManagement.OperationsManager, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
File name: 'Microsoft.EnterpriseManagement.OperationsManager, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
at SCOMClient.Program.Main(String[] args)
We did made the steps from this doc
But can't fix the error.
Any idea?
Thanks,
Ariel
Solved! Go to Solution.
- Labels:
-
Event Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-02-2017 10:15 AM
Hello All,
We do it.
The trick is use .dll SCOM 2012 version to connect to 2016 SCOM version.
The .dll are:
- Microsoft.EnterpriseManagement.Core.dll
- Microsoft.EnterpriseManagement.OperationsManager.dll
- Microsoft.EnterpriseManagement.Runtime.dll
And the version: 7.5.3070.0
We found it in a SDK downloaded from MS page.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2018 01:32 AM
Seems like you uploaded the wrong files or something. Copy the files fresh from the SCOM server, and then try removing all the attachment and attach them again.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2018 09:16 PM
I copied back the dlls from the scom server and updated the JAR files and it is working now.
Thanks.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2018 03:49 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2018 09:16 PM
Thanks Arielgritti.
It worked with the 2016 dll but changed the version value to 2012

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-10-2018 11:44 PM