Proj Pro 2k3 MSI MST issue...
Why cant all repackaging/applying MST's be simple?
Im now trying to apply a transform to MS Porj Pro 2k3...when I use WPS6 Workbench/Proj to create a transform...it bonks out after putting in the serial number. A dialogue comes up and states that it completed successfully, creating an MST and shortcut, however neither are created.
Now the rub. I create a MST manually...I go into my Setup Editor, the Product => Properties to input the serial under the property ProductID...save and compile my transform, create the shortcut manually, then run it. The install starts then craps out saying that the key is incorrect.
Am I inputing the key incorrectly, I just put it in as one long string...assuming that no other characters are needed (minus spaces obv).
AB1D1 2GHIJ K3M4O P5R67 UVXYZ
Also note there is a PIDTemplate of the following, note that the last the tilde in the last octet has 6 spaces as opposed to 5.
72077<````=````=````=````=`````>@@@@@
Any help is appreciated.
Im now trying to apply a transform to MS Porj Pro 2k3...when I use WPS6 Workbench/Proj to create a transform...it bonks out after putting in the serial number. A dialogue comes up and states that it completed successfully, creating an MST and shortcut, however neither are created.
Now the rub. I create a MST manually...I go into my Setup Editor, the Product => Properties to input the serial under the property ProductID...save and compile my transform, create the shortcut manually, then run it. The install starts then craps out saying that the key is incorrect.
Am I inputing the key incorrectly, I just put it in as one long string...assuming that no other characters are needed (minus spaces obv).
AB1D1 2GHIJ K3M4O P5R67 UVXYZ
Also note there is a PIDTemplate of the following, note that the last the tilde in the last octet has 6 spaces as opposed to 5.
72077<````=````=````=````=`````>@@@@@
Any help is appreciated.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
gmorgan618
17 years ago
Normally Serial's / CD Keys for M$ products have no delimiters ... so if the key is A7877-FDSCA, you would input A7877FDSCA
Log a manual installation and then search for the first 5 characters of the cd Key -- this will tell you if the property you are setting is correct and the format that should be used...
Good luck
Log a manual installation and then search for the first 5 characters of the cd Key -- this will tell you if the property you are setting is correct and the format that should be used...
Good luck
Posted by:
sizemore
17 years ago
Well I am not using the spaces, it's one long string, again without spaces. The PIDTemplate doesnt look right to me the last octet has allowance for 6 spaces. Even after editting the PIDTemplate it will still error out.
If I try to Debug via WPS, Debugger.exe crashes with error: Get Info: Incorrect Data Type.
What I ended up doing was use ORK to create the MST (which cannot be editted by WSP (newb info [:)])) then just threw in the keys that I needed to make the appropriate end results.
If I try to Debug via WPS, Debugger.exe crashes with error: Get Info: Incorrect Data Type.
What I ended up doing was use ORK to create the MST (which cannot be editted by WSP (newb info [:)])) then just threw in the keys that I needed to make the appropriate end results.
Posted by:
rpfenninger
17 years ago
Could it be that you need another tool?
I'd recommend to use the Microsoft Office 2003 Resource Kit to create a MST file for Office applications.
Download it here.
Hope this helps
Cheers
I'd recommend to use the Microsoft Office 2003 Resource Kit to create a MST file for Office applications.
Download it here.
Hope this helps
Cheers
Posted by:
sizemore
17 years ago
Roger that RPF, that's what I ended up doing for this project, so much quicker and cleaner using ORK as well.
Thanks for looking out.
Thanks for looking out.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.