This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Why does my WaterGems model crash everytime I try to import a submodel?

Hi,

I'm running WaterGems Connect Edition 1 Update (10.01.01.04). Every time I try to import a sub-model, WaterGems crashes. I have tried compacting the database, tried the 32 bit version etc.. The only procedure that works if I export as a Epanet file, import it back into WaterGems, save as another file and then do the import as sub-model. The previous Select 6 version worked well. Its with the Connect version that I have problems. Any suggestions on what might cause the software to crash?

thank you.

Parents
  • Hello Johan, 

    Is it happening for a single model or for all the models? Did you test with sample models located at C:\Program Files (x86)\Bentley\WaterGEMS\Samples?

    If it is model specific then , can you please copy .wtg & .wtg.sqlite file to a new location and open model from there and see if you can import the submodel or not. 

    If this does not help then please upload model and submodel for our testing. 

    Sharing model files

    Regards,

    Sushma Choure

    Bentley Technical Suppport

  • The file names are : dewater_main.wtgpkg.zip and GTP_Dewatering_WaterGems_Model.wtgpkg.zip

  • Hello Johan,

    This may be related to the names of the scenarios in the two models. Each of the models has two scenarios which are called "Base". Try renaming the child scenario in each of these to something like "New Scenario." The test that I did was deleted the child scenario from Hydraulic Model GTP_Dewatering.wtg and renamed the child scenario in dewater_main.wtg to "New Scenario." When I did this and imported dewater_main.wtg.sqlite as a submodel, the issue did not occur.

    For more information on submodels, see this link.

    Regards,
    Scott

    Answer Verified By: Sushma Choure 

Reply
  • Hello Johan,

    This may be related to the names of the scenarios in the two models. Each of the models has two scenarios which are called "Base". Try renaming the child scenario in each of these to something like "New Scenario." The test that I did was deleted the child scenario from Hydraulic Model GTP_Dewatering.wtg and renamed the child scenario in dewater_main.wtg to "New Scenario." When I did this and imported dewater_main.wtg.sqlite as a submodel, the issue did not occur.

    For more information on submodels, see this link.

    Regards,
    Scott

    Answer Verified By: Sushma Choure 

Children