Search This Blog


Tuesday, November 18, 2014

BO XI R 3.1 - Changing Business Objects Server Hostname

If you need to change the hostname of BOE XI 3.1 server machine follow these steps

1.     Disable all job servers so schedules are protected until you are confident your changes have been executed correctly.
2.     Change the machine name. Restart the server and 3.0 backend is solid and working.
3.     Reconfigure the application servers. Stand alone or not, these may need to be reconfigured:
a. Java based (Tomcat, Jboss, etc):
- Make a copy and then edit the WEB.XML files which in Tomcat are under the following directories:
1. /webapps/CmcApp/WEB-INF
2. /webapps/InfoViewApp/WEB-INF
- Edit each of the Web.xml files with a text editor
Navigate to the context-param key. Edit to read as follows:
b. .NET based (IIS)
- Create a copy and then edit the WEB.CONFIG files which are in the following directories:
1. \BusinessObjects Enterprise 12.0\WebContent\InfoViewApp\CmcApp\
2. \BusinessObjects Enterprise 12.0\WebContent\InfoViewApp\InfoViewApp\
Navigate to the context-param key. Edit to read as follows:
4.     Reconfigure the web.xml files if you have added any cluster and cluster member information in them or other references to the old server name
5.     Reconfigure the shortcuts created by the install: delete the old shortcuts and create new ones using the new URL
6.     Node names: if you have performed a default installation, the install creates a node with the name of the server in the format .
You can keep the old naming without affecting the functionality of the Business Objects Enterprise Installation but if you want to rename the nodes for more clarity:
- log on to the CMC, navigate to Servers select Properties and rename it
- create a new node, add it to the cluster, then delete the old one
7.     SIA node: it is not possible to change the SIA node name, you should create a new one and then create a new set of servers associated to the new SIA, once all tests confirm that the Business Objects deployment is fully functional you can delete the old one
8.     Ensure the File Repository Servers are still referencing the correct location for the file store root directory
CMC > Servers
They may still be using local location defined by default variables or they may have changed.
Confirm they are still configured correctly.
9.     Database reporting: If there is a database on this server and you have created any machine name specific references to it for db reporting, these will need to be re-configured as well. Such configurations will not affect our application specifically but it will affect our application's ability to service your user requests.
10.     Change the default URL ("SI_VIEWER_URL") if you need to email the report to the users. Refer to the SAP Note 1259126 for the details.

Refer also to:

Please note that changing just IP Address should NOT have  any impact on the system.

Monday, May 26, 2014

Desktop Compatibility Pack (DCP) with SAP BI Platform 4.1 SP1

Desktop Compatibility Pack (DCP) 

The “Desktop Intelligence Compatibility Pack” has been delivered in Fix Pack (FP) 6.1 which is to be installed over Desktop Intelligence XI 3.1 SP6 desktop product. 
When installed, it  allows the Desktop Intelligence reports, users, universes and database connections to be managed by the BI 4.1 platform. 

The goal is to allow Desktop Intelligence users and content to move to BI 4 as easily as possible.
The Desktop Intelligence Compatibility Pack helps in scenarios with reports are difficult or costly to convert to Web Intelligence.
Don't bet on "DCP" to keep your Deski documents alive, this feature is only there to facilitate your migration project and nothing more. We must not forget that a migration project is often associated with a project to convert your Deski (.REP) documents to Webi (WID).

The  steps to follow for installing are the following:
1.       Install SBOP Enterprise Clients 3.1 Service Pack 6
2.       Install SAP BI 4.1 Clients
      Mandatory components to be installed
      Web Intelligence Rich Client
 Report Conversion Tool
3.       Install SBOP Enterprise Client Tools XI 3.1 FixPack 6.1 or later (Please apply the latest SBOP Enterprise Client Tools XI 3.1 FixPack)
1.       XI 3.1 FixPack should be installed AFTER BI 4.1 Client Installation
2.       If you are upgrading from SBOP Enterprise Client Tools XI 3.1 FixPack 6.1 to 6.2, then please refer to SAP NOTE: 1903183

        You can refer to the SAP NOTE: 1896617, for a sample script on how to create a slient installer, this can be customized as per requirements.

Friday, May 16, 2014

Webi 4.0 Error: c3_qtds_error_it_505

Error c3_qtds_error_it_505

SAP BO 40 SP 8
Db Oracle 10 i

The problem was that no group had the right at least to view this connection

So in order to solve the error we gave the view right to the specific group

Another solution you can try to solve this problem requires to follow these steps:

Log on to CMC->Universe Connection->Manage->Top level Security
Assign the Data access right in Relational connection
Choose your connection 
Data Access(Owner right)
Use Connection (Owner Right)

Wednesday, March 26, 2014

Soon: troubleshooting with UMT & Promotion Management

Dear readers
soon I will write down for you troubleshooting  with Upgrade Management Tool  and Promotion management
while migrating from XI R3.1 SP 4 to BI 4 sp8.
Best regards

Tuesday, March 4, 2014

CCM Error: Visual C++ Runtime library

CCM  Error : Visual C++ Runtime library

BI 4 SP 8
Windows Server 2008 R2 sp1

On opening the CCM tool from the BO server it crashed more times.

In our case we just restared the Server and this solved the problem.

Wednesday, February 26, 2014

Error:RWI 00226 - Cannot initialize Report Engine Server. (Error:RWI 00226)(Error:INF)

 Cannot initialize Report Engine Server. (Error:RWI 00226) (Error:INF)

Environment BO XI R3.1 SP 4
Windows Server 2008 R2  sp1 

While rescheduling a Webi report one of our users experienced the error in exam.

In our case we just restared WebIntelligence group servers:

Wednesday, February 19, 2014

HTTP Status 500 - BI Launchpad URL after moving BI 4 server under Windows Domain

After moving the server under Win Domain
both cmc and bi launchpad url erased the following error:


SAP BI 4.0 SP 8
Microsoft Windows Server 2008 R2

HTTP Status 500 -

type Exception report
description The server encountered an internal error () that prevented it from fulfilling this request.

note The full stack trace of the root cause is available in the Apache Tomcat/6.0.35 logs.

The problem was caused by the user wich started SIA wich was Windows Domain user that was administrator of the machine, we have to change the user that started the SIA that is BO Administrator