COM+ registration: the folder path ... contains an invalid

Having trouble running Advanced Installer? Got a bug to report? Post it all here.
Post Reply
davidsmith
Posts: 59
Joined: Sun Jul 12, 2009 8:33 pm

COM+ registration: the folder path ... contains an invalid

Post by davidsmith » Mon Jul 13, 2009 2:39 am

I am using AI 7.1.1.

If I use the COM+ screen to register a COM+ DLL, Foobarworld.dll, I'm getting the following error message when I run the .msi file.

"The folder path 'Foobar~2.dll|Foobarworld.dll' contains an invalid character."

I can register this DLL just fine if I do it directly from the Files and Folders screen.

It looks like it might be a bug in AdvancedInstaller where it is keeping an 8.3 and long file names, and is forgetting to unpack them correctly before registering the file. The AdvancedInstaller delimiter character between the two file names '|' looks like the issue.

In the COM+ Properties, I have:

Files:
Foobarworld.dll

Export Flags:
65

Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact:

Re: COM+ registration: the folder path ... contains an invalid

Post by Cosmin » Mon Jul 13, 2009 1:19 pm

Hi,

Please note that the COM page can register only files which have an 8.3 name format. Currently this is not specified in the User Guide, but it will be starting with the next version.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

davidsmith
Posts: 59
Joined: Sun Jul 12, 2009 8:33 pm

Re: COM+ registration: the folder path ... contains an invalid

Post by davidsmith » Mon Jul 13, 2009 5:32 pm

Can I reliably register third party COM DLLs using their 8.3 file names instead of their long names?

If not, is there any plan to fix this limitation?

Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact:

Re: COM+ registration: the folder path ... contains an invalid

Post by Cosmin » Tue Jul 14, 2009 12:48 pm

Hi,
Can I reliably register third party COM DLLs using their 8.3 file names instead of their long names?
Yes, if this doesn't cause a name conflict.
The limitation is in Windows Installer, but in a future we will try to implement a workaround.

Regards.
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Post Reply