Hi everyone. I am new to packaging and need some help with ICE error.

On packaging I am receiving an ICE03 - Invalid Format String

Problem is in the Registry table and the column Value.

U6}D``o9R?KtQhi?XANATFTm8DqSV@4ubojGCqa6+iu*_y9t~=5gD^ZnrR_'*!!6ijs!H=QHtAj^2H}3eva4RvV}}?.oBwDB?pfiqP{HC'kyd@m4!AIEzdFVo{ur_AJ()@Z(3sz57e+'kdNk072!`9{)%XW0Ob-f7`zRWwz{[\[]AJG89vxdd8=Lc)[\]]v4Ga&Axo4-A[\[]vN85q=7R8jPvX8fm[\]]Z1zjZHp5*Aez{A3C?&Ua7@9j'OFovVXoNjL2?66kYx,e[\[]SX!hRiLl@P6=mTV+,S6T7Oqg@uKeEha@eB53&J3A!.L&3wF)fZg8a3fZrMG810so,0Iqh4.@i+8m=Gii06LnvPZtcP-9OcjN.=r2Y8ReaderProgramFiles

As you can see with this string it has 4 close brackets followed by 4 open brackets. Now I know to rectify I can just put the required amount of curly brackets in the string but I have firstly no idea where to put the { }.
Do I just wrap the whole string or place the required { } adjacent to the corresponding { } . Or can I just delete all the { } ?

Secondly by adding or removing { } I have no idea what is happening to the package. I'm assuming that the { } work like a mathematical equation and the text within the { } is processed first.

Your help and assistance is much appreciated.

Oh and this was one of the easier strings. Some have string lengths a couple of hundred chars in length [&:]
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I'm willing to bet you have captured a package which is already in MSI format. If so, don't!
Answered 09/02/2008 by: VBScab
Red Belt

Please log in to comment
0
Hhhhm. Not sure to be honest. I thought it was an installShield but that may have been a wrapper for an MSI. I'll check. :)
Answered 09/02/2008 by: ninjamaster
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: ninjamaster
I'll check. :)
What's the registry key that the value's associated with? That'll give it away.
Answered 09/02/2008 by: VBScab
Red Belt

Please log in to comment
0
SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\68AB67CA7DA73301B7447A0000000000\Features

?
Answered 09/02/2008 by: ninjamaster
Senior Yellow Belt

Please log in to comment
0
Sussed it. It was indeed an InstallShield wrapper around an MSI. Ran the installshield which unpacked the files and pulled out the MSI. I'll do a transform :)
Answered 09/02/2008 by: ninjamaster
Senior Yellow Belt

Please log in to comment
0
Once you have your transform, make sure you run the vendor's install "over the top" of yours, having a) run a lightweight snapshot tool (I use Ziff-Davis's In Control) to monitor any changes and b) edited the 'Uninstall' registry branch to fool WI into thinking the product isn't installed. Why? Because some vendors are too bone idle to include in the MSI all the functionality they require and resort to decades-old script in the EXE stub loader.
Answered 09/02/2008 by: VBScab
Red Belt

Please log in to comment
0
Many thanks for the info :)
Answered 09/02/2008 by: ninjamaster
Senior Yellow Belt

Please log in to comment
0
OK. I made my transform. Easy enough. :) But when running the MSI with the MST it complains because it's looking for a CAB file (That's obviously part of the original wrap).

Is this the scenario you were describing?
Answered 09/02/2008 by: ninjamaster
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity