asked on

Error installing Visual Basic 6 program

Hi,

Today I tried to install my Visual Basic 6 program on a Windows 2000 SP3 machine (using the administrator account).
I generated an install package with the Package and Deployment wizard which is also provided with Visual Basic 6 (on my own development machine).
I copied that setup program onto a cd and used that cd to copy the setup program on the D partition of my Windows 2000 SP3 machine.
When I double clicked on the setup.exe I get this error:
The system could not locate the file: 'D:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\msftqws.pdw\ST6UNST.EXE'. Would you like to browse for the file yourself?

When I check that location, the file is not present, actually no files are present whatsoever, it is an empty directory.
Locating the file manually does not seem to help either.

I also get this error: Cannot start main setup program! (CreateProcess() returned error code 0x00000002H)

So basically the setup does not uncompress any files from the CAB file nor does the main setup program launch correctly.

I ve tried the exact same setup program on 5 different computers and it works like a charm, no problems whatsoever.

Now my question: what am I doing wrong with this one pc? How come that my program cannot install itself?

Any help and suggestions are more than welcome!

Thanks in advance!

Osmodean

nffvrxqgrcfqvvc

ST6UNST.EXE is just the Un-Installer .exe to uninstall the application.
http://support.microsoft.com/kb/194776/EN-US/

Open the Windows Control Panel.
2. Double-click the System icon, and click the Environment tab.
3. In the System Variables list, click Path.
4. In the Value box, add the necessary path information, as shown above, for both the \Windows and \Windows\System32 directories for the given user, and separate these two entries with a semicolon (;).
5. Click OK to exit the System Properties dialog box. The Visual Basic application should now install without the error message listed above.

osmodean

ASKER

This may be a stupid question but is Windows 2000 SP3 a Microsoft Windows-based Terminal Server Client?

Also what do they mean by: "The error above can be avoided by modifying the path environment variable on the Terminal Server client to contain the exact path of the \Windows and \Windows\System directories."

Is that the absolute path to the windows and windows system directory? Cause the example they give is a bit strange.

Could it be like: C:\WINDOWS and C:\WINDOWS\SYSTEM ?

Thanks in advance!

Osmodean

nffvrxqgrcfqvvc

Try setting it to this:

C:\Documents and Settings\Administrator\Local Settings\Temp

nffvrxqgrcfqvvc

You should try and copy all the files the the ROOT of the C:\ drive. But keep your CD in the cd-rom and try to run the setup from the hard disk.

nffvrxqgrcfqvvc

I dont even think creating a partition on drive d: creates a folder structure pointing to the Local Settings folder like it is on the C:\DRIVE

ie.
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\msftqws.pdw\ST6UNST.EXE <=== this path probrably exists.

But:

'D:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\msftqws.pdw\ST6UNST.EXE' <---- this path doesn't exist on your D:\ partition.

You know what I mean?

nffvrxqgrcfqvvc

<<<< The system could not locate the file: 'D:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\msftqws.pdw\ST6UNST.EXE'

Casue1:
Damaged diskette, or setup file.

Cause2:
Left over files from a previous installation attempt

ASKER CERTIFIED SOLUTION

nffvrxqgrcfqvvc

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Matti

Hi!

>I also get this error: Cannot start main setup program! (CreateProcess() returned error code 0x00000002H)
This normal comes when media is damaged, try to make another CD.
It can't read what's in the cab.

http://support.microsoft.com/default.aspx?scid=kb;en-us;290887
Try this patch before your installer, it can update VB runtime if it's out of date.

Matti

nffvrxqgrcfqvvc

Yes. If you don't have the VB Service Pack 6. Then you should download it.

osmodean

ASKER

Thank you for all your answers, I will try all suggestions and post if they worked or not!

nffvrxqgrcfqvvc

Thanks, so which one of those options resolved the issue? Was it a bad disk?

osmodean

ASKER

It was a full harddrive (3,74 mb was left) and misconfigured userrights in windows 2000.
Thanks for the solutions!