Exporting Results from GoldSim - Exception Access Violation Fatal Error and model crashing

Answered

Follow

Apurva Gollamudi

• June 23, 2020 12:41

Model version: GoldSim 12.1.4 operating on a Network Licence

We have been encountering an issue with a few models that were working fine until recently, where the GoldSim models crash at the end of the simulation without exporting results to Excel, and the error is Exception_Access_Violation (see screenshot below).

When we set the model to "do not export" and try to export all the results manually, GoldSim just closes by itself and does not export anything. It seems to export fine when we just try exporting individual results elements.

We have already tried the following:

1. Ensure no background instances of Excel are running in the task manager
2. Keeping Excel closed during simulation and export
3. OneDrive and SharePoint Sync is off
4. Starting the simulation after saving and restarting GoldSim
5. Restarting computer
6. Saving as a new model version
7. Uncheck the "clear previously written cells" box in the result elements

Another issue (possibly unrelated) came up as part of this troubleshooting exercise - every time we hit “Export Now” in the model settings, it switches to the “export automatically after running”, even if we switch it back to “Do not export” every time. 

1

• 

  Jason

  • June 23, 2020 15:31

  Apurva,

  Thanks for posting in the GoldSim Forum. I'd like to understand more about how these models are set up. Can you open one of the models that is exhibiting this issue and tell me:

  • Version of Office and Windows
  • Duration, basic time step, number of realizations and/or scenarios
  • Go to the Information tab of Simulation Settings: How many elements in your model and how much memory is required
  • How many Time History results are you exporting and within these, approximately how many results are you linking to? Are any of these non-scalar?

  It might also help to see an example of one of these models so I can try running it on my end to diagnose. If this is a possibility, I can send you a separate message with a private link to share the model. Thanks for your patience. I look forward to hearing back from you soon.

  -Jason

  0

  Comment actions Permalink
• 

  Apurva Gollamudi

  • June 23, 2020 15:53

  Hi Jason,

  Small Update: We got the export to partially work after deleting all the Excel files and allowing GoldSim to create new Excel files. However, not all the result elements exported even with this workaround. When we tried to re-export and overwrite the newly created Excel files, the model crashed again.  

  In response to your questions, we've encountered this issue with a few different model files and on different computers (albeit different versions of what is ultimately the same model).

  Version of Office and Windows: We are running GoldSim on Windows 10 and run Microsoft Office 365 for Enterprise. I have a 64-bit version. Most of the folks who encountered this issue operate on a network licence but we found the same issue on a standalone licence as well.

  Simulation Duration: The duration of simulation didn't really matter (the model crashed with a 1 year run time as well as a 100 year run time).

  Time step: Basic time step of 1 day. Reporting time step is weekly.

  Number of Realizations: Didn't seem to matter. The model crashed with 1 realization as well as 5 realizations.

  Number of Elements: (varies a bit between model versions but one example in the screenshot below)

  

  Time History Results being exported: 48 elements

  Number of results being linked to and non-scalar elements: There are several non-scalar exports in the result elements. Typically, we would be exporting a vector of about 40 items and a couple of instances of a matrix of 40X4.

  Thanks again for your assistance in troubleshooting this issue.

  - Apurva

   

  0

  Comment actions Permalink
• 

  Apurva Gollamudi

  • June 23, 2020 18:50

  RESOLVED

  We discovered that the model was setup to export different statistics (10^th, median and 90^th percentile) into different Excel files under different sub-directories. However, the files themselves within each sub-directory were given the same name (e.g., Flows.xlsx). We had to rename the files to be unique (e.g., Flows-high.xlsx, Flows-low.xlsx) to prevent GoldSim from crashing.

  1

  Comment actions Permalink
• 

  Jason

  • June 23, 2020 19:44

  Apurva,

  Thanks for posting the resolution to this issue. I was able to reproduce this by simply exporting time history results of 1 output to 2 different Excel files with the same name located in different sub-directories. When I change the Excel file names to be different, the problem goes away for me as well. We will look into this to see if we might be able to fix this in a future release. For now, we recommend that anyone exporting to more than 1 Excel file to give them all unique names.

  Thanks,

  Jason

  0

  Comment actions Permalink

Please sign in to leave a comment.