Vista Business 64-bit, HRESULT -2147010895

[chrisb1980]

Hi,

I have an installation project containing 2 EXEs and 3 OCXs built in Visual C++ 2008, that installs fine on XP, etc. but testing it on Vista Business 64-bit I have an error registering the OCXs in the package.

The error that I get is:

Module c:\windows\SysWOW64\xxxxxx.ocx failed to register.
HRESULT -2147010895
Contact your support personnel.

I get the same error for each of the three OCX files in the package.

The application itself runs OK following the installation (suggesting that the VC90 merge modules were successfully installed), but the controls fail to load as they aren't registered.

Is there a known solution for this issue?

Thanks,

Chris

[Cosmin]

Hi Chris,

I'm not sure why you are encountering this behavior. Can you please try using regsvr32.exe to register the files manually on the machine with the problem and see if it works? Also, does this happen on multiple machines?

Regards,
Cosmin

[chrisb1980]

Hi,

Will try manual regsvr32 and let you know.

We only have one vista machine (for testing such installations!), I wouldn't use it myself...

Chris

[chrisb1980]

Hi,

No regsvr32 fails too with "The specified module could not be found".

Chris

[Bogdan]

Hi,

Please make sure that you are using the tool correctly. If you are using it correctly and it still fails to register most likely the problem resides in the .OCX files.

Regards,
Bogdan

[chrisb1980]

Oops, it appears that Vista can't find the OCXs unless I specify the full path...

Anyway, "regsvr32 c:\windows\SysWOW64\xxxxx.ocx" now gives:

The module c:\windows\SysWOW64\xxxxx.ocx was loaded but the call to DllRegisterServer failed with error code 0x80040200.

Interestingly, if I build the OCXs with static CRT and MFC linkage then the controls install and run OK. This is strange as the manifest files for the OCXs show the same dependencies as the EXEs when built with dynamic linkage.

Chris

[chrisb1980]

Googling for that error code suggests that it's a permissions issue, but the account I'm using has Administrator rights.

I'm not too familiar with the UAC stuff in Vista, but does it have something to do with that?

Chris

[Cosmin]

Hi,

Did you run the registration command from an elevated command prompt? For this you can run "cmd.exe" as an Administrator. If you did and the behavior is the same, you can try recompiling the files on Vista. You should also make sure that all their dependencies are present on the machine.

Regards,
Cosmin

[chrisb1980]

Hi,

Well, I'm not planning on asking our customers to manually run regsvr32 for each OCX in the package, that's not a very useful solution.

Recompiling on Vista sounds as if it might break the installation on XP, 2K, etc. so that's not a viable solution either.

How do I install the OCXs from Advanced Installer with elevated priviledges?

Chris

[Cosmin]

Hi Chris,

Well, I'm not planning on asking our customers to manually run regsvr32 for each OCX in the package, that's not a very useful solution.

If the files can be registered using "regsvr32.exe", you can use custom actions which launch it with custom commands for each OCX.

How do I install the OCXs from Advanced Installer with elevated priviledges?

If the installation runs with Administrator privileges, the files will also be installed with Administrator privileges.

Regards,
Cosmin

[chrisb1980]

If the installation runs with Administrator privileges, the files will also be installed with Administrator privileges.

I tried launching the msi from a command prompt with administrator priviledges and that still gives the same error for the OCXs.

I think the simplest thing will be to statically link the OCXs, it's more trouble than it's worth for our tiny Vista userbase to mess around with custom actions.

Chris