Integration Manager Bugs Fixed in Microsoft Dynamics GP 2018

Microsoft Dynamics GPEarlier in the year we added a new ERP Support Analyst to our support team and we’ve been doing training to bring him up to speed. While I was doing Integration Manager training, I was giving him some cuationary advice about error messages and tried to reproduce some of the annoying errors I’ve encountered in the past, only to find out that three of them have been fixed without me realising.

The fixes are:

Debugging Integration Manager Crashes

Microsoft Dynamics GPWe’ve had two separate clients recently log calls where Integration Manager was crashing while performing an integration.

The first client was doing an Inventory Items integration on Microsoft Dynamics GP 2015 R2 and the other was doing a Sales Transaction integration on Microsoft Dynamics GP 2016 R2.

Both of the integrations had been running fine for quite a long period of time before starting to crash; no changes had been made to either system and I’ve not been able to determine why Integration Manager (IM) has started crashing.

However, by the use of two ini file switches, we were able to determine what error was being encountered by IM resulted in a crash.

The two switches are already present in the ini file (C:\Program Files (x86)\Microsoft Dynamics\Integration Manager nn/Microsoft.Dynamics.GP.IntegrationManager.ini by default) whre the False value needs to be changed to True:

[IMGPPrv]
ShowDynamics=False
DoUIRedraw=False

When these switches are set to True, the Microsoft Dynamics GP windows are not hidden when the integration runs.

We found that for the Inventory Items integration, accounts either didn’t exist, didn’t allow account entry or were inactive; for the Sales Transaction integration, Analytical Accounting (AA) had been enabled for one of the accounts and the integration didn’t handle AA.

I created a VB script for the Inventory Items integration to check the accounts in the Before Document script and cancel the document if the account was going to be a problem.

Hands On With MDGP 2018 RTM: Integration Manager First Run

Microsoft Dynamics GPMicrosoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

With Integration Manager now installed, the final step in it’s installation is to run it and enter the license key.

It is important that the first time Integration Manager is launched, you do so by right clicking and selecting Run as Administrator; this ensures that Integration Manager has sufficient privileges for writing the necessary registry entries.

When Integration Manager starts, you will be presented with a Register Now/Later window; to use Integration Manager, a licence key must be entered, so click Register Now:

Integration Manager: Register Now

Continue reading “Hands On With MDGP 2018 RTM: Integration Manager First Run”

Hands On With MDGP 2018 RTM: Install Integration Manager

Microsoft Dynamics GPMicrosoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

If you are going to be using Integration Manager with eCOnnect Adaptors, make sure eConnect has been installed on the client before following the steps in this post.

To install Integration Manager, launch the setup utility from the installation media:

Depending on server settings, you might receive multiple security warnings during the installation; click Run on each one as it appears:

And, under the Additional Products header, select on Integration Manager and click Install on the popup menu:

Microsoft Dynamics GP 2018 setup utility

Continue reading “Hands On With MDGP 2018 RTM: Install Integration Manager”

Integration Manager Sales Order Integration – “The Sales Intrastat Entry window is open”

Microsoft Dynamics GPJust before Christmas I was creating an integration for a client in Integration Manager which would integrate Sales Orders, but unfortunately I was receiving an error message:

Integration Log
Integration: Eriks SO Integration (ID: 8)
Action: None
Start Time: 23/12/2016 11:05:38

  23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0    Opening source query...
  23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0    Initializing Source...
  23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0    Establishing source record count...
  23/12/2016 11:05:38 Source: IIntegrationEngine_Run, Status Code: 0    Beginning integration...
1:  Order  Insert Failed 5. Seconds 
    DOC 1 ERROR: The Sales Intrastat Entry window is open. - The Sales Intrastat Entry window is open.
  23/12/2016 11:05:43 Source: FinishIntegration, Status Code: 3    Integration Failed
  23/12/2016 11:05:43 Source: FinishIntegration, Status Code: 3    Integration Results
    1 documents were read from the source query.
    1 documents were attempted:
        0 integrated without warnings.
        0 integrated with warnings.
        1 failed to integrate.

Finish Time: 23/12/2016 11:05:43

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

Completion Status: Completed
Integration Status: No Documents Succeeded

Continue reading “Integration Manager Sales Order Integration – “The Sales Intrastat Entry window is open””

Hands On With Microsoft Dynamics GP 2016 R2: Integration Manager First Run

Microsoft Dynamics GPWith the release of Microsoft Dynamics GP 2016 R2 it’s time for a series of “hands on” posts where I go through the installation of all of it’s components; the index for this series can be found here.

The first time you run Integration Manager after installation, you need to right click and Run as Administrator. This makes sure that all of the relevant registry entries are created:

Integration Manager on the Start menu

Continue reading “Hands On With Microsoft Dynamics GP 2016 R2: Integration Manager First Run”

Hands On With Microsoft Dynamics GP 2016 R2: Install Integration Manager

Microsoft Dynamics GPWith the release of Microsoft Dynamics GP 2016 R2 it’s time for a series of “hands on” posts where I go through the installation of all of it’s components; the index for this series can be found here.

With eConnect installed I can now install Integration Manager with both sets of adapters (Dynamics GP and eConnect).

To do this launch the setup utility from the installation media and, under Additional Products click on Integration Manager:

Microsoft Dynamics GP 2016 Setup Utility

Continue reading “Hands On With Microsoft Dynamics GP 2016 R2: Install Integration Manager”

VBA for Integration Manager to Insert Vendor EFT Bank And Email Addresses

Microsoft Dynamics GPI did a SQL Script back in October 2014 which allowed Vendor EFT Details to be inserted, but, if the client is going to run it themselves, requires the assistance of the IT Department as end users don’t usually have access to SQL Server Management Studio.

For most clients, this hasn’t usually been a problem, but a number of the clients I have worked with recently have had multiple projects on the go at the same time. This has meant that while an IT representative can be available, it isn;t usually very timely and can delay UAT.

As such, I wrote some VBA script for Integration Manager which inserts both the Vendor Email and EFT Details. Continue reading “VBA for Integration Manager to Insert Vendor EFT Bank And Email Addresses”

Integration Manager Error: Cannot Open Database “GPLIV” Requested By The Login

Microsoft Dynamics GPWe’re in the middle of large upgrade project at the moment for a client and encountered an error when trying to run an integration.

This particular integration is an Account one, which has been extended with VB Script which checks to see if the segments exist, and if not, it inserts them. When a user tried to run the integration, they get the following error:

Opening source query...
Establishing source record count...
Beginning integration...
DOC 1 ERROR: System.Data.SqlClient.SqlError: Cannot open database "GPLIV" requested by the login. The login failed.
DOC 2 ERROR: System.Data.SqlClient.SqlError: Cannot open database "GPLIV" requested by the login. The login failed.
DOC 3 ERROR: System.Data.SqlClient.SqlError: Cannot open database "GPLIV" requested by the login. The login failed.
Integration Failed
Integration Results
    3 documents were read from the source query.
    3 documents were attempted:
        0 integrated without warnings.
        0 integrated with warnings.
        3 failed to integrate.

I did some double checking and it turned out that the user who was doing the testing had two Domain accounts (one with full name and one with initial and surname) and were not using the one I had configured originally.

All of the other users I had worked with had been using Domain accounts of initial and surname, which was the one I had configured, but this particular user was using the account with their full name.

Adding this Domain user account to the database with the DYNGRP role resolved the problem.

Execute Batch File In Integration Manager

Microsoft Dynamics GPI can’t remember why I created this code, but it allows a batch file to be run from an Integration Manager script:

/*
Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (http://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int).
*/
Set objShell = CreateObject("WScript.Shell")
Set objExec = objShell.Exec("B:\IM.bat")

I’m posting it here so I don’t lose it for when I remember why I write it, and perhaps it may be useful to others.