MORE INFORMATION
By default, SQL Server 2005 Analysis Services automatically generates minidump files when an exception occurs. For the default installation, the minidump files are written to the %ProgramFiles%\Microsoft SQL Server\
\MSSQL.x\OLAP\Log folder and include the following information:
- All thread stacks
- Second-order memory that is referenced by pointers on the stack
- Information about the Process Environment Block (PEB)
- Information about the Thread Environment Block (TEB)
- Information about recently unloaded modules
- Thread state information
Note MSSQL.x is a placeholder for the corresponding value for the system. To determine the corresponding value for the system, determine the value of the MSSQLSERVER or the named instance registry entry under the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\OLAP
The
Exception section in the Msmdsrv.ini file controls the memory dump file generation. The file is located in the %ProgramFiles%\Microsoft SQL Server\
MSSQL.x\OLAP\Config folder. When you open the file in Notepad, you notice a section in the
Exception XML tag that resembles the following:
<Exception>
<CreateAndSendCrashReports>1</CreateAndSendCrashReports>
<CrashReportsFolder/>
<SQLDumperFlagsOn>0x0</SQLDumperFlagsOn>
<SQLDumperFlagsOff>0x0</SQLDumperFlagsOff>
<MiniDumpFlagsOn>0x0</MiniDumpFlagsOn>
<MiniDumpFlagsOff>0x0</MiniDumpFlagsOff>
<MinidumpErrorList>0xC1000000, 0xC1000001, 0xC1000016, 0xC11D0005, 0xC102003F</MinidumpErrorList>
<ExceptionHandlingMode>0</ExceptionHandlingMode>
<CriticalErrorHandling>1</CriticalErrorHandling>
</Exception>
You can control the behavior of generating the memory dump file by modifying the settings in this section. You can also modify these settings in SQL Server Management Studio. For more information about these settings, visit the following Microsoft Developer Network (MSDN) Web site:
How to disable the automatic memory dump file for Analysis Services
The value of the
CreateAndSendCrashReports setting determines whether a memory dump file will be generated. This setting can have one of the values that are listed in the following table.
Value | Description |
0 | This value specifies that Analysis Services does not generate any memory dump file. Additionally, the value of the other settings under the Exception section is ignored. |
1 | This default value enables the memory dump file. However, SQL Server 2005 Analysis Services does not send an error report to Microsoft. |
2 | This value specifies that SQL Server 2005 Analysis Services generates a memory dump file and sends an error report to Microsoft. |
When the
CreateAndSendCrashReports setting is set to 1 or 2, the other settings in the
Exception section can control the type of the memory dump file and what information to include in the memory dump file.
How to configure SQL Server 2005 Analysis Services to generate a full dump file automatically
To configure SQL Server 2005 Analysis Services to generate a full dump file automatically when an exception occurs, you can set the
SQLDumperFlagsOn setting to 0x34. Additionally, if you want to configure SQL Server 2005 Analysis Services to generate a full dump file that includes the handle information, you can set the
SQLDumperFlagsOn setting to 0x34 and the
MiniDumpFlagsOn setting to
0x4. For example, the
Exception section in the Msmdsrv.ini file may resemble the following:
<Exception>
<CreateAndSendCrashReports>1</CreateAndSendCrashReports>
<CrashReportsFolder/>
<SQLDumperFlagsOn>0x34</SQLDumperFlagsOn>
<SQLDumperFlagsOff>0x0</SQLDumperFlagsOff>
<MiniDumpFlagsOn>0x4</MiniDumpFlagsOn>
<MiniDumpFlagsOff>0x0</MiniDumpFlagsOff>
<MinidumpErrorList>0xC1000000, 0xC1000001, 0xC1000016, 0xC11D0005, 0xC102003F</MinidumpErrorList>
<ExceptionHandlingMode>0</ExceptionHandlingMode>
<CriticalErrorHandling>1</CriticalErrorHandling>
</Exception>
How to generate a full dump file that includes handle information manually
To troubleshoot issues such as a server that stops responding (hangs), you may want to generate a full dump file that includes handle information manually. To do this, you can run the Sqldumper.exe utility at the command prompt together with the following arguments:
Sqldumper.exe PID 0 0x34:0x4 0 PathToDumpFile
Note PID represents the process ID of the SQL Server 2005 Analysis Services process.
PathToDumpFile represents the folder to which the dump file is written.
For more information about how to use the Sqldumper.exe utility to generate a dump file, click the following article number to view the article in the Microsoft Knowledge Base:
827690
How to use Sqldumper.exe to generate dump files for Windows applications