Installation problem

I have created an application in VB6 and wish to install it into another computer. I used the Deployment Wizard to create my installation package. I loaded the package into my target computer and ran the setup program. Halfway thru the installation, I got the following message and the installation failed. "The file 'c:DOCUME~1NORHIS~1LOCALS~1Tempsmsftqws.pdw$(DLLSelfRegisterEX)' could not be registered because it was not found.' Need help urgently to solve this problem. Anybody can suggest other proper way to install an application written in VB6 into another computer?

Answer Wiki

Thanks. We'll let you know when a new response is added.

Are you norris??

Discuss This Question: 2  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Quantumkev
    I am not sure, but it sounds like there may be a dependency issue. I found some info on MSDN that may be helpful to you. I don't have much experience with VB6, as I have primarily developed in .NET. I know in that enviroment, you have to be sure to include 'dotnetfx' as part of the installation package, or it will not deploy properly. I hope the link is helpful to you.
    0 pointsBadges:
  • Idesign4u
    From the looks of your error message... the answer looks simple: a particular file that the setup program is looking to register on the other computer is missing! -- but the solution is not so simple... you must determine exactly which file is missing, and where is it expecting to find that file. The answers to that lie within your setup file itself: for it contains all expected paths and file names, which are (first of all) based upon their occurrance in the system on which you created the program, and then as they relate to wherre they are to end up on the new system. Microsoft's Deployment wizard is supposed to handle all of that (invisibly, for the most part) for you. But the truth is, it doesn't always work out that way in practice. You also have to be aware of version issues surrounding any ".dll"s that may be required by your application. Sometimes a target system may not allow you to "update" to an older version that you may have in your setup files. To help you any further, I would have to see a listing of all of the files your setup is trying to install and/or register, as well as their directory location: source and target.
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: