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

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Build error - Serialization version mismatch detect, Version of file 209. Version of dll 208

(1) ShareShare
ReportReport
Posted on by 66
Hi experts,
 
I am trying to build my package and build failed with following error:
I have checked on Build server, when performing DB sync on build machine I am getting the same error.
 
To fix this issue (On build server) I tried to stop service SQL reporting, stop iis , refresh model, full build (with custom models), and sync database but it not work. Message Error : Serialization version mismatch detect, make sure the runtime dlls are in sync with the deployed metadata. Version of file '209'. Version of dll '208'.
 
I found one blog where they suggested solution : Serialization version mismatch detect, make sure the runtime dlls are in sync with the deployed metadata. Version of file '209'. Version of dll '208.
But not sure how and where to check DLL as per above solution.
 
 
Build error:
Error during AOS update: Exception calling "CreateRuntimeProvider" with "1" argument(s): "Serialization version mismatch detect, make sure the runtime dlls are in sync with the deployed metadata. Version of file '209'. Version of dll '208'."
 

Exception             : System.Management.Automation.MethodInvocationException: Exception calling

                        "CreateRuntimeProvider" with "1" argument(s): "Serialization version mismatch detect, make sure

                        the runtime dlls are in sync with the deployed metadata. Version of file '209'. Version of dll

                        '208'."  Microsoft.Dynamics.AX.Metadata.Storage.MetadataReadException: Serialization

                        version mismatch detect, make sure the runtime dlls are in sync with the deployed metadata.

                        Version of file '209'. Version of dll '208'.

                           at Microsoft.Dynamics.AX.Metadata.Storage.RuntimeDeserializer.DeserializeObject(BinaryReader

                        reader) in D:\dbs\sh\l23t\0413_191000\cmd\0\Source\Kernel\Metadata\Metadata.Storage\Runtime\Runt

                        imeDeserializer.cs:line 22

                           at Microsoft.Dynamics.AX.Metadata.Storage.Runtime.RuntimeModelManifestProvider.Cache..ctor(ID

                        ictionary`2 archives, RuntimeProviderConfiguration configuration) in D:\dbs\sh\l23t\0413_191000\

                        cmd\0\Source\Kernel\Metadata\Metadata.Storage\Runtime\RuntimeModelManifestProvider.cs:line 328

                           at

                        Microsoft.Dynamics.AX.Metadata.Storage.Runtime.RuntimeModelManifestProvider..ctor(IDictionary`2

                        archives, RuntimeProviderConfiguration configuration, Boolean ignoreStrictSetting) in D:\dbs\sh\

                        l23t\0413_191000\cmd\0\Source\Kernel\Metadata\Metadata.Storage\Runtime\RuntimeModelManifestProvi

                        der.cs:line 74

                           at Microsoft.Dynamics.AX.Metadata.Storage.Runtime.RuntimeMetadataProvider..ctor(RuntimeProvid

                        erConfiguration configuration, Boolean extensions, ExtensionLoader`1 formExtensionLoader,

                        ExtensionLoader`1 tableExtensionLoader, ExtensionLoader`1 enumExtensionLoader,

                        ExtensionLoader`1 menuExtensionLoader, ExtensionLoader`1 securityRoleExtensionLoader,

                        ExtensionLoader`1 securityDutyExtensionLoader, ExtensionLoader`1 dataEntityViewExtensionLoader,

                        ExtensionLoader`1 edtExtensionLoader, ExtensionLoader`1 viewExtensionLoader, ExtensionLoader`1

                        querySimpleExtensionLoader, ExtensionLoader`1 menuItemDisplayExtensionLoader, ExtensionLoader`1

                        menuItemActionExtensionLoader, ExtensionLoader`1 menuItemOutputExtensionLoader,

                        ExtensionLoader`1 workflowTemplateExtensionLoader, ExtensionLoader`1

                        workflowTaskExtensionLoader, ExtensionLoader`1 workflowApprovalExtensionLoader) in D:\dbs\sh\l23

                        t\0413_191000\cmd\0\Source\Kernel\Metadata\Metadata.Storage\Runtime\RuntimeMetadataProvider.cs:l

                        ine 254

                           at Microsoft.Dynamics.AX.Metadata.Storage.MetadataProviderFactory.CreateRuntimeProvider(Runti

                        meProviderConfiguration configuration) in D:\dbs\sh\l23t\0413_191000\cmd\0\Source\Kernel\Metadat

                        a\Metadata.Storage\MetadataProviderFactory.cs:line 151

                           at CallSite.Target(Closure , CallSite , Object , Object )

 
 
 
 
 
 
I have the same question (0)
  • Martin Dráb Profile Picture
    238,127 Most Valuable Professional on at
    It sounds like if you have a binary module in source control that's been built on a higher F&O version than what you have on your build server. Can't it be the case?
     
    When did it start failing? Did the build server worked but it started failed after a recent change? If so, what was the change?
  • VK-05090405-0 Profile Picture
    66 on at
    Hi Martin
     
    Actually I was tried to upgrade my Build server from 10.0.38 to 10.0.40 but build was failed last week and
    I aborted my upgrade. Then I was trying to create build on earlier version 10.0.38 but build is failing with following error:
     
    "Serialization version mismatch detect, make sure the runtime dlls are in sync with the deployed metadata. Version of file '209'. Version of dll '208'."
     
    I can see still build version is on 10.0.38.
  • Martin Dráb Profile Picture
    238,127 Most Valuable Professional on at
    You seem to be saying that you that you need 10.0.40 to build your code but your build server don't meet these requirements and therefore it can't build your code. The solution is creating a build server on the right version.

    If you have a problem with the upgrade, simply deploy a new VM on 10.0.40.
  • VK-05090405-0 Profile Picture
    66 on at
    Hi Martin,
     
    Before try to upgrade my build server on 10.0.40, I was successfully able to build the package but last
    week I tried to upgrade my build server on 10.0.40 but upgrade got failed and aborted my 10.0.40 build server upgrade.
    Still my build server is on 10.0.38 but after abort I am getting following build error.
     
    Please suggest the solution to fix following version error 
     "Serialization version mismatch detect, make sure the runtime dlls are in sync with the deployed metadata. Version of file '209'. Version of dll '208'."
     
    Note: I tried to do full build on my build server but still exist.
     
  • Martin Dráb Profile Picture
    238,127 Most Valuable Professional on at
    If you really want to invest your time fixing the build server corrupted the attempted upgrade, the first step I recommend is deleting the modelstore backup. Inconsistency there with the actual F&O version can cause this error.
  • Suggested answer
    Anthony Blake Profile Picture
    2,975 Super User 2025 Season 2 on at
    Hi,
     
    Just deploy a new build box, it will also save you the hassle of clearing out the Dynamics Backup folders, and is good practice to do periodically anyway to ensure all the installed tools are up to date.
     
    Anthony

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

News and Announcements

Season of Giving Solutions is Here!

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 > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Abhilash Warrier Profile Picture

Abhilash Warrier 679 Super User 2025 Season 2

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 421 Super User 2025 Season 2

#3
Martin Dráb Profile Picture

Martin Dráb 282 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans