Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ProjectWise
  • Product Communities
ProjectWise
ProjectWise Design Integration Forum Error 126 Could not load mcm.dll when opening a drawing from Projectwise after having an upgrade from V8I to Microstation connect edition
    • Sign In

    • State Suggested Answer
    • Replies 8 replies
    • Answers 2 answers
    • Subscribers 65 subscribers
    • Views 753 views
    • Users 0 members are here
    • MicroStation Connect Edition

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

    Kandappu Suthakar
    Offline Kandappu Suthakar over 1 year ago

    Hello,

    I am getting the above error when I open a drawing from Projectwise in Microstation ever since we had the upgrade from Microstation V8I to MIcrostation Connect edition.  I really appreciate your inputs to fix this issue.

    Thanks

    • Sign in to reply
    • Cancel
    Parents
    • Jan Ĺ legr
      0 Offline Jan Ĺ legr Fri, Nov 18 2022 8:58 AM

      Hi Kandappu,

      please be aware this is MicroStation Programming forum, but your question is about ProjectWise integration issue. I recommend to move your question to ProjectWise Design Integration forum. To move existing discussion to another forum, use More > Move  tool, available under your original post.

      Kandappu Suthakar said:
      ever since we had the upgrade from Microstation V8I to MIcrostation Connect edition.

      Did you upgrade ProjectWise Explorer version as well? Maybe also workspace must be modified.

      It looks like in your workspace, old configuration was left, so MicroStation CE tries to load mcm, which does not exist or is old (V8i) version.

      With regards,

        Jan

      Bentley Accredited Developer: iTwin Platform - Associate
      Labyrinth Technology  |  dev.notes()  |  cad.point

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Gabriel Cozma
      0 Offline Gabriel Cozma Fri, Nov 18 2022 3:12 PM in reply to Jan Ĺ legr

      The issue is a bit more complex, and it seems to be migrating on each workstation he uses. We just updated our Microstation users from V8I to Connect Edition and no one else has the error except him.  Multiple users were logged on his machine with no errors, however in every workstation he logged in had the same error and Microstation is crashing. I tried deleting his profile, reimaging his machine, cleaning the ProjectWise local folder but error is still there. Microstation is working locally, the error comes only when opening the files from ProjectWise.

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Reject Answer
      • Cancel
    Reply
    • Gabriel Cozma
      0 Offline Gabriel Cozma Fri, Nov 18 2022 3:12 PM in reply to Jan Ĺ legr

      The issue is a bit more complex, and it seems to be migrating on each workstation he uses. We just updated our Microstation users from V8I to Connect Edition and no one else has the error except him.  Multiple users were logged on his machine with no errors, however in every workstation he logged in had the same error and Microstation is crashing. I tried deleting his profile, reimaging his machine, cleaning the ProjectWise local folder but error is still there. Microstation is working locally, the error comes only when opening the files from ProjectWise.

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Reject Answer
      • Cancel
    Children
    • Robert Hook
      0 Offline Robert Hook Fri, Nov 18 2022 3:19 PM in reply to Gabriel Cozma

      Gabriel Cozma,

      There is a MicroStation CONNECT Key-in command "Show Configuration" that may permit you to compare a Good User (same file/workspace in PW) with the Bad User's text files.  If you keep all things equal between both users, then using a text differencing tool like: windiff, tkdiff, git, BeyondCompare, etc.; you should be able to spot the (configuration/install) issue rather easily.

      HTH,
      Bob



      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel

    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies