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?
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.
Hi Aparna, has Microsoft resolved this issue, or is it still with them?
No, it is not resolved.
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.