Quantcast
Viewing all articles
Browse latest Browse all 3196

Installation Issue, SAP BusinessObjects Dashboards 4.1 SP01

Folks,

 

I'm an installation packager for a large financial organization, and I'm responsible for setting up 3rd party products so that they can be silently and smoothly installed on user's desktop workstations with minimal fuss, using BMC Marimba as the deployment tool.  Right now I'm struggling a bit with SAP BusinessObjects Dashboards 4.1 SP01.

 

The problem is with the SAP installer deciding the Product Key is invalid.  This is what's happened so far:

 

The installer was first run in "record" mode, which created a response file.  The deployment was then set up to the installer with the "-r" switch pointing to the recorded response file. The first problem was that the record mode does not record the license key, so I had to added that to the response file via a manual edit.

 

Manually installing with the corrected response file led to another meessage about the Environment Variable  R_SHLIB_LIBRARY_PATH pointing to old binaries.  This was slightly misleading as the EnvVar was not defined at all.  Research led to the following item in the Release Notes:

 

Message stating that "The Product keycode is not valid." appears after providing a valid keycode ADAPT01640957

 

The article instructed setting the EnvVar to point to C:\Program Files (x86)\SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\ (this is for Win7-64).  So, the deployment was modified to set the EnvVar, but, of course, the process running the install does not see such a change until the next reboot.  So, the deployment was broken into 2 parts - the first part sets the EnvVar (System) as instructed, and then Reboots the target machine.  The second part runs following the reboot.  However, even then, the silent install fails - the log indicates the product key was found to be invalid (see line 1450 in the attached log file).

 

What's mystifying is that if I manually run the install with the same response file (and thus the same product key), immediately following the above failure, the product installs just fine.  This demonstrates that the product key is indeed valid. And it can be demonstrated that the EnvVar is properly set.

 

I'm out of ideas.  Any suggestions?

 

Regards,

TSMayham


Viewing all articles
Browse latest Browse all 3196

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>