path error when registering COM dll

[KirkAtRISA]

When installing an msi that registers a com dll (on Win 7 SP1, 64 bit), windows installer complains about a folder path:

MsgBox-bad-char-in-folder-path.png (23.35 KiB) Viewed 3861 times

File is located here:

AI-Files-screen.png (40.32 KiB) Viewed 3861 times

COM registered here:

AI-COM-screen.png (28.71 KiB) Viewed 3861 times

Reproduce by running the msi here:
https://drive.google.com/file/d/193lko7 ... sp=sharing

Verbose log for this msi is here:
https://drive.google.com/file/d/1v1vZ6B ... sp=sharing

All project files are in this rar:
https://drive.google.com/file/d/1inmOS2 ... sp=sharing

(I posted this problem at support@advancedinstaller.com a couple days ago before I realized that this board is the primary way to post problems, sorry about the duplication)

thanks

[Daniel]

Hello Kirk,

Thank you for giving Advanced Installer a trial.

From what I see in the log file there might be the case that the related DLL file is not actually installed/deployed on target machine. Not sure why though. Check line 692 of your log file:

Code: Select all

MSI (s) (A0:64) [17:14:00:471]: The file represented by File table key 'RISALicenseManagerCOM.dll' has no eligible binary patches

Can you please go to "Files and Folders" double click on your "RISALicenseManagerCOM.dll" file, and from "Operations" tab select the "Always overwrite existing files" option? Then rebuild and test again the scenario.

If this still doesn't help you, then as another workaround you can remove the COM registration entry you added in "COM" page of your project. Then from "Files and Folders" page double click again on your "RISALicenseManagerCOM.dll" file and go to "Registration" tab and use the "Extract registration info from native library" option.

Let us know if this helped.

All the best,
Daniel

[KirkAtRISA]

Thanks Danel,

that 2nd option "Extract registration info from native library" did the trick.
The dll now shows up properly in the COM node:

COM entries - corrected.png

It bothered me first time around that it appeared under COM+, when it's not a COM+ object...

thanks again,

Kirk Evans

[Daniel]

You are always welcome Kirk.

I am glad you got this working.

All the best,
Daniel