I am having a reoccurring issue with not being able to open gINT. I am running version 10.02.00.04 on a Windows 10 Pro machine (version 1909) and am getting the loop error that has been reported in the past:
gINT cannot locate a gINT library
Please browse to your library file
If you do not select a library gINT must exit
Attempts to select a library results in the message popping up again.
I have uninstalled gINT and the 32-bit Access Database, reinstalled gINT from the Bentley website and let gINT reinstall the Access Database, then restart the computer. This does work, but only temporarily. I have turned off Windows updates in attempt to stall Windows from changing the Access Database with updates. However, it seems that every time I come back to try and open gINT (a few days to a week or two later), I'm right back to square one and have to do this whole process over again.
What is the permanent fix that can be implemented so that this issue can be resolved and it is no longer necessary to uninstall and reinstall every time I would like to use this program?
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:
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
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.
Thank you for the response Aparna. We'll keep doing what we've been doing.
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.
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.