web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Intergration DB issues...
Microsoft Dynamics GP (Archived)

Intergration DB issues after moving GP 2013 to new server

(0) ShareShare
ReportReport
Posted on by Community Member

HI everyone

I move our Dynamics 2013 server to a new server to a new domain

recreated all my users

GP works great, but when we try to run integration using the same im.mdb file that was on the old system

we get errors

i can open some interrogations but not others - is there a trick to  to moving the im,mdb ?

*This post is locked for comments

  • Suggested answer
    Romryan Profile Picture
    Romryan on at

    see the link below

    mohdaoud.blogspot.com/.../export-and-import-integration-manager_1490.html

  • Suggested answer
    Redbeard Profile Picture
    Redbeard 12,931 on at

    In addition to the import export feature, you can use the Tools menu to create a new Integration Manager Database (IMD) file, to isolate the integration(s) you wish to move from one server to another. To do this choose Tools > Create Database then give the database a name (something clever like Export.imd).  You can then copy this database to the new server, and import the integrations you exported to Integration Manager Database on the new server.

    By default, the Integration Manager Database mapped during the default installation of Integration Manager can be found under Tools > Options > General > Default Integration Manager Database and is typically C:\Program Files (x86)\Microsoft Dynamics\Integration Manager 12\Samples\IntegrationManagerSamples.IMD...

    If more than one user is accessing Integration Manager, you'll need to put the Integration Manager Database into a shared location on the server, and map each Integration Manager installation to the shared location.

    Finally, every integration has a source(s). There are many potential types of sources, like delimited files, or ODBC sources. These sources must exist on the new server, if you want the integration to work. So, if you have a source file that is stored on a local drive on Server 1, and you move the Integration but not the source file to Server 2, the integration will not work.  The source file information can be found by double-clicking on the Source under Sources in the Integration in Integration Manager on the General Tab in the File field.

    Moving or Exporting/Importing the Integration(s) is only one part of the process. You must also make sure the source files for the Integration(s) are updated relative to the new server. You should also make sure the path to your Integration Manager Database is a shared location, if more than one user is involved.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans