[OR] Corridor Throws Error When Attempting to Edit a Parametric Constraint

I cannot open the Corridor Objects tool (Bucket Icon) so to modify a corridor I have to use the Properties dialog box selected from the Project Explorer.

I was trying to change the stations for a Parametric Constraint but when I would edit the station I would get a Property is not Valid dialog box with Details of Object reference not set to an instance of an object.

Next I tried to simply change it from Enabled = True to False and the same thing happens and eventually the MicroStation has stopped Working dialog box opens.

How can I recover a working and editable corridor from this file?

  • Why can't you use the Corridor Objects tool? Does it work for none of your corridors, or just that one?

    Have you tried turning it off and back on? using the key-in "civil display browser"? That might fix the problem of the Corridor Objects tool, and it might solve your most immediate problem too.

    Or, as my mom says, it might cure what ails you and might help besides.

  • What the begeezus is that?

    On my (and others) PC's it seems like our corridors get this way very quickly.

    Keyed in "civil display browser" and played with a few buttons. Got a nice display of Green "objects".

    After that, tried the Bucket tool - Bam! Try to ID my corridor and get the Bentley "email us the error" dialog box, followed by the Abort, Ignore, Retry dialog box.

    Try again and get an Dot Net Exception and shortly thereafter, the software crashes and closes without any warning.

    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration
    Maryland DOT - State Highway Administration User Communities Page

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
  • That last part sounds about right.

    Anyway, I've seen the same thing at times: all green. One distinct memory I have is of knowing that something was wrong, so I scanned through the first level under each main type of element. Eventually I got to seeing red. I was able to fix it that way. I can't guarantee that you won't be wasting time if you do the same, but that's my experience. Usually the problem is more obvious.

    Basically, that window seems to be an assemblage of all civil elements within your working file. It's sometimes helpful to delete certain things, such as once I decided to delete something under DynamicCrossSectionSpace because it was giving me trouble, and that helped. (Of course later I found that a different series of steps would have worked too, but I wasn't aware at the moment. And that same series of steps might not work for a different problem that deleting the DynamicCrossSectionSpace.)

    I'm out of guesses, but I have no memory of a corridor doing that to me. In fact, in my experience, if they go bad I can still look at Corridor Objects, though nothing happens if I make any changes. Usually, the cause has something to do with superelevation not being associated with the alignment correctly, or the terrain might be faulty, or whatever.