This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Install error on Windows 2000 only
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Aug 04, 2008
09:24 PM
Install error on Windows 2000 only
Hi,
I am working on a InstallScript MSI package with IS2008.
Now I ran into a annoying problem: the package works fine on all OS flavors (XP/W2K3/Vista), but not on W2K. I got the following error message on W2K:
Error: -3 Patch Package
I have no idea what that is for and I am not that familiar with Script MSI project. The log file (setup.exe /V"/l*v") is attached.
Can anybody give me some hints?
Thanks,
Peter
I am working on a InstallScript MSI package with IS2008.
Now I ran into a annoying problem: the package works fine on all OS flavors (XP/W2K3/Vista), but not on W2K. I got the following error message on W2K:
Error: -3 Patch Package
I have no idea what that is for and I am not that familiar with Script MSI project. The log file (setup.exe /V"/l*v") is attached.
Can anybody give me some hints?
Thanks,
Peter
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Aug 05, 2008
12:38 PM
Hmmm, I think I got some clue -
If I log to the same machine as a different user (tried with local admin instead of my personal credential), the install works without the error; or if I re-ghost the system, it also works. So it sounds to me like some cach or like resides on the system (I modified the feature/components in the new builds) that conflict with the contents of the new package.
If that's true, I have two questions: 1) how to clear out the cach, or turn off caching? 2) Why it only happens on W2K, not other OSs? Maybe there is a trigger (reg/config/etc) that I can use to turn it off on W2K, but other OSs have default to 'off'?
Thanks,
Peter
If I log to the same machine as a different user (tried with local admin instead of my personal credential), the install works without the error; or if I re-ghost the system, it also works. So it sounds to me like some cach or like resides on the system (I modified the feature/components in the new builds) that conflict with the contents of the new package.
If that's true, I have two questions: 1) how to clear out the cach, or turn off caching? 2) Why it only happens on W2K, not other OSs? Maybe there is a trigger (reg/config/etc) that I can use to turn it off on W2K, but other OSs have default to 'off'?
Thanks,
Peter