Ref: https://communities.bentley.com/products/hydraulics___hydrology/f/haestad-hydraulics-and-hydrology-forum/179147/connect-edition-update-2-release-of-watergems-watercad-hammer-sewergems-civilstorm-sewercad-and-stormcad-build-10-02-01-xx
Hello, I am having trouble opening multiple different models since installing this update. I do not believe these models to be corrupted since they have been opened many times (not saved/overwritten) since January/February (the save date) using the first Update 2 release. The error message of "Operation was forbidden in current the mode." seems to be correlated to this latest release. Some Update 2 models still open fine, and all of the pre-Update 2 models I checked also open fine.
May be worth noting that I went through the steps outlined in this other post, but with no success.
https://communities.bentley.com/products/hydraulics___hydrology/w/hydraulics_and_hydrology__wiki/8251/error-opening-existing-model-error-in-the-application-or-operation-invalid-without-a-current-index
Hello Andrew,
I have split your question to a new thread.
Can you provide a copy of one of the models in question? (File > Save to Package) - Sharing Hydraulic Model Files on the OpenFlows Forum
Can you think of anything that is different with the models that experience the issue? Are you using Change Tracking with a password set? Do you have a Bing Map attached?
Does it make any difference if you open the model database? (select "database files" from the "files of type" dropdown in the file open dialog and select the model's corresponding .sqlite file)
Regards,
Jesse DringoliTechnical Support Manager, OpenFlowsBentley Communities Site AdministratorBentley Systems, Inc.
Hi Jesse, thanks for starting the new thread and for the suggestions. I uploaded a copy of the model for your review. Unfortunately, opening as a database resulted in the same error. Change Tracking is off, and I am not sure if there is a Bing map set up in this model (I have been adding them to models as I update them but not sure if this one has it yet). Thanks for your support, let me know if there is anything else I can do.
Andrew
Hi Andrew, thanks for sending the model. I can reproduce the same error, and have made several attempts to find a solution, to no avail.
I will escalate this issue to our development team for investigation and will let you know as soon as I have an update. In the meantime, please check if the backup files exhibit the same problem.
Thank you, Jesse. I also tried the .bak files but they reproduced the error. I found an archived version of the model from February and the error occurred with that older version as well.