polardetective

The first step is installation! There have been several queries and issues that come up during and post installation for SAP BusinessObjects XI 3.1 / BI 4.0 / BI4.1. On several occurrences it has been observed that solving the installation issues involved steps that should have been performed prior to the installation. Here are my two cents on the necessary prerequisites for installation of the tool that I’ve come across while handling installation issues.

This is applicable for both Server installations or Client tool installations. Also, this is applicable for fresh installations as well as support pack/fix pack installations. The basic principle behind these configurations is that the installer should experience no hindrance while placing the files onto the server/machine. The roadblocks in question can occur from the operating system.

SAP Business Object 4. Installation Video. Installing SAP Bo with BI 4.0 Trial version. Download Part 5 Client Tools. START the installation. Hi EveryoneHave installed BOE 4.0 server platform on a virtual machine running Windows Server 2008 R2. Now trying to install the Client tools. I execute the startup. 2029788 - Can you install SAP BusinessObjects Business Intelligence 4.0, 4.1 or 4.2 client tools as side by side on the same machine?

The security measures, intrusion prevention tools (such as Firewalls and Antivirus) and the network security tools are responsible for blocking/prohibiting certain executable to run or files to be placed at their intended locations. COMPATIBILITY To start with, the hardware and software configuration of the server or client machine that we’re installing SAP BusinessObjects on must be supported. SAP provides a supported platforms guide or “Product Availability Matrix” (PAM) for several products. These can be found at the following URL: You can also refer the following KBA: Here is an example of a page from the PAM document which shows the hardware requirements. The product version is also included in the screenshot. Click on the screenshots to see a larger & clear image. Source: SAP Once the environment on which the installation will be performed is supported and compatible, we move on to the Windows specific configurations.

OS CONFIGURATION Below are the configurations, if set correctly will not cause any files to not be placed on the server during installation. • User privileges • Data Execution Prevention (DEP). • User Account Control (UAC). • Firewall/Antivirus Let’s tackle each one by one.

User privileges: The OS user installing the software needs to have complete LOCAL ADMINISTRATIVE rights. As a part of administrator’s group the user must also have the following security settings enabled: • Act as a part of the Operating System.

• Allow log on locally. • Logon as a service It has been observed that setting the above incorrectly causes issues with certain server executions post-installation.

It is also necessary that the user installing the product must have full control over the following locations: • Installation media. • Installation location.

• “temp” locations • Any other directory levels that may be involved (custom Filestore location, etc.). Asp To Exe. The rights must be full locally, as well as over a domain if we are installing a distributed configuration.

Data Execution Prevention (DEP): Microsoft Windows has an in-built setting which is used to set rules on how the system executes certain programs, features, etc. While installing BusinessObjects, we usually set this option to allow minimum Windows Server 2003: • Start ->Right-click on My Computer ->Properties.

• Click on the “Advanced” tab. • Select “Settings” under “Performance” category. • Click on the Data Execution Prevention tab and select the first option: “Turn on DEP for essential Windows programs and services only”. Click on the screenshots to see a larger & clear image. Windows Server 2008: • Start ->Right-click on My Computer ->Properties. • Advanced System Settings. • Click on the “Advanced” tab.