State of knowledge

October 2026

Relevant for
ProCall 8 Enterprise
ProCall Desktop for Windows

Observation

The ProCall Desktop for Windows crashed. 

Procedure for analysis

  • Check if the latest version of ProCall Enterprise is installed and update if necessary.
  • Check that the system requirements are met.
  • Check if corresponding ProCall Enterprise Known Issues and Limitations have been published.
  • Check whether a currently known cause of the crash is documented below.
  • Check: Can an event or operation be located where this behavior occurs?

Further procedure after the analysis

  • In the ProCall client, set the logging to debug:   
    Creating a debug log for ProCall client
  • Prepare client so that a full memory dump (crash dump) is written in case of a crash:
    Creating a full memory dump on the ProCall client
  • Re-enact event or if this is not possible, wait for the next crash to occur
  • Note which action was performed last before ProCall Desktop for Windows crashed and at what time this happened.
  • After restarting ProCall Desktop for Windows, create the log files.
  • Save the Windows Event Logs (Event Viewer).
    The application or system logs may contain important information about the crash and its cause.
  • Create a ticket in our portal https://jira.estos.de/servicedesk/customer/portals and submit the collected data and information.

Currently known causes of crashes

Crash in Sentry Error Reporting

If the Microsoft Windows profile contains one or more umlauts that are also used in the Microsoft Windows user path specifications (USERPROFILE, APPDATA, LOCALAPPDATA), ProCall Desktop for Windows crashes during the initialisation of Sentry Error Reporting

...
01.12.2025 07:00:01:101;32;mainthread-25960;CECtiClientApp::InitInstance;Init Help
01.12.2025 07:00:01:102;32;mainthread-25960;CECtiClientApp::InitInstance;Init Exceptionhandling
01.12.2025 07:00:01:102;4;mainthread-25960;CECtiClientApp::InitInstance;Init Exceptionhandling: Sentry
--> End of log output at log level "Debug" --> Application crash
CODE

and the Microsoft Windows Event Viewer or Microsoft Windows Reliability and Problem History shows an application error in module ECtiClient.exe.

This behaviour affects version 8.9 of ProCall Desktop for Windows. 

Resolved with Version 8.9.2 ProCall 8 - Release Notes 8.9.2


A temporary workaround for this issue is to use the registry entry DUMP (DWORD) with a value of 2, as documented in the article Creating a full memory dump on the ProCall client.

Further information