Debug logging requires valuable resources on your computers and servers. Having it run all the time would be wasteful. That’s why debug logging for ezeep Print App and ezeep Connector are designed to be enabled when needed and disabled afterwards.


Enabling debug logging to identify printer creation issues in the ezeep Print App is done by creating two registry values.

  1. On the machine running the ezeep Print App, open the Windows registry by typing regedit.exe in the Windows search bar.
  2. Navigate to HKLM\SOFTWARE\THINPRINT\TPAutoConnect
  3. Create the following Registry Values and Data
  • Name: DebugLevel Type: DWORD (32-Bit) Data:3F (hex)
  • Name: DebugFile         Type: STRING Data: file path to log file e.g. c:\logs\printercreate.log
  • Make sure that the folder you used in the file path exists and can be written to by users as well as the operating system.

       4. Restart the service TP AutoConnect Service


The following logs are useful in identifying printing issues:


To generate the log for the ezeep local printing connector:

HKLM\SOFTWARE\THINPRINT\CLIENT the values:

Name: DebugLevel Type: DWORD (32-Bit) Data:DF (hex)

Name: DebugFile         Type: STRING DATA: file path to log file e.g. c:\logs\printercreate.log

After recreating the issue and making sure the debug log file is created, stop debug logging by changing the data for DebugLevel to 0.


To generate a log for the TCP protocol module on the virtual desktop:

HKLM\SOFTWARE\THINPRINT\tpsw32

Name: DebugLevel Type: DWORD (32-Bit) Data:3 (hex)

Name: DebugFile         Type: STRING DATA: file path to log file e.g. c:\logs\tpsw32.log

After recreating the issue and making sure the debug log file is created, stop debug logging by changing the data for DebugLevel to 0.


To generate a log for the Thinprint Port Provider on the virtual desktop:

HKLM\SOFTWARE\THINPRINT\

Name: DebugLevel Type: DWORD (32-Bit) Data:2 (hex)

Name: DebugFile         Type: STRING DATA: file path to log file e.g. c:\logs\thinmon.log

After recreating the issue and making sure the debug log file is created, stop debug logging by changing the data for DebugLevel to 0.