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

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
  • Ok, but moving to the latest release is not always that simple. Support should understand that the new version requires everyone working on the project to upgrade to that new version. If not then not everyone will be able to edit or create civil objects. Of course I am describing the recent SS4 release.

    I still believe that there is an underlying issue that is causing these errors. Temporarily fixing an issue is not a permanent.

    Disabling the geopak.3.0.cfg removes the ability to use the SUE tools.
Children