Can't solve ICE03 warning string overflow(greater than length permitted in column)Installshield2009
I have created my msi project in installshield2009 . To solve subjected warning i do following , that i read from another forum,
To do window xp logo validation , i get this warning message.
I open my msi project in orca utility. Then export the table defined in warning message and open that .idt file in notepad and change the legth of column from s72 to s46 , and import again that file in project that open in orca utility ,though I get the same error message . I also change the length to s255 but no sufficient result found.
Please reply if anyone can.Please[:)]
To do window xp logo validation , i get this warning message.
I open my msi project in orca utility. Then export the table defined in warning message and open that .idt file in notepad and change the legth of column from s72 to s46 , and import again that file in project that open in orca utility ,though I get the same error message . I also change the length to s255 but no sufficient result found.
Please reply if anyone can.Please[:)]
0 Comments
[ - ] Hide Comments

so that the conversation will remain readable.
Answer this question
or Comment on this question for clarity
Answers
please tell me detalil about how to use property, thnx for taking interest .
Please log in to comment
True but it does clean up the validation errors. As Ian said there really isn't much benefit in resolving them anyway. If the app needs a string that long there isn't much you can do about it
pramod_er123 - if you want to use the property method.. copy the offending long string to the clipboard, goto the property table and add a new row (call the property whatever you want, don't use all uppercase though) and paste the long value into the value field.
Then go back to the table with the validation error and replace the long string value with your property name in square brackets (e.g. [propertyname1] )
Run validation and the ICE03 should disappear. You can create as many properties as you need for the number of ICE03s
Hope it helps,
Rob.
pramod_er123 - if you want to use the property method.. copy the offending long string to the clipboard, goto the property table and add a new row (call the property whatever you want, don't use all uppercase though) and paste the long value into the value field.
Then go back to the table with the validation error and replace the long string value with your property name in square brackets (e.g. [propertyname1] )
Run validation and the ICE03 should disappear. You can create as many properties as you need for the number of ICE03s
Hope it helps,
Rob.
Please log in to comment
please reply for my question regarding ice03 string overflow warning. my deadline for this task is near , please reply
Please log in to comment
thnx for reply but
in warning message it display
ICE03 Warning String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.21022.08.Microsoft_VC90_ATL_x86.RTM.CEC8F2E3_AC9A_357C_BFCB_BFAC37C4AC50
but in registry table i cannot find any column reg_downlevel_manifest.21022.08.Microsoft_VC90_ATL_x86.RTM.CEC8F2E3_AC9A_357C_BFCB_BFAC37C4AC50
when i open project in orca utility i find this and change it to property called p1 that i have created in installshield2009 property table as u say but still warning come, it is not error i remind u.
in warning message it display
ICE03 Warning String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.21022.08.Microsoft_VC90_ATL_x86.RTM.CEC8F2E3_AC9A_357C_BFCB_BFAC37C4AC50
but in registry table i cannot find any column reg_downlevel_manifest.21022.08.Microsoft_VC90_ATL_x86.RTM.CEC8F2E3_AC9A_357C_BFCB_BFAC37C4AC50
when i open project in orca utility i find this and change it to property called p1 that i have created in installshield2009 property table as u say but still warning come, it is not error i remind u.
Please log in to comment
reg_downlevel_manifest.21022.08.Microsoft_VC90_ATL_x86.RTM.CEC8F2E3_AC9A_357C_BFCB_BFAC37C4AC50
It will be in the 1st column of the registry table, use the search facility if you are having touble finding it. It is the value column data that you will want to turn into a property.
I'm not sure what you mean by "i have created in installshield2009 property table" - that doesn't make sense to me but then I'm not really an installshield user... you are using the normal property table right?
Cheers,
Rob.
It will be in the 1st column of the registry table, use the search facility if you are having touble finding it. It is the value column data that you will want to turn into a property.
I'm not sure what you mean by "i have created in installshield2009 property table" - that doesn't make sense to me but then I'm not really an installshield user... you are using the normal property table right?
Cheers,
Rob.
Please log in to comment
I have created this msi project in Installshield2009. When i run window xp logo validation i get this warning.
Also i get following warning
ICE83 Warning The keypath for Global Win32 SXS Assembly (Component_=uplevel.21022.08.policy_9_0_Microsoft_VC90_ATL_x86.RTM.A50B7592_50BC_31A9_9E25_32121F451D37) SHOULD NOT be it's manifest file for assemblies other than Win32 Policy assemblies Component KeyPath uplevel.21022.08.policy_9_0_Microsoft_VC90_ATL_x86.RTM.A50B7592_50BC_31A9_9E25_32121F451D37
but in component table component id column does not contain this type of field then how can i find it is which component A50B7592_50BC_31A9_9E25_32121F451D37 , please reply I am fresher in this
Also i get following warning
ICE83 Warning The keypath for Global Win32 SXS Assembly (Component_=uplevel.21022.08.policy_9_0_Microsoft_VC90_ATL_x86.RTM.A50B7592_50BC_31A9_9E25_32121F451D37) SHOULD NOT be it's manifest file for assemblies other than Win32 Policy assemblies Component KeyPath uplevel.21022.08.policy_9_0_Microsoft_VC90_ATL_x86.RTM.A50B7592_50BC_31A9_9E25_32121F451D37
but in component table component id column does not contain this type of field then how can i find it is which component A50B7592_50BC_31A9_9E25_32121F451D37 , please reply I am fresher in this
Please log in to comment
....looks like you're incorporating the Microsoft Visual C++ 9.0 merge module. Since it's Microsoft, and since it's a merge module, I'd personally leave this warning alone.....(note the actual row of data will only appear in your compiled MSI, and NOT your ISM)
Please log in to comment
i get following error while perform xp logo validation
ICE27 Error Unknown action: 'Action1' of AdvtExecuteSequence table. Not a standard action and not found in CustomAction or Dialog tables AdvtExecuteSequence Action Action1
ICE27 Error Action: 'Action1' in AdvtExecuteSequence table has an invalid sequence number. AdvtExecuteSequence Sequence Action1
As suggested in installshield2009 help file i remove that action1 from advtexecutesequence table , though it is not solved, what i have to do, please reply
Please log in to comment
Sir , as you say i ignore ice03 warning . I disturb u once again , I get following warning
i get following error while perform xp logo validation
ICE27 Error Unknown action: 'Action1' of AdvtExecuteSequence table. Not a standard action and not found in CustomAction or Dialog tables AdvtExecuteSequence Action Action1
ICE27 Error Action: 'Action1' in AdvtExecuteSequence table has an invalid sequence number. AdvtExecuteSequence Sequence Action1
As suggested in installshield2009 help file i remove that action1 from advtexecutesequence table , though it is not solved, what i have to do, please reply
i get following error while perform xp logo validation
ICE27 Error Unknown action: 'Action1' of AdvtExecuteSequence table. Not a standard action and not found in CustomAction or Dialog tables AdvtExecuteSequence Action Action1
ICE27 Error Action: 'Action1' in AdvtExecuteSequence table has an invalid sequence number. AdvtExecuteSequence Sequence Action1
As suggested in installshield2009 help file i remove that action1 from advtexecutesequence table , though it is not solved, what i have to do, please reply
Please log in to comment
Comments