SAP BusinessObjects XI 3.1 SP2 – Before You Install…
I came across a recently technical support article that I felt was so important, I wanted to pass it on to anyone and everyone who might be upgrading their SAP BusinessObjects XI 3.1 environment to SP2. If you try the installation, BEWARE! Without following the advice below you might find that it takes several hours! Below are the instructions I gleaned for a recently published technical article.
SP2 Is Slow to Install
Installing XI 3.1 Service Pack 2 on a Windows environment may take a long time (several hours) to complete and here’s why.
- The problem is with the process of the MSP (Microsoft Patch) installer that we are using for the SP2 install on Windows platform.
- The install/validate check routine in this process takes approximately around 80% of the install time.
- When using this installer the process to find and replace a large amount of files takes a long time.
Workaround
As the main bottleneck in the Install process is a MSFT Install/Validate check routine, the workaround is to skip the check by performing a Silent Install
There is a significant reduction in the total time taken. NOTE: We can skip the check only on MSI 3.x., the silent install does not help on MSI 4.x. Please refer to the installation guide for xi31_sp2_install_en.pdf and refer to page 21.
Regarding how to run in Silent mode:
- We need to generate an ini file firstly with the command line: setup.exe -w <response filepath>\<filename>.ini
- Next, run the silent install with the command line: setup.exe -r <response filepath>\<filename>.ini where <response filepath> is the path to the .ini file you created created in step 1.
- You then need to run the silent install with the commandline: setup.exe /qn+
This runs the installer with all default options and automatically redeploys the war files to the BOBJ-installed Tomcat
Caution:
Note that because the Install/Validate check routine is skipped in order to improve performance, there is a potential scenario where the machine may run out of resources e.g. lack of disk space, partway through the installation. In such a scenario, the system should be rolled back to where it was before originally, and the appropriate logs will be made (assuming logging was enabled).
Limitation of workaround
There were changes between MSI 3.x and MSI 4.x, such that the MSFT Install/Validate check routine is also always executed in machines with MSI 4.x, regardless of whether it is a GUI or Silent installation. Accordingly, the silent install does not help if the MSI 4.x has been installed on the Windows. Regarding how to know the version of MSI installed on the computer currently, we may right click the file C:\windows\system32\msiexec.exe, choose “Properties”, check tab “Version”, or you can run, from the commandlilne, “msiexec /?” and hit enter. There is no way to downgrade the MSI from 4.x to 3.x except re-installing Windows.
SAP Note 1356691 for the XI 3.1 Service Pack 2 Install and Deployment Guide PDF. The section for Silent Install begins on page 21.
I’ve read reports of it taking up to 18 hours, so several hours is kind of an understatement. Mine took a little less than six hours on my (virtual) test machine. I’m not sure which version of MSI is running on my OS, I’m guessing 4.x, it being Server 2008. In which case my silent install didn’t help to shorten the process.
I’m confused by your step 3 (run setup.exe /qn+). I don’t remember doing this. Isn’t it the case that you either use a response file or run a scripted setup (with the parameters in the command line)?
I was going to do the upgrade for a client this coming Friday, but I’m hesitant now, because their installation has got a limited amount of free disk left and I don’t want it to abort prematurely.
Sandor – Thanks for your comments. If you download the install XI 3.1 SP2 installation manual (located http://bit.ly/XI2lP), the section regarding silent installs, page 103, includes some additional flags you can use. The /qn+ will prompt you when the installation is finished.
I definitely would NOT do the install unless I had plenty of disk space. You don’t want to run out of disk space half way through an install. That would be bad news.
Hopes this helps. Let me know.