gINT cannot locate a gINT library

RE: gINT cannot locate a gINT library

Chelsea Schultz — Wed, 14 Sep 2022 16:52:32 GMT

We've had to switch to deploying x64 bit office to get around the issue - keeping the 32 bit office installed with automatic updates from Microsoft breaks gINT 2-3 times a month otherwise. In case that helps you.

RE: gINT cannot locate a gINT library

Aparna M — Wed, 14 Sep 2022 16:34:37 GMT

No, it is not resolved.

RE: gINT cannot locate a gINT library

Dominic Ostafijczuk — Wed, 14 Sep 2022 09:04:24 GMT

Hi Aparna, has Microsoft resolved this issue, or is it still with them?

RE: gINT cannot locate a gINT library

Judy Smith — Wed, 30 Jun 2021 13:48:13 GMT

We have been able to solve this issue (for the most part) by setting each user up with the library on their local machine (we use the C:\Users\Public\Public Documents\Bentley\gINT folder to copy our main library to, then in gINT system properties we put this file path as the library, then choose the file path to the master library on their local servers for gINT to be able to update the library as needed when the master has been changed. So far, this has worked well for us and we are not getting the "gINT Cannot find a library" error. Hope that helps you, too.

RE: gINT cannot locate a gINT library

Chelsea Schultz — Wed, 30 Jun 2021 13:44:05 GMT

Is there any movement or updates on this issue? We're in a really bad spot (as I imagine many other companies are) that we either have to let office updates run and fix 50+ computers running gINT multiple times a month, or hold our users back from getting Office updates they need.

RE: gINT cannot locate a gINT library

Daniel Wuellner — Tue, 12 Jan 2021 19:09:21 GMT

Thank you for the response Aparna. We'll keep doing what we've been doing.

RE: gINT cannot locate a gINT library

Aparna M — Tue, 12 Jan 2021 19:05:11 GMT

Hi Daniel,

We have filed a ticket with Microsoft on this Access Database issue. Until a permanent fix is worked out, unfortunately repair or reinstall of 2010 Access Database 32 is the way to go around.

RE: gINT cannot locate a gINT library

Daniel Wuellner — Tue, 12 Jan 2021 19:01:23 GMT

Hi Aparna,

Just wanted to check to see if there's any movement or additional details on this issue? Or a creative/stable solution for the interim?

Over the last few months I've used a 'semi-permanent' workaround on certain client PCs of replacing the MSO365 version w/ a standalone earlier version of MSO and a standalone earlier version of MS Access runtime to run our in-house database w/ success but this is not available on our client PCs which require MSO365.

The simplest temporary solution I've found seems to be an in-place re-install of the database engine w/ the version packaged w/ our version of gINT (roughly as simple as the repair solution which seemed to break the Access runtime depending on version).

Thanks,

Daniel

RE: gINT cannot locate a gINT library

Marylou Lamberton — Tue, 15 Dec 2020 18:29:03 GMT

Hello Aparna,

Thank you for the quick reply. Your help is greatly appreciated. I will try the repair process and test over time too see if it helps.

RE: gINT cannot locate a gINT library

Aparna M — Thu, 10 Dec 2020 18:11:28 GMT

Hi Marylou,

This issue is happening due to Microsoft Office 365 updates. These office updates are breaking the 32 bit Access database 2010 engine which is required for all gINT files to read and operate. We have filed a ticket for this issue with Microsoft, but unfortunately will get reset with Office updates until this is fixed.

Instead of reinstalling the Access database engine each time, you can try to repair the access database engine.

Here are the steps you try mentioned in this post:

communities.bentley.com/.../gint-won-t-open-november-2020---closes-after-splash-screen