TEM Component Dump File Location
Where can I find dump files created by the TEM components?
For applications that run as a service (BESClient, FillDB, GatherDB, etc.), the dump file is written to:
For example, by default this would be:
C:\Program Files\BigFix Enterprise\BES Client\BESClient.dmp
For applications that run in a user context (BESConsole, BESAdmin, etc.), the dump file is written to:
For example: C:\Documents and Settings\Administrator\Local Settings\Application Data\BigFix\BesCon~1.dmp
Dump files can be created by a number of causes. In order to identify the cause of the dump file, please open a service request to have the dump file analyzed.
If you receive a popup message that indicates "Please tell Microsoft about this problem", click the "To see what data this error report contains, click here link which should bring you to a new popup with a couple of additional links. From this popup click on the "To view technical information about the error report, click here" which should then bring up another popup with entries indicating the "Error Report Contents".
Make a copy of the dump file referenced here prior to closing the popup window, and send the copy directly to TEM. Also note that if you close this dialog box prior to copying the dump file, Microsoft may remove the dump file.
Minidumps may need to be explicitly enabled. Make sure that the following are set:
[HKEY_LOCAL_MACHINE\Software\BigFix] "WriteMiniDumps"=dword:00000001 "MINIDUMP_TYPE"=dword:00000002
[HKEY_USERS\S-1-5-18\Software\BigFix] "WriteMiniDumps"=dword:00000001 "MINIDUMP_TYPE"=dword:00000002
The simplest and best way to get a dump file is to use the Sysinternals tool procdump available at http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx?ppud=4. It is a command-line tool that makes it easy to get a dump file that can be readily analyzed.
For example, to write a dump of the Console:
procdump BESConsole.exe c:\console.dmp
To get a full memory dump:
procdump -ma BESConsole.exe c:\console.dmp
In addition, for a hung process or one that consumes a lot of CPU, it is often important to get two or three dumps to easily determine the cause of the hang or CPU spike.