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: ISDEV : warning -7212: The icon for the setup.exe could not be updated
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 25, 2011
03:57 AM
ISDEV : warning -7212: The icon for the setup.exe could not be updated
In the Setup.exe tab of Suite project's release viewer, i set Setup.exe icon file,
then build this project, get the following warning:
"ISDEV : warning -7212: The icon for the setup.exe could not be updated. Setup.exe will use the default icon."
This is limitations in the evaluation version of InstallShield 2012?
Kevin
then build this project, get the following warning:
"ISDEV : warning -7212: The icon for the setup.exe could not be updated. Setup.exe will use the default icon."
This is limitations in the evaluation version of InstallShield 2012?
Kevin
(13) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 25, 2011
10:27 AM
I don't believe this is an evaluation limitation. Can you successfully use this icon for setup.exe in a Basic MSI or InstallScript project? Could you attach the icon's source file here for us to look into?
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 25, 2011
10:50 AM
MichaelU wrote:
I don't believe this is an evaluation limitation. Can you successfully use this icon for setup.exe in a Basic MSI or InstallScript project? Could you attach the icon's source file here for us to look into?
Hi, Michael
The icon is extracted from system file Notepad.exe.
It's ok in the Basic MSI or InstallScript project, just for Suite project failure.
Kevin
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 25, 2011
10:54 AM
Update: I have tried to specify a single icon file directly, it's ok in Suite project.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 23, 2011
06:45 PM
I'm running into the same issue. I'm using a .ico file which has worked fine with other non-suite IS projects for replacing the setup.exe icon. I tried some other .ico files as well, including smaller ones (the intended one supports up to 256 x 256, 32bit for full win7 support, but I also tried an older 48x48 (also 32bit) icon). I cleared the read-only flag on the .ico file, but this didn't help.
Since I haven't seen a flood of reports of this error, and Kevin indicated it now works for him, it sounds like this is intermittent, or only affects certain users. Can anyone shed some light on other potential causes or workarounds for this problem?
Thank you.
Since I haven't seen a flood of reports of this error, and Kevin indicated it now works for him, it sounds like this is intermittent, or only affects certain users. Can anyone shed some light on other potential causes or workarounds for this problem?
Thank you.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 25, 2011
12:14 AM
I have seen this in the suite packages with all scenario's. The Icons we use work fine in the basic MSI packages. Is there a specific requirement for the suite icon?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 26, 2011
12:16 PM
I also am having issues. My ico file works in basic msi packages just fine but will not work on the suite project. I have the full premier edition, not the evaluation.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 27, 2011
10:40 AM
The attached zip file contains a fix for the original problem reported, the issue with specifying an icon from within a non .ico file.
To apply this fix please follow the instructions below
- Close all instances of the IDE
- Make a backup of ISToolsU9.dll from the System folder below the InstallShield 2012 installation folder
- Drop the new file in place
- Open IDE and build
If there are any problems please let me know.
This fix is targeted specifically for the problem with non .ico files. I have not been able to reproduce the problem of using an ico file in house so if you are experiencing this problem could you please provide file that can be used to demonstrate this issue and I will take a look.
To apply this fix please follow the instructions below
- Close all instances of the IDE
- Make a backup of ISToolsU9.dll from the System folder below the InstallShield 2012 installation folder
- Drop the new file in place
- Open IDE and build
If there are any problems please let me know.
This fix is targeted specifically for the problem with non .ico files. I have not been able to reproduce the problem of using an ico file in house so if you are experiencing this problem could you please provide file that can be used to demonstrate this issue and I will take a look.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 27, 2011
11:07 AM
Thanks for the hotfix John. I thought I'd give it a try even though you mentioned it targetted the non-ICO file case, but it did in fact fix the issue I was having using a .ICO file, so all is well now. Wanted to mention it for others who are also using .ICO files and facing this issue.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 07, 2011
04:55 AM
I happen to have created an executable in Visual Studio that has its icon declared as a string id i.e. "APPICON" against the ico file. I get the same warning message -7212 when i try to use that icon from that executable file but no problems when using the source ico file from the HDD. N.B. My project is an Installscript MSI one.
Could this be causing your warning ?
I tried the fix you suggested and replaced the ISToolsU9.dll, but it did not fix the warning.
Could this be causing your warning ?
I tried the fix you suggested and replaced the ISToolsU9.dll, but it did not fix the warning.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 17, 2011
04:05 PM
JohnCresswell wrote:
This fix is targeted specifically for the problem with non .ico files. I have not been able to reproduce the problem of using an ico file in house so if you are experiencing this problem could you please provide file that can be used to demonstrate this issue and I will take a look.
John,
I have attached the ico file that I am attempting to use as the Suite project's ARP icon. It errors with:
ISDEV : warning -7212: The icon for the setup.exe could not be updated. Setup.exe will use the default icon.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 25, 2011
12:54 PM
I was having trouble with .ico files as well. The patched dll provided for other type files also worked to fix my .ico issue.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 26, 2011
12:21 PM
CoreyZ: I meant to ask earlier, but what operating system are you building on? I was able to use your icon successfully, but that was on a Windows 7 machine.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 30, 2014
06:01 AM
setup.exe not build using my custom icon, throws error: "ISDEV : warning -5031: The icon for the setup.exe could not be updated. Setup.exe will use the default icon." even after download and replace the "istoolsu9.dll".
Using Myicon48x48.ico file as custom icon but the setup.exe always build with default MSI icon, This problem facing from last few days only before that it worked without any problem.
Please help me to resolve this error.
Using Myicon48x48.ico file as custom icon but the setup.exe always build with default MSI icon, This problem facing from last few days only before that it worked without any problem.
Please help me to resolve this error.