sanjay-singh
asked on
How to make single instance Installer with InstallShield 2010
We have Install Script MSI type of project and we make a single setup.exe installer for our product.
We find that users can click on setup.exe multiple times and thus spawning multiple Installers at the same time. We then get following error:
"Unable to save file *.msi. The file exists."
The error snapshot is attached also.
How can we ensure that only one installer is running at any given time and if user clicks on setup.exe again they are just ignored?
Since the issue happens during extracting msi, I cannot even write any custom action to restrict this using some mutex or any other logic.
We find that users can click on setup.exe multiple times and thus spawning multiple Installers at the same time. We then get following error:
"Unable to save file *.msi. The file exists."
The error snapshot is attached also.
How can we ensure that only one installer is running at any given time and if user clicks on setup.exe again they are just ignored?
Since the issue happens during extracting msi, I cannot even write any custom action to restrict this using some mutex or any other logic.
ASKER
Thanks for the response.
We have been using InstallScript MSI for a long time because we had to do a lot of customizations and it was serving our purpose. I don't think it is an option now to switch to Basic MSI.
I also see that it is not that unusual. I tried with SQL Server Express 2005 installer and Firebird 2.5 Installer, and they both seemed to suffer from this problem.
Do you think of any other pointer to solving this?
We have been using InstallScript MSI for a long time because we had to do a lot of customizations and it was serving our purpose. I don't think it is an option now to switch to Basic MSI.
I also see that it is not that unusual. I tried with SQL Server Express 2005 installer and Firebird 2.5 Installer, and they both seemed to suffer from this problem.
Do you think of any other pointer to solving this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I've requested that this question be deleted for the following reason:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned and is now flagged for deletion.
If there is a valid solution, please OBJECT and indicate the comments that are, or would otherwise lead to, a solution.
Use the specific format https:#axxxxxxxx for comment ID(s).
Also, please don't object simply because the author did not respond to your comment. While we understand this is frustrating, unfortunately we cannot force the author to return to the question. Unless you feel you have presented a valid, verifiable solution we'll simply delete the question.
Experts-Exchange Auto Deleter
No comment has been added to this question in more than 21 days, so it is now classified as abandoned and is now flagged for deletion.
If there is a valid solution, please OBJECT and indicate the comments that are, or would otherwise lead to, a solution.
Use the specific format https:#axxxxxxxx for comment ID(s).
Also, please don't object simply because the author did not respond to your comment. While we understand this is frustrating, unfortunately we cannot force the author to return to the question. Unless you feel you have presented a valid, verifiable solution we'll simply delete the question.
Experts-Exchange Auto Deleter
The answer was given: it's not possible.
If it indeed does not happen with the sample installation, then you'll have to figure out what has been tweaked in the real one.
That said, the recommended type of the project is "Basic MSI", while Installscript is better to avoid.