I am using Microstation V8i SELECTseries 10
Version 08.11.09.919
When I load Civtools the Message Center will say "Civtools loaded" But then I am unable to click on anything else, I eventually have to task manager > end task on microstation to be able to restart.
The only fix I have tried is I redownloaded Civtools but that did not work.
This is happening to other people in my office as well.
Hi Levi,
Sorry to hear that you are experiencing these issues.Here are some recommendations I think would be worth a try in no particular order:
1. Try opening MicroStation files with a different user/project/interface combination. Try something like "examples" User, "No Project" for Project, & "default" set for Interface.2. Try resetting prefs and deleting temp fileshttps://communities.bentley.com/products/microstation/w/microstation__wiki/8978/how-to-reset-user-preferences-and-delete-microstation-s-temporary-files
3. Restore MicroStation to factory defaultshttps://communities.bentley.com/products/microstation/w/microstation__wiki/8671/restore-microstation-to-factory-defaults
4. Check the version of Civtools and ensure it is compatible with the version of MicroStation you are running.If none of those steps work, do you know if there are any machines at the organization that are not experiencing the issue?
Hello Jayson,
Thank you for the reply
1. Where do I find the user user/project/interface combination?
2. Reset my prefs and deleted the temp files but no change
3. Restored MIcrostation to factory defaults but no change
4. How do I check the version of Civtools and where do I find a compatiblity chart?
5. Of the 4 people in my department that currently use microstation 3 of the 4 are having the freezing issue and 1 is not, the one that isn't is using the same version of microstation as me (08.11.09.919) we are all using the same .ma file because it is located on our server.
Levi Hitt said:1. Where do I find the user user/project/interface combination?
Open MicroStation directly from the Desktop shortcut as opposed to opening a file. You can also run the ustation.exe located here:C:\Program Files (x86)\Bentley\MicroStation V8i (SELECTseries)\MicroStationIt should look like this:
Levi Hitt said:4. How do I check the version of Civtools and where do I find a compatiblity chart?
I don't think something like this would be available, but I would imagine the Civtools download from these links would probably work with any v8i version. Try the downloads here if you have not already:https://communities.bentley.com/products/microstation/w/bentley_library__wiki/3941/civil-toolshttps://communities.bentley.com/products/microstation/m/bentley_library_utilities/197318
Levi Hitt said:Of the 4 people in my department that currently use microstation 3 of the 4 are having the freezing issue and 1 is not, the one that isn't is using the same version of microstation as me (08.11.09.919) we are all using the same .ma file because it is located on our server.
This is good to know. I think if we compare the "good" machine to the "bad" machine, we can narrow down the issue even more to understand it better.One thing I would try is to configure MicroStation to read your MDL apps on a local drive if at all possible and see if that helps. Seems like the network could be a factor when combined with your custom configuration.
For next steps, follow the steps here for v8i on the "good" machine and then a "bad" machine. You can post the resulting msdebug.txt files to your reply so we can analyze. Be sure to rename them so they are discernible (i.e. GOODmsdebug.txt & BADmsdebug.txt).
-Jayson P.
Apologies, looks like my link did not work in the previous post.For next steps, follow the steps here for v8i on the "good" machine and then a "bad" machine. You can post the resulting msdebug.txt files to your reply so we can analyze. Be sure to rename them so they are discernible (i.e. GOODmsdebug.txt & BADmsdebug.txt).
I redownloaded civtools and placed it on my desktop and will load from there
1. changing the user/project/interface combination did not change the issue.
BADmsdebug.txtGOODmsdebug.txt
Here are the debug files named the way that you asked.