It may be the other COM files in the setup that can't load this file during its self-registration process. Run regsvr32 via an administrator-launched command line windows for each COM file and see which file triggers the error.
It is possible that the required files are NOT binaries - they can even be image files, but in cases where I have seen this, the problem has generally been a missing language-dll for a regular COM dll.
Use Dependency Walker to determine dependencies for binaries in general. Run this on the DLL mentioned in the error message. As far as I recall you can even launch an EXE file and get a full report on all files loaded into the process.
Use Regspy2 to manually extract COM information from binaries. I have seen EXE files where only this tool has been able to extract the COM information. You then manually import the exported REG files to the correct component in your setup and disable automatic COM extraction.
Just did a search, seems Stefan has answered the exact same problem earlier: http://forum.install...showtopic=21463
Edited by Glytzhkof, 08 April 2014 - 21:11.