Quantcast
Channel: Andrew Bell's Activities
Viewing all articles
Browse latest Browse all 4948

Crash Reports: procedure and routing

$
0
0

 Product(s):MicroStation
 Version(s):08.11.09.608
 Environment:N\A
 Area:Security
 Subarea:General

Problem

User has concerns about the log files being transmitted to Bentley when MicroStation crashes, would like to know what route these crash reports take and if it is possible to prevent these logs from being send.



Solution

Mike Stratoti has provided a clear explanation on the automatic procedure of crash report transmittels, and I like to share these with you

The code that handles the transmission is written in VBScript so it can be reviewed by anyone. Customers can modify the transmittal behaviour if required.
This can be found in either the file manageExceptionLogs.hta or manageExceptionLogs.vbs, based on the version of the Bentley product.

The default sequence of handling a crash report is as follows:

  1. When a Bentley product detects a problem, 2 files are being generated; MiniDump.dmp and ExceptionLog.log
  2. The Bentley application then launcehs manageExceptionLogs.hta (of manageExceptionLogs.vbs)
  3. Next, manageExceptionLogs does the following:
  1. Allows the user to add any comments about the crash
  2. Manages the local history of the crash data
  3. Seeks permission from the user to send the crash report to Bentley for analysis
  4. Transmits the information to Bentley via a web service

The MiniDump.dmp is an abbreviated snapshot of the memory containing only stack and module information. Minimal "heap" memory is captured.
The ExceptionLog.log is a statement by the applicaiton of what it was doing at the time of the crash. It contains several sections including loaded modules, input queue, DGN models, etc. in plain text.
Details of graphics card information is also captured.

There are a few options available to influence this process:

  1. To prevent the roports from bein send you can delete the file manageExceptionLogs.hta (or manageExceptionLogs.vbs). This is a very poor solution and it is not recommended.
  2. Various administrative policies can be enforced using Windows Group Policy, product configuration, etc. via the environment variable "BentleyQualityReportControl"
    The function "CrashReport_determinePolicy" has documentation on the various options available. For example "Disable Auto Transmit" may be just what the user wants.
    The crash reports can be sent using HTTP or SMTP.
    In case of STMP, crash reports can be sent to the CAD Manager for determination if the reports should be forwarded to Bentley. Two variables in the code, in the section beginning with the comment "CHANGE THE NEXT 6 VARIABLES TO MATCH YOUR ENVIRONMENT", that can ficilitate this;
    "g_emailCADAdministrator" and "g_emailHostname"
  3. Set teg configuration variable "MS_ProcessExceptionLog" (can be found in the preferences.cfg for MicroStation CONNECT Edition or msfiles.cfg for MicroStation V8i) to control what is launced if the product detects a problem.
    This variable can also be set from within MicroStation

More about Managing Exception Logs can be found in MicroStation Help, under Programmed Customizations > Command Line Arguments and Exception Logs > Managing Exception Logs




See Also

Managing Exception Logs



 Original Author:Rene vandenBrink

Viewing all articles
Browse latest Browse all 4948

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>