This is a heads-up to Microsoft and anyone planning on deploying the latest Update 1.25.
On patch tuesday 14th of february Microsoft released Service Update 1.25 for Microsoft Dynamics CRM (on-premises) 9.1/ for on-premise deployments under KB5035110 (v9.1.25.17)
I noticed yesterday when checking that this update was gone but today(29th of february) a new release of this update was available KB5035110 (v9.1.25.19).
As I usually do when new updates are available I install and verify them in my test environment, which I did with the first released update of Update 1.25 without any errors or issues during install or with the environment post install.
However I today tried this new released version and basically nothing is working, e.g. AsyncService is crashing on start along with the Dynamics 365 Web(w3wp).
They throw the following error
AsyncService:[2024-02-29 19:47:11.903] Process:CrmAsyncService |Organization:00000000-0000-0000-0000-000000000000 |Thread: 6 |Category: Platform.Async |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: 00000000-0000-0000-0000-000000000000 |ActivityId: 184d692b-932f-45e7-9458-26e6e0b8dae0 | AsyncService.StartServiceComponents ilOffset = 0xB
>Exception while starting async service: MSCRMAsyncService - System.TypeLoadException: Could not load type 'Microsoft.Xrm.RemotePlugin.Client.Config.ClientRoleType' from assembly 'Microsoft.Xrm.RemotePlugin.Common, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
> at Microsoft.Xrm.RemotePlugin.CrmProvider.Client.SandboxCrmProviderAutofacModule.Load(ContainerBuilder builder)
> at Autofac.Module.Configure(IComponentRegistry componentRegistry)
> at Autofac.ContainerBuilder.Build(IComponentRegistry componentRegistry, Boolean excludeDefaultModules)
> at Autofac.ContainerBuilder.Build(ContainerBuildOptions options)
> at Microsoft.Xrm.Kernel.Composition.CompositionRoot.Compose()
> at Microsoft.Crm.Asynchronous.AsyncService.StartServiceComponents(Object state) Exception: System.TypeLoadException: Could not load type 'Microsoft.Xrm.RemotePlugin.Client.Config.ClientRoleType' from assembly 'Microsoft.Xrm.RemotePlugin.Common, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
> at Microsoft.Xrm.RemotePlugin.CrmProvider.Client.SandboxCrmProviderAutofacModule.Load(ContainerBuilder builder)
> at Autofac.Module.Configure(IComponentRegistry componentRegistry) +0x21
> at Autofac.ContainerBuilder.Build(IComponentRegistry componentRegistry, Boolean excludeDefaultModules) +0x51
> at Autofac.ContainerBuilder.Build(ContainerBuildOptions options) +0x1e
> at Microsoft.Xrm.Kernel.Composition.CompositionRoot.Compose() +0x10c
> at Microsoft.Crm.Asynchronous.AsyncService.StartServiceComponents(Object state) +0xb
W3WP:Process information:
Process ID: 6488
Process name: w3wp.exe
Account name: XXXXXXXXXXXXX (masked)
Exception information:
Exception type: HttpException
Exception message: Could not load type 'Microsoft.Xrm.RemotePlugin.Client.Config.ClientRoleType' from assembly 'Microsoft.Xrm.RemotePlugin.Common, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
at System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app)
at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)
Could not load type 'Microsoft.Xrm.RemotePlugin.Client.Config.ClientRoleType' from assembly 'Microsoft.Xrm.RemotePlugin.Common, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
I have checked and this Microsoft.Xrm.RemotePlugin.Common.dll was updated in the latest release v9.1.25.19 .
I've tried both replacing it with the one from prior release v9.1.25.17, that throws a new error.
I've also ran a repair on the Dynamics 365 installation for good measure but yeah, same error which sort of was expected.
I hope this reached someone in the D365 team at Microsoft, but for anyone planning on upgrading to the latest Update 1.25 I'd suggest you hold for a bit.
613
Share
Report
All responses (
Answers (
