Vista - failed to register com (activex) control

[harryhollander]

Morning,

I have a couple of install projects that run fine on XP but don't in Vista. The user is the Administrator, and I have set Requested User Privilege Level as Administrator. Various files give errors during install.

Desperate here .... I can't install on Vista

Example...
failed to register com (activex) control c:\windows\system32\chilkatcrypt2.dll failure in load library (0 (193) this came up 3 times

Any help appreciated.

thanks

[jassing]

wow; I thought I answered this question just a bit ago.

Why is it registering the same file 3 times is what I have question about.
In case you missed the questions in your other post:
1) can you register the file on vista manually?
2) have you used depends.exe on the com file to see if there's a file missing or invalid?

[harryhollander]

Thanks for the reply,

Yep sorry I wasn't sure whether to post in 7 or 8, and I didn't see the other reply.

There are no other dependencies for that file as it is standalone, but in any event this full install runs fine in XP.

I haven't tried to register it manually no. I will do. I'm thinking though is has something to do with Permissions and UAC ?

thanks

[harryhollander]

Hello Jassing,

Actually I just noticed that you responded to a message I left on the original response you made to garylyb

Anyway... on your question of the 3 messages, good question, there is no reason that I can see why that should come up three times becasue there is only one statement in the script that refers to that module.

cheers

[jassing]

Originally Posted by harryhollander

Thanks for the reply,

Yep sorry I wasn't sure whether to post in 7 or 8, and I didn't see the other reply.

There are no other dependencies for that file as it is standalone, but in any event this full install runs fine in XP.

I haven't tried to register it manually no. I will do. I'm thinking though is has something to do with Permissions and UAC ?

thanks

Well; I don't know if it's a suf7 or suf8 issue for you; nor can we say it is or it isn't uac...
Register the files manually; report back
run depends.exe on the com file; report back
check the installer, why is it trying to register the same file 3 times?
Maybe post the install log as well.

Saying it "works on xp but doesn't on vista" is like saying "Well; it works here so it's your problem" If there's a file missing that it needs (I'm finding it hard to believe that a COM object uses NO other dll's or system files) or it's not the right version (like a 32bit object in a 64bit world) etc -- there's LOTS of reasons why it may not work on one system and it does on another... it takes some ground work to identify it.

[jassing]

Originally Posted by harryhollander

Hello Jassing,

Actually I just noticed that you responded to a message I left on the original response you made to garylyb

Anyway... on your question of the 3 messages, good question, there is no reason that I can see why that should come up three times becasue there is only one statement in the script that refers to that module.

cheers

.... and that line is?
Why don't you post the .sf8 file?
(or sf7)

[harryhollander]

>>> there's LOTS of reasons why it may not work on one system and it does on another... it takes some ground work to identify it.

Yes good point.

SF7 File attached as requested.

Dependencies
msasn1.dll << this is already on the PC
Crypt32.dll

thanks

[Ulrich]

I use the Chilkat libraries as well, but haven't seen yet this kind of problem you related. You aren't using the current version of the component, maybe an update could help...

The dependency files for ChilkatCrypt2.dll are kernel32.dll, user32.dll, gdi32.dll, advapi32.dll, ole32.dll, oleaut32.dll and crypt32.dll.

I couldn't find any script in the installer, just FindAndCloseProcessByName(). Where is the statement in the script that refers to this component?

Ulrich

[jassing]

Sounds like you two are using different versions of the component; since Ulrichs' list doesn't list msasn1.dll

Could the msasn1.dll be "older" -- did you use depends.exe to see if anythign is flagged in red?

I have found that sometimes, putting a "problem" dll to the end of the install list (change it's install order) helps; but only if you're also installing it's dependancies)

Could you post the logs from a "good" system and "failing" system?