Is anybody able to install BO XI R3.1 SP2 op their PC ? I cannot install it. My PC runs on XP SP2.
RikDeclercq 
(BOB member since 2006-09-28)
Are you getting an error?
Jay Riddle 
(BOB member since 2008-12-03)
Hi Jay, first you should install SP3 for XP for the best result. Then adjust the registry according to the steps listed here by MS:
http://support.microsoft.com/kb/925336
Here are a few of the steps:
Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers
Note Before you modify this key, we recommend that you back up this key. To do this, right-click CodeIdentifiers, and then click Export. Save the file to a location where you can find it on the computer.
Change the PolicyScope registry value. To do this, double-click PolicyScope, and then change the setting from 0 to 1.
Close Registry Editor.
After the install adjust your Tomcat settings to the following:
-XX:MaxPermSize=180M
That sould get you started.
daiban (BOB member since 2008-08-31)
But does this mean that BO XI3.1 is not supported for SP2 ? 
RikDeclercq 
(BOB member since 2006-09-28)
Which BOE components are you trying to install anyway?
The BOE server components require a Server OS (such as MS Windows Server 2008, etc. and not Windows XP nor Windows Vista).
And again as someone asked previously already: What kind of error are you getting during install?
Andreas 
(BOB member since 2002-06-20)
Mmm, now I see there is no SP2 available for Windows XP (I probably downloaded the sofware for Windows Server on IA32 32bit). Maybe you don’t need to upgrade the client tools ? My BO clients are on XI R3.1 FP1.8. I’ll check it out but extra info is appreciated.
“BOBJ ENTERPRISE XI 3.1
AIX 32bit
HP-UX on IA64 64bit
HP-UX on PA-RISC 32bit
Linux on IA32 32bit
Solaris on SPARC 32bit
Windows Server on IA32 32bit”
RikDeclercq (BOB member since 2006-09-28)
Rik,
Those are server OS specifications
Rik - the client tools should ALWAYS be on the same SP/FP release as the server side. Perhaps you’re running the server + client tools installation as opposed to the Client Tools only install?
Jay Riddle (BOB member since 2008-12-03)
This is what I do. I surf to the SAP BO portal and go to Help & Support => SAP BusinessObjects Support => Support packages: service packs, fix packs, merge modules => SBOP ENTERPRISE => BOBJ ENTERPRISE XI 3.1 => BOBJ ENTERPRISE XI 3.1 . I then get the window with only Server Operating System. I normally choose Windows Server on IA32 32bit. What am I doing wrong ?
P19-20 of the BusinessObjects XI R3.1 SP2 Update Installation and Deployment Guide:
To install client update packages on Windows
This procedure is used to install update packages that affect the
BusinessObjects Enterprise client applications. This includes the following
packages:
• Live Office XI
• Crystal Reports 2008
• Mobile XI
• BI Widgets XI
• Web Intelligence Rich Client
RikDeclercq (BOB member since 2006-09-28)
Right, assuming you already have the client tools for XI 3.1 installed on XP, you then select:
ENTRPRSECLNTTLS02_0-10007443.EXE BOE XI 3.1 ServicePack 2 (Client Tools) 0 Info 662577 23.07.2009
When you run that package on top of XI 3.1 Client Tools, are you getting an error?
Jay Riddle (BOB member since 2008-12-03)
If I double-click on setup.ex, I get the following error:
BusinessObjects XI 3.0 Setup
The install has detected that a recommended Microsoft patch is not present on this machine. If you continue, the following error message might be displayed: “Error 1718. Fome was rejected by digital signature policy”. To prevent any error messages during installation, please refer to Micorsoft kbase article ID: 925336.
RikDeclercq (BOB member since 2006-09-28)
This is a common error related to large installs using MSIEXEC. I get this error all the time at client sites using Windows Server 2003. However, for XP I believe you need to go to the below page, scroll down to the “Workarounds” section, and follow those instructions:
http://support.microsoft.com/kb/925336
Jay Riddle (BOB member since 2008-12-03)
I also found this. I’m about to try it.
RikDeclercq (BOB member since 2006-09-28)
guys. I’ve also got a similar problem. I download the client tools update, sp2, but when I try to run this (after doing the windows fix) I get an error stating that the update is for boxi 3.1 sp1? then it closes. I have tried downloading again and re running, but get the same error?
any ideas?
J King (BOB member since 2008-07-16)
- Did you follow the instructions of the Microsoft kb ?
- I noticed the following : when doing several installs en uninstalls sometimes an installation fails due to version problems. A solution is to uninstall everything and to start again
RikDeclercq (BOB member since 2006-09-28)
It worked for me, Thanks a ton.
Adious (BOB member since 2009-10-06)
Can anyone confirm that the R3.1 Sp2 client tools is still available for download? I cannot find it anywhere. Searching on the object turns up zilch.
EDIT: OK, found it.
bregent (BOB member since 2004-02-06)
I can confirm. Support Packs are in a different sub-section of the bosap-downloads area. Install 3.1 then get SP2 from the SP/FP area.
Jay Riddle (BOB member since 2008-12-03)
Back to the point earlier about client machine needing SP3… I’m not sure if this is my issue or not. Here’s what’s happening - the base 3.1 client tools install went fine, and I’ve confirmed I can log in to Deski. The 3.1 SP2 intall appears to run happy enough, but then gets to what seems to be the end, with just a little bit of room left in the progress bar, and just sits. I finally killed it earlier, but that really messed things up. Any ideas?
thanks.
Amy Miller (BOB member since 2002-06-07)
That last bit takes a reaaaaally long time. It took over a hour on one machine. I noticed that the disk was severely fragmented so I defragged, uninstalled BO, and then resintalled again. It was significantly faster, but still slower than I would like. It still hangs on that last section for a good 15 minutes.
bregent (BOB member since 2004-02-06)