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
Hi Sylvia,
Thank you. I checked and I did see it listed on this post: https://communities.bentley.com/products/geotechnical1/b/geoblog/posts/additional-information-and-a-workaround-for-users-affected-by-the-microsoft-patch I hope you have been able to work, regardless of the OS version you are using that is affected.
FYI, Microsoft has released a fix on February 12 that we have all been waiting for. More information can be found here: https://communities.bentley.com/products/geotechnical1/b/geoblog/posts/fix-for-gint-users-affected-by-the-january-8-microsoft-patch-has-been-released
Please keep in touch and let us know if the fix works for you, and for reaching out.
I appreciate the link to the list of Microsoft patches. I do not see KB4480970, which is the update that affected most of our computers. Thanks for any help with this.
Hi Angus,
Thank you for asking. I have had two new blogs. One with a temporary workaround, and one with an update that I posted yesterday. We have been working with Microsoft and we have started testing a fix. It should be generally available shortly.
Please fine the new post on this blog site.
As we have information we will post it here.
-Katie
How's the progress on getting this fixed coming along?
I just published a new post with a temporary workaround until Microsoft releases their resolution.
https://communities.bentley.com/products/geotechnical1/b/weblog/posts/additional-information-and-a-workaround-for-users-affected-by-the-microsoft-patch
We find we have to check each day to uninstall the patch. Even if we uncheck the box when it is in queue to load, the patch still loads.
It has become our routine. Will be glad for a fix for this!
Hello again, fellow gINT users,
It has been over 24 hours, and I wanted to let you know that we continue to work with Microsoft to find a workaround that will help you until Microsoft can release a solution.
At this time we still recommend making a back up of your files before attempting to open them, and uninstalling the patch if possible.
If you have been affected, please feel free to reach out to me whether you have been able to uninstall the patch or not. Please include your Windows OS and version, and gINT version.
My email is katie.aguilar@bentley.com.
Thank you for your patience in this matter.
I am updating the list of patches that are known to cause the error.
The list of patches now include (Patch ID (Targeted OS) Link):
Hello Fellow gINT Users,
We continued to work with Microsoft over the weekend regarding this issue, and will continue working with them.
At this time Microsoft has acknowledged the issue in a post, and has anticipates a resolution by early February.
At this time the only viable work around we have is to uninstall the updates. On the site with the issue acknowledgement from Microsoft 3 possible resolutions are listed. We do not recommend them at this time as they seem to not work, and user may lose data.
At this point we do recommend:
The link to the acknowledgement from Microsoft is here. Again, we do not recommend any of the suggested resolutions at this time as we do not know enough to say they will work. In fact, you may end up losing data if do you try them.
Thank you for your patience. We are working with Microsoft for a resolution.
As we head in to the weekend please know that work continues on this issue.
Most users are getting the Unrecognized database warning. However, this issue can manifest in other ways as well. Iterations include a Runtime 0 error, AxfilegINT.gINTfilevalidFNS error, and a Database Structural Problem. I am including a couple of screen shots that we have.
Technical Services have noted some other manifestations as well:
In general, if you are running gINT and you start getting errors, please check your updates and see if you have installed the January 8 patch. If you have, please let us know (and include your Windows OS and version, and gINT Version, as well as a description of how it has manifested. Screen shots are great). If possible, uninstall the patch so you can use gINT again.
Database Structural Problem error:
AxfilegINT.gINTfilevalidFNS error:
Thank you, again, for your patience as we continue work with Microsoft on this issue.
Hi Mike,
Thank you for reaching out.
I just posted below about we think it may be related to the number of characters in a field name. Do you have any fields with greater than 32 characters? Perhaps the CBR module?
You can uninstall the patch and you should be up and running with gINT again.
May I ask which version of gINT you are using? You can email me if you prefer (katie.aguilar@bentley.com).
Hi gINT Users,
I want to give you an update. We are circling in on the issue.
It appears to be related to the database and character length in field names. It appears to be affecting databases with field names greater than 32 characters in length vs any specific Windows OS.
For reference the post is here: https://answers.microsoft.com/en-us/msoffice/forum/all/unrecognized-database-format-after-january-2019/a2518bb6-050d-4e7b-8844-257dbc6a20a2
That being said, if you are using our CBR module which is downloadable from Communities, there is a field that is greater than 32 characters in length and you will likely get an error if you have run the patch. We are using the CBR files to reproduce the error internally.
If you have questions or comments, even if you have updated and you are OK, please feel free to reach out to me (katie.aguilar@bentley.com) or post here as others have. Please include your Windows OS and version, as well as gINT version. Every bit of information does help.
We are still working with Microsoft. This is our highest priority.
Thank you for your patience.
On our systems the error was associated with windows update KB4480966. Windows version 10.0.17134 Build 17134.
Thank you, Craig. Believe it or not, this helps. We appreciate your help.
Hi Katie,
I just checked what updates my computer installed on the 9th. It did install kb4480970. And as noted yesterday, gINT is working fine -- created a new database this morning.
Craig