Database String Pool Corrupted - possible workaround ?
Ever had a transform corrupted by your packaging tool and received the dreaded error Database String Pool Corrupted in the installation log file ?
Help is (possibly) at hand.
I had one of these errors today - the first time I've ever seen it in fact - and found the following method resolved it :
1) Open the base MSI in ORCA
2) Click Apply Transform and browse to the corrupt transform
3) Click Generate Transform and supply a new name for the transform
4) Close Down ORCA, rename the original corrupt transform to Corrupt.MST and rename the one you generated to the original name
That's it ! In my own case a 140KB corrupt transform was reduced to 120KB after being regenerated.
Just thought I'd share this experience with the community [:)]
Spartacus
Help is (possibly) at hand.
I had one of these errors today - the first time I've ever seen it in fact - and found the following method resolved it :
1) Open the base MSI in ORCA
2) Click Apply Transform and browse to the corrupt transform
3) Click Generate Transform and supply a new name for the transform
4) Close Down ORCA, rename the original corrupt transform to Corrupt.MST and rename the one you generated to the original name
That's it ! In my own case a 140KB corrupt transform was reduced to 120KB after being regenerated.
Just thought I'd share this experience with the community [:)]
Spartacus
0 Comments
[ + ] Show comments
Answers (0)
Please log in to answer
Be the first to answer this question
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
