I have a program that I'm attempting to update to the latest version.

Right now its on v3 and i want to get it ot v4. Running the setup.exe straight begins the installation, but then requests the cd so that it can get the MSI file. If you do this, it says that the MSI file isnt valid.

If I run the command <file.msi> /update <file.msp> I get the 1642 error message:

"The installer cannot install the upgrade patch because the program being upgraded may be missing or the upgrade patch updates a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch."

Re-downloading the update doesnt yield any different of a resut.

If I use Orca, the MSI ProductCode matches in both the MSI and the MSP (if im checking them correctly, anyways)

I am running MSIEXEC version 3.01.4000.3959

Any ideas?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi,

Install the MSI and then directly double click the MSP. If it gets installed manually, please do let me know so that i can tell you what needs to be done next. Remember if you can do something manually, then automation is just knowing about the right procedures...

Do give an update..
Answered 10/30/2007 by: matrixtushar
Purple Belt

Please log in to comment
0
But the program is already installed, wont running the MSI reinstall the product, and I loose all of my settings and what have you?
Answered 10/30/2007 by: cjfritz01
Yellow Belt

Please log in to comment
0
Hi CJ,
make sure, the installed MSI has its source available!
Please log the thing and search for errors in the logfile.
BTW: What app are we talking about, here?
Regards, Nick
Answered 10/31/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
The MSI file has its source available. If I point to the MSI file while its on the CD or if I copy the CD over and point to it that way makes no difference.

The log file is as follows:


=== Verbose logging started: 10/29/2007 10:58:04 Build type: SHIP UNICODE 3.01.4000.3959 Calling process: C:\WINDOWS\System32\msiexec.exe ===
MSI (c) (F0:A8) [10:58:04:307]: Resetting cached policy values
MSI (c) (F0:A8) [10:58:04:307]: Machine policy value 'Debug' is 0
MSI (c) (F0:A8) [10:58:04:307]: ******* RunEngine:
******* Product: C:\Documents and Settings\Administrator\Desktop\FM Server 8 for sure\files\FileMaker Server 8.msi
******* Action:
******* CommandLine: **********
MSI (c) (F0:A8) [10:58:04:307]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (F0:A8) [10:58:04:322]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Documents and Settings\Administrator\Desktop\FM Server 8 for sure\files\FileMaker Server 8.msi' against software restriction policy
MSI (c) (F0:A8) [10:58:04:322]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (c) (F0:A8) [10:58:04:322]: SOFTWARE RESTRICTION POLICY: C:\Documents and Settings\Administrator\Desktop\FM Server 8 for sure\files\FileMaker Server 8.msi is not digitally signed
MSI (c) (F0:A8) [10:58:04:338]: SOFTWARE RESTRICTION POLICY: C:\Documents and Settings\Administrator.FWMRPC\Desktop\FM Server 8 for sure\files\FileMaker Server 8.msi is permitted to run at the 'unrestricted' authorization level.
MSI (c) (F0:A8) [10:58:04:338]: Cloaking enabled.
MSI (c) (F0:A8) [10:58:04:338]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (F0:A8) [10:58:04:353]: End dialog not enabled
MSI (c) (F0:A8) [10:58:04:353]: Original package ==> C:\Documents and Settings\Administrator\Desktop\FM Server 8 for sure\files\FileMaker Server 8.msi
MSI (c) (F0:A8) [10:58:04:353]: Package we're running from ==> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\20d238.msi
MSI (c) (F0:A8) [10:58:04:353]: APPCOMPAT: looking for appcompat database entry with ProductCode '{E7DCC274-E5A6-4B97-81E7-E80149F6257B}'.
MSI (c) (F0:A8) [10:58:04:353]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (F0:A8) [10:58:04:353]: MSCOREE not loaded loading copy from system32
MSI (c) (F0:A8) [10:58:04:432]: Original patch ==> C:\Documents and Settings\Administrator\Desktop\FileMaker Server 8.0v4 Updater\Files\FileMakerServer8v4Updater.msp
MSI (c) (F0:A8) [10:58:04:432]: Patch we're running from ==> C:\DOCUME~1\ADMINI~1.FWM\LOCALS~1\Temp\20d239.msp
MSI (c) (F0:A8) [10:58:04:447]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'C:\Documents and Settings\Administrator\Desktop\FileMaker Server 8.0v4 Updater\Files\FileMakerServer8v4Updater.msp' against software restriction policy
MSI (c) (F0:A8) [10:58:04:447]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (c) (F0:A8) [10:58:04:447]: SOFTWARE RESTRICTION POLICY: C:\Documents and Settings\Administrator\Desktop\FileMaker Server 8.0v4 Updater\Files\FileMakerServer8v4Updater.msp is not digitally signed
MSI (c) (F0:A8) [10:58:04:447]: SOFTWARE RESTRICTION POLICY: C:\Documents and Settings\Administrator\Desktop\FileMaker Server 8.0v4 Updater\Files\FileMakerServer8v4Updater.msp is permitted to run at the 'unrestricted' authorization level.
MSI (c) (F0:A8) [10:58:04:447]: SequencePatches starts. Product code: {E7DCC274-E5A6-4B97-81E7-E80149F6257B}, Product version: 8.0.4.1, Upgrade code: {D877E4AE-5CBC-4AF2-AD76-0AA2DBA2F0CC}, Product language 1033
MSI (c) (F0:A8) [10:58:04:447]: PATCH SEQUENCER WARNING: C:\Documents and Settings\Administrator\Desktop\FileMaker Server 8.0v4 Updater\Files\FileMakerServer8v4Updater.msp patch will not be sequenced because it does not contain any transform that may apply to product!
MSI (c) (F0:A8) [10:58:04:447]: SequencePatches returns success.
MSI (c) (F0:A8) [10:58:04:447]: Final Patch Application Order:
MSI (c) (F0:A8) [10:58:04:447]: Other Patches:
MSI (c) (F0:A8) [10:58:04:447]: Unknown\Absent: {6B9DA660-5AB5-4C9C-B388-0BE1828C0244} - C:\Documents and Settings\Administrator\Desktop\FileMaker Server 8.0v4 Updater\Files\FileMakerServer8v4Updater.msp
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer an
d that you have the correct upgrade patch.
C:\Documents and Settings\Administrator\Desktop\FM Server 8 for sure\files\FileMaker Server 8.msi
MSI (c) (F0:A8) [10:58:04:447]: Product: FileMaker Server 8 - Update '{6B9DA660-5AB5-4C9C-B388-0BE1828C0244}' could not be installed. Error code 1642. Additional information is available in the log file c:\install2.log.
MSI (c) (F0:A8) [10:58:04:447]: Note: 1: 1708
MSI (c) (F0:A8) [10:58:04:447]: Note: 1: 2729
MSI (c) (F0:A8) [10:58:04:447]: Note: 1: 2729
MSI (c) (F0:A8) [10:58:04:447]: Product: FileMaker Server 8 -- Installation failed.
MSI (c) (F0:A8) [10:58:04:447]: Attempting to delete file C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\20d239.msp
MSI (c) (F0:A8) [10:58:04:463]: MainEngineThread is returning 1642
=== Verbose logging stopped: 10/29/2007 10:58:04 ===


The App is FileMaker Server 8. Searching their website or calling their tech support is pretty useless.
Answered 10/31/2007 by: cjfritz01
Yellow Belt

Please log in to comment
0
This might be a long shot, but do you have any other products from this vendor already installed on the machine, and more specifically, have you had other patches from this vendor that you have applied to those products ?

The reason I ask this is that I am wondering whether the Package Code of the patch you are currently working with has not been made unique.

If you already have a patch installed on the system (for another product) but which has the same package code as the patch you are trying to install, then when you attempt to use the current patch, Windows Installer may be trying to use the other cached patch and then flagging an error because the cached one doesn't relate to the FileMaker Server 8 product.

A test you could try (with care) would be to temporarily move all the existing cached MSP files from the C:\Windows\Installer folder to another folder and then try applying the patch you are working with. Make sure you restore all the MSP files you moved back to C:\Windows\Installer when you have finished.

As I said, a long shot - but it might be worth a try.

Regards,

Spartacus
Answered 10/31/2007 by: spartacus
Black Belt

Please log in to comment
0
Yes, I do have other products from this vender installed on the machine.

All three of the products that are on this machine I do believe have been updated like this before with previous patches from the vender.

I tried moving all of the cached installer files as you suggested but it does not yeild any different of a result.
Answered 10/31/2007 by: cjfritz01
Yellow Belt

Please log in to comment
0
The reason the patch wont apply is because of this line in the log -
Unknown\Absent: {6B9DA660-5AB5-4C9C-B388-0BE1828C0244}

The product code for the already installed app is not what the patch is looking for, so cant be applied. There maybe a way to change a table property or something, but I couldnt find it, lots more experienced people than me on here that maybe able to assist.
I had a similar issue with MS SQL Tools 05 when trying to apply SP2. A colleague of mine scripted the package and applied SP1 to the msi. But, he also changed the product code, so when i came to apply SP2, i got the same error as you. I found no way of changing the code, and eventually gave up and created a script that removed everything SQL and Sp1, and then installed SQL rtm, and then installed SP2. Ugly, but it works.
Answered 11/04/2007 by: reds4eva
Second Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity