This has been my error for the last week:
I get this error as soon as I open one of my files. I am wondering if anyone has seen this before, and how to reliably fix it. I have activated the problem file, and dropped the civil elements in effort to fix it, with mixed results. I fixed it once by deleting the apparent violating geometry and was able to work for a few hours, only to have the error reappear later that day. I have since dropped civil elements via activation several times, only to fix it once, but not the fix was not reproducible with other copies of the file. Thanks!
The .net errors are typically hard to troubleshoot to know WHY exactly an error occurred. I believe in a lot of cases it has to do with how the geometry is ruled to other elements and perhaps broken as base elements are edited/copied/renamed, so those elements nullify how different elements are built. But we haven't been able to find a direct relationship to a workflow and troubleshooting these errors.
If you can post the DGN file which is having the issue, we can attempt to find the trouble element in the file which is causing the crash. In some cases you can just recreate that that geometry and reassociate any civil elements to it to "repair" the relationships.
Also, what is the exact version of InRoads you are using so we can make sure you are on the latest release of the product?
http://communities.bentley.com/products/road___site_design/f/5922/t/110086
For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki