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

Notifications

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) / The ConnectionString p...
Microsoft Dynamics GP (Archived)

The ConnectionString property has not been initialized in Integration Manager

(0) ShareShare
ReportReport
Posted on by Dana Haessig 385

I have a client who is receiving the error:  'The ConnectionString property has not been initialized' when trying to run Integration Manager.  They have uninstalled and re-installed Integration Manager, but this does not resolve the issue.  I have not found anything useful for troubleshooting this error, and I am hoping someone has encountered it before.  They are running GP2010.

*This post is locked for comments

I have the same question (0)
  • MG-16101311-0 Profile Picture
    MG-16101311-0 26,225 on at

    In the past we've seen this error when there are issues within the current .NET framework installs on the machine. To resolve this, we've found that installing/repairing the current .NET framework installs on the machine seems to take care of it.

    Here are the .Net Framework download links.

    Microsoft .NET Framework Version 1.1 Redistributable Package

    www.microsoft.com/.../details.aspx

    Microsoft .NET Framework Version 2.0 Redistributable Package

    www.microsoft.com/.../details.aspx

    Microsoft .NET Framework 3.0 Redistributable Package

    www.microsoft.com/.../details.aspx

    Make sure to install all 3 versions of the framework. It is certainly possible that you already have one or more of these versions installed, but they may be damaged. Running the install will go over the top of an existing install repairing any damaged files.

  • Verified answer
    Michael Marinaro Profile Picture
    Michael Marinaro 9 on at

    I know this is an old post, but we solved this issue by repairing the Access database using the ODBC repair utility.  

    Just go to Data Sources (ODBC) in the Control Panel (or C:\Windows\Syswow64\odbcad32.exe if you're on a 64 bit machine).  Click Add... and select Microsoft Access Driver (*.mdb) and click Finish.  Click on the Repair button, and then browse to your IM.mdb database and click OK.  

    Just thought I'd put this out there in case anyone else has the same problem.  Let me know if you would like details.  

    Thanks

    Mike

  • ToddZ Profile Picture
    ToddZ 20 on at

    Thanks Micheal that worked for me.

  • Community Member Profile Picture
    Community Member on at

    Michael's post also worked for my client.

  • Community Member Profile Picture
    Community Member on at

    I experienced a similiar issue over the last couple of days. To correct my issue, I compacted the original database and gave it a new name. Then renamed the original Integration database. Rename the newly compacted integration database to the same name as the original. All issues were resolved. As a budding GP Administrator, how often are you compacting the integration database? My database is shared among several users.

  • Community Member Profile Picture
    Community Member on at

    do you have any other details for this?

    thanks

  • Michael Marinaro Profile Picture
    Michael Marinaro 9 on at

    Hi Carolyn,

    I'm not sure what other details you would like. Please follow up with a little more information to help us help you.

    Thanks,

    Mike

  • Community Member Profile Picture
    Community Member on at

    Michael,

    Do you know what causes the issue in the first place? Or tell me why the repair fixes the issue?

    Thanks,

    Paul

  • Michael Marinaro Profile Picture
    Michael Marinaro 9 on at

    Hi Paul,

    Integration Manager uses an Access database to store information about the integration routines, etc.  Access databases tend to get corrupted and have integrity issues over time if they are not regularly maintained.  This is especially true in multi-user environments. The error message in Integration Manager is simply a symptom of the underlying database corruption.  

    office.microsoft.com/.../compact-and-repair-a-database-HA010341740.aspx

    Thanks,

    Mike

  • Community Member Profile Picture
    Community Member on at

    Mike,

    My client has been having this issue recur multiple times a week, and the repair fixes the issue, but it comes back within a day or two. I also tried the compact option after it came back for the third time and it still returned after that. he is the only one using this database and it is local on his machine (not using a terminal server). Any other thoughts on what could be causing this or a way to fix this?

    Thanks,

    Paul

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 2

#2
mtabor Profile Picture

mtabor 1

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans