Service Manager
A family of System Center products for managing incidents and problems.
237 questions
We solved it for our SCSM 2022 using SMLets Exchange Connector.
SCSM Exchange Connector Issues on SCSM 2022
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 38%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELT%3C/text%3E%3C/svg%3E)
Lutz Timmy
6
Reputation points
Hello MS Support
Since the upgrade to SCSM 2022, the Exchange Connectore 4.1 no longer works correctly.
The connection to the server is not the problem, also the refresh interval does not cause any problems. But no emails are opened as tickets and the mails are not fetched from the mailbox.
Do you know this problem, or is this new?
Thanks in Advance
Timmy
4 answers
Sort by: Most helpful
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 13%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
Jonas Sjöstrand 6 Reputation points2023-01-03T13:43:41.91+00:00 -
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 48%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKS%3C/text%3E%3C/svg%3E)
K So 0 Reputation points2023-02-19T17:51:02.7066667+00:00 Exchange Connector: Unable to process email for , message=Could not load file or assembly 'Microsoft.Identity.Client, Version=4.38.0.0, Culture=neutral, PublicKeyToken=0a613f4dd989e8ae' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
This is the error we've seen occur on 3 test servers thus far. If anyone has a fix for the Exchange 4.1 SCSM connector it would be greatly appreciated.
-
K So 0 Reputation points
2023-02-19T18:13:05.1466667+00:00 Anyone have success with the 4.1 Exchange Connector on SCSM2022. Built 2 test servers and tried the Microsoft Hyper-V eval server and keep running into the same error.
Exchange Connector: Unable to process email for , message=Could not load file or assembly 'Microsoft.Identity.Client, Version=4.38.0.0, Culture=neutral, PublicKeyToken=0a613f4dd989e8ae' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Lot of folks are recommending using SMLetsExchange connector as an alternative but, it would be nice to see if anyone has had success with the 4.1 connector. Thanks!
-
K So 0 Reputation points
2023-02-20T20:35:29.9633333+00:00 Found a fix but, unfortunately not sure it can be used in production. Used gacutil.exe to import the assembly from the Microsoft Identity Client 4.38.0.* dll into the Global Assembly cache and emails started to flow. Hope Microsoft can incorporate this fix in a later update.
Rundown:
- Install VS Community Edition on server
- Unzip the Microsoft Identity Client 4.38.0.0_ nuget package.
- Open Developer Powershell for VS2022.
Run gacutil.exe /i Microsoft.Identity.Client.dll
- Verify email flow to O365 mailbox.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 43%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP1%3C/text%3E%3C/svg%3E)
PerserPolis-1732 1,841 Reputation points2024-08-27T12:59:56.4966667+00:00
Sign in to comment -
-
Simon Ren-MSFT 35,391 Reputation points Microsoft Vendor2022-05-17T08:31:12.617+00:00 Hi,
Thanks for posting in Microsoft MECM Q&A forum.
Maybe the troubleshooting guides are helpful:
https://tdemeul.bunnybesties.org/2021/06/troubleshooting-scsm-exchange-connector.html
https://www.pei.com/scsm-exchange-connector/
Please note: The links are not from Microsoft, just for your reference. Thanks for your time.Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. -
Jonas Sjöstrand 6 Reputation points
2022-12-22T10:55:31.003+00:00 We experience the same problem with the exchange connector since upgrading to SCSM 2022.
Did you find any solution to it?
-
K So 0 Reputation points
2023-02-20T20:33:49.9766667+00:00 Found a fix but, unfortunately not sure it can be used in production. Used gacutil.exe to import the assembly from the Microsoft Identity Client 4.38.0.* dll into the Global Assembly cache and emails started to flow. Hope Microsoft can incorporate this fix in a future update.
Rundown:
- Install VS Community Edition on server
- Unzip the Microsoft Identity Client 4.38.0.0_ nuget package.
- Open Developer Powershell for VS2022.
Run gacutil.exe /i Microsoft.Identity.Client.dll
- Verify email flow.
Office 365 Email Connector and app registration working as designed.