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

Announcements

Introducing our New Video Series: Community Spotlight
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Complier Error: Gettin...
Microsoft Dynamics AX (Archived)

Complier Error: Getting missing file error Dynamics.AX.SourceDocumentation.Queries.0.netmodule

(0) ShareShare
ReportReport
Posted on by Michael Morin

I am getting the error below when a client is trying to install our Model file:

Abnormal termination with unhandled exception. Exception key: aee55154-bd8e-4f6c-a3c1-78080dfafc59. System.IO.FileNotFoundException: Could not find file 'J:\AosService\PackagesLocalDirectory\VPEDIAX7\bin\Dynamics.AX.SourceDocumentation.Queries.0.netmodule'.

The Model compiles fine on my Dev system, and that file is not in the folder.

Since the update to the model I changed some Entities by removing them then added some Views/Queries so I could do Unions rather than have 3 different entities. 

I don't believe I am doing anything special in my objects. Everything is pretty vanilla. Can someone point me in the right direction?

*This post is locked for comments

I have the same question (0)
  • Martin Dráb Profile Picture
    Martin Dráb 238,624 Most Valuable Professional on at

    How are you "installing your model file"? What do you mean by a model file in the first place? Does it mean that you have copied the model folder (including all files) and the model descriptor file from your Dev box?

    You're clearly not talking about a deployable package, because it contains already compiled code.

  • Michael Morin Profile Picture
    Michael Morin on at

    I'm using ModelUtil.exe -export -metadatastorepath="J:\AosService\PackagesLocalDirectory" to generate an *.axmodel file. Sorry I'm a bit green. That model file is being sent to the client.

  • Martin Dráb Profile Picture
    Martin Dráb 238,624 Most Valuable Professional on at

    Aha, I see. So does it fail when running ModelUtil.exe -import or at some later point?

  • Michael Morin Profile Picture
    Michael Morin on at

    No. The import works fine. It is when they try to build the Model.

  • Martin Dráb Profile Picture
    Martin Dráb 238,624 Most Valuable Professional on at

    One more question and I'll hopefully understand on which page we're.

    Do you use Dynamics AX > Build models... in Visual Studio? With Build referenced packages?

  • Michael Morin Profile Picture
    Michael Morin on at

    Yes but with no build references.

  • Michael Morin Profile Picture
    Michael Morin on at

    Hi Martin,

       I am now able to get the error on my dev system but I'm still not sure what it is. It happens in VS when I right click the project and Build. I get the following errors messages that lead into the error. Hopefully that helps a bit. Could there be some problem with the labels?

    Dynamics AX build started 11/01/2016 19:47.

    Dynamics AX build step: Metadata validation started.

    Dynamics AX build step: Metadata validation completed (635 ms).

    Dynamics AX build step: X++ compilation, label generation and resource deployment started.

     : Compilation failed.

    J:\AosService\PackagesLocalDirectory\VPEDIAX7\VPEDIAX7\AxReference\Dynamics.AX.SourceDocumentation.xml(0,0):  AssemblyFileNotFound: Assembly 'Dynamics.AX.SourceDocumentation, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' failed to load because it was not found.

    J:\AosService\PackagesLocalDirectory\ApplicationSuite\Foundation\AxReference\Microsoft.Dynamics.AX.ManagedInterop.xml(0,0):  AssemblyFileNotFound: Assembly 'Microsoft.Dynamics.AX.ManagedInterop, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' failed to load because it was not found.

    J:\AosService\PackagesLocalDirectory\ApplicationPlatform\ApplicationPlatform\AxReference\Microsoft.OData.Edm.xml(0,0):  AssemblyFileNotFound: Assembly 'System.Xml, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e' failed to load because it was not found.

    J:\AosService\PackagesLocalDirectory\VPEDIAX7\VPEDIAX7\AxDataEntityView\EDIPurchaseOrderLineEntity.xml(0,0):  UnhandledException: Abnormal termination with unhandled exception. Exception key: 17a7059d-e059-4926-90a5-461bbe26c523. System.IO.FileNotFoundException: Could not find file 'J:\AosService\PackagesLocalDirectory\VPEDIAX7\bin\Dynamics.AX.SourceDocumentation.Queries.0.netmodule'.

    File name: 'J:\AosService\PackagesLocalDirectory\VPEDIAX7\bin\Dynamics.AX.SourceDocumentation.Queries.0.netmodule'

  • Chris Roehrich Profile Picture
    Chris Roehrich 289 on at

    Does your model need a reference to the SourceDocumentation package?  Just a guess based on the error message.  I was getting similar errors on my project until I made a reference to several more packages that apparently my project needed.

  • Martin Dráb Profile Picture
    Martin Dráb 238,624 Most Valuable Professional on at

    It seems that some assemblies, namely 'Microsoft.Dynamics.AX.ManagedInterop and System.Xml failed to load. I would try a few things:

    1. Make sure that you run Visual Studio as administrator.
    2. Build your model including referenced packages.
    3. Build Application Suite model alone to see whether it's something wrong there or not.
    4. Consider using Assembly Binding Log Viewer to understand why the assemblies can't load.
  • Michael Morin Profile Picture
    Michael Morin on at

    I had a friend get on with me. Turns out the error was coming from a project that I thought I had deleted the other day. Apparently the *.xml files were still sitting in the PackagesLocalDirectory\VPEDIAX7\VPEDIAX7\AxDataEntityView folder. However the VS project and objects (Entities) were no longer in my solution and the project could not be imported from the export I had made. We manually deleted the xml for the objects (Entities) in question and that corrected the issue.

    Still the original problem remains with the deleted project, but I'm not sure how much time I will spend digging into it. I am going to redo the project I deleted, in increments. This way if I find the issue again I will have a better hint at what I am doing that causes it. I can only say that the Entity I deleted, that was causing this issue, was very large, with a lot of joins and logic. To the point that dropdowns were taking 1 minute to appear. I will build it in a more modular fashion and see if I have more luck.

    Thank-you for your time Martin. It is greatly appreciated.

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

Introducing our New Video Series: Community Spotlight

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 > 🔒一 Microsoft Dynamics AX (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans