Internal Error 2715
I am getting the following error when compiling my installshield solution. It is only a warning, and still compiles, and installs successfully.
However, I don't have a custom action in the database. However, I think I did have one a long time ago, but now I think that this error, and the one below, might be related.
-------------
Validating Custom Action sequencing
ISDEV : warning -6525: The Custom Action CA_CONFIIS4_Uninstall.3643236F_FC70_11D3_A536_0090278A1BB8 in the InstallExecuteSequence table is run from an installed file. It must be sequenced after the InstallFiles action. Ensure that the Custom Action is sequenced properly and that the base actions exists in the sequence.
C:\Program Files\InstallShield X\IsDev.exe\-6525
-------------
However, when I try to create a quickpatch project, and install it, I get an Internal Error 2715 when trying to execute it.
Are the two related, or is there a possibility that they could be?
Cheers,
Ian.
However, I don't have a custom action in the database. However, I think I did have one a long time ago, but now I think that this error, and the one below, might be related.
-------------
Validating Custom Action sequencing
ISDEV : warning -6525: The Custom Action CA_CONFIIS4_Uninstall.3643236F_FC70_11D3_A536_0090278A1BB8 in the InstallExecuteSequence table is run from an installed file. It must be sequenced after the InstallFiles action. Ensure that the Custom Action is sequenced properly and that the base actions exists in the sequence.
C:\Program Files\InstallShield X\IsDev.exe\-6525
-------------
However, when I try to create a quickpatch project, and install it, I get an Internal Error 2715 when trying to execute it.
Are the two related, or is there a possibility that they could be?
Cheers,
Ian.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
Siddi_sgp
18 years ago
Have a look at all places to delete the occurence of the Custom Action from your msi tables.Check the directory structure. There nust be a missing folder.
Posted by:
iandavidcarter
18 years ago
Hi siddi_sgp,
Unfortunately I had been ims-informed by a colleague as to the preparation of installations for upgrades / patches.
I was told to create two separate builds - one compressed and one uncompressed (perform 2 builds).
This was wrong. To create the original package you need to unpack the compressed exe and compile the patch against that.
This then worked ok.
Thanks for the post.
Ian.
Unfortunately I had been ims-informed by a colleague as to the preparation of installations for upgrades / patches.
I was told to create two separate builds - one compressed and one uncompressed (perform 2 builds).
This was wrong. To create the original package you need to unpack the compressed exe and compile the patch against that.
This then worked ok.
Thanks for the post.
Ian.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.