While installing ZCC Helper on Linux devices, if any of the following error message is displayed, then perform the steps mentioned in the Workaround section:
Error setting value: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Error setting value: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Error setting value: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Workaround: Run the following commands:
/usr/bin/gconftool-2 -s /desktop/gnome/url-handlers/zcclaunch/command '/opt/novell/zenworks/zcchelper/bin/zcchelper "%s"' -t string /usr/bin/gconftool-2 -s /desktop/gnome/url-handlers/zcclaunch/needs_terminal false -t bool /usr/bin/gconftool-2 -s /desktop/gnome/url-handlers/zcclaunch/enabled true -t bool /usr/bin/gconftool-rebuild
While installing ZCC Helper on Linux devices, if any of the following error message is displayed, then perform the steps mentioned in the Workaround section:
/usr/bin/xdg-mime: line 545: /root/.local/share/applications/defaults.list.new: No such file or directory grep: /root/.local/share/applications/defaults.list.new: No such file or directory /usr/bin/xdg-mime: line 547: /root/.local/share/applications/defaults.list.new: No such file or directory /usr/bin/xdg-mime: line 549: /root/.local/share/applications/defaults.list.new: No such file or directory mv: cannot stat `/root/.local/share/applications/defaults.list.new': No such file or directory
Workaround: Run the following commands:
mkdir .local/share/applications xdg-mime default zcchelper.desktop x-scheme-handler/zcclaunch || true update-desktop-database
After installing ZCC Helper on 64-bit SLES 11 devices, ZCC Helper might not launch.
Workaround: Install 3rd party JRE (8.x or higher version) manually, and then set the ZCC_JAVA_HOME path variable.
If you are using wayland display manager, ZCC Helper might not launch.
Workaround: Logout and log into the device using the x11 display manager.
If the ZENworks Management Zone is configured with an L4 switch, then ZCC Helper might not work as expected.
Workaround: If the ZENworks Management Zone is configured with an L4 switch, then perform the following steps manually on all ZCC servers in the zone:
The ZCC servers should be directly reachable from the management console.
Append the following setting to the existing settings in the custom-config.xml file:
<setting id="changezcclaunchServer">
<value>true</value>
</setting>
The custom-config.xml file location:
On Windows: ${ZENWORKS_HOME} \services\zenserver\webapps\zenworks\WEB-INF\conf\
On Linux: /opt/microfocus/zenworks/share/tomcat/webapps/zenworks/WEB-INF/conf/
Restart ZENworks server services.
After configuring the settings, ZCC Helper contacts the Primary Server behind the L4 switch that generated the zcclaunch custom protocol token, instead of contacting the L4 switch.