Posts Tagged ‘XI 3.1 SP2’

BusinessObjects XI 3.1 SP6 full build available…

March 27th, 2013 14 comments

I was reviewing my SAP Support Portal Newsletter after returning from vacation and discovered that SAP has released SAP BusinessObjects Enterprise XI 3.1 Service Pack 06 – Full Build.  I really wasn’t expecting that — but I was happy to see it.  It sure beats worrying about the correct ‘upgrade path’ to such as the complications associated to moving to SP5.

XI 3.1 SP6 has released on all the standard platforms:  Linux on IA32 32bit,  HPIA_64,  HP-UX on PA-RISC 32bit,  AIX 32 Bit,  Solaris on SPARC 32bit.

Although I’ve been actively using v4.0 for a while, I know that many SAP Analytics customers haven’t yet made the transition to v4.0.

I would definitely like to hear from customers who are still waiting to make the move to find out where the hesitation is.  From what I understand most of the core stability issues have been resolved.

Highlights on XI 3.1 SP6

The big standout I saw was support for Windows Server 2012, which I had been asked about several times and I’m glad to see it’s there.

This release also fixes an outstanding issue with the length of the opendocument URL character limit of 2083 characters, which can be an issue if you are doing a lot of document to document hyperlinking.

If you are interested in additional details around what’s new, you can find that here:

You can also find the PAM document here:

Other Notables for XI 3.1

Know your dates and deadlines.  You need to plan to be off XI 3.1 by the end of 2015 and that’s not very far away.

Release to Customer:09/30/2008
General Availability:09/30/2008
End of Mainstream Maintenance:12/31/2015
End of Priority One Support Phase:12/31/2017

It’s hard to believe it’s been 7 years already!  I’m feeling old.

Are You Getting Notifications?

If you have access to SAP Support, then you should also be taking advantage of regular alert notification emails that you can proactively receive from support.   You can sign up for them here:

You can define exactly what products you want to receive notifications about.

Here is a video tutorial that walks you through it.

Don’t delay.  Sign up today.

«Good BI»

SP5: Can’t Get There From Here

January 24th, 2012 2 comments

Administrators take note!

In case you missed it, the straight-forward upgrade between Service Packs has a little wrinkle that you need to be aware of.

Upgrading to XI 3.1 SP5

If it’s been a while since your last upgrade and you are still running BOE XI 3.1 SP2, you may be surprised to find out that you cannot go from SP2 to SP5 in a single upgrade.  I don’t have the details as to why other than the fact that SAP Note:  1664385 tells us it’s not supported.

Only the following upgrades paths are supported:

  • BOE XI 3.1 + SP3 + SP5
  • BOE XI 3.1 + SP2 + SP3+ SP5
  • BOE XI 3.1 + SP2 + SP4+ SP5
  • BOE XI 3.1 + SP3 + SP4+ SP5

I read through the note and there wasn’t any additional explanation as to why, but you can see for yourself:

Remember:  Always read the release notes.

«Good BI»


Where Are You Coming From?

November 3rd, 2009 7 comments

Have you ever been confused by directions or road signs?  Sometimes information doesn’t bring clarity.  Hopefully this blog will bring some clarify to potential issues you might encounter in your upgrade to SP2.  I can’t believe this is my 4th post about the subject.

Issues When Moving From Fix Pack 1.6+ to SP2

I made the move to SP2 several weeks ago from XI 3.1 FP 1.3, but what I have since discovered is that not everyone’s journey has been so straight forward.  If a BusinessObjects system was using XI 3.1 FP 1.6 or later, then you may run into issues after you upgrade to SP2.

It seems that at the time SP2 was being built, all the fixes up to FP 1.5 were included; however there have been a number of additional FixPack releases SAP BusinessObjects XI 3.1 since then.  SAP has released Fix Pack 1.6, 1.7 and 1.8.  These three releases included DLLs that were newer than the DLLs in the SP2 release because they contained fixes that were not originally in SP2.  If this is the case for you will want to move to Fix Pack 2.1 immediately.

What happened?

What I’ve discovered is that due to the desire to keep the size of Service Packs as small as possible, the service pack does not overwrite all the DLLs on the system.  Instead, the service packs looks at your system and only replaces those DLLs which are older than the DLLs within your BusinessObjects XI 3.1 environment.  This means that if you upgraded to FP 1.6, 1.7 or 1.8, some DLLs will be newer than the DLLs contained within SP2.  This can introduce incompatibilities.

For example, if you use WebIntelligence, you may notice that after sometime the WebIntelligence Server stops functioning and you get the following message when opening a WebIntelligence document:

Cannot Initialize Report Engine server: (Error: RWI 00226) (Error:INF)

The Good News

The Good News is that engineering has already identified this issue and has fixed it through the release of Fix Pack 2.1.  If you read the release notes of Fix Pack 2.1, you will see the following:

BusinessObjects XI 3.1 and Crystal Reports 2008 Service Pack 2 Fixed Issues
This Service Pack can only be applied on top of BusinessObjects
Enterprise XI 3.1 / Crystal Reports 2008 SP1. This Service Pack
includes all XI 3.1 FixPacks up to 1.5. Note If you install XI 3.1
SP2 in top of FixPack 1.6 or later, reinstall the latest 2.x FixPack.
Each machine in your deployment must be updated separately with
the patches you require. A separate patch is available for each
BusinessObjects product that has a standalone installation.

There it is.  Tucked into the release notes of Fix Pack 2.1 it explains that if you are on a later fix pack, you need to install Fix Pack 2.1.  I would welcome your suggestions to pass on to the BusinessObjects engineering team of ways to avoid this in the future.

«Good BI»

XI3.1 SP2 Installation Issues Addressed in Re-Release

October 29th, 2009 No comments

Over the last several months, we’ve worked to make customers aware of one of the major issues with the latest upgrade within the XI 3.1 product stack.  The main issue has been that the upgrade is simply too slow.  Way too slow.  I knew that the SAP BusinessObjects product development team has been working on resolving this issue and we have some great news.


The problem only affects Windows and only the BusinessObjects Enterprise package. The problem arises due to limitations of the Microsoft Patch (msp) technology performing disk checking when managing large numbers of files… and the BusinessObjects Enterprice package has lots of those! When run in silent install mode, the installation is significantly faster, but this advantage only works on some versions of Windows (those using Microsoft Installer 3).

RE-RELEASE is available!

If you have an older copy of the SP2 release on your servers, you may just want to update them.  If you go to Service Marketplace, you will see that there is an updated version of the Service Pack (Server+Client) available for download.  These downloads have been updated.

Click image to enlarge

So was the issue completely fixed?  Well, no… not exactly.   In order to get the installer to run fast in interactive mode, either the installer would have to be modified to use the older msi technology or Microsoft will have to fix the issue.  In the meantime, what SAP BusinessObjects has been able to do is to give us an updated version of the installer that is always fast when run in SILENT MODE…. that is… with all versions of Microsoft Installer (3.0/3.1/4.0/4.5).  Therefore be aware.  You must continue to follow the silent installation procedures outlined in my previous posts, however you no longer have to be concerned with what version of the Microsoft Installer is on the Windows Operating System.

And if you are on Unix?  Well, this was never a problem in that case.  This problem only affects the Windows platform.


Finally, thanks to the teams at SAP BusinessObjects for getting this fix released.

«Good BI»

BusinessObjects XI 3.1 SP2 Upgrade Update

September 19th, 2009 No comments

I wanted to write a quick follow-up post to the one I posted earlier about the BusinessObjects XI 3.1 SP2 install.  Now that I’ve done several I wanted to give you some additional heads up on some things.  This is what I’ve learned:

Be Careful of Language Packs

The install can take a long time even with the silent install – If you decided to just install all the language packs what you will find is that each language packs adds just under 30 minutes to the install time per language.  In other words, if you installed English, German, and French your installation will take almost a full extra hour.  The installation daisy chains the installations together.  First it will all the SP2 updates and the english language pack.  Next, it will install French and then German.


Is My Install Done Yet?

When running a silent install you can include the options /qn+ to have the setup.exe program inform you when the installation is done…

setup.exe /qn+ -r <responsefilepath><filename>.ini

there’s only one surprise.  The installer will information you that the installation is complete.  What it doesn’t tell you is that it will install the language packs next.  Yep that’s right… It’s done but not REALLY done.  But because it’s running a silent install you won’t know it.  This is related to the previous issue.  After the main installation completed, it tells you the installation is complete.  It THEN begins to install each of the languages packs.  If you look in the task manager you will see that msiexec.exe is still running.  Be very careful and make sure those language packs have completed before you start trying to clean up the install files.

Good Luck

The issue of the installation of the BusinessObjects XI 3.1 SP2 was a main topic of our recent GABOUG meeting.  There was a strong recommendation from customers to make sure and install the SP2 hotfix that came out just after the release of SP2.  I haven’t read through the technical notes, but apparently there were problems with some SAP universes getting corrupted.  This hotfix will solve that problem.

«Good BI»