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 / Finance | Project Operations, Human Resources, ... / Diagnosing custom repo...
Finance | Project Operations, Human Resources, ...
Suggested Answer

Diagnosing custom reports "Something went wrong whilst generating the report" behaviour

(0) ShareShare
ReportReport
Posted on by RichHims 70

I've seen multiple threads covering this topic, and believe I've gone through the common resolutions (i.e. checking datasets & redeploying reports, full build & DB sync, restarting SSRS).  I've managed to debug through both my data provider CoC methods & the report controller event handler (examples of each below), and up to that point, everything appears to be fine, but when I expect to see the "Loading" spinning wheel of progress in the embedded SSRS report viewer, I instead see the Something went wrong message.  Other SSRS reports than the custom ones render onscreen OK, so I'm fairly sure it's something to do with the customisation.  I haven't been able to view the report server web interface to completely reassure myself that the reports are deployed (it's a Tier 1 environment, so no admin access), but I was getting the Unable to find report design FreeTextInvoice.ReportHRW (or similar) message earlier, so I'm confident the RDLS are there.

I can't see anything helpful in Event Viewer (the best I could get to is a Report viewer running exception event in Applications and Services Logs > Dynamics > AX-SSRSReportViewer > Operational, but that's very short on detail.  Given that I can debug through the extent of the custom code, can anyone please advise next steps of investigation?

I have the same question (0)
  • Suggested answer
    Pedro Tornich Profile Picture
    Pedro Tornich 955 on at

    In this kind of situation, usually I create a new custom report, as simple as possible. Containing only one text field that displays some text.

    Then I check if the new report renders, if it does I start throwing the other stuff in, like adding my custom DP, if it still works, then I start adding the design elements.

    In most cases I find out it's related to some design element property or expression error.

    You can also go the other way around by duplicating the problematic report and then you start by removing all design elements. Add only a text box to show some hard-coded text and try to run it. If it works you will know that your problem lies within the design elements.

    Sometimes, after recreating the entire report layout (while trying to find the culprit) the report just works. I can't explain, but it happens sometimes.

  • RichHims Profile Picture
    RichHims 70 on at

    Thanks Pedro.  Sadly, even a report with just a single textbox holding the report name (as plain text) gives me the same behaviour.  Will see whether a trace can help me, then may need to try removing the customisations to get back to a working state & slowly reintroduce them.  Any other suggestions welcome: I'll hope to report back with what I did.

  • Pedro Tornich Profile Picture
    Pedro Tornich 955 on at

    If you are not able to open a simple report with only one plain text field, then I might think you have an environment issue.

    You can check if it's an env problem by exporting the project to an axpp file and importing it into another dev env.

  • RichHims Profile Picture
    RichHims 70 on at

    I was thinking that other reports rendering successfully (e.g. Vendor aging, Customer transactions) meant that the environment is largely working, but I'll see whether I can find another development environment, thanks.  Given that I've taken the axpp & have the metadata in Azure DevOps as a backup, I've tried removing all of the customisations (deleting objects from within VS, then deleting the relevant package folder on disc before trying a full build of all models, a DB Sync, redeploying the baseline reports & an SSRS restart), and I'm still getting the "Something went wrong whilst generating report".  The full build did give me errors about missing label files, so I might have to look at raising a Microsoft Support issue, but it still feels very much like I need either more information on what the "something" is, and/or a clearer ability to re-baseline the metadata for the environment.

  • RichHims Profile Picture
    RichHims 70 on at

    For posterity, this appeared to be a configuration issue: the absence of Print management settings for the relevant module & form was, it seems, leading to the code identifying the correct report design (the "Processing operation" dialog confirms as much when attempting to render the relevant business document), but something in the SrsPrintManagementController breaking.  Surprising that there were multiple blog posts & threads discusssing custom business documents that didn't mention the need to have an appropriate form setup in place as well, but hopefully others may find this useful

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

#1
Martin Dráb Profile Picture

Martin Dráb 660 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

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

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 307 User Group Leader

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans