Loading InRoads from within MS

Hello -

I like to load InRoads using a custom tool (keyin mdl load civustat.ma).  However, since updating to newer versions of both IR and MS, this tool no longer "works" and results in the following Message Center errors:

"MDL Loader:  Unable to load library (DLL or MDL shared library) CivUstAT"

"OS could not load C:\Program Files (x86)\Bentley\InRoads Group V8.11\bin\CivUstAT.dll, error 126."

The same occurs when trying to "load" from the Utilities->MDL dialog box (the CivUstAT.ma path is listed in both the MS_MDL and MS_MDLAPPS variables).  However, if I select "Browse" and load CivUstAT.ma, it loads with no errors.  I can then close IR and the custom tool and "load" button will work for the duration of the MS session.

Operation also appears perfectly normal when starting IR from the Start Menu shortcut(s).

Is there something I'm not doing properly to get the custom tool to work?

FYI, I'm running InRoads SS2 (08.11.07.536) in MS SS3 (08.11.09.292).

Parents
  • You can also load it with a Function Key.

    Go to Workspace >  Function Keys, and choose your "trigger". I have mine set at ALT+F1. In the Action field, type in:

    mdl l "C:\Path to civustat.ma"

    On my home machine, it's: 

    mdl l "C:\Program Files\Bentley\InRoads Group V8.11\bin\civustat.ma"

  • Yeah, sadly that produces the same .DLL error (I'm using a macro, you're using a function key, same difference).

    Even using that key-in in the Key-in window produces the same .DLL error on my PC. However, if I start InRoads from the MDL dialog then exit InRoads, the key-in will work--because the .DLL is already loaded. I assume you're starting a plain-vanilla workspace, or a project workspace that has no "links" to InRoads--as opposed to starting InRoads from the Start Button. If so, I am very curious why it works for you and not me (and others). Windows version? Installation tricks? ("Oh, you have to install ustn .357 AFTER InRoads SS2!" or "Hey, you didn't run makeinroadsrunwithkeyin.exe!") :-)

    I will admit we're running Windows 7/64, and because of the Draconian rights with the installations, users have had a helluva time getting write access to some folders on the C drive, which has caused some quirkyness across the board with applications. This is exacerbated with Windows Update, which seems to rollback read/write on some folders. Some offices simply charge users with Admin rights, and hope for the best.

  • I'm having issues loading InRoads via key-in also on Win 7 32bit. This worked with XP. I have also noticed if I load InRoads through mdl and then close the program InROads will start with key-in. The other issue is that no matter how I initiate InRoads I get different .dll messages.

    This is the other thread http://communities.bentley.com/products/road___site_design/f/5922/p/83019/231630.aspx#231630 with these issues.

    Mike

    Microstation CONNECT - 10.17.2.61

    ORD - 2021 R1 10.10.1.3

    ORD 2022 R1.1 - 10.11.3.2

    ORD 2022 R3 -  10.12.2.4

    Microstation v8i SS 10 - 08.11.09.919

    Power InRoads v8i - 08.11.09.615

    ProjectWise - 10.0.3.453

Reply
  • I'm having issues loading InRoads via key-in also on Win 7 32bit. This worked with XP. I have also noticed if I load InRoads through mdl and then close the program InROads will start with key-in. The other issue is that no matter how I initiate InRoads I get different .dll messages.

    This is the other thread http://communities.bentley.com/products/road___site_design/f/5922/p/83019/231630.aspx#231630 with these issues.

    Mike

    Microstation CONNECT - 10.17.2.61

    ORD - 2021 R1 10.10.1.3

    ORD 2022 R1.1 - 10.11.3.2

    ORD 2022 R3 -  10.12.2.4

    Microstation v8i SS 10 - 08.11.09.919

    Power InRoads v8i - 08.11.09.615

    ProjectWise - 10.0.3.453

Children
No Data