Management Reporter 2012 CU 13 Now Available!


Management Reporter 2012 CU13 has been posted for download. This release contains quality fixes as well as a number of regulatory features.

Here’s a summary of the new Management Reporter CU13 features:

  • View a report in the web viewer in a grid view
  • Display zero rounded values and zero actual values based on a report definition option
  • Choose where the line number column displays on a report
  • Display date formats in the report header based on regional settings
  • Display calculated rows on the same line for different columns
  • Report on closing transactions for Microsoft Dynamics AX 2012
  • Additional fixes for product defects

In addition to the new features, there has also been a number of changes made to installation and configuration.

  • With Management Reporter 2012 CU13, we have also removed the licensing checks within Management Reporter. All of the Microsoft Dynamics ERPs now support an unlimited licenses model, and we've decided to stop checking for licensing within Management Reporter. If you are not yet on an unlimited license plan, please ensure you stay compliant on your number of users.
  • Microsoft PowerShell 3.0 or later is now a required prerequisite on Management Reporter server machines
  • Changes were made to the database schema. If you had existing queries or scripts, they may need updating
  • Microsoft SQL Server 2005 is no longer supported

For Microsoft Dynamics SL customers, the option to create new legacy integrations has been removed. Existing installations using the legacy connector will work, but you will no longer be able to create new legacy integrations. Customers using the legacy integration should plan to migrate to the data mart.

For Microsoft Dynamics GP 2010 customers, this will be the last supported release.

Known Issues

8/5/2015 - Bug 3660417 - Web Viewer missing scroll bar for reporting tree units. If you use the web viewer and use reporting trees, you may need to use the desktop viewer until this bug is resolved. Download the Re-release of MR CU13 to resolve.

8/26/2015 - Bug 3669431 - "Sequence contains no elements" error occurs on Companies to Company task with CU13. Open a support ticket to get assistance in updating the correct values in the ControlCompanyIntegration table in the ManagementReporter database.

Version Information

Management Reporter CU13 RTM - 2.12.13001.13

Management Reporter CU13 Re-Release 2.12.13002.1

You can view which ERP versions are supported by this release by reviewing our compatibility list here.

 

You can find the download for Management Reporter CU13 here: https://mbs.microsoft.com/customersource/northamerica/MR/downloads/service-packs/MROverview Please note that at the time of this posting the en-us version is available for download; all other versions will be available in the next two days.

Comments (22)

  1. Marc K says:

    Since you're dropping support for GP2010, please bring out hotfixes for any serious or highly visible bugs that are found in CU13 instead of waiting for CU14.  (Such as the bug introduced in CU11 that causes an error message to be displayed every time a generator user closes a report.)

    If you are going to deny future releases to GP2010 users (which doesn't go EOL until 2020), please make their last release a good and reliable one.

  2. Marc K says:

    I ran into a problem updating from CU12 to CU13.  Because of past data integrity problems I reset the data mart when installing a new update.  During the initial integration, the status would reach "Please wait while the Configuration Console finalizes the integration", but it would never actually finish.  In the log I would find:

    Caught Exception: [Microsoft.Dynamics.Integration.Service.Tasks.RecordException] Sequence contains no elements

    Stack trace:

    Inner Exception: [System.InvalidOperationException] Sequence contains no elements

    Stack trace:

      at System.Linq.Enumerable.First[TSource](IEnumerable`1 source)

      at Microsoft.Dynamics.Performance.Integration.Reporting.Adapter.CompanyProvider.InsertCompany(IntegratedCompany item)

      at Microsoft.Dynamics.Performance.Integration.Reporting.Adapter.CompanyProvider.WriteObject(Object value)

      at Microsoft.Dynamics.Integration.Service.Tasks.RecordWork.DoRecordWork(DbMap map, Object key, OperationType operationType, String loggingSourceName)

    Ultimately, I found that records for the already configured companies were missing from Reporting.ControlCompanyIntegration.  After adding in the expected records, I reset the data mart once again and it completed the initial integration.

  3. Torben Hildebrandt says:

    Marc Ks statement of July 31. about not waiting for CU14 if serious or highly visible bugs are found, is very important. We as partners can not base our customers reporting on a tool that we cannot customize / fix, as they and we are used to with AX.

  4. Frustrated User says:

    Mark K, what values should be in the Reporting.ControlCompanyIntegration table?  I have the exact same issue and cannot find what data should be in this table.  thx

  5. Marc K says:

    For me, it was:

    ID = Reporting.ControlCompany.ID

    SourceID = 2

    If you want to test, you could add a new company to GP and then to MR.  This problem only occurs with existing companies already set up for MR.

  6. Tom W says:

    I subscribe to this blog and would like to be notified when something like a Known Issue is inserted. My partner and I have been scratching our heads all day over Bug 3660417. Waiting a few weeks for a hotfix is totally unacceptable. We have fiscal end of year reports to distribute asap. We went to CU13 right away to fix Bug 3602093 in CU12, and now you've broken something that already worked. Thankfully, other comments here may resolve our Adapter problems as well. What should normally take 30-45 minutes, has already taken over 3 days to install CU13.

  7. Marc K says:

    @Tom W: Be happy a hotfix is scheduled for release in a couple of weeks.  Some bugs in CU11 and CU12 had to wait months before they were resolved in CU13.  

    Again, bug 3660417 shows that Q/A of Management Reporter is really poor.  This should have easily been caught.  Ryan, please post a public statement that MR Q/A is going to be revamped and more (high quality) resources are going to be devoted to it.

  8. Paul H says:

    Follow up to the fix from Marc K, the SourceID column should tie to a source in Reporting.ControlIntegrationSource.

  9. UMESH PANDIT says:

    I Un-Installed Management Reporter 2012 CU12 and Installed Management Reporter 2012 CU13, its working like butter!

  10. Vinod SM says:

    I had installed Management Reporter CU 13 after slip streaming it with AX 2012 R3 CU 9 installation files. The installation failed to automatically create a Data Mart database but was successfully able to deploy the same manually via Configuration Console and the integration also did work. But the menu for punching in the license on Report Designer  (Tools>License Information) is missing. Has anybody dealt with a similar issue if so how did you get it sorted out ?

  11. Marc K says:

    Vinod SM,

    The answer to your question is in the blog post.

  12. Hi Ryan,

    Are you aware of security issues with the DM connector ? I've ran a fresh new installation of MR 2012 CU13 on my GP 2015 Test server and cannot set a default company (I'm sysadmin all the way around the SQL and GP server where MR is installed).

    I set my GP companies to 'visible' in MR2012 and they do show up in the MR designer, but at first launch it wants me to set a default company, which fails with the error "Unable to connect to the 'XYZ' company. You don't have access to this company"... which is a non-sense...

    Never had issues in the past on production with the Legacy connector, but the DM has been too unreliable for us to use it in production.

  13. Ryan,

    Here is another bug from CU13... As I could not connect with the DM connector to my GP companies, I uninstalled everything and restarted from scratch, this time selecting the Legacy Connector. I'm unable to install the  MR 2012 Application & Process services with the CU13... it gets into an endless loop during the install process and fails with some errors, not being able to connect the server, but the services never gets installed in the background.

    I restored my Database back to the original state and installed the current version of MR 2012 CU10, which worked just fine. The upgrade process took some time (about 20 min) but that's fine. I then upgraded the MR client in a breeze and everything seems to work.

    However, since this was a restored DB from a live system, the companies in MR are still pointing to the production system... they cannot be deleted, as MR claims they are used in report definitions... How can you switch easily one MR config to another server ? I've tried to edit the tables ControlCompany, ControlConfiguredIntegration & ControlIntegrationSource to point to the new server, but I keep getting an error "The operation could not be completed due to a failure on the server".

  14. Found the solution to my 'failure from server' in previous reply.. There seems to be script that needs to be run against the MR2012 DB when moving to a different server.. credendtial & master pwd problem 馃檪

    mbs.microsoft.com/.../ManagementReporter12_en

    Curiously this was published for DYnamics SL, but seems to apply equally for GP.

  15. Mariano Gomez, MVP says:

    This CU messed up my client's environment. I have spent countless hours trying to get a few reports that were working prior to this update to work again. I have now gone as far as applying the hotfix and just minutes ago re-restored the MR database itself to run the update again. If this doesn't work now I'm going to have to rollback the update. Grrrr!

  16. Adding one more known issue for "sequence contains no elements" for companies to company task. We haven't been able to reproduce this without a step including manually deleting a record from the ControlCompanyIntegration table, but it seems a few folks are hitting this. If you are encountering this error, you can contact support for assistance with resolving via a SQL update.

    @Beat and @Mariano - can you click on email blog author and send me an email with your contact information? We haven't seen either of these issues so would appreciate more specific details.

  17. Matt V says:

    Upgraded to CU13 and had a few issues along the way but recreating the DM fix most of those.

    Everything was working fine but now when I try to connect to the Configuration Console it just crashes. Event viewer has this stack:

    System.Diagnostics.Eventing.Reader.EventLogException: The array bounds are invalid

      at System.Diagnostics.Eventing.Reader.EventLogException.Throw(Int32 errorCode)

      at System.Diagnostics.Eventing.Reader.EventLogReader.GetNextBatch(TimeSpan ts)

      at System.Diagnostics.Eventing.Reader.EventLogReader.ReadEvent(TimeSpan timeout)

      at Microsoft.Dynamics.Performance.Deployment.Reporting.ServiceLoggingViewModel.<.ctor>b__1(Object doesntMatter)

      at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

      at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

      at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()

      at System.Threading.ThreadPoolWorkQueue.Dispatch()

    I've seen this blogged a couple of time but nothing fixed it.

    Also, some reports using Report Tree Definitions that use to take 5minutes to run now don't seem to end, or eventually times out or crahses. It went all the way to completely filling the tempdb on my SQL server and crashing once it was full...

    Any help would be appreciated...

    1. SheilaJR says:

      Do you have any resolutions to the tempdb growing so large? I am having the same issue on a client running CU11 and their tempdb has grown up to 60GB and filling their data drive. Took about 5 months to grow that large. The DM database is about 2GB in size. Really need to resolve so that it doesn't happen again.
      Thank you,
      Sheila

  18. Mitch M says:

    So what is the best version to currently be on? It seems like there have been a string of releases with major bugs. CU10 most stable?

    I'm currently having an issue where the ControlCompanyIntegration table has no records and would love to add records to match the ControlCompany table, however there are also no records in the ControlConfiguratedIntegration table (which is where I'm guessing the SourceID comes from) so I can't manually insert records . . .

    Sigh.

  19. Matt Vail says:

    FWIW... If your Configuration Console crashes at startup with the error "System.Diagnostics.Eventing.Reader.EventLogException: The array bounds are invalid" in the event viewer..., you can try clearing your event viewer log. This seems to have temporarily fixed some of my issues.

    Start->Administrative tools->Event Viewer

    Goto: Windows Logs->Application

    On the right hand side, there's a "Clear Log..." button.

    This will delete everything, not just the MR events.

  20. Rob Klaproth says:

    Ryan, as a longtime supporter and evangelist of the GP product line, I am extremely concerned about the lack of quality lately with the Management Reporter product.  It sure does make FRX look like gold.  It's such a shame that the QA team did not notice that the scroll bar was missing from the tree view in the web browser, so now a hotfix is needed to fix that.  Please escalate to the higher ups that this product needs a MUCH BETTER QA TEAM.  

  21. Error to open or design a report in spanish version (es-es) says:

    When try to opena any report...

    TableLayoutPanel cannot expand to contain the control, because the panel's GrowStyle property is set to FixedSize.

    and then the design close with the nex messagge.

    Firma con problemas:

     Nombre del evento de problema: CLR20r3

     Firma del problema 01: ReportDesigner.exe

     Firma del problema 02: 2.12.13002.1

     Firma del problema 03: 55f0469a

     Firma del problema 04: System.Windows.Forms

     Firma del problema 05: 4.0.30319.34250

     Firma del problema 06: 54d46da6

     Firma del problema 07: 4edc

     Firma del problema 08: 58

     Firma del problema 09: System.ArgumentException

     Versi贸n del sistema operativo: 6.3.9600.2.0.0.16.7

     Id. de configuraci贸n regional: 2058

     Informaci贸n adicional 1: 0237

     Informaci贸n adicional 2: 0237e53c8c871e04e5ef7eecb399bc49

     Informaci贸n adicional 3: ea6c

     Informaci贸n adicional 4: ea6cb32c66b33c882182acdcc8efe05a

Skip to main content