Error with program: RasUnsteady64.exe Exit Code = 157

[bcahill]

Does anyone have experience with Exit Code = 157? What does it mean and do I make it go away?

I am running a large 1D/2D combined HEC-RAS model with version 5.0.5. For the 2D flow areas I am using the Full Momentum equation along with the adaptive time step feature. My 2D hydraulic tables are all current. The simulation will run about a 1/3rd of the way through and then suddenly stop (see image below). Is this a software or geometry problem?

[Anonymous]

Hello, did you find how to fix your issue? i got the same
thank you
Etienne

[bcahill]

I have not been able to fix it as of yet.

[Anonymous]

i got same problem too. How to fix that. Pls help.

[ckatsoulas]

have a look at Chris Goodell’s comments in the post below

http://hecrasmodel.blogspot.com/2013/10/stabilizing-dynamic-unsteady-hec-ras.html

[Anonymous]

I had this happen today, and was able to figure out that it was because of duplicate external boundary conditions in the unsteady flow file.

HEC-RAS isn’t always very good about making sure that the unsteady flow file matches the geometry. In my case, I had deleted the external BC to do something, then re-added them by copying them from another version of the model in RAS Mapper. When I pasted them in, it renamed them with generic names (BC Line 1, etc.). I then renamed two of the lines back to the original names.

When I deleted them, the original entries in the unsteady flow file didn’t get deleted, but when I renamed them, RAS didn’t check the file to see if there was a matching entry, so it added a second copy. When I deleted this extra copy from the file with Notepad, it fixed the problem.

Looking at the whole file, I think I need to do some cleanup, because there are other ‘orphan’ entries that don’t show up in the user interface because the BC locations have been deleted.

[ckatsoulas]

Access violation, usually means you may have a run results layer open in another software such as a GIS program and when you re-run the scenario HECRAS can’t overwrite the results. You need to close the GIS program before running HECRAS.

[Anonymous]

This method worked for me. I had around 15 bridges in my unsteady 2D model with 4 really complicated ones (5-6 culverts closely spaced to simualate piers). I saved my geometry as different versions, removed breaklines one-by-one, and checked the model after each removal. The model ran after the third removal indicating there was an issue with that breakline.

[Author]

Posts