Error 1911
Hi,
I am getting an error called .....
Error 1911. Could not register type library for file [FILENAME]. Contact your support personnel". Is that ok just to deleted the ( filename ) durning capture mode ..
I am getting an error called .....
Error 1911. Could not register type library for file [FILENAME]. Contact your support personnel". Is that ok just to deleted the ( filename ) durning capture mode ..
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
rpfenninger
18 years ago
Posted by:
ekangi
18 years ago
This error informs that the Installer cannot register the file mentioned in the Error Dialog box.
First check whether the file is required by your application.
If required, then register the file manually using "regsvr32" command & capture the registration changes, import the same in your MSI project file, then compile->test final MSI.
Also, the same operation can be done via SelfReg table by placing the file that is required to registered for the proper functionality of the app.
I hope this gives you enough info on file registration.
Regards,
Sanju.[:)]
First check whether the file is required by your application.
If required, then register the file manually using "regsvr32" command & capture the registration changes, import the same in your MSI project file, then compile->test final MSI.
Also, the same operation can be done via SelfReg table by placing the file that is required to registered for the proper functionality of the app.
I hope this gives you enough info on file registration.
Regards,
Sanju.[:)]
Posted by:
nilo
18 years ago
Hi,
If you are using Wise, open your project. Go to View on the menu bar. Then to Setup Editor. Click on Components tab on the left. Go to the component(i.e the file) and double click it. A "File Details" menu appears. Click on the Self-registration tab and select "Do not Register" in the Registration method. Save and Compile.
Hope this helps.
Thank you,
Regards,
Nilo.
If you are using Wise, open your project. Go to View on the menu bar. Then to Setup Editor. Click on Components tab on the left. Go to the component(i.e the file) and double click it. A "File Details" menu appears. Click on the Self-registration tab and select "Do not Register" in the Registration method. Save and Compile.
Hope this helps.
Thank you,
Regards,
Nilo.
Posted by:
sowjanya_230
14 years ago
Posted by:
Yankir
14 years ago
Posted by:
anonymous_9363
14 years ago
That post deals with "proper" TypeLib files i.e. those with a .TLB extension. Most EXEs which contain COM information can be registered by running them with the '/regserver' switch. Thus, if your EXE is called MyEXE.EXE, you register it thus: MyEXE /regserver.
If that fails (which I expect it to), load the EXE into the free MS utility, Dependency Walker. This will list all the files upon which the EXE depends. Any missing ones will be highlighted with a red icon. You can usually ignore those which are shown as errors which have occured because of a load-time dependency. MPR.DLL is probably the most common one of those.
Once you know all the file's dependencies, you can set about fixing them, probably by pre-installing a runtime of some description.
If that fails (which I expect it to), load the EXE into the free MS utility, Dependency Walker. This will list all the files upon which the EXE depends. Any missing ones will be highlighted with a red icon. You can usually ignore those which are shown as errors which have occured because of a load-time dependency. MPR.DLL is probably the most common one of those.
Once you know all the file's dependencies, you can set about fixing them, probably by pre-installing a runtime of some description.
Posted by:
ramsudheer
14 years ago
Posted by:
anonymous_9363
14 years ago
In case you really don't need it - delete it
First check whether the file is required by your application.That's kind of a bizarre assertion, isn't it? How could a file containing objects NOT be needed by the application?
Next:
Also, the same operation can be done via SelfReg tableNEVER use the SelfReg table, or RegSvr32/MSIExec /y. If the file in question has any dependencies and those dependencies are missing, registration will fail using these methods. Use the advertising tables instead. Sure, the app will still fail if the dependencies are missing but your install should be checking for those in any event.
Lastly, I don't think encouraging people to simply bypass things which cause errors is particularly good advice. It's a bit like telling someone whose car is making a loud "engine about to explode" noice to simply turn up the radio volume.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.