Exit Code = 157

[Anonymous]

I am able to run the Muncie example fine, but when I run a model that is very similar I continue to get the following error.

Plan: ‘Unsteady Run with 2D Flow Interior Area’ (GI_FINAL_2D.p07)
Simulation started at: 26Jan2015 01:55:39 PM
Using 64 Bit Computation Engines

Writing Geometry
Completed writing geometry

Geometric Preprocessor HEC-RAS 5.0.0 Beta October 2014
2 Internal Boundary curve(s) have been read in

Finished Processing Geometry

Writing event conditions
Event conditions complete

Performing Unsteady Flow Simulation HEC-RAS 5.0.0 Beta October 2014

forrtl: severe (157): Program Exception – access violation
Image PC Routine Line Source
RasUnsteady64.exe 00000001401F62E2 Unknown Unknown Unknown
RasUnsteady64.exe 00000001401D649F Unknown Unknown Unknown
RasUnsteady64.exe 00000001401B9207 Unknown Unknown Unknown
RasUnsteady64.exe 00000001401B2F2D Unknown Unknown Unknown
RasUnsteady64.exe 00000001401B2C4A Unknown Unknown Unknown
RasUnsteady64.exe 000000013FF880BB Unknown Unknown Unknown
RasUnsteady64.exe 000000013FEF2ECA Unknown Unknown Unknown
RasUnsteady64.exe 000000013FFC557C Unknown Unknown Unknown
RasUnsteady64.exe 000000013FF102DC Unknown Unknown Unknown
RasUnsteady64.exe 0000000140078B48 Unknown Unknown Unknown
RasUnsteady64.exe 000000013FF6CDC6 Unknown Unknown Unknown
RasUnsteady64.exe 000000013FEBEF5E Unknown Unknown Unknown
RasUnsteady64.exe 000000013FEE41CE Unknown Unknown Unknown
RasUnsteady64.exe 0000000140794AC6 Unknown Unknown Unknown
RasUnsteady64.exe 0000000140344D82 Unknown Unknown Unknown
kernel32.dll 0000000076B959ED Unknown Unknown Unknown
ntdll.dll 0000000076DCC541 Unknown Unknown Unknown
forrtl: severe (157): Program Exception – access violation

Error with program: RasUnsteady64.exe Exit Code = 157

[Anonymous]

This happened to me too. It helped to delete one flow boundary and create it new.

[Anonymous]

I had the same error after I edited my 2D mesh. I had forgotten to run the geometric pre-processor within RAS mapper (R-click on 2D Flow Area sub-layer, then select “Compute 2D Flow Areas Hydraulic Tables”)…

I thought that it would automatically do it at the run initiation but it took exception to it and once I did it myself, it worked fine.

[Alquier]

Sometimes it s du to an error in your mesh. Even if you compute your 2D hydraulic tables from Ras mapper the error remain. So in this case you should modify your mesh so as to don’t have any red points in your mesh. It does the trick for me.

[Anonymous]

Have you found the solution, Modeler?

I am having the same problem in 5.0.4 version. It happens to exceed 11 culverts in the modelling.

Thanks in advance for your comments.

[Anonymous]

This worked for me as well. The aforementioned error happened on two occasions. The first was when I deleted all internal inflow hydrographs and replaced them with new ones. The second occasion was when I deleted the inflow hydrographs and did not replace them. By creating a dummy inflow hydro I was able to get the model to run.

[Anonymous]

I have another model that was erroring out with this same Exit Code. I had 4 2D connections with an extreme number of culverts (17, 18, 18, and 20 with a single barrel per culvert group). After deleting these 2D connections, the model was able to run fine. I was able to re-add these connections with just a few culvert groups (3 to 4) and 3 to 9 culvert barrels per culvert group, depending on the structure details.

[Anonymous]

I got this same error on my unsteady 2D model. I tried removing all BCs and adding them back in – didn’t work. I also tried the “Compute 2D Flow Areas Hydraulic Tables” in RAS Mapper, then re-running the unsteady flow analysis – didn’t work.

The unfortunate solution was a general debugging technique mentioned here (ctrl+f ‘157’):

I saved my geometry as different versions, removed individual bridge/culvert breaklines, and checked the model after each removal. My model had around 15 bridges, but 4 were really complicated (5-6 culverts spaced closely to simulate piers). I started by removing those 4 breaklines one-by-one and the model to ran after the third removal. This indicated something was odd with that particular breakline so I made some adjustments to my culverts.

I hope this helps any future modelers who come across the 157.

[ALFREDONAHF]

This happened to me too. It helped to delete duplicate flow boundary data.

[Pouyan]

I had the same error for 2D sediment transport, it was the upstream BC.
Thanks.

[Author]

Posts