Hi Catalin,
thanks for your reply.
We managed to find out, that some of the referenced assemblies in the CustomAction DLL were missing and not correctly loaded.
It seems, that on the machines where the installer worked, the missing DLL was already in the GAC from another application ...