If the ODBC Connector service bundled with the Qlik Data Gateway - Direct Access crashes intermittently, then any active reloads through the connector during the crash may fail with different errors. In this case, it may become necessary to collect crash dump files to proceed further with the investigation.
The logs show an ODBC crash at the time of the issue, this can be verified by reviewing the DirectAccess log located at C:\Program Files\Qlik\ConnectorAgent\data\logs
229 2023-07-26 21:00:59 [Manager ] [WARN ] ODBC process (1912) has exited (exit code: 0), going to restart it
A PowerShell script provided by Qlik's development team is attached to the article. It can be used to create the necessary entries in the Registry. Note: It requires to be executed with admin rights, you might need to change Security Policies for successful execution (Set-ExecutionPolicy RemoteSigned)
- Open the Windows Registry
- Go to the following path HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps
- In the LocalDumps folder, create new registry keys for both dotnet.exe and ConnectorAgent.exe
- In each of the folders, add:
- A String value, name it DumpFolder and indicate the folder path to store the dump files
- A DWORD, name it DumpCount and set it to 10
- A DWORD, name it DumpType and set it to 2
- Reboot the server for the registry setting changes to take effect
![NadiaB_0-1701790948702.png NadiaB_0-1701790948702.png](https://community.qlik.com/t5/image/serverpage/image-id/121063i95969728E2F270A6/image-dimensions/596x82?v=v2)
Once the dump files are available, attach them to the case, along with any other relevant information.
Related Content
Necessary information for Qlik Data Gateway - Direct Access cases
Environment
Qlik Data Gateway - Direct Access (All versions)