This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Converted project cannot open
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 11, 2014
04:15 PM
Converted project cannot open
Hi,
Just installed InstallShield 2013 on my VS2012 system. When I opened a project I previously worked on with InstallShield 2012 Spring Limited Edition it prompted me to upgrade the project, so I said yes. Then it made me reboot my computer, which I thought was odd, but followed directions.
When the computer rebooted I tried opening the project again and now I get the message:
"InstallShield cannot open \\server\share\folder\myprogram\setup\setup.isl. Please contact Flexera Software technical support for more information."
Well I already know they won't help me so I thought I'd post the question here. Anyone know what I need to do to be able to work with this project?
Thanks in advance,
Linn
Just installed InstallShield 2013 on my VS2012 system. When I opened a project I previously worked on with InstallShield 2012 Spring Limited Edition it prompted me to upgrade the project, so I said yes. Then it made me reboot my computer, which I thought was odd, but followed directions.
When the computer rebooted I tried opening the project again and now I get the message:
"InstallShield cannot open \\server\share\folder\myprogram\setup\setup.isl. Please contact Flexera Software technical support for more information."
Well I already know they won't help me so I thought I'd post the question here. Anyone know what I need to do to be able to work with this project?
Thanks in advance,
Linn
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 14, 2014
02:19 AM
Hello Linn,
Kindly make sure the old setup.isl exists in the mentioned path location.
You may also want to try adding a new project to the existing VS solution, so as to integrate it with InstallShield Limited Edition on to the new machine.
Please let me know if you require any further assistance with this.
Thanks,
Chaitra
Kindly make sure the old setup.isl exists in the mentioned path location.
You may also want to try adding a new project to the existing VS solution, so as to integrate it with InstallShield Limited Edition on to the new machine.
Please let me know if you require any further assistance with this.
Thanks,
Chaitra
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 15, 2014
08:55 AM
We had this problem too, IS started the upgrade process but didn't finish it before rebooting.
If you go to the directory where the ISL is at, you will see another file with a numbered extension with the same name. move that file out of the directory and try opening the ISL again. If you have your ISL under source control you might need to get the version from before the upgrade to retrigger the upgrade attempt.
If you go to the directory where the ISL is at, you will see another file with a numbered extension with the same name. move that file out of the directory and try opening the ISL again. If you have your ISL under source control you might need to get the version from before the upgrade to retrigger the upgrade attempt.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 21, 2014
10:34 AM
Thanks for the responses. I checked and the setup.isl file was in the correct directory and I removed the setup.isl.773 file but that didn't help. So I tried jcoone's suggestion and copied the original setup.isl over again and it did prompt to reconvert. This time it seems to have worked, when I open the project I no longer get the error message.
Thanks much!
Linn
Thanks much!
Linn
jcoone wrote:
We had this problem too, IS started the upgrade process but didn't finish it before rebooting.
If you go to the directory where the ISL is at, you will see another file with a numbered extension with the same name. move that file out of the directory and try opening the ISL again. If you have your ISL under source control you might need to get the version from before the upgrade to retrigger the upgrade attempt.
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)