Creating a debug log for the update service for the ProCall client

This article explains how you can create a so-called debug log for the update service for the ProCall client and make it available for analysis.

Logfiles can only be examined if reasonable anchor points are available. Therefore always provide the following additional information:

• • When did a fault occur (timestamp with date and time, at least to the minute)?
  • Which internal extensions were involved?
  • Which external participants were involved?
  • Process of the workflow that led to an error

Registry entry

Please enter the following registry key to set the log level of the update service on the ProCall Client to Debug/ASN.

The log file can be found in the directory: "C:\ProgramData\ESTOS\EACU\EACUSrv.log"

64-bit computer with ProCall Desktop for Windows

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\ESTOS\UCServer4\ACUService]
"Debug"=dword:00000004

Value range

Log file output

The log file(s) can be found in the directory C:\ProgramData\ESTOS\EACU and are based on the naming scheme EACUSrv_x.log (x corresponds to consecutive numbering, with the value 0 representing the most recent log file).

Further information

• The ProCall client update function does not work
• Automatically configure UCServer update service
• Erzeugen eines Debug-Logs des ProCall Clients
• estos ProCall Enterprise Client Logdateien