Error 126 Could not load mcm.dll when opening a drawing from Projectwise after having an upgrade from V8I to Microstation connect edition

What version of Connect and what version of ProjectWise?

Did you verify the 2 are compatible? See the ProjectWise Version Support Matrix (bentley.com) to confirm

Generally with MicroStation when one person has an issue and others don't I suspect the UCF or UPF. When you re-imaged the machine did you restore those from backup or start clean?

When you say you can open MicroStation outside of projectwise, do you get the ProjectWIse login gui or is projectwise do you completely disabled in this configuration?

The versions are compatible. The machine was reimaged from a fresh build. Yes, I am getting the PW login.

Curious: Does the affected User contain any Personal WorkSpace Configuration Variables? He can have a look for himself via Tools > Options from ProjectWise Explorer (click on the Personal WorkSpace tab). Based on your posts, I cannot tell if you are using a Managed WorkSpace in ProjectWise or if you are using locally stored WorkSpace.

Also, can you have the User update (or set) a User Program Association for the File Type (i.e. Application) and include the -debug as the Command Line Argument? Then, have him open a File in ProjectWise to create a Debug Report? I'm curious to see the output.

*Note: You'll need to remove the -debug Command Line Argument after doing so.

When you get the PW login it means the MCM is loading properly when you use that method to open.

Looking at my variables when i've loaded ProjectWise I see it adds paths to the variables:

MS_LIBRARY_PATH
MS_MDL
MS_RSRCPATH

my guess is something is resetting one of those variables preventing ProjectWise is loading for this user.

In addition to checking the personal workspace per Matthew's suggestion, you could try disabling all the application cfg files, except projectwise's, and see if that fixes it. I usually do this by:

• Browse to the C:\Program Files\Bentley\MicroStation CONNECT Edition\MicroStation\config\appl folder
• create a folder in that folder called Disabled
• Copy all the cfg files from the appl folder into the disabled folder (except pw.cfg)
• if that fixes the problem copy the cfg files in Disabled back into appl one at a time and test each time
• If one of the files causes the issue you can examine it

Doing this requires admin privs on the local machine.

When you get the PW login it means the MCM is loading properly when you use that method to open.

Looking at my variables when i've loaded ProjectWise I see it adds paths to the variables:

MS_LIBRARY_PATH
MS_MDL
MS_RSRCPATH

my guess is something is resetting one of those variables preventing ProjectWise is loading for this user.

In addition to checking the personal workspace per Matthew's suggestion, you could try disabling all the application cfg files, except projectwise's, and see if that fixes it. I usually do this by:

• Browse to the C:\Program Files\Bentley\MicroStation CONNECT Edition\MicroStation\config\appl folder
• create a folder in that folder called Disabled
• Copy all the cfg files from the appl folder into the disabled folder (except pw.cfg)
• if that fixes the problem copy the cfg files in Disabled back into appl one at a time and test each time
• If one of the files causes the issue you can examine it

Doing this requires admin privs on the local machine.