Troubleshooting

Typical issues

There is no connection to the workstation module over Citrix ICA.

The issue when device redirection fails to work over Citrix ICA may be caused by the ICA policy that disallows virtual channels by default. Our device redirection products require virtual channel for its operation.

Go to Citrix Studio - Policies and check the Virtual channel allow list policy settings. For proper device redirection this policy should be either disabled, or containing virtual channel and path required by FabulaTech products:

CITRDP3,C:\Program Files\Common Files\FabulaTech\Netlink 3\ftnlsv.exe

More information can be found in the Citrix documentation.

Cannot connect to remote side after installing (reinstalling) Citrix Receiver/Workspace, VMware View Client, Amazon Client, Teradici Client.

The connection to remote side might be lost after installing (reinstalling) remote desktop access software on Workstation side (i.e. Citrix Receiver/Workspace, VMware View Client, Amazon Client, Teradici Client).

As result, a message No connection to workstation module appears on remote side.

It is needed to restart FabulaTech Netlink 3 supervisor service or reboot workstation side, and the issue will be resolved automatically.

If there is a bug with the functionality of our software, do the following:

Enable logging.

On the computer where Printer for Remote Desktop (Server) is installed, download the enable_logs_printerrd_srv.reg file and apply it.
Alternatively, launch regedit, find the LogLevel REG_DWORD value in the following registry locations and set it to 3:

32-bit:
HKEY_LOCAL_MACHINE\SOFTWARE\FabulaTech\Printer for Remote Desktop (Server)
HKEY_LOCAL_MACHINE\SOFTWARE\FabulaTech\Netlink 3

64-bit:
HKEY_LOCAL_MACHINE\SOFTWARE\FabulaTech\Printer for Remote Desktop (Server)
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\FabulaTech\Netlink 3
HKEY_LOCAL_MACHINE\SOFTWARE\FabulaTech\Netlink 3

Restart the service: FabulaTech Netlink 3 supervisor service or reboot your PC.
(Press Win+R, type services.msc, right-click the required service and select Restart. Administrator privileges are required to perform this operation.)
Enable logging on the Printer for Remote Desktop (Workstation) side.

Reproduce the issue you encountered 2-3 times. Remember local time when the problem was reproduced.

Collect the logs.

After you enable logging and restart the services, log files will be created in the following location:
C:\ProgramData\FabulaTech\

Add this folder to archive (right-click, then point to Send to and select Compressed (zipped) folder).

Send compressed logs to us (). Specify local time when the problem was reproduced and both local and remote user names who was involved in the reproducing.

Disable logging (in order to improve the performance of your PC).

On the computer where Printer for Remote Desktop (Server) is installed, download the disable_logs_printerrd_srv.reg file and apply it.
Alternatively, you can launch regedit, find the LogLevel REG_DWORD value in the following registry locations and set it to 0:

32-bit:
HKEY_LOCAL_MACHINE\SOFTWARE\FabulaTech\Printer for Remote Desktop (Server)
HKEY_LOCAL_MACHINE\SOFTWARE\FabulaTech\Netlink 3

64-bit:
HKEY_LOCAL_MACHINE\SOFTWARE\FabulaTech\Printer for Remote Desktop (Server)
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\FabulaTech\Netlink 3
HKEY_LOCAL_MACHINE\SOFTWARE\FabulaTech\Netlink 3

Restart the service: FabulaTech Netlink 3 supervisor service or reboot your PC.
(Press Win+R, type services.msc, right-click the required service and select Restart. Administrator privileges are required to perform this operation.)

If our software crashes, do the following:

Enable dump creation.

To enable Crash Dump, download the enable_dump.reg file and apply it.

Alternatively, enable and configure this feature using the following registry values under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps key:
```
- type: REG_EXPAND_SZ, value: DumpFolder, default value: %LOCALAPPDATA%\CrashDumps
- type: REG_DWORD, value: DumpType, default value: 2
```
Reboot your PC.

Reproduce the issue you encountered 2-3 times. Remember local time when the problem was reproduced.

Collect dump file.

Locate the crash dump file in %LOCALAPPDATA%\CrashDumps folder. Note that if the crashing application runs under the System account, that resolves to %WINDIR%\System32\config\systemprofile\AppData\Local\CrashDumps (%WINDIR%\SysWOW64\Config\SystemProfile\AppData\Local\CrashDumps for 64-bit OS).

Add the crash dump to archive (right-click, then point to Send to and select Compressed (zipped) folder).

Send compressed dump to us (). Specify local time when the problem was reproduced and both local and remote user names who was involved in the reproducing.

If there is a BSOD caused by our software, do the following:

Enable kernel memory dump.

Open the Start Menu, select Control Panel - System.
Find the Advanced/Advanced system settings section.
In the Advanced/Advanced system settings section, click on the Settings button under Startup and Recovery.
Select Kernel memory dump from the Write debugging information drop down menu.
Check both the Write an event to the system log and Automatically restart boxes.
Reboot your PC.

Reproduce the issue you encountered 2-3 times. Remember local time when the problem was reproduced.

Find the file MEMORY.DMP (located on %SystemRoot% folder).