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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Failed to write runtime metadata to disk.

(0) ShareShare
ReportReport
Posted on by 2,720

I have created extensions for SRSPrintDestinationSettingsForm, SRSPrintDestinationSettings class and other elements of reporting framework in my solution. I'm getting below error while building the solution. 

Failed to write runtime metadata to disk. The exception was: 'Unable to read metadata. Offset for element 'AssetTaxStatistic' is beyond the end of file 'J:\AosService\PackagesLocalDirectory\ApplicationSuite\bin\ApplicationSuite_AxReport.md'.'

I have also tried running the full build. Then i'm getting below error. 

Unable to read metadata. Metadata file 'J:\AosService\PackagesLocalDirectory\ApplicationSuite\bin\ApplicationSuite_AxReport.md' is corrupted.

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Basheer17 Profile Picture
    2,720 on at

    I have been working on this solution from many days, it was the first time I encountered this issue.

    I don't know what caused this error, below are the steps i followed to resolve this issue.

    1. I have taken the backup of corrupted file, deleted it from the Bin directory.

    2. Then I’ve run a full build, I didn’t get any error, I’ve also checked the Bin directory it has created the .md file for me but it              was of 1MB size, actual file was of 200MB+ size.  

    3. Then I have tried to open a report from UI, I got “We’re working on it” message.

    4. Created a new project in my custom model (Application Suite package), added all reports to my project by Right click > Customize. I’ve done this because all reports reside in Application Suite model (In custom models if we do any customizations).

    5. I’ve done build on my new project, now the .md file’s size has changed to 200MB+.

    6. After deploying all reports using powershell script I was able to view all the reports

    7. (Optional) do a full build if you aren’t able to view the reports after steps 5 & 6.

    8. Finally deleted all the customized reports from my new project, and deleted the project as well

    Alternate option would be copy the corrupted file from a newly deployed VM, then continue from step 6.

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

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

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans