Troubleshooting Custom Workspaces in InRoads

Jacquelyn Pettus — Wed, 18 Nov 2015 20:11:27 GMT

Current Revision posted to OpenRoads | OpenSite Wiki by Jacquelyn Pettus on 11/18/2015 8:11:27 PM

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.

Troubleshooting Custom Workspaces in InRoads

Kevin McDonald — Fri, 11 Apr 2014 20:55:56 GMT

Revision 4 posted to OpenRoads | OpenSite Wiki by Kevin McDonald on 4/11/2014 8:55:56 PM


	Applies To

	Product(s):	InRoads
	Version(s):	08.11.07.615+
	Environment:	N/A
	Area:	General
	Subarea:
	Original Author:	Jacquelyn Pettus, Bentley Technical Support Group

Problem:

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

Troubleshooting Workflow:

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 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.

Troubleshooting Custom Workspaces in InRoads

Kevin McDonald — Fri, 11 Apr 2014 20:54:55 GMT

Revision 3 posted to OpenRoads | OpenSite Wiki by Kevin McDonald on 4/11/2014 8:54:55 PM


	Applies To

	Product(s):	InRoads
	Version(s):	08.11.07.615+
	Environment:	N/A
	Area:	General
	Subarea:
	Original Author:	Jacquelyn Pettus, Bentley Technical Support Group

Problem:

InRoads will not start when using a custom workspace.

Troubleshooting Workflow:

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 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.

Troubleshooting Custom Workspaces in InRoads

Kevin McDonald — Fri, 11 Apr 2014 20:42:49 GMT

Revision 2 posted to OpenRoads | OpenSite Wiki by Kevin McDonald on 4/11/2014 8:42:49 PM


	Applies To

	Product(s):	InRoads
	Version(s):	08.11.07.615+
	Environment:	N/A
	Area:	General
	Subarea:
	Original Author:	Jacquelyn Pettus, Bentley Technical Support Group

Problem:

InRoads will not start when using a custom workspace.

Troubleshooting Workflow:

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.

www.youtube.com/watch

Troubleshooting Custom Workspaces in InRoads

Jacquelyn Pettus — Thu, 10 Apr 2014 16:33:43 GMT

Revision 1 posted to OpenRoads | OpenSite Wiki by Jacquelyn Pettus on 4/10/2014 4:33:43 PM


	Applies To

	Product(s):	InRoads
	Version(s):	08.11.07.615
	Environment:	N/A
	Area:	General
	Subarea:
	Original Author:	Jacquelyn Pettus, Bentley Technical Support Group

Problem:

InRoads will not start when using a custom workspace.

Troubleshooting Workflow:

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.