• State Verified Answer
  • Replies 33 replies
  • Subscribers 142 subscribers
  • Views 13575 views
  • Users 0 members are here

.NET Framework error when I mouse over a newly opened file with OR cross sections

Derek Schmidt
Offline

This error had already been mentioned in another thread, but I'm creating a new thread because the mention of this error had been a departure from the original post in that thread. With the help and gracious patience of Phil Chuinard, Jan Slegr, and Reginald Wallace, I was able to get rid of it temporarily. 

I'm using Microstation SS3 8.11.09.608 and GEOPAK SS3 .722.

A short review:

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at Bentley.Civil.Objects.UI.Coordinates.CoordinatesManager.ConstructSmartPoint(DPoint3d coordinates, SnapDescriptor snapDescriptor, DynamicCrossSectionSpace space, ObjectKey key)
at Bentley.Civil.Objects.UI.Coordinates.CoordinatesManager.ConstructSmartPoint(DPoint3d coordinates, SnapDescriptor snapDescriptor, IViewport viewport, ObjectKey key) 
at Bentley.Civil.Objects.UI.Coordinates.CoordinatesManager.ApplyConstraint(DPoint3d coordinates, SnapDescriptor snapDescriptor, IViewport viewport)
at Bentley.Civil.Objects.UI.Coordinates.CoordinatesManager.OnFixPoint(IEditableButtonEvent cursorEvent)
at Bentley.Civil.CadSystem.Microstation.MstnInputManager.OnPointFilterEvent(_dPoint3d* ptP, Int32 viewIndex, Int32 eventType) 
at Bentley.Civil.CadSystem.Microstation.?A0x62071685.inqmn_PointFilterFunction(_dPoint3d* ptP, Int32 viewIndex, Int32 eventType)
at Bentley.Internal.MicroStation.CoreHook.DispatchNoHandler(UInt32* argStack, UInt32 mysp, IntPtr pFunc) 
at Bentley.Internal.MicroStation.CoreHook.Dispatch(UInt32* argStack, UInt32 mysp, IntPtr pFunc)

5141.msdebug.txt

7217.exception.log

The problem occurs when I've just opened a file with an open cross section view. It occurs only when I mouse over that window. A workaround is that I can turn off the view and turn it back on and it works fine.

I repaired the .NET Framework installation.

It was fixed almost exactly a week earlier (maybe it's on a 7-day periodic return) by removing two cfg files from the loading process, loading Microstation, then returning them to the process. Those two files were descartes.cfg and geopak.3.0.cfg.

Update:

In today's case, I turned off only the geopak.3.0.cfg and left descartes.cfg active and it worked.

To be more precise, doing this disabled the window that the cross section view was in. After I closed the program, re-activated geopak, then turned on that window, I closed the program once more. When I opened it, I half-expected the .NET Framework error to be raised again but it didn't.

Any advice on ridding myself of this for good?

Parents Reply
  • 0 Offline in reply to Derek Schmidt
    Derek - I'm only able to speak to what I'm experiencing, but yes, when those three conditions are met on my computer the application throws a .net unhandled exception error (null reference) when mousing over an open roads dynamic section view.

    I've heard back from Bentley tech support and they are still unable to reproduce the error on their end. It would help to submit a service request if you are experiencing an issue like this. As of yesterday I'm the only one that has contacted them about this issue, so to them it appears to be an issue isolated to just one user and they don't have any other user data to compare to aid in troubleshooting. The more data they have to compare the quicker this will get resolved.
Children
  • 0 Offline in reply to Michael-Lane
    Every time I've contacted tech support they say "I see someone else is already working on this. Have you checked there?" If they can help effectively, they should be reading this themselves. I don't know what they might expect from me, and if it is something they can help with, they should help all of us collectively, not each of us one at a time. But yeah, I'll consider it next time I see that it's an issue. I did make the change to my accudraw settings file and it looks like you're right. But so far today, I've only been working in a file where I was looking at the profile.
  • 0 Offline in reply to Derek Schmidt
    Update: Bentley support has been able to reproduce this on their end and have filed defect #197796:Crash in Dynamic Cross Sections with 2 Application Windows.

    Answer Verified By: Derek Schmidt 

  • 0 Offline in reply to Michael-Lane
    Good to hear! As an FYI, I tested a small project using SS4 from alignment to cross section sheets and the .NET errors plus crashing has reduced dramatically.
  • 0 Offline in reply to Michael-Lane

    I've come back to this problem because I got this error again--the entire trace is identical.

    This time, I was reviewing dynamic cross sections just fine. (Fine, meaning with no fatal errors I was scanning through my corridor, but I was frustrated by the absence of the indication in plan to see where the cross section was cut.) So I turned on Civil Accudraw and suddenly got this error. 

    Formerly in this thread I'd been using SS3 .722; now I'm using SS4 .845.

    Unknown said:
    Update: Bentley support has been able to reproduce this on their end and have filed defect #197796:Crash in Dynamic Cross Sections with 2 Application Windows.

    I noticed that I'd previously marked this as a solution and so it came back to my attention now. What are the steps Bentley has to reproduce this? I'm curious because I always come to it accidentally.

    Even though I encountered this error in the file in question, when I open the file again everything is fine. Even having turned on Civil Accudraw.

Communities
Support and Services
Training and Learning
Social Media