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
- :
- IS 2010 migration: Cryptic 1603 error
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
Aug 25, 2010
04:48 PM
IS 2010 migration: Cryptic 1603 error
Hello,
We have an existing Basic MSI project that I have been tasked with updating to IS 2010 from IS 2009. I imported the old .ism file and Installshield converted it to the new format.
Upon testing this new installer, I keep getting a 1603 error reported and no real obvious errors or hints on where to go from here. I have scoured the internet the past few days looking for hints but have been unsuccessful.
Target machine is running Windows Server 2008. I believe I have narrowed down the Feature in question that is causing the issue however this feature has a lot of functionality built into it. It is making XML changes, making an IIS application pool, and adding some files to the system. I have "Enable 32-bit applications" setting on all application pools I create on this platform. In the Installer GUI, I see Application pools get created then seemingly rolled back immediately afterwards.
The windows installer log has a few instances of "Return Value 3" but no obvious error to report. The first instance of "return value 3" occurs in this context:
We are making some changes to a Tomcat web-app file. Is this XSI namespace issue a red herring or a possible cause for my issue? I am hesitant to say this is the issue because I an not getting Fatal Errors from ISXmlCosting.
Any help would be great, thank you. 😄
We have an existing Basic MSI project that I have been tasked with updating to IS 2010 from IS 2009. I imported the old .ism file and Installshield converted it to the new format.
Upon testing this new installer, I keep getting a 1603 error reported and no real obvious errors or hints on where to go from here. I have scoured the internet the past few days looking for hints but have been unsuccessful.
Target machine is running Windows Server 2008. I believe I have narrowed down the Feature in question that is causing the issue however this feature has a lot of functionality built into it. It is making XML changes, making an IIS application pool, and adding some files to the system. I have "Enable 32-bit applications" setting on all application pools I create on this platform. In the Installer GUI, I see Application pools get created then seemingly rolled back immediately afterwards.
The windows installer log has a few instances of "Return Value 3" but no obvious error to report. The first instance of "return value 3" occurs in this context:
InstallShield 17:06:42: Processing XPath '//'
InstallShield 17:06:42: Node name: 'web-app' --> Attribute name = 'id', Current Value = 'WebApp_ID', Operation = '1'
InstallShield 17:06:42: Node name: 'web-app' - Attribute name = 'id', Old Value = 'WebApp_ID', New value = 'WebApp_ID', Actual New Value = 'WebApp_ID'
InstallShield 17:06:42: Node name: 'web-app' --> Attribute name = 'version', Current Value = '2.4', Operation = '1'
InstallShield 17:06:42: Node name: 'web-app' - Attribute name = 'version', Old Value = '2.4', New value = '2.4', Actual New Value = '2.4'
InstallShield 17:06:42: No namespace for prefix xsi found
InstallShield 17:06:42: Node name: 'web-app' --> Attribute name = 'xsi:schemaLocation', Current Value = '', Operation = '1'
InstallShield 17:06:42: Node name: 'web-app' - Attribute name = 'xsi:schemaLocation', Old Value = '', New value = 'http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd', Actual New Value = 'http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd'
Action ended 17:06:42: InstallFinalize. Return value 3.
We are making some changes to a Tomcat web-app file. Is this XSI namespace issue a red herring or a possible cause for my issue? I am hesitant to say this is the issue because I an not getting Fatal Errors from ISXmlCosting.
Any help would be great, thank you. 😄
(1) Reply
Aug 27, 2010
11:00 AM
So after removing the XML files changes for that particular file, the issue disappeared. :eek:
EDIT: The issue was found to be with the XML file attributes we were adding to these xml files. I deleted the attributes that were left over from IS2009 project and all installed fine.
EDIT: The issue was found to be with the XML file attributes we were adding to these xml files. I deleted the attributes that were left over from IS2009 project and all installed fine.