Error 800AC351 While Saving Microsoft Dynamics GP

Microsoft Dynamics GPI 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 fileMicrosoft 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:

  1. Launch GP and open the Visual Basic Editor
  2. Opened modified report in the Microsoft Dynamics GP VBA project
  3. Added and removed a space from the end of one line
  4. Compiled the entire project to check for errors
  5. Save VBA project
  6. 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.

Upgrading Management Reporter 2012: Post Upgrade Connection Problem

Microsoft Dynamics GPIn 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?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.

Upgrading Management Reporter 2012
Upgrade the Server Components
Upgrading the Database
Upgrading the Clients
Post Upgrade Connection Problem

FRx Migration Wizard Failure

Microsoft Dynamics GPI 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:

FRx Database - Catalog Table

Continue reading

Integration Manager Error: ‘Input string was not in a correct format’

Microsoft Dynamics GPI 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 formatIntegration 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 (Microsoft Dynamics GP menu >> Tools >> Integrate >> Integration Manager); 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.

Management Reporter Error Opening Column Definition

Microsoft Dynamics GPDuring 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.Management Reporter: The operation could not be completed due to a problem in the data provider framework.

Continue reading

Integration Manager Log Report Failure

Microsoft Dynamics GPAfter 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=9.0.0.0, Culture=Neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specifiedLog Report Failure: Could not load file or assembly ‘Microsoft.ReportViewer.WinForms, Version=9.0.0.0, 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.

Management Reporter ‘Bad or missing data…’ error

Microsoft Dynamics GPI’ve had this post in my queue for a while after it got overlooked, but I figure it is still worth posting.

We received a call on the service desk from a client who was having problems with Management Reporter; whenever they tried to generate a report they received the following error:

Bad or missing data was encountered while loading the report and its building blocks. Report generation has been cancelled.Bad or missing data was encountered while loading the report and its building blocks. Report generation has been cancelled.

Continue reading

SmartList Builder Will Be Disabled Until It Is Initialized By The System Administrator

Microsoft Dynamics GPI have been involved in several upgrade projects with clients recently where we have been upgrading them from Microsoft Dynamics GP 2010 through to Microsoft Dynamics GP 2013. Since this version was launched, SmartList Builder has been pushed back out to eOne, the original ISV.

So, after doing the normal upgrade process, we have then installed the latest version of SmartList Builder from the eOne website. However, this has not been a smooth process.

One of the clients started receiving the following error message whenever a user tried to access SmartList:

SmartList Builder Will Be Disabled Until It Is Initialized By The System Administrator

Continue reading

Integration Manager Bank Transaction – Unimplemented Cast From Btype ‘BROWSETYPE_UNKNOWN’

I’ve been configuring an integration in Integration Manager for a client recently to assist with an Intercompany Bank Reconciliation process. When we started discussing the integration I had taken a quick look at the sample Bank Transaction integration which ships with Integration Manager and had no problem.

As the project progressed and I created the Bank Transaction integration on the client’s server I encountered the below error:

Intercompany Bank Transfer - Transaction Progress

Show/Hide Error Message

Integration Log
Integration: Intercompany Bank Transfer - Transaction (ID: 66)
Action: None
Start Time: 25/02/2014 14:36:53

  25/02/2014 14:36:58 Source: IIntegrationEngine_Run, Status Code: 0    Opening source query...
  25/02/2014 14:36:59 Source: IIntegrationEngine_Run, Status Code: 0    Establishing source record count...
  25/02/2014 14:36:59 Source: IIntegrationEngine_Run, Status Code: 0    Beginning integration...
1:  GBP  Insert Failed 2. Seconds 
    DOC 1 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
2:  GBP  Insert Failed 0. Seconds 
    DOC 2 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
3:  GBP  Insert Failed 0. Seconds 
    DOC 3 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
4:  GBP  Insert Failed 0. Seconds 
    DOC 4 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
5:  GBP  Insert Failed 0. Seconds 
    DOC 5 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
6:  GBP  Insert Failed 0. Seconds 
    DOC 6 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
7:  GBP  Insert Failed 0. Seconds 
    DOC 7 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
8:  GBP  Insert Failed 0. Seconds 
    DOC 8 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
9:  GBP  Insert Failed 0. Seconds 
    DOC 9 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
10:  GBP  Insert Failed 0. Seconds 
    DOC 10 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
11:  GBP  Insert Failed 0. Seconds 
    DOC 11 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
12:  GBP  Insert Failed 0. Seconds 
    DOC 12 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
13:  GBP  Insert Failed 0. Seconds 
    DOC 13 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
14:  GBP  Insert Failed 0. Seconds 
    DOC 14 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
15:  GBP  Insert Failed 0. Seconds 
    DOC 15 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
16:  GBP  Insert Failed 0. Seconds 
    DOC 16 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
17:  GBP  Insert Failed 0. Seconds 
    DOC 17 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
18:  GBP  Insert Failed 0. Seconds 
    DOC 18 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
19:  GBP  Insert Failed 0. Seconds 
    DOC 19 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
20:  GBP  Insert Failed 0. Seconds 
    DOC 20 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
21:  GBP  Insert Failed 0. Seconds 
    DOC 21 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
22:  GBP  Insert Failed 0. Seconds 
    DOC 22 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
23:  GBP  Insert Failed 0. Seconds 
    DOC 23 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
24:  GBP  Insert Failed 0. Seconds 
    DOC 24 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
25:  GBP  Insert Failed 0. Seconds 
    DOC 25 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
26:  GBP  Insert Failed 0. Seconds 
    DOC 26 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
27:  GBP  Insert Failed 0. Seconds 
    DOC 27 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
28:  GBP  Insert Failed 0. Seconds 
    DOC 28 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
29:  GBP  Insert Failed 0. Seconds 
    DOC 29 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
30:  GBP  Insert Failed 0. Seconds 
    DOC 30 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
31:  GBP  Insert Failed 0. Seconds 
    DOC 31 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
32:  GBP  Insert Failed 0. Seconds 
    DOC 32 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
33:  GBP  Insert Failed 0. Seconds 
    DOC 33 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
34:  GBP  Insert Failed 0. Seconds 
    DOC 34 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
35:  GBP  Insert Failed 0. Seconds 
    DOC 35 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
36:  GBP  Insert Failed 0. Seconds 
    DOC 36 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
37:  GBP  Insert Failed 0. Seconds 
    DOC 37 ERROR: Unimplemented cast from Btype 'BROWSETYPE_UNKNOWN'
  25/02/2014 14:37:12 Source: FinishIntegration, Status Code: 3    Integration Failed
  25/02/2014 14:37:12 Source: FinishIntegration, Status Code: 3    Integration Results
    37 documents were read from the source query.
    37 documents were attempted:
        0 integrated without warnings.
        0 integrated with warnings.
        37 failed to integrate.

Finish Time: 25/02/2014 14:37:12

Source Total: 37
Successfully Integrated: 0
Integrated With Warning: 0
Failed: 37

Completion Status: Completed
Integration Status: No Documents Succeeded

I fiddled around without being able to identify a cause of the problem and, while I was doing this, found that the 37 transactions in the file had actually integrated despite the error message (an error in IM usually means the transaction or line will not be successfully integrated).

I brought a copy of the Integration Manager back to my test system and ran it on there and all of the files integrated without error.

The difference between my test system and the client’s system is that I have Microsoft Dynamics GP 2013 Service Pack 2 while the client is still on Service Pack 1.

In the medium term we will be upgrading the clients system to service pack 2, but in the meantime we’ll need to make do with increasing the number of permitted errors and accepting that an error will be displayed even as the transaction is integrated.

File Not Found: VBA6.DLL

While VBA is falling out of favour with Microsoft Dynamics GP (by dint of not being supported in the web client) it is still useful for those clients who do not use, and have no intention of using, the web client.

One such client was recently installing some new XenAPp servers using Windows Server 2012; when they tried to open a window with a VBA customisation they received the following error:

File Not Found: VBA6.DLLFile Not Found: VBA6.DLL

Fortunately, Beth Gardner posted the answer to the Developing for Dynamics GP blog.