Software Deployment

I'd say it depends on the file. In case you really don't need it - delete it. Otherwise try to fix the error.
Does a verbose log bring up more useful information that you could post here?

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.[:)]

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.

Hi,
but i am getting the error for .exe file...
so i cannt register with regsvr32...
so in that case what could be the solution?

(error 1911: could not register typelibrary for file [.exe]..) this was the error description. this error i am getting while installing the package.



thanks

Check http://itninja.com/blog/view/sysprep-"factory-mode"4 if this is useful.

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.

For registering type libraries, you can use the below commandline.

C:\WINDOWS\system32\URTTemp\regtlib.exe <Full path of .tlb file>

In case you really don't need it - delete itFirst 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 table NEVER 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.