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
    Parents
    • 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
    • Molly Watts
      0 Offline Molly Watts Wed, Oct 1 2014 2:57 PM in reply to caddcop

      The program association you have set as the default (with the red check) looks correct, and will be what's used when double clicking the file.  What it does is use the class name (Bentley.PowerInRoads.Applicaton)  to determine where that application is installed on the machine you are running ProjectWise.   What I can't see is if you have any command line options configured with it, can you expand the + next to that specific association?



      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • caddcop
      0 Offline caddcop Wed, Oct 1 2014 3:33 PM in reply to Molly Watts

      The top one is the one I try to use. The second one is how I find out what is assigned when and how. The rest are apparently what is used when I run without using Remote Desktop, except for the PowerSurvey icon, but I seldom use that one.


      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
    • Molly Watts
      0 Offline Molly Watts Wed, Oct 1 2014 4:00 PM in reply to caddcop

      Do you have a test file that you can try removing any managed workspace configuration settings blocks, double click the file and do you get the same error messages?



      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • caddcop
      0 Offline caddcop Wed, Oct 1 2014 4:42 PM in reply to Molly Watts

      How do I remove any managed workspace configuration settings blocks? Please answer this, even after you read on...

      I am still learning PW nuances. We are a client / end user and not the PW administrators so everything I am doing is on the client side.

      OK, I went into the Configuration dialog box and removed the lines that tried to load the MDL's. Then, I edited the primary search paths > visible MDL Applications to add the paths these MDL's need. I used a mixture of predefined variables and fixed paths.

      Since making these edits, I can load locally or via the VPN/Remote Desktop and the full application loads.

      I did notice that the network folders in this office do not function in the RWK using their drive letter, but with a \\tsclient\A\, where the mapped drive was A:\.


      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
    • Molly Watts
      0 Offline Molly Watts Thu, Oct 2 2014 10:05 AM in reply to caddcop

      Removing the managed workspace depends on how they are assigned.  if its at a folder level, you might just be able to uncheck the "allow inheritable configuration block associations..." box at the bottom of the workspace tab in the document properties.  

      It sounds to me that you will need to work with the ProjectWise Administrator of the datasource to determine why you are getting these errors.  



      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    Reply
    • Molly Watts
      0 Offline Molly Watts Thu, Oct 2 2014 10:05 AM in reply to caddcop

      Removing the managed workspace depends on how they are assigned.  if its at a folder level, you might just be able to uncheck the "allow inheritable configuration block associations..." box at the bottom of the workspace tab in the document properties.  

      It sounds to me that you will need to work with the ProjectWise Administrator of the datasource to determine why you are getting these errors.  



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

    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