Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We just upgraded to 188.8.131.52 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=184.108.40.206, 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)"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 (220.127.116.11) 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?
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.
We are investigating this internally.
Will come back here with an update once we have any valuable information.
"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)
I can confirm the problem as well. Everything worth knowing has already been described by MyAmazingD365Name.
Thanks for the preliminary work!
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
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.
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
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) (v18.104.22.168->v9.1.9.X)
Thank you for all your comments here!
A new build was released:
Thank you again for your engagement!
Business Applications communities