Integration Manager – Cannot Create ActiveX Component

Microsoft Dynamics GPI’ve probably said this before, but Integration Manager can be both very useful and also most infuriating, because when you get an error the error message usually isn’t useful.

However, my most recent problem with Integration Manager did actually produce a useful error message:

Integration Manager - Integration 'Invoices' is not ready to run due to the following problems: The destination could not be initialized due to the following problem: Cannot create ActiveX component.

Integration Manager

Integration 'Invoices' is not ready to run due to the following problems:
- The destination could not be initialized due to the following problem:

Cannot create ActiveX component.

I did a search and found a most useful KB article from Microsoft which detailed the problem (Microsoft Dynamics GP hadn’t been written to the registry correctly) and also the solution.

I read the whole article and decided to try a shortcut of starting with step 3 of re-registering the Dynamics.exe. To do this open a Run or Command Prompt and type the following (this particular problem was encountered with Microsoft Dynamics GP 20103 R2):

"C:\Program Files (x86)\Microsoft Dynamics\GP2013\Dynamics.exe" /regsrver

When I retried the integration, it ran through without further problems.

Integration Manager Syntax Error (Missing Operator) In Query Expression

Microsoft Dynamics GPA client recently logged a problem with our Service Desk to report that an Integration Manager integration wasn’t working; when trying to run the integration they received an error message on every line of the integration:


Opening source query...
Establishing source record count...
Beginning integration...
DOC 1 ERROR: Syntax error (missing operator) in query expression 'UCase(DATE#######) = UCase('' AND [RUN NUMBER] = ')''.
DOC 2 ERROR: Syntax error (missing operator) in query expression 'UCase(DATE#######) = UCase('' AND [RUN NUMBER] = ')''.
.
.
.
DOC 10 ERROR: Syntax error (missing operator) in query expression 'UCase(DATE#######) = UCase('21 January 2015') AND UCase([RUN NUMBER]) = UCase('HP33')'.
DOC 11 ERROR: Syntax error (missing operator) in query expression 'UCase(DATE#######) = UCase('21 January 2015') AND UCase([RUN NUMBER]) = UCase('HP33')'.
ERROR: Max Errors Exceeded at 11, Integration Canceled
ERROR: Integration canceled during document integration.
Integration Failed
Integration Results
    100 documents were read from the source query.
    11 documents were attempted:
        0 integrated without warnings.
        0 integrated with warnings.
        11 failed to integrate.

After doing some debugging of the integration, we identified the problem as being caused by the source column headers; all of which had multiple # at the end.

For example, as you can see in the above error message, DATE was displaying as DATE#######.

We went through the source removing all of the # symbols and were then able to run the integration without receiving more errors.

Integration Manager Error: ADO Field Is Nothing

Microsoft Dynamics GPIntegration Manager is a great tool for getting information into Microsoft DYynamics GP, but it can also be infuriating at times with the error messages it produces when there are problems.

I recently received an error message when trying to integrate some debtors:

Show/Hide Error Message

Integration Log Integration: Debtors (ID: 1) Action: None Start Time: 09/10/2014 08:49:37 09/10/2014 08:49:37 Source: IIntegrationEngine_Run, Status Code: 0 Opening source query... 09/10/2014 08:49:38 Source: Microsoft.Dynamics.GP.IntegrationManager.IMProvider, Status Code: 33624151 ERROR: Unable to open source queries because Query 'Debtors' is not found in the database. - ADO Field is nothing. Unable to open source queries because Query 'Debtors' is not found in the database. - ADO Field is nothing. ADO Field is nothing. 09/10/2014 08:49:38 Source: FinishIntegration, Status Code: 3 Integration Failed 09/10/2014 08:49:38 Source: FinishIntegration, Status Code: 3 Integration Results 0 documents were read from the source query. 0 documents were attempted: 0 integrated without warnings. 0 integrated with warnings. 0 failed to integrate. Finish Time: 09/10/2014 08:49:38 Source Total: 0 Successfully Integrated: 0 Integrated With Warning: 0 Failed: 0 Completion Status: Incomplete Integration Status: No Documents Succeeded

Continue reading

Hands On With Microsoft Dynamics GP 2015 RTM: Integration Manager First Run

Microsoft Dynamics GPNow that Microsoft Dynamics GP 2015 RTM is available, I thought I could follow my usual pattern of posting a series of posts on how to install and configure both Dynamics GP, but also the additional products which ship with it. You can find the series index for these posts here.

The first run of Integration Manager is something needed on each client. When staring Integration Manager for the very first time it is important to Run as Administrator.

When Integration Manager starts for the first time, you will be prompted to Register Now or Register Later; if you choose the latter option, Integration Manager will close:

Integration Manager

Continue reading

Hands On With Microsoft Dynamics GP 2015 RTM: Integration Manager Installation

Microsoft Dynamics GPNow that Microsoft Dynamics GP 2015 RTM is available, I thought I could follow my usual pattern of posting a series of posts on how to install and configure both Dynamics GP, but also the additional products which ship with it. You can find the series index for these posts here.

Integration Manager is a handy tool to have around; it allows easy integration of CSV or text files from a multitude of sources (once a suitable integration template has been created).

Its installation process is straightforward. Start the steup.exe and, under Additional Products select Integration Manager:

Microsoft Dynamics GP 2015

Continue reading

Integration Manager – The RPC Server Is Unavailable

Microsoft Dynamics GPDuring 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)

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.

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.

Integration Manager – An Item With The Same Key Has Already Been Added

I was working with a client the other day with Integration Manager to import some purchase orders when we received the following error on some of the purchase orders:

5. 820909 Insert Failed 0. Seconds
DOC 4 ERROR: An item with the same key has already been added.

The vast majority of the documents integrated without problem. When we examined the documents which failed, we determined that those which failed were those which had a currency of Euro.

Integration Manager errors are typically very unhelpful and this was no different; the first thing we checked was to see if the PO Number existed in GP, but as we expected it did not.

We did some investigating and found that the Euro Exchange Rate’s Transaction Rate Default in GP was defined as Exact Date; I was able to update this to Next Date after which the integration stopped producing errors.

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.