Continuing the discussion from Problem with "Testing your LIBPF™ SDK install":
What happens here is that you installed one of the public demos, which are activated for one site identifier, whereas the SDK you have received produces binaries that are activated for another site identifier (the site identifier is an alphanumerical code assigned to every customer).
plutil -p /Library/Preferences/com.libpf.LIBPF.plist | grep SiteId
This should print something like:
"1-0.SiteId" => "com.example_1.0"
The SDK you have received is activated for it.unige_1.0, which I guess is different from what you’ll get above.
The easiest thing you can do to solve this issue is perform the automatic activation (menu Settings -> Activate) from one of the packages specific to your own site identifier, that you have received together with the SDK.