Since there is no information on this error, I think it would be nice to keep it on the internet: "Meshing failed with the following error: Mesh output file not found" error is really bothering. The reason of this error is unknown to me, so the answer.
For my current tunnel model, the inclusion of bolts (emb. beam) seems to cause the problem.
Dear Berk,
The main error mentions that meshing has failed. The description of the error indicates the fact that Input is searching for the output file after the finite element mesh is generated but it is not found.
Based on the above it is clear that the meshing procedure was not successful and actions should be taken to check for reasons why.
Typically the problems are related to the geometry created in the model. Inaccurate geometry generated can cause problems to the meshing procedure. PLAXIS Input program offers some tools to identify and fix geometry problems such as:
In general, since each project is unique it might require a different approach but the above applies to almost all cases.
If you have problems despite the suggestions above, please submit a service request.
Then, one of our support engineers can check in detail what is going on with your project: https://apps.bentley.com/srmanager/ProductSupport
Hi Berk,
I've come across this error several times, it usually happens when making alterations to the modell. I have no indication that it is related to any of the structure types. As a workaround I've found that initiating a new mesh with a 'very coarse' element distribution might work, and then you can remesh with your preferred element distribution setting, saving your work.
Thanks for the answer. This is quite new error to me, but it seems to be around for some time. I have submitted a support request and waiting for the answer. Checkgeometry shows some close proximity, however, all of the points are due to bolts created using tunnel designer which I don't have a chance to move.
Thank you for your message.
I agree with the first comment. My colleague had the same error in a totally unrelated model. Your workaround did not apply to my case.
;)