Creating a full memory dump for an estos process

In the current versions of the products listed above, the default configuration generates a memory dump via the third-party application Sentry in the event of a crash.

In specific situations, however, it may be necessary to analyse a full memory dump or a crash report generated by Microsoft Windows Error Reporting.

This article explains how to configure error reporting.

Please only use these settings if it is actually a crash .

Please always follow the instructions or requirements provided by the relevant support team.

Even in the event of a crash, the debug logs for the relevant application are required.

The following options are available for error reporting:

• Sentry Error Reporting
• Creation of a mini dump (small memory dump) by the application itself,
• Creation of a full memory dump by the application itself,
• Generation of an error report via Microsoft Windows Error Reporting.

The option is selected via a registry entry in the Microsoft Windows Registry.

A registry entry Dump of type DWORD is used for this

• In the case of estos ProCall 8 Enterprise, there is a registry key HKEY_LOCAL_MACHINE\Software\ESTOS\UCServer4\Server and
• in the case of estos MetaDirectory 6, in the registry branch HKEY_LOCAL_MACHINE\SOFTWARE\ESTOS\MetaDirectory\Server

to be deposited.

An application can only write to a memory image if the operating system still permits it.

Procedure

Sentry Error Reporting

In the default configuration of estos products, error reporting is set to Sentry . A registry entry Dump either does not exist or contains the value 0.

An error report generated using Sentry is stored locally and, where technically feasible, also made available to estos for analysis.

Further information can be found in the article What kind of data does estos collect and why?.

Die Ablageorte für die Sentry Fehlerberichte sind im Installationsstandard:

Autonomous error reporting by the application

If estos ProCall 8 Enterprise or estos MetaDirectory 6 generates an error report automatically, you can choose between creating a mini dump or a full dump.

Proceed as follows to prepare the relevant application for creating a memory dump independently:

1. Run regedit.exe
2. Navigate to 
   HKEY_LOCAL_MACHINE\Software\ESTOS\UCServer4\Server  in the case of estos ProCall 8 Enterprise
   HKEY_LOCAL_MACHINE\SOFTWARE\ESTOS\MetaDirectory\Server in the case of estos MetaDirectory 6
3. Click on the  menu Edit -> New -> DWORD (32-bit) Value
4. Enter Dump as the name
5. To create a full memory dump, enter the value 2  (decimal); to create a mini dump, enter the value  1  (decimal)
6. Restart the relevant services of the application
7. In the event of a future crash, a full memory dump or a mini dump will now be generated in "c:\crashreport".

Example of how to enable a local full memory dump for the estos ProCall 8 Enterprise Server

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\ESTOS\UCServer4\Server]
"Dump"=dword:00000002

Microsoft Windows Error Reporting

Using Windows Error Reporting , you can determine, which application has crashed  (e.g. EUCSrv.exe, EUCMediaServer.exe, uc-media-server.exe, MetaAdmin.exe, MetaServer.exe, CalendarReplicator.exe, AnalyticsDataService.exe, AnalyticsReportingService.exe, AnalyticsWebserver.exe, EUCWeb.exe, etc.).

Key information regarding application crashes can be found in the Microsoft Windows Event Viewer (eventvwr.exe).

In the following path , you should check whether  Windows has generated a dump itself:

C:\ProgramData\Microsoft\Windows\WER\

It should be noted that although Windows creates a file for every crash, if the process crashes repeatedly for the same reason, these files will not be populated.
A populated memory dump has an approximate size of 150 MB – 2 GB. If the files are only a few KB in size, they are empty and unsuitable for analysis.

If crash dumps are not being written, you can force this to happen by following the instructions below: 
http://msdn.microsoft.com/en-us/library/windows/desktop/bb787181(v=vs.85).aspx

Example of how to enable a Microsoft Windows Error Reporting dump for the MetaDirectory Administrator (MetaAdmin.exe)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\MetaAdmin.exe]
"DumpType"=dword:00000002
"DumpCount"=dword:00000100
"DumpFolder"="c:\\crashreport"

Further information

• Creating a debug log from UCServer
• Generating a debug log from MetaDirectory
• What data does estos collect, and for what purpose?
• Creating a full memory dump on the UCServer
• Creaating a full memory dump of the MetaDirectory