If the reason behind this is because you do not have access to the certificate, you can try to proceed as it follows:My constraint, is I can not sign the installer using the inbuilt "Digital Signature" window of Advanced Installer.
Indeed, you are right. I am afraid I am not aware of any workaround for this issue other than using the card to sign the EXE on the build machine.This only works if you append a new signature to the EXE, you cannot replace it. This means we would have a test certificate signature going out on our EXEs labeled by the machine that built it, which may (and likely is) not be acceptable for all of our customers.
By following what I have said, here is what will actually happen: the MSI will be signed once (by the test certificate), while the EXE will be signed twice (by the test certificate and by your main certificate). At install time, the check will be done and, by seeing that the MSI and the EXE have been signed with the same certificate (the test certificate), the error will no longer be spawned.If I do the things that you suggested, the signature of the MSI and the EXE will still not match as MSI would be signed by a test certificate and EXE by the main certificate. Please correct me if I am wrong.
It's 12.5.1 for me.I'm curious what the CreateVersion of your AIP file is?
Thats my understanding as well. I was hoping maybe that would be part of the reason behind the signing issue.prerak6962 wrote:It's 12.5.1 for me.I'm curious what the CreateVersion of your AIP file is?
If my understanding is correct, it's the version of the Advanced installer using which the project was created for the very first time.
I will double check with my team and my own logs (to see what actions happened), however I recall that the MSI when logged would still report "Installation Successful", and for sure didn't send me to the "Are you sure you want to cancel installation" message.Catalin wrote:From what I know, in the older versions, we would fail the installation, but without displaying any error messages (silently).
The AIPs that we manually modified the CreateVersion return an Installation Successful in the logs, however they do not actually perform any of their actions... this maybe the silent failure you're talking about? (However I'm not very interested in this case... it doesn't seem wise to change that variable without know all of what it does).Catalin wrote:Hello Korr,
Sure. Please let me know the results of the investigation.
All the best,