When duplicating an event (unidirectional), an error is generated causing WaterGEMS to crash. The error is sometimes also generated when adding a new event. We're using the latest version of WaterGEMS (10.02.01.06). This bug has been happening since updating to version 10.02.00.43 from 10.01.01.04, so version 10.01.01.04 did NOT contain the bug that generates this error. I've uploaded a model file with some support files (exception log, error screenshot, and an .mp4 file showing the handling sequence that leads to the error) using Bentley Secure File Upload.
We've already tried all those options, the error keeps getting thrown. We also tried starting with a brand new model (new submodel from a different base model), the error kept popping up...
Somehow I am not able to recreate the issue with your model please see below video which shows adding flushing event at same location as you had shown for crash video. I tried in one of the sample model from our sides, in that case I could reproduce the crash once, but it didn't happen again so it was a random behavior.
However from the model you uploaded I see that you are using version 10.02.00.43, so I tried in that version as well but couldn't reproduce the crash with your model.
But since you are facing the crash for this model, I will send the error log file for further investigation to the development team.
Bentley Technical Suppport
The attached movie file and crashlogs were indeed created before we updated to the latest version, in the latest version the error still exists. I could upload the crashlogs for the new version aswell if that would help?
Hi Joeri, we can reproduce the issue when duplicating, and are looking into it. Thanks for your patience.
Jesse DringoliTechnical Support Manager, OpenFlows ProductsBentley Communities Site AdministratorBentley Systems, Inc.
Answer Verified By: Joeri Legierse
Hi Joeri, our developers are now looking into this via Defect 1037572, Service Request 7000932277. We hope to have a fix for you soon.
Just to close the loop on this thread - the crash when duplicating or adding events in these circumstances has been resolved and a new cumulative patch set was sent to Joeri. Information on patch sets can be found in the following article: Cumulative patch set frequently asked questions
I have also added a note about this issue and its solution to the main Flushing Technote
This is a post on the crash that Joeri Legierse reported. Unfortunately the bug fix keep returning.
We're still using the latest version of WaterGEMS (10.02.01.06). The following actions are set up by three different people with three different models and the three of us received the same error message:
I hope you can fix the problem.
I have used the Secure File Upload. The ZIP-file is "20190911 - WaterGEMS Error Flushing Analysis (part 2, more detailed).ZIP"
I met with your colleagues this week and this was one of the things we discussed. Thank you for providing the details - I can reproduce the issue even in a sample file and have escalated this back to the development team for review. I have also reopened the related Service Request (7000932277) and will keep you updated when I have a fix/solution. Thank you for your patience.
Jeffrey, and updated patch set has been made available, to address this issue. I have sent it to you and your colleague Erik via Service Request 7000932277
Thank you for fixing the error. We have tested this patch and this problem is solved. We have found an other issue when we open a table.
The hydraulic model crashes when the table "Flushing Result Browser" is opened. Do I have to make a new report for this error?
We are happy with the new patch, so thanks again!
Jeffrey RamkisoenEvides - Hydraulic Department
Hi Jeffrey, thanks for confirming that the patch worked.
For the new issue where the Flushing Results Browser does not work properly - it is generally best to start a new forum thread for a new issue (or for a crash/defect, a Service Request can sometimes be better). I can reproduce the issue and will discuss with our developers and get back to you shortly.