Have a solution to Error 1911!

[Gary Kercheck]

Earlier today I posted in the installshield.express.vb group about a problem
with revving an Active X EXE component of a VB project and getting error
1911 on install. After exhausting virtually every option I decided to go
into the Registry on the build machine and manually delete all references to
the Active X component. I did a very careful search/delete operation using
the name of the Active X component on the entire registry. After doing this
I rebuilt both the component and the main VB application in Visual Basic. I
rebuilt my InstallShield Express project and to my amazement the install
went perfectly and the application runs as it should. There HAS to be a
better way of getting around this error and I hope InstallShield addresses
this because it is a major annoyance. What should have been a simple
operation (upgrading an Active X .EXE component) consumed the better part of
three days on my end.

Gary Kercheck
SW Engineering Manager
Sekidenko, Inc.

[Ken Halter]

In most cases, your registry search/delete can be done by unregistering the
ocx/dll/exe and run RegClean. This'll clear out the left over info and
create an Undo file in case you need it. I couldn't find references to error
1911 in isx help and since you say it was cured by rebuilding the
components, it's very likely that it's a VB related problem.

"Gary Kercheck" <gary.k...@sekidenko.com> wrote in message
news:3b3a...@12.41.20.38...

[CB]

"Ken Halter" <KHa...@KHalter.8k.com> wrote in message
news:3b3b6105$1...@12.41.20.38...

> In most cases, your registry search/delete can be done by unregistering
the
> ocx/dll/exe and run RegClean. This'll clear out the left over info and
> create an Undo file in case you need it. I couldn't find references to
error
> 1911 in isx help and since you say it was cured by rebuilding the
> components, it's very likely that it's a VB related problem.

1911 is a Windows Installer error (hence you won't find it in the ISX help.
But, if you click on the MSI Help Library on the ISX help menu, you will
find it). The Windows Installer help gives this info:

Could not register type library for file [2]. Contact your support
personnel.

If you can call that info, that is :-).

> "Gary Kercheck" <gary.k...@sekidenko.com> wrote in message
> news:3b3a...@12.41.20.38...

> > this because it is a major annoyance. What should have been a simple
> > operation (upgrading an Active X .EXE component) consumed the better

This may be the source of the problem - if you're upgrading then the control
is already registered. Although there should be any problem with this, the
Windows Installer may have trouble registering a control that's already
registered (I know that regsvr32.exe doesn't, but I suspect that Windows
Installer doesn't use that). Perhaps the control needs to be unregistered
before the upgrade ?

Cheers
Craig

[Steven Wicinski]

There's a good chance the error was because it was looking at the wrong
registration entries when it produced the new copy. We just recompiled a slew of
our programs, and one of my people can't run the EXEs, even though he's
up-to-date on all the files. I think its also related to the fact he's got five
different registrations for the DLL on his machine.

I do my final compiles on a completely separate machine (our server), such that
I don't have to worry about file changes I make on my work machine screwing up
the final product (I started this after I installed some program that updated my
DLLs without me knowing it, causing later compiles to not work on machines the
program was already installed on).