You are currently reviewing an older revision of this page.
MSDebug File
Operating System: ALL (that are certified to run the versions of MicroStation above)Document Number: 8227What is an MSDebugAn MSDebug.txt file is the output created from running the ustation.exe with the -debugswitch. The information that gets dumped to the file contains a list of all the configurationfiles that run, and what variables where set by each file. The -debug switch creates themsdebug.txt file in the same directory where the ustation.exe file is located. Thedirectories for specific versions of MicroStation are outlined below.1. Default location for MicroStation V8 - C:\programfiles\Bentley\Program\MicroStation2. Default location for MicroStation J - C:\Bentley\Program\Microstation3. Default location for MicroStation 95\SE - C:\win32app\ustationHow to create an MSDebugYou can create the msdebug.txt file several ways. To create anMSDebug.txt file, start MicroStation with the -debug parameter:1. From a DOS prompt \Command WindowGo to a Command prompt and change to the directory where ustation.exe islocated and type the following command: ustation -debugExamples:For MicroStation V8 - c:\programfiles\Bentley\Program\Microstation\ustation - debugFor MicroStation J - c:\bentley\program\microstation\ustation -debugFor MicroStation 95\SE - c:\win32app\ustation\ustation -debugYou should get a DOS window that says "Debugging output saved to[msdebug.txt]".Hit the escape key.Locate the msdebug.txt file in the appropriate directory.2. From the MicroStation shortcut iconInsert a -debug switch into the MicroStation shortcut.Examples:For MicroStation V8 - Shortcut TARGET: "javascript:void(null);" -debugFor MicroStation J - Shortcut TARGET: "javascript:void(null);" -debugFor MicroStation 95\SE - Shortcut TARGET: "javascript:void(null);" -debugSave the changes and then double click the icon.You should get a DOS window that says "Debugging output saved to[msdebug.txt]".Hit the escape key.Locate the msdebug.txt file in the appropriate directory.
NOTE: Remember to remove the switch from the icon after creating theMSDebug.txt file.
3. From the Windows "Run" command windowChoose Start > RunType the path to the ustation.exe file
Examples:For MicroStation V8 - c:\program files\Bentley\Program\Microstation\ustation.exe -debugFor MicroStation J - c:\Bentley\Program\MicroStation\Ustation.exe -debugFor MicroStation 95\SE - c:\win32app\ustation\ustation.exe -debugClick OK.You should get a DOS window that says "Debugging output saved to [msdebug.txt]".Hit the escape keyLocate the msdebug.txt file in the appropriate directory.How to make use of the MSDebug fileThere are basically two sections to the MSDebug file. The first sectioncontains a list of all the configuration files that run, and what variables were set byeach file. Each configuration file that gets run has a starting point and an endingpoint identified as follows:1. Processing macro file[C:\Bentley\Program\MicroStation\config\mslocal.cfg]2. End of macro file [C:\Bentley\Program\MicroStation\config\mslocal.cfg]Located in-between these two lines are all variables and their settingsthat get loadedfrom that particular configuration file:Examples:Processing macro file[d:\Bentley\Program\MicroStation\config\system\mslocale.cfg](system): MS_SPELLINGLANGUAGE=AmericanEnglish [AmericanEnglish](system): MS_HELPLOAD_LANGUAGE=en [en]End of macro file [d:\Bentley\Program\MicroStation\config\system\mslocale.cfg]Processing macro file [d:\Bentley\Program\MicroStation\config\appl\qvisgl.cfg](appl): MS_GRAPHICSACCELERATOR=qvisgl [qvisgl]End of macro file [d:\BentleyProgram\MicroStation\config\appl\qvisgl.cfg]It also indicates at what level the variable has been set, i.e. system,appl, user, site, project, or predefined.Below is a list of default configuration files that should be listed inthe MSDebug.txt:
The last section of the MSDebug.txt file is the Configuration Variable SummaryHere you will find the following:1. A listing of all configuration variables2. At what level each variable was set3. The full path to the location of the files4. Whether or not the variable is locked or unlockedUsing the MSDebug.txt file to help trouble shoot Processor exceptionerrorsThe msdebug file can help you trouble shoot Processor exception errorsby helping you find where specific files are located. The steps for this procedure arelisted below:1. Create the msdebug.txt file and then open it in notepad.2. Search for the following variables using the Search > Find drop downmenu, in notepad:MS_USERPREF (this will tell you where your user preference file islocated)MS_INITAPPS (this will tell you if any other programs are beinginitiated during startup)MS_SYMBRSRC (this will point you to the location where all theMicroStation resource files are located)MS_DGNAPPS (this will tell you what other programs are being launchedwith MicroStation)MS_DGNMACROS (this will tell you what macros are being launched with MicroStation)_USTN_UIPATH (this will tell you the location of any *.m0* files)3. Be sure to click the "next" button in the Search dialog box to besure you find all instances of the variables.