I installed OBD U10 (latest) on all computers at the office. We switched from U8. I first uninstalled U8 and did a clean install of U10. We refer to a Configuration at our server (virtual B-drive).
All computers seem to work as expected, all users are working without problems. However, there is one computer that sometimes seems to have a problem soon after opening the software. This computer runs Windows 11, but so do a lot of others that don't have an issue.
When opening OBD, you can chose a workset and file to open, but then the program crashes without getting to the point of loading the file or even loading the interface.
This error refers to a log file being created (see attached file). This error appears maybe 1 out of 10 times. The other times it just works fine.
Anyone can make more out of the log-file, to see what could be the problem?
What I tried before was to repair OBD and even to uninstall/reinstall OBD, but it didn't change anything.
3857.exception.log
Hey Stefan,
How did you update OBD last time ?Since you mentioned you did switch from U8 to U10, how about the workflow you followed. Did you update OBD from CONNECTION Client or had a fresh reinstallation like uninstalling U8 first and then install U10 ?
Best Regards, Arindam
Hi Arindam,
At first I just installed it over the existing U8 version, using a downloaded installation file from the Bentley servers.
Later on when I noticed the issue, I uninstalled it completely and reinstalled it with that installation file again.
Windows 10 pro
OpenBuildings Designer Connect Edition Update 10.10.01.151
Still the same situation here...
I get this several times a day, no explanation, just quits after.
The latest version is definitly less stable than the previous versions.
And while previously you got the option to 'Ignore', which often worked, you now have no option to restart the program (and ending with the same error).
Sorry for coming back late. I would like to know when you reinstalled OBD U10 at that time did you clean up all OBD related folder like from Program files and Program Data ?
We generally recommend to do this clean reinstallation when an abrupt crash is happening while opening a new Dgn file.
Yes exactly, no option to ignore and continue. no message telling you what is causing the error or crash, so you have to spend hours or days searching through references looking for the offending geometry.
It would be nice if the error message or the log file weren't so cryptic, allowing you to narrow down the issue to where the problem appears so you have a clue where to start.
For what it is worth: sometimes when a file always gives me the error on opening, I open it in an old version (V8i Select Series 6), which opens it without issues. When getting back to Connect Edition, I can open it again. Same with some caching of DVs, which failed in Connect. Just open them in V8i and set them to cached there. Once cached, Connect has no issue reloading the cached view.