17 replies to this topic

[Barvaz]

Hi,

I've an installation file that contains dozens of components – Only three of them are define as dynamic file linking.
The setup is already released to many customers and I can't change/fix it.
Now I need to create a patch and each time it failed with the following error:

ISDEV : warning Val0015: The CreateFolder table contains new content. Therefore, if you are packaging this upgrade as a patch, you will not be able to make it an uninstallable patch.

New ID are generated for the dynamic files linking in each build and therefore I got this error.
Does anyone have an idea how to solved this problem? How can I make any work around to create patches "includes" dynamic file linking
Please note – I will have to create many patches for this version so one time solution is not good for me

Please advice
Many Thanks

[Stefan Krueger]

Is it really a requiremtn for you to be able to uninstall the patch?

[Barvaz]

Yes - i must enable to remove the patch, Why do you think its a problem?

I even tried to made the following workaround:

1) Backup the MainSetup.ism to MainSetup_ORIG.ism
2) Open MainSetup.ism
3) Physically deleted three components which define as Dynamic file links! Not by RemoveFiles table, deleted them so that there will not be a part of the RTM setup!
4) Rebuild MainSetup.ism setup.
4) Copy MainSetup.ism to UpgradeSetup.ism
5) Generate new Package Code and update three exe.
6) Compile the UpgradeSetup.ism
7) Create patch that the previous setup is MainSetup.msi (Exclude the three components which define as Dynamic file links!) and the latest is UpgradeSetup.msi

Then I installed the patch on a machine that already has the original installation setup which released to the customer (INCLUDE the three components which define as Dynamic file links!).
The updated three executables were refreshed on the environment but in the ARP I didn't see the patch to remove ("Allow patch to be uninstalled" check box was set on).

What do you say? Do you think that this solution\Work around makes sense and could work?

Where can I see in the registry that the patch is installed?

Thanks.

[Stefan Krueger]

[Barvaz]

No - i didn't add/change any folders in the new version - just change some existing files that are included in STATIC components.
The dynamic components are only for the initial setup and very likely that they will not change during the life time of the version - Therefore I asked if it possible to produce the same initial setup file, without these components, and install its like a patch on top of the original installation.
off course i prefer to fix it in the original setup without workaround.

As i remember i fill in the Patch Optimization field.

According to your questions, it's not possible to add or change any *folders* in the new version, add or change any files in the new version, remove any files or folders or change some existing files that are included in dynamic components?

Appreciate your help.
Thanks

[Barvaz]

Thanks Stefen, fill in the Patch Optimization field solved the dynamic file linking problem (CreateFolder) – Do you see any future problem with that?
Now I can:
1) Create an error-free .msp file.
2) The patch installation ended with no error and the target objects were refreshed as expected!
3) I can't see the patch in the ARP (Uninstall an update section) - Allow patch to be uninstalled check box was set on!

If I try to uninstall the patch by the following msiexec command I received "The patch is not applied to this product." error message

[Stefan Krueger]

[Barvaz]

The Machine where I've installed the setup file includes MSI 5.0 - So this isn't the issue.
I'm trying to create the first minor upgrade on the RTM version.
Do you think that the missing MsiPatchMetadata Table can cause the problem? can i add it manually?
Did i looking for the patch installation in the registry in the correct path?

[Stefan Krueger]

[Barvaz]

My setting Schema of my .msi is 200 - But how it's related?

[Stefan Krueger]

Schema specifies the version of MSI that the package is compatible with. Uninstallable patches were not supported in MSI 2.0, this functionality was added in a later version.

[Barvaz]

Hi,

I realized my problem but not exactly weary how to fix it - I'd be happy to accept your offer.
When I wrote my setup I wanted to provide a full user interface for all the maintenance operations. This I have done by using the "Uninstall/Change" button instead of the three Modify\Repair\Uninstall buttons.
I made it according to the instructions in the attached links:

http://www.advancedi...nge-button.html and http://www.microsoft...e-programs.aspx

After installing the product the following entries exist in the registry:

[Stefan Krueger]

I don't think you can put the patch under your custom uninstall entry. Maybe you could make an additional custom entry for the patch, but that's not really nice.

Instead of marking the package as ARPSYSTEMCOMPONENT, you could use ARPNOREMOVE (and ARPNOREPAIR if you also want to hide the Repair button). Now with only the Modify button, users will always enter the full UI and then select the desired operation from the MaintenanceType dialog.

[Barvaz]

Ok, I tried to recover the Change Button as part of the patch installation by made the following step:

1) Delete my custom uninstall entry using RemoveRegistry:
Software\Microsoft\Windows\CurrentVersion\Uninstall\[MyApplication]
Successfully passed

2) Change the value of "SystemComponent" to "0" in order to unhide items from ARP.
Change it under: Software\Microsoft\Windows\CurrentVersion\Uninstall\[PRODUCT_CODE]
I tried to change it in two ways:
• System Configuration -> Registry ….
• Change property ARPSYSTEMCOMPONENT to 0
Failed, I could not change its value!

3) Change the value of "Disable Change button" to "No" from General Information
Failed, I could not change its value

Any Idea how can I do it?

Thanks,

[Barvaz]

How can I changed the value of any existing registry key by patch? Can I?

[Stefan Krueger]

You should be able to set a new value to an existing registry entry. But I'm not sure you can change the system component setting during a patch.

[Sakthi]

I fill in the Patch Optimization with previous msi/msm. but still I see CreateFolder table with new entries of dynamically linked subfolders 

 

Removal of dynamically linked subfolder are the only way to get ride of this error? I have ~200 subfolder from some third party software 

 

are there any other alternatives to get ride of this patch build error?

 

many thanks in advance.

 

QUOTE Yes - i must enable to remove the patch, Why do you think its a problem?

Many patches can't be uninstalled, so I thought maybe you could live with this limitation.

Did you add or change any *folders* in the new version?
Did you add or change any files in the new version?
Did you remove any files or folders?
Or did you only change some existing files that are included ion dynamic components?

When you run the build wizard, do you fill in the Patch Optimization field? (see screenshot). It should help keeping the IDs unchanged.

 

 

[Stefan Krueger]

You can drag your folder structure from source to destionation view and InstallShield will automatically create components for you.