Crystal Reports XI - Incorrect Product Code

Hey All,

I was wondering if someone would be able to help me. I am attempting to packaging Crystal Reports XI to deploy through group policy. I have got the transform to a stage where the .msi will open, etc but when it gets the stage of the product key, it says its invalid, even tho if i run the installer through setup.exe the code is accepted. I am wondering if there is some special formating needed for the PIDKEY property in the transform. Any help would be greatly appreciated.



I have followed instructions in the post http://itninja.com/question/install-string-for-crystal-reports-xi

0 Comments   [ + ] Show comments

Answers (3)

Posted by: aogilmor 13 years ago
9th Degree Black Belt
that is a problem with a lot of setup.exe installations I've seen. If there's a way to log the setup.exe installation you could look in the log and see what the PIDKEY property is set to. Does the vendor have a silent switch for setup.exe or any resources you can use?
Posted by: nheim 13 years ago
10th Degree Black Belt
Hi Dan,
install the app with the setup.exe, but switch on MSI logging and have a look in the logfile. Search for the command line. Most likely, you find the calling options you need to execute the MSI without the launcher.
Hope this gives you some ideas.
Regards, Nick
Posted by: SpriteAM 13 years ago
Senior Yellow Belt
I had a similar problem when I tried getting a transform going. Ended up resolving it by making sure the propery name for PIDKEY was in all caps.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


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