Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ProjectWise
  • Product Communities
ProjectWise
ProjectWise Design Integration Forum Managed Workspace fails to load in 10.00.02.320 but not in 10.0.01.171
    • Sign In

    • State Not Answered
    • Replies 3 replies
    • Subscribers 62 subscribers
    • Views 2087 views
    • Users 0 members are here

    Managed Workspace fails to load in 10.00.02.320 but not in 10.0.01.171

    Tim Knaus
    Offline Tim Knaus over 5 years ago

    I have run into an issue with a client hosted projectwise managed workspace. I am attempting to open files in their projectwise using the 10.00.02.320 PW Explorer client but I get this error when trying opening a microstation file. 

    If I open the same file in the same location with the 10.00.01.171 PW Explorer client it works with no issues. Since I am unable to see/investigate the client managed workspace I have run out of ideas as to the cause of this problem. Has anyone run into similar issues with Client versions causing managed workspaces issues?

    I know this isn't much to go on but I thought maybe someone has had similar issues.

    Thanks...

    • Sign in to reply
    • Cancel
    • Gary Mansager
      0 Offline Gary Mansager Mon, Sep 10 2018 5:39 PM

      Would recommend turning on the debugging options. That will help tell you what's wrong. This is found under PW>Tools>Options | Settings Tab, expand Managed Configuration and expand Export relative path errors handling. Click the Prompt User radio button. This may tell you what is wrong.The 320 build is less error tolerant, and if a condition is false, the MW may not load for example. Other areas to look such as a MS_DGNAPP that is not found, or MS_INITAPPS may be the culprit.

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Jeff Burrill
      0 Offline Jeff Burrill Tue, Sep 11 2018 4:55 PM

      My suggestion - turn up your pwc.log file and dig in. The error messages will be there - cryptic as they may be, but without turning up the logging, you won't have much context to work with.

      I struggled for quite a while with Last error 222 with a managed workspace ever since upgrading my client to PW 10.00.02.265. Same thing - the managed workspace works fine and MicroStation will open when using PW Connect 10.00.01.171, but not 02.265.

      I was able to resolve the issue, which turned out to be a relatively easy fix, but it was VERY difficult to find. In my case, the managed workspace was built based on custom local workspace we had used for many years. We included one directory from PW that had a handful of our standard cfg files that were (at the time) too much effort to bring into CSB's. A CSB was added that touched that directory and then told it to include those cfg's if it existed. And it worked flawlessly until I upgraded to 2.265.

      As it turns out, there were a few %level directives in some of those cfg files that it did not like, though the error only mentioned a problem with invalid "LevelUtils". The wording of the error message sent me way down the wrong rabbit hole for a long time. Because it used the word "level", I kept looking for something related to MicroStation levels. Maybe it's a bad or missing MDLAPP or something along those lines, or some conflict in a MS_LEVEL* var. Nope. %level. It also did not like an ' mark within a variable declaration. Why that triggers now and not before (because the value resolved as expected before and included the ') only Bentley programmers know, but that's what happened.

      Bentley REALLY needs to provide some better MWS debugging to go along with these more stringent processing requirements. It simply should NOT have been this difficult to resolve. Options like Gary mentions are great, but the problem in this case is that they don't hit in the step where this fails and throws a nearly useless error code. Adding -debug to the open command program association is also of no use either for the same reason.

      Please note that I post here on a voluntary basis and am not a Bentley employee. 

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Tim Knaus
      0 Offline Tim Knaus Wed, Sep 12 2018 3:34 PM in reply to Jeff Burrill

      Thanks for the response, I will definitely give that a go..

      • 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