Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VB 6.0 Setup will not overwrite Outdated files. 1

Status
Not open for further replies.

jayare1948

Programmer
Apr 14, 2003
16
0
0
US
My Application was developed on a WIN2000 Pro Machine(SP3).
Visual Basic Enterprise/Visual Studio SP 3.0. I can install
the application on Win 98/ Win 2000 machines with no problem. During the setup it will prompt the user to reboot
to update out of date files (VBRUN ETC). On one Win2000 Pro
machine it prompts user to update files, user selects "OK",
machine reboots but the files are not updated. So when the
user attempts to run setup again the prompt to Update the outdated files and reboot comes up again- over and over.
I had the client go to the microsoft site and download the
VB6.0 runtime .exe and run that setup. Still no go! I was
thinking that the client may have some program/service
running in background that is using one of the files
that the installer is trying to update? I had client
close every possible program and close everything
in systray to no avail! Any suggestions??????
 
Sounds like a permissions problem - Have you tried installing using a user with admin priveleges?
 


It's the Windows File Protection service that reverts the 'outdated' file back to the previously installed version. These system files are normally updated when the service packs are installed. Upgrade the client with SP3 (or to whatever SP level on the development machine), or remove the offending file from installation package.




Mark
 
Reply to Don :
User logged on as member of Administrators group
Reply to Mark:
Files in question are the ones required for VB60 Runtime
VB6STKIT.DLL,COMCAT.DLL,STDOLE2.TLB,ASYCFILT.DLL,OLEPRO32.DLLOLEAUT32.DLL,MSVBVM60.DLL
 
To Mark:
Your Post hit the spot and completely solved the problem!
Target machine was Win2000Pro SP 2.0. Development machine
Win2000 Pro 3.0. Upgrade SP on target machine solved problem. Thanks bunch!!


jayare
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top