I am new to supporting Microstation so treat me easy ;)
I've got a remote user who had MS lock up on her while saving a file. She was forced to hard reset the machine, when it came back up the file she had been working on was gone. I've googled and I see that MS can generate both minidumps and exception logs but looking in %temp% and user/appdata/local/bentley resulted in nothing found.
Does MS need to be configured to create those logs/files and if so how do you do it?
Connect r14 10.14.00.109 self-employed
There are times when these exception and minidump log files are not created and when the software locks up or hangs you can record exactly what has occurred on this users system by configuring their system to produce a hang dump. It is also good to know what was being performed at this time when the hang occurs and whether it is specific to a particular file. The exact version of MicroStation is also useful so we can advise if a newer release may help to resolve your issue.
RegardsAndrew BellTechnical SupportBentley Systems
Mark Schmidt said:Microstation Connect Edition 10.0.0 is not generating
Does the user really use version 10.0.0? MicroStation users 4 digits numbering system, so I guess it's 10.00.00.25 (can be shortened to 10.0.0.25).
When this version is really used, it's seriously old version, not recommended to use today. It was the first CONNECT Edition version, released nearly 5 years ago! As you can imagine, the first version are not very good usually and MicroStation was not different. Today CE Update 14 (build 10.14.01.109) is much better (in fact, it's probably the first version fast and stable enough to be used in more complex projects).
Mark Schmidt said:I see that MS can generate both minidumps and exception logs
Yes, MicroStation creates these two files when (A) anything goes wrong and (B) MicroStation is still in a condition to create the logs.
Mark Schmidt said:Does MS need to be configured to create those logs/files and if so how do you do it?
No, MicroStation is configured to produce logs by default. But when more detail logging is required, the variables mentioned by Bob Rayner can be used.
Mark Schmidt said:when it came back up the file she had been working on was gone
I guess exception log and minidumps will not help too much in this case, because it sounds more like Windows issue than MicroStation problem. Especially when machine hard reset was necessary and not simple "kill MicroStation".
Did you check Windows logs, whether anything was reported by operating system?
Mark Schmidt said:resulted in nothing found.
When crash is serious (MicroStation is too corrupted to create logs or the crash is caused by Windows), the log and minidump are not created. It's quite rare situation, but can happen.
When MicroStation hangs (the process still exists) but Windows still lives, in addition to procedure described in wiki (in Andrew Bell) you can create minidump from Task Manager:
Labyrinth Technology | dev.notes() | cad.point
Thanks Andrew, I assumed that was the case here as I've seen applications affect Windows to such a degree that a hard reset is in order many times in the past. As I mentioned I am no expert when it comes to Microstation, in fact I've only been here a year and this is the first company that I've worked for that's used it.
This particular user is on version 10.08.00.37, I have other users on 10.12.00.40