web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Answered

On-Premise 9.1.9.5 Upgrade - Unsigned DLL Error

(3) ShareShare
ReportReport
Posted on by 25

We just upgraded to 9.1.9.5 and ran into the following issue. After the upgrade (before we even upgraded the organizations), the sites threw the following error:

"Exception information: Exception type: ConfigurationErrorsException Exception message: Could not load file or assembly 'Microsoft.Crm.UClient.MainClient, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)"

pastedimage1647387394232v2.png

After some research we discovered that MS apparently forgot to sign the DLL. Here is a comparison shot of the old (9.1.75) version and the new (9.1.9.5) version. You'll notice the entire Digital Signatures tab is missing from the new version (in addition, the old version is 13.8KB and the new is only 5KB)

We fixed it by copying over the old version and the sites seem to be working now (both the ones we upgraded in Deployment Manager and the ones we did not), but we haven't done extensive testing nor do we know what may not be working with the old DLL in place. Thankfully it's our dev environment and we aren't planning on upgrading our production environment anytime soon though. Anyone else run into this?

pastedimage1647387532879v3.png

pastedimage1647387383299v1.png

I have the same question (0)
  • Verified answer
    PhilipK Profile Picture
    613 on at

    Did see the same testing when deploying it yesterday.

    Worth mentioning I've checked that the file is unsigned in both the Swedish along with the English bits of the update so it's not simply a packaging flaw on the English one.
    Thus MS most likely have automated packaging flow for all languages so it is kinda expected.

    Other thing I also noticed along with the above was that Event Viewer no longer can load after the "Server" bits of the patch was deployed..
    I verified Event viewer twice(pre/post update) twice by reseting my VM.
    Even if I run my test env. on Windows Server 2022(unsupported) It's not unlikely this is a problem even if Windows Server 2016, but can't verify atm.

    So if anyone at Microsoft sees this post, I would strongly suggest this is raised.

    /Philip

  • Pedro Cadavez de Freitas Profile Picture
    on at

    Hello,

    We are investigating this internally.

    Will come back here with an update once we have any valuable information.

  • MyAmazingD365Name Profile Picture
    25 on at

    "Other thing I also noticed along with the above was that Event Viewer no longer can load after the "Server" bits of the patch was deployed.."

    Thanks. Just as a heads up, we are not seeing the issue with Event Viewer (Server 2016)

  • dieter.m Profile Picture
    25 on at

    I can confirm the problem as well. Everything worth knowing has already been described by MyAmazingD365Name.

    Thanks for the preliminary work!

  • PhilipK Profile Picture
    613 on at

    Good to get that confirmed, it might just be my environment and not even Windows Server 2022 in general..
    But as I know it's not officially supported OS the issue is something I will have to handle my self.

    I'll report back if my Event Viewer issue would magically get resolved as well once we have a solution for the orginal .DLL issue.

    /Philip

  • Pedro Cadavez de Freitas Profile Picture
    on at

    Hello All,

    I could repro on my W2016 environment, so it is not specific to any customer.

    I would ask to hold any investigation on your side, since the ball is on us currently.

  • Suggested answer
    Pedro Cadavez de Freitas Profile Picture
    on at

    Hello again,

    After engaging the responsible teams, it was confirmed that the workaround of replacing the dll with the old one  is the right approach for now, since that dll does not contain any logic.

    We posted anyway this information on the download page for 1.9

    support.microsoft.com/.../service-update-1-9-for-microsoft-dynamics-crm-on-premises-9-1-ac199135-707b-4a32-bc02-08250f03793d

    We will be deploying an updated version of that until the end of the week that customer in all situations can install (as it will be a higher build than the current one) (v9.1.9.5->v9.1.9.X)

    Thank you for all your comments here!

  • Suggested answer
    Pedro Cadavez de Freitas Profile Picture
    on at

    Hello All,

    A new build was released:

    support.microsoft.com/.../service-update-1-9-for-microsoft-dynamics-crm-on-premises-9-1-ac199135-707b-4a32-bc02-08250f03793d

    Thank you again for your engagement!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 74 Super User 2025 Season 2

#2
Daniyal Khaleel Profile Picture

Daniyal Khaleel 32 Most Valuable Professional

#3
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 31 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans