While trying to configure the legacy connector in Management Reporter 2012 recently I received an error message while the entered settings were being validated:
Validation Messages - Database configuration: The master password could not be validated against the password policy
Continue reading “Error Configuring The Management Reporter 2012 Legacy Connector”
A client recently logged an issue with Management Reporter producing an error when they tried generating a report. As is commonly the case, the error in the Queue Status window wasn’t terribly informative, but we did get a more detailed error when looking in the Windows Event Log:
Microsoft.Dynamics.Performance.DataProvider.Core.RequestException: The source system request did not complete successfully. ---> System.ArgumentOutOfRangeException: The length of the value is invalid. \r\nMinimum supported length: 1 \r\nMaximum supported length: 512
From the error message, we have an item which is the wrong length. I took a shot and guessed that the problem might be down to the budgets as I have seen corruption in client’s systems before which has caused problems with Management Reporter.
One quick select later confirmed that there was a corrupt record in the Budget Master (GL00200) table. I deleted this entry using the below code:
DELETE FROM
GL00200
WHERE
BUDGETID = ''
After which the client confirmed Management Reporter was able to generate the report successfully.
The Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.
The thirty third Feature of the Day is Management Reporter Data Integration. In Microsoft Dynamics GP 2015, the user can determine the data that is available to the Microsoft Dynamics Management Reporter DataMart, improving the performance and giving the user control over the data selected.
Â
The user can choose per company (including sample company) if they want the General Ledger data available for reporting.
Â
The user also has the ability to include or exclude Analytical Accounting data for each company:
I am slightly puzzled by this feature of the day as you can simply not import a company into Management Reporter if you don’t want to report on it. While I steer clients away from AA where possible, I am not entirely opposed to it, but I do wonder who would want to report on AA without also wanting to be able to report on the GL.
The roles targeted by this feature are:
The Inside Microsoft Dynamics GP blog has started a series of posts on the new features of, the soon to be released, Microsoft Dynamics GP 2015. As I have done for the last two releases, I intend to shadow these posts and add my own opinions on these new feature; the series index is here.
The twenty sixth Feature of the Day is Management Reporter in Business Analyzer.This features enables users to add Management Reporter content to the Microsoft Dynamics Business Analyzer app:
Continue reading “MDGP 2015 Feature of the Day: Management Reporter in Business Analyzer”
In this short series of posts, I’m going to take a look at upgrading an installation of Management Reporter 2012 to the latest Rollup. The series index can be found here.
Over the last three posts I covered the upgrade of the Management Reporter server and client components. If the components and database has been upgraded as covered in the posts then you should not see the error message shown below:
Management Reporter — Can’t connect to the Management Reporter server. Do you want to specify a different server address?This error is one seen at a client who had done the upgrade on the server and the majority of clients. But one user who had been on holiday that day hadn’t had their PC updated and wasn’t aware it had been done. So when they tried logging into Management Reporter they logged the issue.
A short client upgrade later and they were up and running without further problems.
In this short series of posts, I’m going to take a look at upgrading an installation of Management Reporter 2012 to the latest Rollup. The series index can be found here.
With the server fully upgraded we now need to upgrade all of the clients. To do this start the same setup.exe as used to upgrade the server components and select Management Reporter Client:
Continue reading “Upgrading Management Reporter 2012: Upgrading the Clients”
In this short series of posts, I’m going to take a look at upgrading an installation of Management Reporter 2012 to the latest Rollup. The series index can be found here.
In the previous post I covered the upgrade of the server components; in this one I’m going to finish the upgrade of the server which requires that the database also be upgraded.
To do this run the Configuration Console from the Windows Start screen; you’ll see a Task List in the bottom right corner of the window showing thre items:
Continue reading “Upgrading Management Reporter 2012: Upgrading the Database”
In this short series of posts, I’m going to take a look at upgrading an installation of Management Reporter 2012 to the latest Rollup. The series index can be found here.
The first step in upgrading Management Reporter is to update the server components. To do this download the latest Rollup from either PartnerSource or CustomerSource. Run the downloaded MSI and specify a path to extract the files into (by default the files will be extracted into the same folder as the MSI, so I typically create myself a folder called MR and extract the files into that:
Continue reading “Upgrading Management Reporter 2012: Upgrade the Server Components”
In this short series of posts, I’m going to take a look at upgrading an installation of Management Reporter 2012 to the latest Rollup.
The post will serve as the series index:
I have a number of clients who have been using Microsoft Dynamics GP for a number of years and who we are now upgrading again. A few of them continued using FRx when they upgraded to Microsoft Dynamics GP 2010, but now they are upgrading to Microsoft Dynamics GP 2013 they also need to switch to Management Reporter 2012 as FRx is not supported with the latest versions of Microsoft Dynamics GP.
Most of these migrations proceed without a problem, but I did have one client where the Migration Wizard ran through and returned a successfully completed message. However, when I logged into the Report Designer to check the migrated building blocks, I found that there was nothing there.
As a double-check, I re-ran the Migration Wizard to the same effects so I started to do some investigation. I eventually took a look in the FRx database and found a number of corrupt rows in the Catalog table like the one below:
