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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Adding Deployable Pack...
Finance | Project Operations, Human Resources, ...
Suggested Answer

Adding Deployable Package to Development VM D365

(0) ShareShare
ReportReport
Posted on by Dynamics 365 for fi... 25

I am trying to add a pre-developed customized package to our development virtual machine using the following command: 

AXUpdateInstaller.exe devinstall

But the following error continue to pops-up:

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 '181'. Version of dll '172'."

I searched over the internet and the only solution was to do full build from Visual Studio, however, the build ran successfully with no errors but still cannot add the packages.

I have the same question (0)
  • arkaitzv Profile Picture
    arkaitzv Microsoft Employee on at

    Hi Ahmed,

    You probably want to have a look to the following Yammer thread where this was discussed: [View:https://www.yammer.com/dynamicsaxfeedbackprograms/#/Threads/show?threadId=87670353313792:750:50]

    In short, this can happen if you have updated your dev box from the commandline using the devinstall switch. Instead, you need to follow the instruction described in this article https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/install-deployable-package#collect-topology-configuration-data

    Let me know if this helps you.

  • Suggested answer
    nmaenpaa Profile Picture
    nmaenpaa 101,166 Moderator on at

    To me it seems like your dev VM has older D365 version, than what is required for the deployable package. The target machine must have same or higher version than the build machine where the deployable package was created.

    What app/PU version do you have? "172" sounds old to me.

    I also think that Arkaitz's comment is not correct. Devinstall is exactly the right way to install AOT deployable package (= package that contains customizations). The other process (where you collect topology data and so on) is required for Microsoft updates.

  • arkaitzv Profile Picture
    arkaitzv Microsoft Employee on at

    You are right, I should have said DefaultTopologyData and not devinstall. Sorry for the confusion here.

    The yammer discussion that I referenced describes a situation where a customer updated their dev box from 8 to 10 but they didn't update the DefaultTopologyData file and ended up in a similar (if not the same) situation as described by Ahmed here which is surfacing after they deploy the custom code.

    It could very well be also what you say, but I think we need Ahmed to give us more details of this environment and how they came into this situation.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the January Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 576 Super User 2026 Season 1

#2
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 366

#3
Adis Profile Picture

Adis 256 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans