Problem regitering MSADO25.TLB 1

[elibb]

hi.. im have vb6.0 application, and im making an installer with the visual studio installer, but when i try to install it, i get this error:
"Error 1904
Module c:\....\MSADO25.TLB failed to register
HRESULT -2147024769
Contact your support personel"

does anybody know what can i do??

thank you very much

Eli

 

[cassandra]

Check your seupt.lst file and make sure the tlb is TLBRegister not dllselfRegister. Update your setup.lst file and re-install. Make sure you also check the setup.lst in your support folder.

Cassandra

 

[elibb]

im using the visual studio installer, and i only have this options for the tlb file:

vsifrNone
vsifrSelfReg
vsifrFont

i dont see a .lst file created...
what should i do??

thank You very much

Eli

 

[sunaj]

Cassandra,

Nice one. I've been looking for that.
Do you know why the package and deployment wizard behaves like that? Is is a documented bug?
Sunaj
'The gap between theory and practice is not as wide in theory as it is in practice'

 

[Norris68]

The PDW seems to have problems registering type libraries.

I also use Visual Studio Installer, and the procedure for getting a TLB to install is poorly documented and not easy to understand.

You need to find out the LibID of the type library by using OLE View (or similar). Then, add it into the Type Libraries in Associations. Make sure the type library will not self register (in Files, Outputs). The same goes for any COM objects you use (except they are listed in in COM Objects).

The ideaology behind this is that if you allow components to self register the setup program cannot remove them as it doesn't know anything about the registration. By adding the files into Associations the setup program registers the components instead of the object itself and therefore knows how to remove them afterwards.

 

[cassandra]

Sunaj,
Yes this is a known bug. Microsoft has a tendency of not reporting bugs until the problem has been fixed. Eli, let us know if what Norris suggested worked for you.

Cassandra

 

[elibb]

it worked!! i changed the .lst file, and then it worked..
but still.. i dont like to make my installers that way very much, i liked to use the Visual Studio Installer..

also i downloaded InstallShield Professional, but i didnt understand it.. does anybody know about a good tutorial?? or can explain a bit how to personalize the forms, put a serial number and that stuff???

thank You very much.

and Cassandra thank you very much for your adivce.. it got me out of trouble with my client in the meantime.

 

[elibb]

it worked!! i changed the .lst file, and then it worked..
but still.. i dont like to make my installers that way very much, i liked to use the Visual Studio Installer..

also i downloaded InstallShield Professional, but i didnt understand it.. does anybody know about a good tutorial?? or can explain a bit how to personalize the forms, put a serial number and that stuff???

thank You very much.

and Cassandra thank you very much for your adivce.. it got me out of trouble with my client in the meantime.

Eli

 

[sunaj]

I know that this is an old thread but I just happend to come across this page

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q299645

which documents the bug and possible solutions... Sunaj
'The gap between theory and practice is not as wide in theory as it is in practice'