Problem:

InRoads will not start when using a custom workspace.

Troubleshooting Workflow:

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 workspace.  If InRoads launches properly, it is very likely there is a problem with the custom workspace.
  
  
• Open the custom User Configuration File (*.ucf) or Project Configuration File (*.pcf) in Notepad.  Use the "#" character to comment out everything in the file.
  
  
• Verify that InRoads will load with all lines commented out in the UCF or PCF.
  
  
• Now, begin to uncomment 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.
  
  
• 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
    
    
• 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.