Qlik Community

Ask a Question

Support Knowledge Base

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Announcements

Troubleshooting Replicate Crashes on Windows.

David_Fergen
Digital Support
Digital Support

Troubleshooting Replicate Crashes on Windows.

When encountering a crash Replicate will generate a mini-dump that will be located at the following directory:

C:\Program Files\Attunity\Replicate\data\minidumps


If you observe files created in this folder, it could mean that one or more of the Tasks crashed at some point. While Replicate has sophisticated mechanisms to recover from crashes, it is always recommended to contact support and provide the relevant information.

This dump usually contains minimal info without full memory dumps. In many cases this may not be enough.


A Full dump will usually contain the complete memory dump of the failed process and will allow to debug the problem more accurately. The disadvantage of Full dumps is that they are very large in size.

SOLUTION

There are two methods to get a Full Dump from a Replicate Task:



Method 1 -- Replicate to generate full dumps

Add an environment variable on the Windows machine called AREP_CRASH_DUMP_TYPE and set the value to FULL.

The AREP_CRASH_DUMP_TYPE can have any of these values:
 

Value

Description

NONE

Functionality is disabled

MINI

Set MINI Dumps (default)

FULL

Set Full Dumps.

Changing the value of this environment variable requires restarting the Replicate service.



Advanced Tip To confirm the change, you can check the Windows Registry using the following key:
 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\repctl.exe
The value of DumpType could be (NONE=, MINI=1, FULL=2).
 

David_Fergen_0-1595443876725.png

 

 


Method 2 -- Using the Debug Diagnostic Tool (DebugDiag)

DebugDiag is a standard Microsoft utility that allows you to configure the dump and all of it's aspects using the DebugDiag Collection utility.
Using DebugDiag also means you don't have to restart the Replicate service.

Here are the steps to enable Full Dumps for Replicate:

1.    Download and install the latest DebugDiag X64 v2 from Microsoft:
https://www.microsoft.com/en-us/download/details.aspx?id=49924
2.    Run the DebugDiag 2 Collection utility.
3.    Click on Add Rule.
3.    Select “Crash”.
4.    Select “A specific process”
5.    Write repctl.exe in the “Selected Process”.
6.    Select the followings:

- “Full Userdump” in the “Action type for unconfigured…”
- Set value of 5 in the “Action limit”.
- Set value of 10 in the "Maximum number of userdumps..."
 

This is important so that you don't fill the storage with large dumps.

 

David_Fergen_1-1595443876728.png

 

7.    Click Next.
8.    Select the directory you want dump to be generated in.
9.    Select “Activate the rule Now”.

Important Notes

  • Include several dumps if possible, upload them compressed to the Support Portal.
  • If the dumps are very large and you are unable to upload them, ask the support engineer for an Upload site.
  • Always include Replicate logs files from the timeframe of the crash (Task, repctl, ...).
  • If the problem is reproducible set all logging to VERBOSE for short period of time, and attach these logs.
  • Attach the latest export of the Task (JSON file).
Labels (2)
Version history
Revision #:
4 of 4
Last update:
‎2020-08-28 06:06 AM
Updated by: