Product(s):	InRoads
Version(s):	08.11.07+
Area:	General

 

Problem:

InRoads will not start when using a custom workspace or InRoads launches but is missing certain tasks/menus/functions.

Possible Solutions:

When using a custom workspace, it is possible that some of the configuration variables defined by the user can conflict with the necessary variables that are defined by the InRoads product. The result is that InRoads may not launch properly or may not start at all.

The following workflow is the best practice for troubleshooting this problem:

• Verify that the problem is a result of the custom workspace by launching InRoads in an untitled (or new) workspace.  If InRoads launches properly, it is very likely there is a problem with the custom workspace.
  
  
• There are several variables that are more likely than others to cause a conflict with InRoads.  Pay special attention to:
  
  
  • Any of the variables that start with CIVIL_
  • MS_CELLLIST
  • MS_DGNAPPS
  • MS_DGNLIBLIST
  • MS_GUIDGNLIBLIST
  • MS_LIBRARY_PATH
    
    Variables such as the MS_DGNAPPS and MS_LIBRARY_PATH can affect the InRoads startup, and variables such as the MS_GUIDGNLIBLIST affect the various tasks and menus InRoads loads into MicroStation.
    
    One way to troubleshoot these variables, is to add the "-debug" switch to the Target path in the icon, then review the resulting 'msdebug.txt'.
    The following video demonstrates how to use the 'msdebug.txt' file to troubleshoot an error in InRoads:
    

    www.youtube.com/watch

    
    
    
    
• One of the more common errors encountered is when one of the above variables is defined using "=" instead of ">".  ">" appends the configuration variable.  "=" overwrites the variable - and often times the definitions required for InRoads to launch.
  
  
• Rename any custom or edited CFG files in your workspace and test to see if the issue can be isolated to a specific CFG file.
  
  
  • If so, open the configuration file in Notepad and use the "#" character to comment out everything in the file.
    
    
  • Then, begin to un-comment a block of text at a time and attempt to launch InRoads.  Using the process of elimination, the line that is causing the conflict can be isolated.