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
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Issue with installer on Win2k8R2 built using IA 2009 SP2
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
‎Jul 15, 2013
07:00 AM
Issue with installer on Win2k8R2 built using IA 2009 SP2
Recently switched from IA 2009 to IA 2009 SP2.
Previously the built output using IA 2009 (not SP2) worked fine on Win2k8R2, after upgrading to SP2, it fails to work.
When i run my project on Win2k8R2, it shows error saying "ZGGfxUtil.loadImage : loading failed for com/zerog/ia/installer/images/billboard_default.png".
I have project specific billboard images and were working properly for before upgrading to SP2.
Strange thing is i see this problem only on Win2k8R2, for other windows like Win2k3 and Win2k3R2 it works fine.
Any pointers will be of great help.
Previously the built output using IA 2009 (not SP2) worked fine on Win2k8R2, after upgrading to SP2, it fails to work.
When i run my project on Win2k8R2, it shows error saying "ZGGfxUtil.loadImage : loading failed for com/zerog/ia/installer/images/billboard_default.png".
I have project specific billboard images and were working properly for before upgrading to SP2.
Strange thing is i see this problem only on Win2k8R2, for other windows like Win2k3 and Win2k3R2 it works fine.
Any pointers will be of great help.
- Tags:
- installanywhere2009
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 15, 2013
09:28 AM
Also I am not referring to billboard_default.png in my project
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 02, 2013
08:57 AM
Have you tried to check with support in order to see if this is a known issue (a.k.a. a bug)?