error 1620
I have transformed a vendor supplied msi and installed it. When pushed (quietly) with SMS it installed fine as an admin but it gives me error 1620 as a user. The error message reads "This installshield package could not be opened. Contact the application vendor to verify that this is a valid windows installer package" The log is pasted below also. Please help! I have tried all things including group policiy, restarted some services. The package is installing a lot of dlls and merge modules in system32.
LOG FILE NOW FOLLOWS.
=== Verbose logging started: 2/24/2005 14:37:01 Build type: SHIP UNICODE 2.00.2600.1106 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (3C:F4): Resetting cached policy values
MSI (c) (3C:F4): Machine policy value 'Debug' is 0
MSI (c) (3C:F4): ******* RunEngine:
******* Product: \\qlbsms2\TeradataSQL61_S531.msi
******* Action:
******* CommandLine: **********
MSI (c) (3C:F4): Note: 1: 2203 2: \\qlbsms2\TeradataSQL61_S531.msi 3: -2147023570
MSI (c) (3C:F4): MainEngineThread is returning 1620
=== Verbose logging stopped: 2/24/2005 14:37:01 ===
LOG FILE NOW FOLLOWS.
=== Verbose logging started: 2/24/2005 14:37:01 Build type: SHIP UNICODE 2.00.2600.1106 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (3C:F4): Resetting cached policy values
MSI (c) (3C:F4): Machine policy value 'Debug' is 0
MSI (c) (3C:F4): ******* RunEngine:
******* Product: \\qlbsms2\TeradataSQL61_S531.msi
******* Action:
******* CommandLine: **********
MSI (c) (3C:F4): Note: 1: 2203 2: \\qlbsms2\TeradataSQL61_S531.msi 3: -2147023570
MSI (c) (3C:F4): MainEngineThread is returning 1620
=== Verbose logging stopped: 2/24/2005 14:37:01 ===
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
theagb
19 years ago
Thank you TXCatalyst for responding. Actually, this is the standard way we push apps here and the user does have rights. This package is pushed together with so many other apps to the user. All the other apps got installed successfully except this one.
See, I tried something else lately as an experiment. I repackaged the .msi and pushed it. Guess what! It was installed successfully to the user box BUT the windows taskbar was missing from the desktop. We are not allowed to repackage msi but just troubleshooting. Again I could not find the registry or whatever was "eating up" the taskbar.
I went through all these to tell you that it is unlikely to be a permissions issue.
See, I tried something else lately as an experiment. I repackaged the .msi and pushed it. Guess what! It was installed successfully to the user box BUT the windows taskbar was missing from the desktop. We are not allowed to repackage msi but just troubleshooting. Again I could not find the registry or whatever was "eating up" the taskbar.
I went through all these to tell you that it is unlikely to be a permissions issue.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.