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
↧
Comment on Microsoft update for January 8 prevents users from being able to open a gINT project
↧
Comment on Microsoft update for January 8 prevents users from being able to open a gINT project
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.
↧
↧
Comment on Microsoft update for January 8 prevents users from being able to open a gINT project
Thanks Katie. We will give it a try
↧
Comment on Microsoft update for January 8 prevents users from being able to open a gINT project
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. Regards, Craig
↧
Comment on Microsoft update for January 8 prevents users from being able to open a gINT project
Thank you, Craig. Believe it or not, this helps. We appreciate your help.
↧
↧
Forum Post: export fence to pdf
I am trying to export fence diagrams to pdf, but when I do, the text is jumping up on the line. I cannot figure out why. I exported the same file to a .jpg file and the text is in the proper place. Can anyone help with this issue? I have examples below, the only difference is the pdf vs jpg option at export. Thank you
↧
Forum Post: New Layer in Graph
We recently have been seeing this issue appear when some one tries to output a graph again after they printed one. So if a user prints a sieve graph (only one page) then tries to print another one the error appears. I found the feed from 7 years ago. Has this ever been resolved? If you just let gINT output all of the pages it will work fine. If you try to run another set the error appears and will lock gINT up. We are using the latest version of gINT Connect 10.00.01.07. Please advised what can be done to resolve this.
↧
Forum Post: RE: export fence to pdf
Check the "vertical alignment" in your Text vs Depth properties box, main tab. "Middle" will put the text on the line, and "top" will put it just below the line. I am not sure of the difference between exporting to pdf vs jpeg,
↧
Forum Post: RE: export fence to pdf
Hi Brenda, I would also check the Vertical offset property of the text versus Depth. To move text off of line slightly choose a small negative number IE -0.05 and make sure the offset Units is set to page
↧
↧
Forum Post: RE: export fence to pdf
I have exactly the same issue. Anyone got a suggestion?
↧
Comment on Microsoft update for January 8 prevents users from being able to open a gINT project
On our systems the error was associated with windows update KB4480966. Windows version 10.0.17134 Build 17134.
↧
Comment on Microsoft update for January 8 prevents users from being able to open a gINT project
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. Regards, Katie
↧
Comment on Microsoft update for January 8 prevents users from being able to open a gINT project
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). -Katie
↧
↧
Forum Post: RE: Fit text within area
Hi Jeff, A text vs depth entity wraps based on the column width you define. When text is rotated 90 degrees, the lines at the top and bottom are the top and bottom of the range and that can vary throughout the depth of the borehole. That is why wrap won't work. The easiest answer is to put a carriage return in input. For example Florence LS Mbr
↧
Forum Post: RE: export fence to pdf
your suggestion worked, thank you
↧
Comment on Microsoft update for January 8 prevents users from being able to open a gINT project
Hello again, fellow gINT users, 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: Users can not open the file at all Users don’t get the error until they make a change, save, and then change to another file. 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. Regards, Katie
↧
Forum Post: RE: Modifying sediment core logs
and by cordgrasses (Spartina spp.) in particular, are increasing in incidence globally, with dramatic ecosystem‐level consequences liteblue
↧
↧
Comment on Microsoft update for January 8 prevents users from being able to open a gINT project
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: Backups of gINT files be made. At a minimum before trying to open a gINT File. Users Check the “Suppress Automatic File Compaction” option to prevent compaction as it may lead to data loss. To do this, in gINT, go to File => System Properties => General and check the radio box for “Suppress Automatic File Compaction” 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. -Katie
↧
Comment on Microsoft update for January 8 prevents users from being able to open a gINT project
Dear gINT Users, 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): KB4480964 (Windows 8.1, Windows Server 2012 R2) https://support.microsoft.com/en-us/help/4480964/windows-8-1-update-kb4480964 KB4480973 (Windows 10, version 1703) https://support.microsoft.com/en-us/help/4480973/windows-10-update-kb4480973 KB4480970 (Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1) https://support.microsoft.com/en-us/help/4480970/windows-7-update-kb4480970 KB4480978 (Windows 10 Version 1709 for x64-based Systems) https://support.microsoft.com/en-us/help/4480978/windows-10-update-kb4480978 KB4480966 (Windows 10, version 1803) https://support.microsoft.com/en-us/help/4480966/windows-10-update-kb4480966 KB4480116 (Windows 10 version 1809 and Windows Server 2019) https://support.microsoft.com/en-us/help/4480116/windows-10-update-kb4480116 KB4480961 (Windows 10 version 1607, Windows Server 2016) https://support.microsoft.com/en-us/help/4480961/windows-10-update-kb4480961 Regards, Katie
↧
Forum Post: RE: Extract zones from gINT using GIDEntity
Hi Joe, Yes that is correct the Zones are entities in GIDraw, entity type 42. The bounding rectangle is publicly available (the min* values) but the vertices are hidden in an array in the entity attributes. As you suggest they can be exported. If you double click on the zone entity in the Input ..Site Map Tab you will see an export option.
↧