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 :
Microsoft Dynamics GP (Archived)

Management Reporter regional option error

(0) ShareShare
ReportReport
Posted on by

I am suddenly receiving an error on certain companies when running existing reports.  The report fails with "The regional option for company 'XXXX' is not valid."  and "Bad or missing data was encountered while loading he report and it building blocks.  Report generation has been cancelled."

I have rebooted the server, rebuilt the Data Mart and checked everything else I can think of.  3 of 27 companies receive this error on every report, all others function normally.

 

The only thing that has changed is that I have added 5 new companies to get ready for 2016.  I created them on the live company.  I have since configured the same companies on a test server and backed them up and restored them on the live server.  The companies that receive the error are all long time existing companies tha have not been restored.

 

Upgraded MR to the latest CU in September.

 

Any ideas?

*This post is locked for comments

I have the same question (1)
  • Suggested answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on at

    For these new companies that you have created, did you enable visibility to management reporter in GP 2015 in the system settings ?

    Are you using multi currency?

  • Verified answer
    Community Member Profile Picture
    on at

    This is a known issue with CU13 and lower (3647752). To prevent the issue from occurring, upgrade to CU14:

    mbs.microsoft.com/.../MROverview

    To correct any bad settings which occurred prior to upgrading to CU14:

    1. Run this script against the ManagementReporter SQL database:

    select * from ControlCompany

    --If you are using CU13, the table name needs to be Reporting.ControlCompany.

    2. Note the CultureName field which is 2nd from last. You may see settings such as "chr-Cher-US'. You will need to correct the CultureName to a valid setting:

    update ControlCompany set CultureName = ‘en-US’ where Code = 'ABC'

    --If you are using CU13, the table name needs to be Reporting.ControlCompany.

    3. Restart Report Designer if it was open and try the reports again.

    The actual issue (3647752) flips the CultureName when making changes to the settings under Company -> Companies in MR. Upgrading to CU14+ should prevent it from changing again.

  • Syed Wajid Ali Profile Picture
    25 on at

    Thank you Really great time.. Save a lot of time .

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!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans