HHCRTL.OCX Not Registering

[neilkonitzer]

I have a VB6 application that uses the hhctrl.ocx component. During installation on a client machine, the Install window shows -

Copying Files. Please standby.
Processing hhctrl.ocx (3 of 3)

Then this window Pop Up appears-

"Setup cannot continue because some system files are out of date on your system. Click OK if you would like setup to update these files for you now. You will need to restart Windows before you can run Setup again. Click Cancel to exit setup without updating system files."

At this point my options have this effect -
If 'Cancel' setup exits without installing
If 'OK' then this window appears...

I press "OK" and Files are copied then a second popup is displayed showing...

"Do you want to restart Windows now? If you choose ‘No’ you will not be able to run setup again until after the system is rebooted at a later time."

This cycle keeps on repeating.

I have tried Googling this problem and for some reason cannot come up with a solution. Does anyone have a clue what is going on here?

 

[jebenson]

The most relevant thing I could find was a site that stated your machine has to have ITSS.DLL, ITLOCAL.DLL and WININET.DLL installed in order to register HHCTRL.OCX. Maybe if you include these files from your development machine in the installation package and register them first your error will be eliminated.


I used to rock and roll every night and party every day. Then it was every other day. Now I'm lucky if I can find 30 minutes a week in which to get funky. - Homer Simpson

 

[BobRodes]

Sounds like you're using the PDW. PDW has a known problem with this loop:

1. CAB file contains a later version of a DLL used by the system on the target machine.
2. PDW attempts to install later version, requires reboot of system so system can use it too.
3. System behavior (now, "this behavior is by design", mind you) has changed since the time the PDW was created. Due to backward compatibility problems with DLLs, system will not accept later versions of system DLL's unless they are installed either by a service pack or a hotfix. DLL version is set back to what it was prior to install attempt.
4. PDW repeats number 2, et voila. You have your loop.

All fixes entail making sure that the CAB file doesn't have a later version of the DLL than the target machine, and fall into the categories of upgrading the target system or downgrading the source. Keep in mind that the version that the PDW installs is not necessarily the version that is on the source machine. Note the directory in which your source file is found; the default is c:\program files\microsoft visual studio\vb98\wizards\pdwizard\redist.

Of course, you might not be using the PDW, but your problem almost certainly has the same source if you're using something different.

HTH

Bob