Unable to create response transform

I am working on BusinessObjects XIR2 trying to create the response transforms,it asks fot the setup.exe to run.I tried changing the Condition of BlockUnlocalizedMlbInstall custom action from "ProductLanguage = -1" to "0 And ProductLanguage = -1" in the InstallExecuteSequence and InstallUISequence tables and passing INSTALLSWITCH=Client as a property on cmd line but no luck.It reports the windows installer error - PIDKEY not defined.This application does not require any license.

I'm doing the Client Installation.The PIDtemplate is defined to value = <`````-```````-```````-````> in the MSI.

Is there any specific value that I need to define for PIDKEY to create a response transform?

Expecting an urgent reply since this is a business critical application and to be delivered on time.

0 Comments   [ + ] Show comments

Answers (5)

Posted by: anonymous_9363 15 years ago
Red Belt
This is an object lesson in how NOT to package software. What a mess.

I presume you've read all the entries in the Package KB? http://itninja.com/link/for-those-who-want-to-have-a-customised-netscape-6.x-rollout---here-is-the-client-customization-kit2

You also need to look out for the Custom Action which rewrites EVERY property which you have patiently set in the property table, meaning that the installation run will install exactly NONE of the features. See posts 8 and 10 here http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning2867&mpage=1&key=business%2Cobjectsꝳ

Oh and if you're using Wise Package Studio, it is almost certain that at some point it will choke on the BO MSI. Sometimes, it might gracefully complain that there are more than 80 (I think) entries in the Media table but, more usually, it will simply exit. No error message, no log, nothing. Superb...

Lastly, this is the wrong forum for your post. This forum is for errors returned by the Windows Installer engine e.g. 1603, 1911, 1720 and so on. It should be in 'Package Development'.
Posted by: sandyran 15 years ago
Senior Yellow Belt

I tried using both these threads earlier and now disabling those CA's,but still no luck!!!

I read for PIDKEY that - The PIDKEY property contains the part of the Product ID entered by the user. The ValidateProductID action validates the Product ID entered by comparing the PIDKEY property to the PIDTemplate property.

It appears to me that the PIDKEY is generated at the time of installation but the setup log file doesn't says anything about this property.The ProductID is defined to value "notnone" in the property table of the MSI.

Let me know if you want me to try out anything else.
Posted by: anonymous_9363 15 years ago
Red Belt
Forget PIDKEY. The BO MSI doesn't use it for any real purpose, as the product has its own licensing. I have NO idea why it's included in their MSI: laziness, I suppose.

If all else fails, try a bunch of your own property-setting CAs but schedule them after the ones which the brain-dead Seagate packager put in (which he then proudly overrides with the one which resets ALL of them...LOL). Maybe the name of that has changed in your release? I have seen one which uses the same name as the one I did, but with a 'bo' prefix!
Posted by: turbokitty 15 years ago
6th Degree Black Belt
As an aside, I used to work at Business Objects and their MSI guy has no idea what he's doing. I offered to help, but was refused. [:)]
Posted by: anonymous_9363 15 years ago
Red Belt
As an aside, I used to work at Business Objects and their MSI guy has no idea what he's doing. "Can't we get you on Mastermind, Sybil? 'Sybil Fawlty, specialist subject, The Bleedin' Obvious'" LOL
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ