Business Objects installation notes

From Provider Wiki

Jump to: navigation, search

In July 2007, ISC will begin to roll out the new version of Business Objects – Business Objects Enterprise XI release 2 sp2 (“XIR2”). This is a major upgrade, and while we do not anticipate that it will require re-training users, there are significant differences that local support providers need to know about. See http://www.upenn.edu/computing/da/bo/busobjupgrade/ for more information.



Contents

The following instructions will allow the target use to create and modify the key w/o needing administrative access

The Fun instructions for BO 5.14 users:

Tweak registry for LocalMachine|Software

  • Run: regedt32 (2k) or regedit (XP)
  • click on HKEY_Local_Machine|Software
  • (2k) Select the Security menu, choose Permissions

or (XP) Edit menu|Permissions

  • click Advanced, select the {<sid>} user in the list
E.g. S-1-5-21-1779672970-1582333133-359561344-1008
  • Click View/Edit
  • For the "Apply Onto" drop-down list, Check that it has: “This Key only”
  • For imaged Allocations computers, the correct permissions should be set, so you can probably leave them alone.
  • They should be: the only Permissions checked are:
Allow column: Query Value & Set Value & Create Subkey
  • Click on the “Change” button to the right of the Name field
  • In the "Look in" (or "From this Location") drop-down list, select the Local machine (i.e. instead of sas.upenn.edu)
  • Scroll down to the local group “BusObjAccess” (or BusObj-Access)
  • Select “BusObjAccess” and click ok, ok, ok, ok, ok, ok.
  • Close regedt32/regedit

Add the user's login (probably their domain self, else their local account) to the local group “BusObjAccess”

  • Right click on My Computer, choose Manage
  • Open "Local Users and Groups" and select Groups
  • Open “BusObjAccess” and click Add
  • If others in their office will use BO 5.14 at their computer, add their accounts too.
  • create a Business Objects icon on the user's desktop. The path is:
C:\Program Files\Business Objects\BusinessObjects 5.0\busobj.exe

(first check if there is Business Objects 5.1 on the Program menu)

Have user login as themselves (restricted user) to the workstation to test if BO runs ok and lets them login.

They can click through the wizard to the point where they see the Universes that they have access to. If they don't see what they should or used to see, then their username/password may be wrong.


Troubleshooting Notes:

If they get an error about key or lsi files, check the permissions on:

c:\program files\business objects

Make sure that User or Autheticated User has Modify, and that it is inherited to all sub-folders and files.

From Jason Watkins, SAS Computing

Personal tools