Dear gINT Users,
Microsoft released a patch on Tuesday January 8. Items in that patch will make the gINT database un-recognizable, and you will not be able to open gINT.
At this time we do not know the specific item in the patch, but we are working on things. This has our highest priority.
The error is non version specific for gINT.
Please watch this space for updates and information. We will be forth coming with more details as we find them.
Regards,
Katie
Katie Aguilar, PE
Product Manager I
katie.aguilar@bentley.com
We are working with Microsoft at this time add address the issue with the patch.
If you experience this issue please email me with your company information along with your Windows OS, Windows Version, gINT version, and contact information. We are tracking this issue and gathering information to help solve it. You can email me at katie.aguilar@bentley.com.
If you are willing and able, one temporary work around is to uninstall the updates. Once that is done, you should be able to use gINT again.
We do not know if it is version specific to gINT at this time.
We believe it is the following patches released by Microsoft.
Patch Number (OS) Targeted Link
KB4480964 (Windows 8.1) https://support.microsoft.com/en-us/help/4480964/windows-8-1-update-kb4480964
KB4480973 (Windows 10) https://support.microsoft.com/en-us/help/4480973/windows-10-update-kb4480973
KB4480970 (Windows 7) https://support.microsoft.com/en-us/help/4480970/windows-7-update-kb4480970
We suspect it is related to the Jet Engine Database.
Once installed, users get the following error:
Error 3343: Unrecognized database format
DatabaseAx.DBCloneFnB: DAO.Database: Unrecognized database format…
Thank you for your help and patience in this matter.
Hi Katie,
We are expreincing the same issue on multiple computers. We are using Windows 7 profesional and Gint Version 8.30.02.39 with Somat Engineering Inc. Should we attempt the patches above?
Ron
Hi Ron,
If you are experiencing the issues, then you have the patches installed already. At this time the path forward is to uninstall the patches mentioned above. Those patches are the suspected cause of the issue.
Thanks Katie. We will give it a try