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?
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
Answer Verified By: Derek Schmidt
After seeing this error for the first time in four months, I reviewed this thread.
Unknown said:Ok, I suppose it wasn't that simple, the crash still occurs if civil accudraw is enabled when switching between models that have a cross section view open. So, the crash occurs when all of the following occur: 1. A model opens with dynamic section view(whether opening Microstation from scratch, or just switching between models in your current session) 2. You have the "two application windows" preference set 3. civil accudraw is enabled
I did have Civil Accudraw enabled at the time of the error--I was loading a file from an already-running instance.But after reviewing this post, I tried to trigger the error again by enabling Civil Accudraw (both HUD mode and toolbox mode)--but not with Civil Accudraw set to load automatically. That didn't trigger anything. I even tried loading the file with both Civil Accudraw and Microstation Accudraw running too. I moused over all the views, including the dynamic cross section view (which I remember as triggering the error in the past).
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.