Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ProjectWise
  • Product Communities
ProjectWise
ProjectWise Design Integration Forum Running PW when using Remote Desktop
    • Sign In

    • State Not Answered
    • Replies 14 replies
    • Subscribers 59 subscribers
    • Views 6907 views
    • Users 0 members are here

    Running PW when using Remote Desktop

    caddcop
    Offline caddcop over 9 years ago

    Any thoughts on if there are issues when doing this? Here is my setup:

    • Remote PC is running Windows 8.0 Pro x64
    • Local PC is running Windows 7.0 Pro x86
    • MicroStation Application is Power InRoads Ss2 (most current version)

    A DOS window opens with clues as to what issues I see.

    Note that the path for Power InRoads is not ..\Program Files (x86)\.. but ..\Program Files\.. which would be correct if I was running PW on my local PC.

    The result is - I cannot run any Power InRoads commands. I also setup a -debug application in ProjectWise so I could Run AS... and run a debug on the configuration. But it does not seem to help too much as there is a bunch of Hocus Pocus going on that creates that tmp file on the fly so I can't see where its getting this wrong path.

    • Sign in to reply
    • Cancel
    • caddcop
      0 Offline caddcop Sat, Sep 20 2014 8:32 AM

      Does PW read a registry setting to find the paths to certain programs? If so, is there a way to force it to read from the remote desktop?

      Or do I need to remove the associations and recreate them - is it using the path from there? Because I actually have multiple associations for PowerInRoads and when logged in via remote desktop, only the Program Files (x86) versions have icons. When I log-in local, the Program Files version are the only ones with icons. So something know the difference.


      Charles (Chuck) Rheault
      CADD Manager

      MDOT State Highway Administration

      • MicroStation user since IGDS, InRoads user since TDP.
      • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Scott M. Turner
      0 Scott M. Turner Sun, Sep 21 2014 6:12 PM in reply to caddcop

      ProjectWise application configurations use the registry settings from the PC where the application configuration was created (unless using the OOB settings or explicit paths).

      If you have more than one PC with multiple versions of the same software, you can configure PW to handle this; just build separate Actions for each version of the application.  If you know the class name that you need, you can build this manually.  Otherwise temporarily install PWA on the PC where the software is installed and build the action you need.  Keep in mind that you may have separate configurations for different versions or 32/64 bit.

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • caddcop
      0 Offline caddcop Sun, Sep 21 2014 9:27 PM in reply to Scott M. Turner

      When I am on Remote Desktop, I am running ProjectWise and Power InRoads on a Windows 8, 64 bit PC, but accessing the remote desktop from a Windows 7, 32 bit install. My Association points to my Program Files (x86) path for Power InRoads, but when PW builds its temporary cfg file, its using paths based upon Program Files for certain MDL Applications. Because it handles building and using its own temporary cfg file, I don't know how to correct this.


      Charles (Chuck) Rheault
      CADD Manager

      MDOT State Highway Administration

      • MicroStation user since IGDS, InRoads user since TDP.
      • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Scott M. Turner
      0 Scott M. Turner Sun, Sep 21 2014 9:55 PM in reply to caddcop

      Can you run PIR on the W8 machine without ProjectWise?

      If yes, the issue is in the integration.

      If no the issue is (at least) in the application.

      From what you say above you also are using workspaces. Have a look at the configuration blocks for each node and make sure that any paths can be evaluated correctly.  If any of the paths point to a local folder where the path is in 8.3 notation, open a DOS prompt on the W8 box and see if the path evaluates to the same location as it does on the W7 box.

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • caddcop
      0 Offline caddcop Mon, Sep 22 2014 10:12 AM in reply to Scott M. Turner

      Outside of PW, the application loads correctly.

      In the PW local cache folders, there is a workspace folder and in it are many of the PW config files that do their hocus-pocus that makes PW work like it does. In there, I can see the places where the Program Files (x86) is replaced with the Program Files path. I was able to create an msdebug.txt file, too.

      I can tell you exactly where it goes south. PW_MANAGEDWORKSPACE_SHADOW_MS_DGNAPPS and MS_DGNAPPS

      The third file created contains these lines at the top of the file:

      # This file is automatically generated. Changes will not be persisted.
      # This file represents the Configuration Settings Block: Personal Workspace: 1085
      PW_MANAGEDWORKSPACEENABLED>453;

      Then, further down in this file - it contains these lines which are the problem:

      MS_DGNAPPS>C:\Program Files\Bentley\PowerInRoads V8i\PowerInRoads\CivilPlatform\DialogExt.ma
      PW_MANAGEDWORKSPACE_SHADOW_MS_DGNAPPS>(453,1907,6)|C:\Program Files\Bentley\PowerInRoads V8i\PowerInRoads\CivilPlatform\DialogExt.ma
      MS_DGNAPPS>C:\Program Files\Bentley\PowerInRoads V8i\PowerInRoads\InRoadsGroup\bin\CivUstAT.ma
      PW_MANAGEDWORKSPACE_SHADOW_MS_DGNAPPS>(453,1907,7)|C:\Program Files\Bentley\PowerInRoads V8i\PowerInRoads\InRoadsGroup\bin\CivUstAT.ma
      MS_DGNAPPS>C:\Program Files\Bentley\PowerInRoads V8i\PowerInRoads\InRoadsGroup\bin\gpkdgnAT.ma
      PW_MANAGEDWORKSPACE_SHADOW_MS_DGNAPPS>(453,1907,8)|C:\Program Files\Bentley\PowerInRoads V8i\PowerInRoads\InRoadsGroup\bin\gpkdgnAT.ma
      MS_DGNAPPS>C:\Program Files\Bentley\PowerInRoads V8i\PowerInRoads\InRoadsGroup\bin\gpkgalserverAT.ma
      PW_MANAGEDWORKSPACE_SHADOW_MS_DGNAPPS>(453,1907,9)|C:\Program Files\Bentley\PowerInRoads V8i\PowerInRoads\InRoadsGroup\bin\gpkgalserverAT.ma

      So, how to I tell PW that this path it uses in these locations is incorrect?

      In the msdebug.txt, the path to InRoads is initially correct and the places it is used start out correct, but eventually this code appears to redefine it to the wrong Program Files folder.


      Charles (Chuck) Rheault
      CADD Manager

      MDOT State Highway Administration

      • MicroStation user since IGDS, InRoads user since TDP.
      • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
      • 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