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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Cannot run some report...
Microsoft Dynamics AX (Archived)

Cannot run some reports after compiling all reports, should I recompile the AOT?

(0) ShareShare
ReportReport
Posted on by user5555 7,437

Hi,

I made some changes to the SalesPackingSlip report. By accident my cursor was on top of the reports in the AOT and so compilation started for all reports. I thought this would not be an issue. But now it seems some reports cannot be run anymore like 'LedgerTotalAndBalanceList' which is one of the reports we use most. It seems compilation did also not run succesfully for all reports. I think this is quite strange since compilation should not throw any errors at all.

I imported this report again to see if that would fix it (at least for that report). But unfortunately that is not true. Still 2 compilation errors: periodInterval : The enumeration does not exist. and same for yearToDate.

What can be the underlying issue of this? I was thinking of compiling the whole AOT..but maybe that is not such good idea after this experience.

J.

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at
    These errors should go of when you do a recompile again. Sometime Ax compiler fails to do a proper compilation until you do some small change like adding a comment or space and recompiling again. Might sound weird but works with us.. If you prefer a complete compile and still bothered about the time it takes, then switch compiler to "Message window" from Form and set diagnostic level to "No warnings". This will ensure your compilation goes lightning fast. Also disable BP checks if enabled.
  • Jag Profile Picture
    Jag on at

    Hi there,

     first of all stop your AOS and then delete the axapd.aoi file after that compile the whole application.

     Regards

     

    Jag

  • user5555 Profile Picture
    user5555 7,437 on at

    Hi,

    Thank you for the replies. I am doubting a bit. The DateFlags enum is missing after that compilation took place on all reports. I tried to look it up but I cannot find it. I restored a backup of my production before compilation to check if that enum would exist there. But it doesn't. The strange thing is that the backup of my production where I did not run that compilation still works on the report. What is BP deviation documented anyhow? The reports not working have the DateFlags in it and I read it is in SP1. I believed SP1 had been installed. How to check?

    //BP Deviation Documented
    display Name periodInterval()
    {
        return strfmt("@SYS54524", date2StrUsr(fromDate, DateFlags::FormatAll), date2StrUsr(toDate, DateFlags::FormatAll));
    }

    I found next 2 posts:

    http://blog.amer-ax.com/?p=244

    http://www.eggheadcafe.com/software/aspnet/33667269/dynamics-ax-2009-sp1--dateflags-issue.aspx

     Actually stating reinstalling the AOS or Client with SP1. Shall I try a compilation first?

    J.

  • Community Member Profile Picture
    Community Member on at
    Hi, I suggest you follow what amer has said in his blog. If it is a know issue. @BP Deviation documented This was a standard[Code security] introduced with Ax 4.0. The FileIOPermission, CodeAccessPermission all this were introduced along with this. The BP Deviation is to be applied on a display method when it has been verified for the risk of information disclosure. IF this is not done then the System records a BP error. You can refer to the document below for more information. http://download.microsoft.com/download/b/6/e/b6e77418-cde2-4ed4-a920-60d7f2d17757/Microsoft%20Dynamics%20AX%20Writing%20Secure%20X++%20Code.doc
  • Jag Profile Picture
    Jag on at

    This is to do with your client is not of the same version of your server. You might have applied SP1 on server but your client is not on SP1.

  • user5555 Profile Picture
    user5555 7,437 on at

    Hi,

    If I would be in charge of development I would throw some message/ warning if the versions would not match. In de test environment the reports still work with same AOS and same clients. However, in production after compilation not.

    How to check the versions?

    Kernel version: 5.0.593.0
    Application version: 5.0.1500.358

    J.

  • Jag Profile Picture
    Jag on at

    Hi,

    This is where your issue you have AX AOS running as AX2009 whereas your application in AX2009 SP1.

    Please update your AX AOS with SP1.

    You check the AOS and client version as follows:

    find AX32SERV.EXE on your AOS server and right click on it and select properties and you can see the version.

    find AX32.EXE on the machine where you have installed client and right click on it and select properties and you can see the version.

     Jag 

  • user5555 Profile Picture
    user5555 7,437 on at

    Hi,

    I think my client application is wrong since it has not the same version as the AOS. My partner did not give the client installation to us so I installed the client of the MSDN download. That version seems of older version: Kernel version: 5.0.593.0 where the AOS and the client installed on the server seem to have version: 5.0.1500.358.

    If I do click on about ..I get on my server 2 identical versions: 5.0.1500.358. I started a compilation on the server where both versions are similar. In this scenario compiling should run without any problems and the report issues should be gone. You agree that I should upgrade my client? I will check customer source if there is a SP1 download of the client software. I could not find it last time, so I will look again.

    For MS I would suggest to add an additional warning/ error messages if the assembly versions of aos and client do not match.

    J.

  • user5555 Profile Picture
    user5555 7,437 on at

    Hi,

    Thank you all for your input. This issue has been resolved by compiling the complete AOT on the server again using the similar client kernel version as the AOS.

    J.

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

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