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
Unknown said: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.
Absolutely. While I understand that fixes are applied in future versions, a patch should be provided for the folks operating an older generation for this reason. Imagine Windows 98 SE users being forced to upgrade to Windows ME, or Windows XP users being forced to upgrade to Windows Vista just because their was a fatal bug in the older edition.
I'm with Sean on this one. I've only been able to work with the real estate that 2 application windows offers. And knowing the workaround is enough for me to just grin and bear it. Obviously I'd like to not see the error, but if it's that or lose the second window, I'll take the second window with the error and just work around it. Still, it shouldn't be, as we all agree.
Then perhaps it has something to do with a setting in %localappdata%\Bentley\MicroStation\8.11\. I'm not sure where to begin to advance from there.
EDIT: As a test, when I renamed the MicroStation folder mentioned above to _MicroStation, I did not get the error we've been discussing. After renaming it back, I did get this error. Any guesses at which file and setting that offends? I'd guess something featuring the key words civil, dynamic, cross section, and view.
Following this method, I've established that it's not in the .upf that I'm using, and it's not in the civil nor civil_commands folders.
EDIT: I've renamed everything in the prefs directory with an underscore at the beginning of the name. Apparently none of it makes any difference. The error still comes up. It only does not come up when I've renamed the MicroStation directory (or perhaps any other directory in the path). So I'm not much closer to finding the solution after all. What I just realized is the all the files in the prefs' parent directory. That's my next test.