Remote launch of Klocwork tooling on slave machine fails reporting:

1. Plugin failure when checking for presence of Klocwork installation on Master node (not slave)
2. Remote command execution failure due to file path separator problems with Windows master and Linux slave

Attachment "console1.txt" shows the plugin checking for Klocwork installation on the master windows node - this fails because Klocwork is only installed on the slave node. If you create a dummy folder "\data\Klocwork" on the master, the plugin execution continues as shown in attachment "console2.txt". This shows execution of the Klocwork tools on the remote Linux machine. However, this fails due to file path separator problems (a mixture of forward- and back-slashes in the path) - attempting remote execution of "\data\Klocwork/bin/kwinject"

These problems seem to be caused by mixture of Windows and Linux master & slave combined with the fact that Klocwork is not installed on the master node.