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: IS 2011 Catastropic Failure when installing a feature
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
Sep 03, 2010
10:38 AM
IS 2011 Catastropic Failure when installing a feature
I just purchased and upgraded to IS 2011 Pro from IS 2008 Pro and have converted my existing installscript project to 2011. I found that when I select a particular feature to install I will get a catastrophic failure error which makes it completely unusable.
I was able to replicate this by creating a new installscript project in IS 2011 Pro as follows.
Setup Design with:
Feature 1 – Component 1
Feature 2 – Component 1
Component 1 has dynamically linked files with sub folder enabled, include *.* .
There is one file in a directory which is three levels deep.
Install with custom setup type then select and install only “Feature 2”. Also see attached images.
I have attached the sample project with all the files included, extract it to C:\ .
Can someone please confirm this issue? Thanks.
I was able to replicate this by creating a new installscript project in IS 2011 Pro as follows.
Setup Design with:
Feature 1 – Component 1
Feature 2 – Component 1
Component 1 has dynamically linked files with sub folder enabled, include *.* .
There is one file in a directory which is three levels deep.
Install with custom setup type then select and install only “Feature 2”. Also see attached images.
I have attached the sample project with all the files included, extract it to C:\ .
Can someone please confirm this issue? Thanks.
(7) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 03, 2010
01:17 PM
I've been able to reproduce this behavior with a sample project here. We are currently investigating this issue and will post back here when more information is available.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 03, 2010
02:21 PM
After further investigation, the issue appears to be caused by path/string handling during component transfer, only in the case where a component is associated with multiple features such as this case. It is possible to work around this behavior by including a file in the root folder of a component (this ensures the component is not just a directory placeholder, and avoids the path/string handling issue).
We hope to have a code based solution available for this soon.
We hope to have a code based solution available for this soon.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 03, 2010
03:18 PM
Please try rebuilding and testing your project after applying the attached hotfix. To apply the hotfix:
1. Make a backup copy of C:\Program Files\InstallShield\2011\Redist\Language Independent\i386\ISP\ISSetup.dll.
2. Replace ISSetup.dll in the folder from step one using the attached file.
3. Rebuild and test your project.
Please let us know if this helps.
1. Make a backup copy of C:\Program Files\InstallShield\2011\Redist\Language Independent\i386\ISP\ISSetup.dll.
2. Replace ISSetup.dll in the folder from step one using the attached file.
3. Rebuild and test your project.
Please let us know if this helps.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 05, 2010
08:47 PM
Thanks for the hotfix.
I have applied it, the build and installation of the sample project was sucessful.
I have also tried it on our existing project with success.
I have applied it, the build and installation of the sample project was sucessful.
I have also tried it on our existing project with success.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 29, 2010
05:29 PM
joshstechnij wrote:
Please try rebuilding and testing your project after applying the attached hotfix. To apply the hotfix:
1. Make a backup copy of C:\Program Files\InstallShield\2011\Redist\Language Independent\i386\ISP\ISSetup.dll.
2. Replace ISSetup.dll in the folder from step one using the attached file.
3. Rebuild and test your project.
Please let us know if this helps.
I had this problem, and your hotfix fixed it. This was with IS 2011 Professional. Will you be releasing it to the rest of your customers as an update?
Thanks,
Morgan
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 30, 2010
03:40 AM
The hotfix for this issue is the same file from a different issue (Q210954). However, the version stamp of the file from this thread is earlier (17.0.0.716).
Does version 17.0.0.717 from hotfix Q210954 resolve BOTH issues?
Does version 17.0.0.717 from hotfix Q210954 resolve BOTH issues?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 30, 2010
11:12 AM
We generally build hotfixes cumulatively, so yes, the fix for both should be in the later version of the .dll. I don't have any dates, but I do expect we'll see some sort of roll-up release of this and other fixes relatively soon.