When loading Civtools Microstation freezes. Any ideas on a fix?

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 files
https://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 defaults
https://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)\MicroStation
It 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-tools
https://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.

Hi Levi,
Thanks for supplying those msdebug log files.
I took a look at them, and I did not see anything that jumped out to me. I'll let you know if I can find anything further.

Note that I was able to reproduce this issue as well using a v8i SS10 build. It seems like this could potentially be a Windows OS issue caused by an update, the OS version, etc.

Since MicroStation v8i is no longer a supported version, no fix can be made programmatically on Bentley's side, but you might have a few options since you have a working machine available. 

First, I would recommend to temporarily freeze all Windows updates to the working machine's OS.
Second, compare the Update History on the non-working machine to the working machine (Windows Settings>Update & Security>View update history). Try uninstalling any recent updates on the non-working machine so that the history matches the working machine. Keep in mind, your IT admin may need to get involved depending on your organization's security and procedures.

Hi Levi,
Thanks for supplying those msdebug log files.
I took a look at them, and I did not see anything that jumped out to me. I'll let you know if I can find anything further.

Note that I was able to reproduce this issue as well using a v8i SS10 build. It seems like this could potentially be a Windows OS issue caused by an update, the OS version, etc.

Since MicroStation v8i is no longer a supported version, no fix can be made programmatically on Bentley's side, but you might have a few options since you have a working machine available. 

First, I would recommend to temporarily freeze all Windows updates to the working machine's OS.
Second, compare the Update History on the non-working machine to the working machine (Windows Settings>Update & Security>View update history). Try uninstalling any recent updates on the non-working machine so that the history matches the working machine. Keep in mind, your IT admin may need to get involved depending on your organization's security and procedures.

That is the issue for sure

All of the troubled computers were updated last week and the one that was still working was last updated 2 months ago.

He has frozen his updates, I do have access to a connect version of microstation that I have used a little bit, (just more use to the old) so this may force me to start using it more often

Hi Levi,

Thanks for the update.

There are some methods available to make CONNECT "feel" like v8i. 
Should you need assistance with migrating to CONNECT, I would recommend filing a Service Request online via https://apps.bentley.com/srmanager/ProductSupport

If you choose to file a Service Request, let me know and our team will be on the lookout to assist.

-Jayson P.

I will go ahead and file that request now

Thank you for all of the help!!

Anytime I feel a recent Windows Update breaks something in MicroStation V8i (as the case here), I simply reinstall the latest Bentley V8i prerequisite pack (version 08.11.09.03) - and it usually resolves whatever V8i functionality was broken by the recently installed Windows update. Others recently reported this issue at my company. Without testing, I simply reinstalled the Bentley V8i prerequisite Pack - and the CivTools appears to be working OK in MicroStation V8i (SS10).

HTH

Do you know where to find a download link for the prerequisite pack. We are having this same issue however given v8i support has been discontinued I am unable to find the pack for download.