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:
BUDGETID = ''
After which the client confirmed Management Reporter was able to generate the report successfully.
A client reported an error to our service desk recently when they were working with an Account Transactions SmartList which they were trying to filter to exclude a particular Account Category. When they entered the search criteria they received a string of error messages.
Microsoft Dynamics GPGPS Error: 58
I ws recently doing some work for a client, one part of which was to configure Microsoft Dynamics GP to duplicate creditors created in one company into another using the PM Master Trigger functionality in the Professional Services Tools Library (PSTL).
When I tried to enable the trigger I received the following error message:
Microsoft Dynamics GP – The stored procedure failed to enable taVendorInsert returned the following results: DBMS: 4920, Microsoft Dynamics GP: 0
During a recent implementation I was importing a file of 30,000 items into Microsoft Dynamics GP using Integration Manager when, part way through the integration, the following error started being produced:
9057: ITEM-NUMBER-1 Insert Failed 6. Seconds
DOC 9057 ERROR: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) - The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
9058: ITEM-NUMBER-2 Insert Failed 0. Seconds
DOC 9058 ERROR: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) - The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
9059: ITEM-NUMBER-3 Insert Failed 0. Seconds
DOC 9059 ERROR: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) - The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
I was working onsite with a client during an upgrade of Microsoft Dynamics GP from version 10 to 2013 recently, and after doing some work on a client we started receiving an error when trying to log out..
The error we received was the following:
Microsoft Dynamics GP – Unknown error 0 – 800AC351 occurred saving the project file
After a little testing to see if we could easily determine the problem, I did a quick online search and came up with this post from Vaidy Mohan which was the same error, but for a different VBA project.
The steps I tried and found to be successful were slightly shorter and easier than those Vaidy needed:
- Launch GP and open the Visual Basic Editor
- Opened modified report in the Microsoft Dynamics GP VBA project
- Added and removed a space from the end of one line
- Compiled the entire project to check for errors
- Save VBA project
- Log off from GP
To verify the problem was resolved we closed and reopened Dynamics GP and didn’t see the error when closing it again.
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.
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:
I was working on a new integration template for a client recently and after accidentally closed Integration Manager instead of just the Destination Mappings window I started getting the below error message when I reopened and tried running the integration:
Integration Manager – The destination could not be initialized due to the following problem: – Input string was not in a correct format
It took me a few minutes of fiddling around to work out the problem, but when I did it was a bit of a face/palm moment.
The project I was working on had some customisations in Microsoft Dynamics GP as well as a new integration template. When I logged in first thing I had started GP using Run as Administrator and then launched Integration Manager from the Tools menu ( ); but, when reopening it, I had launched it from the Windows Start screen.
This meant that GP itself was running under the administrator account, but Integration Manager was running under my user account. I closed Integration Manager again and then launched it from the GP menu, so that it was running under the same user account as GP itself, and was able to run the integration without further problems.
During a recent upgrade of a client from Microsoft Dynamics GP 2010 to Microsoft Dynamics GP 2013 we also did a migration of FRx to Management Reporter.
After doing the test upgrade and migration I tested Management Reporter and everything was working fine. However, a month later when I was back on site for the live upgrade and some additional training, I found that Management Reporter was no longer working correctly.
When I tried to open a column definition I received an error:
Management Reporter: The operation could not be completed due to a problem in the data provider framework.
After recently upgrading a client to Microsoft Dynamics GP 2013 they have been doing some testing. As well as GP itself they also use Integration Manager to integrate data from other systems.
Part of their testing plan involved testing the integrations; good thing they did as one problem, not a large one though, was found.
When trying to view the error logs the following error was produced:
Log Report Failure: Could not load file or assembly ‘Microsoft.ReportViewer.WinForms, Version=188.8.131.52, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The system cannot find the file specified
The solution is to install the Microsoft Report Viewer Redistributable which can be found here.