Package Deployment Failure on Windows 2000

[velociraptor]

Anyone have an idea why the standard VB6 Package Deployment, Setup.exe fails to update the required files on a Windows 2000 platform?

After running setup.exe, Windows reboots to in an attempt to update files. The next time you run setup.exe it complains about having to update files before it can run, "again"!

Is there a way to get around this without having to repackage the app?

 

[PcProgrammer]

Check if the W2000 service packs are up to date.

 

[CajunCenturion]

I would guess that the problem is centered around 3 DLL's, those being OLEPRO32, OLEAUT32, and STDOLE2. When you packaged application contains newer version of any of these 3 DLL, then the installer will try to update them, but since they are always loaded by the OS at boot time, they can't be updated.

The easiest solution is the insure that you have older copies of these three DLLs in your packaged application that are on the target machine.

The PDW obtains the version of these files that our found in the following directory:

C:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Redist

After saving the ones already there, I would try and find the oldest copies of these 3 DLLs that I could find, and copy them into the Redist directory, then repackage the app
Good Luck
------------
Select * from Users where Clue > 0
0 rows returned

 

[DrinkN1]

I had this problem awhile ago. In my case, the system was set up to clear the temp directory on boot. That is where the PDW stores the files until the system can move them over when it is rebooted. So, I fell into a loop...Update, Re-boot, Clear temp, try to update with files in temp, Update again, Re-boot, etc.

Sure, could be a million reasons why you are having this issue, but this was the culprit of mine.

Drink N 1

 

[CCLINT]

Or just get, or have the customer get, the latest service pack for Windows 2000...