Could not Register Type Libraries
Hello All,
I have created an msi by capturing an exe. But while installing the msi it is giving me the error 'could not register the Type Libraries' for three files. By seeing the log file I could not get the reason why it cannot register them. Could any one please let me know the reason for this.
Below is the log file
Thank You.
I have created an msi by capturing an exe. But while installing the msi it is giving me the error 'could not register the Type Libraries' for three files. By seeing the log file I could not get the reason why it cannot register them. Could any one please let me know the reason for this.
Below is the log file
Action 15:05:04: RegisterTypeLibraries. Registering type libraries
MSI (s) (40:58) [15:05:04:337]: Executing op: TypeLibraryRegister(,,FilePath=C:\WINDOWS\system32\vcf132.ocx,LibID={042BADC8-5E58-11CE-B610-524153480001},Version=256,,Language=0,HelpPath=C:\WINDOWS\system32\,BinaryType=0,IgnoreRegistrationFailure=0)
RegisterTypeLibraries: LibID: {042BADC8-5E58-11CE-B610-524153480001}
MSI (s) (40:58) [15:05:04:337]: QueryPathOfRegTypeLib returned -2147319779 in local context. Path is '
MSI (s) (40:58) [15:05:04:337]: CMsiServices::ProcessTypeLibrary runs in local context, not impersonated.
MSI (s) (40:58) [15:05:04:337]: ProcessTypeLibraryCore returns: -2147312566. (0 means OK)
MSI (s) (40:58) [15:05:04:337]: Note: 1: 2108 2: C:\WINDOWS\system32\vcf132.ocx 3: -2147312566
DEBUG: Error 2835: The control ErrorIcon was not found on dialog SetupError
Internal Error 2835. ErrorIcon, SetupError
Error 1911.Could not register type library for file C:\WINDOWS\system32\vcf132.ocx. Contact your support personnel.
MSI (s) (40:58) [15:09:11:103]: Product: MyProduct -- Error 1911.Could not register type library for file C:\WINDOWS\system32\vcf132.ocx. Contact your support personnel.
MSI (s) (40:58) [15:09:11:103]: Executing op: TypeLibraryRegister(,,FilePath=C:\Program Files\ALK Technologies\PMW250\Mapping\COM\pcmgole.dll,LibID={84211971-9B69-11D3-B537-00104B87FEAA},Version=256,,Language=0,HelpPath=C:\Program Files\ALK Technologies\PMW250\Mapping\COM\,BinaryType=0,IgnoreRegistrationFailure=0)
RegisterTypeLibraries: LibID: {84211971-9B69-11D3-B537-00104B87FEAA}
MSI (s) (40:58) [15:09:11:103]: QueryPathOfRegTypeLib returned -2147319779 in local context. Path is '
MSI (s) (40:58) [15:09:11:103]: CMsiServices::ProcessTypeLibrary runs in local context, not impersonated.
MSI (s) (40:58) [15:09:11:103]: ProcessTypeLibraryCore returns: -2147312566. (0 means OK)
MSI (s) (40:58) [15:09:11:103]: Note: 1: 2108 2: C:\Program Files\ALK Technologies\PMW250\Mapping\COM\pcmgole.dll 3: -2147312566
DEBUG: Error 2835: The control ErrorIcon was not found on dialog SetupError
Internal Error 2835. ErrorIcon, SetupError
Error 1911.Could not register type library for file C:\Program Files\ALK Technologies\PMW250\Mapping\COM\pcmgole.dll. Contact your support personnel.
MSI (s) (40:58) [15:09:41:556]: Product: MyProduct -- Error 1911.Could not register type library for file C:\Program Files\ALK Technologies\PMW250\Mapping\COM\pcmgole.dll. Contact your support personnel.
MSI (s) (40:58) [15:09:41:556]: Executing op: TypeLibraryRegister(,,FilePath=C:\Program Files\ALK Technologies\PMW250\Connect\COM\pcmsole.dll,LibID={F7AD5330-F290-11D2-B2EA-00104B7527F7},Version=256,,Language=0,HelpPath=C:\Program Files\ALK Technologies\PMW250\Connect\COM\,BinaryType=0,IgnoreRegistrationFailure=0)
RegisterTypeLibraries: LibID: {F7AD5330-F290-11D2-B2EA-00104B7527F7}
MSI (s) (40:58) [15:09:41:556]: QueryPathOfRegTypeLib returned -2147319779 in local context. Path is '
MSI (s) (40:58) [15:09:41:556]: CMsiServices::ProcessTypeLibrary runs in local context, not impersonated.
MSI (s) (40:58) [15:09:41:556]: ProcessTypeLibraryCore returns: -2147312566. (0 means OK)
MSI (s) (40:58) [15:09:41:556]: Note: 1: 2108 2: C:\Program Files\ALK Technologies\PMW250\Connect\COM\pcmsole.dll 3: -2147312566
DEBUG: Error 2835: The control ErrorIcon was not found on dialog SetupError
Internal Error 2835. ErrorIcon, SetupError
Error 1911.Could not register type library for file C:\Program Files\ALK Technologies\PMW250\Connect\COM\pcmsole.dll. Contact your support personnel.
MSI (s) (40:58) [15:10:12:837]: Product: MyProduct -- Error 1911.Could not register type library for file C:\Program Files\ALK Technologies\PMW250\Connect\COM\pcmsole.dll. Contact your support personnel.
MSI (s) (40:58) [15:10:12:837]: Executing op: ActionStart(Name=RegisterUser,Description=Registering user,Template=[1])
Action 15:10:12: RegisterUser. Registering user
MSI (s) (40:58) [15:10:12:837]: Executing op: UserRegister(Owner=a,Company=x,ProductId=none)
RegisterUser: {32AC6711-C4F0-4C84-A536-073F07428E7C}
MSI (s) (40:58) [15:10:12:853]: Executing op: ActionStart(Name=RegisterProduct,Description=Registering product,Template=[1])
Action 15:10:12: RegisterProduct. Registering product
MSI (s) (40:58) [15:10:12:853]: Executing op: ChangeMedia(,MediaPrompt=Please insert the disk: LABEL,MediaCabinet=Cabs.w1.cab,BytesPerTick=0,CopierType=2,ModuleFileName=C:\WINDOWS\Installer\3f2e9a.msi,,,,,IsFirstPhysicalMedia=1)
DEBUG: Error 2902: Operation ixoFileCopy called out of sequence.
DEBUG: Error 2835: The control ErrorIcon was not found on dialog SetupError
Internal Error 2835. ErrorIcon, SetupError
Internal Error 2902. ixoFileCopy
MSI (s) (40:58) [15:10:41:165]: Product: MyProduct -- Internal Error 2902. ixoFileCopy
Action ended 15:10:41: InstallFinalize. Return value 3.Thank You.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
I don't think this would apply here as the file being registered is an OCX. My suspicion would fall upon missing dependencies. As ever, run ProcMon and then try and register the file. ProcMon will immediately show you if a file is missing.
You may want to pre-empt that by loading the OCX into Dependency Walker. With the latter, remember you can ignore dynamically loaded files (MPR.DLL is one which turns up regularly).
You may want to pre-empt that by loading the OCX into Dependency Walker. With the latter, remember you can ignore dynamically loaded files (MPR.DLL is one which turns up regularly).
Posted by:
naveen.packager
13 years ago
Hi VBScab,
Thanks for your reply. I have regestired the ocx file file with procmon running, the file registred sucessfully and procmon dint show up any missing file.
However when i drop the three files into dependency walker it is showing up two missing dependencies for the three files which is shown in the image below.
Does it mean that i need two include these two files with registrations in the package? This is the first time I am into this type of scenario so dont have idea how to handle this.
Your help is greatly appreciated.Thank you for your help.
Thanks for your reply. I have regestired the ocx file file with procmon running, the file registred sucessfully and procmon dint show up any missing file.
However when i drop the three files into dependency walker it is showing up two missing dependencies for the three files which is shown in the image below.
Does it mean that i need two include these two files with registrations in the package? This is the first time I am into this type of scenario so dont have idea how to handle this.
Your help is greatly appreciated.Thank you for your help.
Posted by:
anonymous_9363
13 years ago
I suspect the registration worked when you ran ProcMon because you registered the file from the directory containing the 2 files.
When you drop the file on to DW, it - like MSIExec - cannot find the files because you don't launch DW from the folder containing them and they're not in the PATH. You have some choices:
- stop registering files using RegSvr32/MSIExec which is bad practice anyway, for precisely this reason. Add a check for these files and a LaunchCondition that advises the user that dependencies are missing.
- add the folder containing the "missing" files to the PATH [shudder]
- copy the files to %SystemRoot%\SYSTEM32 [slightly less vigorous shudder]
BTW, remember I said you could ignore the dynamically-loaded stuff like MPR.DLL, the files highlighted in pink/red.
When you drop the file on to DW, it - like MSIExec - cannot find the files because you don't launch DW from the folder containing them and they're not in the PATH. You have some choices:
- stop registering files using RegSvr32/MSIExec which is bad practice anyway, for precisely this reason. Add a check for these files and a LaunchCondition that advises the user that dependencies are missing.
- add the folder containing the "missing" files to the PATH [shudder]
- copy the files to %SystemRoot%\SYSTEM32 [slightly less vigorous shudder]
BTW, remember I said you could ignore the dynamically-loaded stuff like MPR.DLL, the files highlighted in pink/red.
Posted by:
naveen.packager
13 years ago
Thanks VBScab.
No, I dont have the files in the directory.
I am not self registring the files. I have captured the application and the msi is containing the registration with advertising. It is giving the error of typlib registration during installation.
I will try what you have suggested and let you know.
Thank you very much.
I suspect the registration worked when you ran ProcMon because you registered the file from the directory containing the 2 files.
No, I dont have the files in the directory.
stop registering files using RegSvr32/MSIExec which is bad practice anyway, for precisely this reason
I am not self registring the files. I have captured the application and the msi is containing the registration with advertising. It is giving the error of typlib registration during installation.
I will try what you have suggested and let you know.
Thank you very much.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.