Business Objects 5.1.9 - WebIntelligence 2.7.5 Windows Readme Me

Copyright  Business Objects 2004. All rights reserved. 

Contents

  * BusinessObjects
  * Designer
  * Supervisor
  * BusinessQuery
  * OLAP Essbase Access Pack 
  * OLAP Express Access Pack
  * IBM DB2 OLAP Access Pack
  * BusinessObjects OLAP Connect
  * Broadcast Agent
  * Installer
  * Connectivities
  * BusinessQuery SDK
  * InfoView/WebIntelligence
  * WebIntelligence for OLAP Data Sources
  * International
  * Business Objects 5.1.9 / WebIntelligence 2.7.5

Adobe Acrobat Reader is no longer available for installation on volume 2 of the
Product CD.
You can download Acrobat Reader for free at the Adobe web site: 
http://www.adobe.com.

Please note that the graphics library has changed in Service Pack 6.  As a 
result, the appearance of graphs has changed. For more information, refer to 
the WebIntelligence portion of the Readme or contact your regional technical 
support.

------------------------------------------------------------------------
BusinessObjects
 
General Information
Known Issues 
Limitations  
Zero Admin BusinessObjects
------------------------------------------------------------------------

General Information

Deactivated enhancement  

  *	In BusinessObjects 5.1.8, a new enhancement was implemented which 
  	caused some performance issues when refreshing a BusinessObjects
  	document that had over 10000 rows. It had been setup to avoid using 
  	100% of CPU usage. This fix has now been deactivated in BusinessObjects 
  	5.1.9. 
	If you want to reactivate this enhancement, you must modify your Windows 
	registry. To do so:
	1. Click Start and click Run. 
	2. Type regedit and click OK. 
	3. Move to the following key: \HKEY_LOCAL_MACHINE\SOFTWARE\
	Business Objects\BusinessObjects\5.0\BusObj Configuration\BusinessReporter\ 
	4. Click the DWORD Value command of the Edit menu and enter 
	YieldInMilliseconds. 
	5. Double-click your newly created DWORD value and enter a value in the 
	Value data box. The possible values are from 0 to 30 with 0 equal 100% CPU 
	usage. 
	6. Exit the Registry Editor and restart your computer. 
	
Issue related to the fix implemented for bug #1061399

  *	Bug 1061399 was partially fixed on Service Pack 9. Tables do no overlap; 
  	however, the format is not applied from the second page onwards. Instead 
  	of overlapping, tables are joined. This issue has been fixed on the 6.x 
  	versions of BusinessObjects.
  	
Issue related to the fix implemented for bug #1069891

  *	Bug 1069891 was partially fixed on Service Pack 9. If you have a 
  	BusinessObjects report with a section and you activate the Hide Section 
  	Header option for the section and Hide Block option for the table, the 
  	section name is not hidden when the formula to hide the section and table 
  	are identical. 
	This feature works fine with BusinessObjects 6.x. 

Issue related to the fix implemented for bug #1080953

  *	Bug 1080953 was partially fixed on Service Pack 9. If you create a 
  	BusinessObjects report that contains a text cell with over 35 lines and 
  	it just happens that the table exceeds the current page, the table header 
  	will appear on one page while the body on the following page. 
	
Known Issues 

Printing  

  *	When the installed printer drivers do not differentiate colors, 
	Reporter shades the color differences to lessen the impact and 
	improve the quality of the print job. 

Using Breaks in BusinessObjects with an InfoView license 

  *	When running BusinessObjects with only an InfoView license, you 
  	cannot apply the "Breaks" setting to cells. 

BusinessObjects Reporter with MDAC 2.5 Service Pack 1 

  *	An "Out of Memory Error" occurs if you use BusinessObjects Report 
	with MDAC 2.5 SP1.
  	Workaround: Install Windows 2000 Service Pack 2 or do not install 
	MDAC 2.5 Service Pack 1 (2.51.5303.5) if you are on Windows NT4. 
	
Installing Business Objects

  *	When installing Business Objects on Windows 2000, if you have user 
	rights only, the Business Objects shortcut is not created (Start\
	Programs\BusinessObjects 5.1). You must launch Business Objects 
	through Windows Explorer. 

Downloading 3-tier BusinessObjects with Windows NT and Netscape 7.0
  	
  *	The 3-tier BusinessObjects download does not work when performed on 
	Windows NT using Netscape 7.0. An error message is returned from the 
	plugin finder page indicating that the plugin is not found. 

3-tier BusinessObjects in offline mode 

  *	An InfoView user to whom the supervisor has not granted the right to 
	log in to full-client applications in offline mode will not be able 
	to launch BusinessObjects from the portal (3-tier BusinessObjects) to 
	edit BusinessObjects documents. 3-tier BusinessObjects should be 
	launched from the Start bar to edit documents in offline mode. 

Contextual help button 

  *	In 5.1 BusinessObjects modules, if you click on the contextual help 
  	button and then on a common toolbar icon (such as Query Panel or Data 
  	Provider) a generic help window appears instead of the description of 
  	the selected feature. 

Data Providers 

Queries and Universes

  *	Due to updates in BusinessObjects version 5.1.x, the group by clause 
	in the SQL is not generated in the same way as in previous versions. 
	BusinessObjects now refers to the select statement of an object 
	instead of the qualification (dimension, attribute, measure) of an 
	object. 
  *	If you use a measure with 'none' as an aggregate function (in the 
	object's definition in the Designer) in a block containing data from 
	different data providers, you may encounter problems displaying all 
	the values of the measure.
  	If the object is an ID you should qualify it as a dimension instead 
	of a measure in Designer.
  	Otherwise you can do the following: Set an alternative Aggregate 
	Function for this measure in Designer (Sum, Count, Average, Minimum, 
	or Maximum) or use a UserFormula in BusinessObjects (UserFormula = 
	<Measure>; by default a UserFormula has an aggregate function Sum). 
	Then use the feature Avoid duplicate rows aggregation in the 
	BusinessObjects report. If some values are still not displayed, use 
	the function Multicube to display them (=Multicube(<Revenue>) instead 
	of =<Revenue>)." 
  *	When using ranking in a block that has multiple data providers, if you 
	include a sum, the value returned may be incorrect. To avoid this 
	problem, you should use the Multicube() function instead of the Sum() 
	function. 
  *	A Multicube with a mono data provider is not supported in free-hand
	SQL.
  *	When you open or create a query on a derived universe, the procedure 
	depends on whether or not you have been granted rights for Real-time 
	refresh by the BusinessObjects Supervisor.
	If you are a Real-time refresh granted user, each time you create or 
	edit a query on a derived universe that has been exported, the base 
	universe is refreshed if necessary. This will require a connection to 
	the universe domain each time the query is edited.
	If you are not a Real-time refresh granted user, the first time in a 
	session that you create or edit a query on the derived universe, the 
	base universe will be imported if necessary. But if this base universe 
	is re-exported later during the same session of BusinessObjects, it 
	will not be re-imported. You must force import; for example, by 
	selecting the Tools/Universes/Refresh command.
  *	When you create or edit and then run a query, or when you refresh it 
	from the Data Manager (including automatic refresh) and press the 
	Escape key to interrupt the process, the "Discard the results" option 
	which used to appear in the "Interrupted Execution" dialog box is now 
	dimmed. If you interrupted the query and still want to discard the 	
	results, we advise you to select the "Stop the execution and keep the 	
	partial results" option and click OK. Then, open the Data Manager, 
	select the relevant query and click on the Purge button. However, note 
	that if you click the View button from the Query Panel to open the Data 
	Manager and then stop the query, the Purge button is also dimmed. The 
	"Discard the results" option is not dimmed when refreshing a query from 
	the Data/Refresh command. 
  *	You can still import a universe with BusinessObjects when the secured 
  	connection linked to this universe has been deleted in the repository. 
	No error message appears to warn you that no connection is associated 
	to the universe and that the universe is still imported but is not 
	usable (the .unv file is 0KB). 
  *	If you use a "Null" result in a decode SQL definition, you cannot apply 
	a format in the report. The format can be correctly applied by using 
	"Null+0". 
  *	The "Values..." button is grayed if you create two queries, each 
	containing a prompt and then change the prompt in the second query and 
	run the first. 
  *	We recommend you do not select blank values in prompts with InList and 
  	NotInList operators. 

Personal Data Files 

  *	4.1 documents containing a data provider based on a dBASE file (.dbf) 
	must be edited so that they can be used properly in version 5.1. For 
	this type of document, the file format is no longer set to dBase but is 
	set to Excel 97. To get the correct format back, select the Data/Edit 
	Data Provider command and in the Personal Data Access dialog box, 
	select the "dBASE Files (*.dbf)" format. 
	Freehand SQL 
  *	If you run a Free Hand SQL statement to create or drop a table on an 	
	Oracle 7.3 or 8.x database, you receive the connection or SQL sentence 
	errors: 
  	ORA-0955 name is already used by an existing object or ORA-00942 table 
	or view does not exist even though the SQL statement has been correctly 
	executed. 

Reports 

Display 

  *	When viewing reports with Netscape, the report fonts, cell size, and 
	space between cells are not correctly displayed. 

Sorts 

  *	For Business Objects products version 5.1/2.7.1, the Sort feature has 
	been updated to comply with ISO standards. This means that some 
	characters for example, spaces, punctuation and symbols, are treated 
	differently. 

Computing Data and Display

  *	Inserting a variance calculation on a local variable or a formula 
	containing running aggregate functions, for example RunningSum, returns 
	a computation error message. 
Calculations 

  *	Business Objects has discovered a few issues that cause BusinessObjects 
  	5.1 to return incorrect results in certain limited circumstances. These 
  	circumstances can occur when reports contain multiple data providers or 
  	cubes, or when they use the NoFilter() function. For additional details 
  	or assistance, contact Online Customer Support or WW Customer Advocacy. 
  *	When you define a formula containing the InList operator as a variable 
	and check the "Evaluate the formula in its context" option, a bracket 
	is sometimes missing from the context definition. This means that when 
	you insert the variable in a block, it returns a #SYNTAX error. To fix 
	this, you need to redefine the context in the Variables dialog box. 
  *	Variables containing other variables which use constants in their 
	formula may return an incorrect result if you change the type of the 
	inner variables. 
  *	When you use the function 'NoFilter', you can get a wrong result if you 
	don't create first the formula in a new variable then apply the 
	'NoFilter' function to this variable. 
Filters 

  *	In a block containing data from several data providers, if you filter 
	on a formula based on dimensions from several data providers, the 
	filter will be correctly applied to the body of the block, but may not 
	be applied to the footer of the block. 
  *	It is recommended that you no longer use filters on measure objects, as 
	they sometimes return incorrect results.
Report Formatting 

  *	When you specify a format for a negative value in the Negative text box 
	on the Number tab of the Cell Format dialog box, you must include the 
	minus symbol (-) before the format. For example, to specify a negative 
	format with three decimal places, you should enter -0.000. 
  *	BusinessObjects will allow you to create a crosstab using incompatible 
  	dimensions. However, if you do this, your crosstab may have an empty 
	axis. If you drill through on crosstabs containing incompatible 
	dimensions, the results obtained will be incorrect. 
  *	BusinessObjects will allow you to create sections which have blocks 
	containing incompatible dimensions. This will give incorrect results. 
  *	With linked tables, if you select the repeat block on every page option 
	on the Table Format dialog box, you should apply this option to all the 
	tables, otherwise the blocks may overlap. 
  *	In reports, a block set to repeat on every page sticks to the header of 
  	another block at the top of each subsequent page.
  	Workaround: Insert an empty cell between two tables sometimes repeats 
	the first block on every page without having the second block attached 
	to it.  
  *	When the display of a block or a cell exceeds 70% of the page layout, 
	the "Repeat on every page" option is not applied; otherwise the blocks 
	will overlap from the second page onwards.
  	Workaround: Do not use the "Repeat on Every Page" option. 
  *	Saving a document as HTML with different types of borders is displayed 
	with one and the same type of border in HTML. 
  *	The Center Value Across Break option has no effect on a long cell, even 
	if this option is activated in the Breaks dialog box. 

Queries 

  *	If you create a combined query that contains three or more queries 
	using the MINUS operator, the results displayed may be incorrect. For 
	example, the combined query query1 MINUS query2 MINUS query3 is 
	processed as query1 MINUS (query2 MINUS query3). 

Ease of Use

  *	In some cases, hourglass management is still incorrect. 

Saving Documents

  *	When saving as a .html file, a report containing a block with spaces 
  	before/after data text, the spaces are not correctly converted into 
	HTML and do not appear when you display your report in an HTML browser. 
  *	When saving a report as a .pdf file the fonts Symbol and Zapfdingbats 
	are not converted if the font style is bold and/or italic. 

OLE Server 

  *	When you resize a report inserted as an OLE object in a client 
	application, the display may not be correct (i.e. the data of the last 
	column may spill outside the table). 

Exchanging Documents 

  *	When importing a document containing the Euro character in its name on 
	a machine, on which the Euro patch has not been installed, you get the 
	message "Import failed" with no further details given. We advise you to 
	avoid using the Euro character in the file name of your documents. 
  *	If you are building reports containing the Euro character, make sure 
	that the fonts used to display the Euro character are installed on all 
	client machines used to view the reports. These fonts should be the 
	same ones installed on the machine used to build the reports. 

Drill Mode 

  *	If you interrupt a query retrieving a new dimension selected in the 
	Drill Through dialog box and  then choose to keep the previous results, 
	the selected dimension is no longer available to drill through on. If 
	you want to make this dimension available again to drill through on, 
	open the Query Panel, click on the Scope of Analysis button and 
	deselect the dimension. 
  *	The arrow icon for the drop-down list on the Drill toolbar is not 
	displayed when a dimension name contains more than 255 characters. 

Send to Users and Categories 

  *	You may encounter problems using categories with WebIntelligence 
	documents when performing a search in BusinessObjects. You may only see 
	the BusinessObjects documents and not the WebIntelligence documents. 
	Miscellaneous
  *	Objects separated by commas are not supported because commas cause a 
  	concatenation. 
  	Workaround: redefine the SQL. 

Limitations

Data Providers

OLE DB support 

  *	BusinessObjects does not support OLE DB under Windows 9x.  As a result, 
	you cannot enter a data source name when using the OLE DB data provider 
	and the drop down list of data sources is also empty. 
  	Since the OLE DB provider uses the Incoming Named Pipe connection 
  	functionality (not supported in the Windows 9x OS) to browse and 
	display SQL servers on the domain, you cannot see the server list under 
	Windows 9x. 

Free-hand SQL 

  *	When you run a script that selects a numeric column, the results are 
  	automatically aggregated. To avoid this, open the Data Manager, qualify 
	the column as a dimension, then run the script again. 

Miscellaneous 

  *	In the Data Manager dialog box, if you click on the Refresh button or 
	if you use the Universe option to run a query on a different universe, 
	you can no longer cancel actions prior to the refresh or the change of 
	universe. 
  *	When opening a Business Objects report, version 4 or version 5, in 
	Business Objects version 5.X you may encounter problems when you use 
	Multicubes with mono Data Providers. 

Personal Data File 

  *	If you cannot create a new data provider using a *.csv file, open the 
	Windows Control Panel, double-click on Regional Settings and set the 
	regional settings to English (United States). 
  *	Exporting data to a text file (i.e. .txt, .csv) may return unexpected 
	results with certain Windows Regional Settings (year format set to 2 
	digits, i.e. 'yy'). To avoid this, set the year format to 4 digits, 
	i.e. 'YYYY' in the Windows Regional Settings before exporting your 
	data. BusinessObjects must be relaunched after this change has been 
	made. 

Reports 

Report Formatting 

  *	Universe designers can apply formats to objects when creating 
	universes. When you add such an object to an existing query, the 
	predefined format is not taken into account when a new column 		
	containing the corresponding data is automatically created in the 
	block. The format applied to the data displayed in the previous column 
	is used instead. To get the predefined format back, open the Slice and 
	Dice Panel and click on the Reset Block(s) command. 
  *	In version 4.1, the break footer separating cells - with shading set to 
	"None" - were always white whatever the block shading. In version 5.1, 
	these cells - with shading set to "None" - are of the same color as the 
	block shading color. This change may affect the look of your reports 
	(.rep and .htm). 
  *	If you predefine objects in a universe, we advise you to set a number 
	format (use "Standard", for example) for the measures contained in this 
	universe. Otherwise, if you build a query containing Country, Month and 
	Revenue, for example, and Month is formatted, Revenue will have the 
	same number format as Month. 

Report Functions 

  *	External functions using Time variables are not supported. You can 
	extract time values from dates. 
  *	Certain functions (like Left(,) or concat) are not supported under 
	Windows 2000 with MDAC 2.6. 

Drag and Drop Behavior 

  *	You cannot insert a variable using drag and drop to the left, right, 
	bottom or top of a free-standing cell containing an OLE object. 
	
Queries 

  *	You cannot run a query if the SQL sentence exceeds the allowed limit of 
	65536 characters. 

Printing 

  *	You cannot use advanced printer driver options with BusinessObjects. 
	You can use only the printer options on the Page Setup dialog box. 
  *	Some PLC printer drivers do not support scaling of documents so 
	changing the scaling factors in the Page Setup dialog box is ignored. 
  *	The hyperlinks are not activated if you have selected the option "Print 
	as Business Objects 4.1". 

Euro Character 

  *	If you want to print several reports containing the Euro character at 
	the same time, you must use the same printer (and the same printer 
	driver). If you use different printers, the Euro character will not be 	
	printed in the second (and subsequent) reports. 
  *	To print a report which contains a Euro symbol on an HP Printer with a 
	PostScript driver, you may have to do the following:  
	Open the Page Setup dialog box and click Printer\Properties\Advanced. 
	Select "True Type Font" in "Graphic" and check the option "Download as 
    	Softfont". 
    	Validate your choice. 

OLE Server

  *	If you want to work with a BusinessObjects report as an OLE object, we 
	suggest that you open a BusinessObjects session just before working 	
	with container documents in order to improve the performance of the OLE 
	server. 
  *	The use of BusinessObjects toolbars when you are in another application 
	using OLE2 is not supported. 
  *	We advise you not to work with large BusinessObjects reports inserted 
	as OLE objects in a Word for Windows document. You might not be able to 
	edit the reports in Word for Windows. 
  *	If your report contains a lot of pages, it may not be entirely inserted 
	as an OLE object in another application. 
	
Automation Object Model 

  *	For more information regarding Automation Object Model, please see the 
	BusinessObjects SDK section in the Developer Suite readme. 

Zero Admin BusinessObjects

Known issues 

  *	When you upgrade your Business Objects servers to Service Pack 7 or
  	greater, you must also upgrade all BusinessObjects 5.1.x clients that 
	connect to those servers. Because the communication between the client 
	and the server was optimized in BusinessObjects 5.1.7, client versions 
	prior to Service Pack 7 cannot communicate with Business Objects 
	servers later than Service Pack 7. 
  	Refer to the Deploying 3-tier BusinessObjects guide for more 
	information. 
  *	The following message may be displayed if the Query Panel has been open 
	for several minutes: "A connection required to refresh this document is 
	unavailable". If this happens, click OK and re-run your query. 

Installing Zero Admin BusinessObjects via an Internet Browser

	If the installation of Zero Admin BusinessObjects via an Internet 
	browser fails, there are no error messages to explain to you what 
	happened. If installation is unsuccessful, please check whether one of 
	the following is at cause: 
  	* The maximum number of WIQT processes on the WebIntelligence server 
	has been exceeded. 
	* There is not enough space on the local hard disk to decompress the 
	Zero Admin BusinessObjects installation package 
	* There was a problem with the connection to the server during 		
	installation. 
	* The server was overloaded because too many users were trying to 	
	download at the same time. 
	* The user who is trying to install Zero Admin BusinessObjects has not 
	been given the correct rights by the Supervisor to use Zero Admin 
	BusinessObjects. Users need rights to BusinessObjects and to 
	WebIntelligence. 
  	* The Zero Admin BusinessObjects installer was unable to install all 
	the required dll files. 

Password and error messages with Zero Admin BusinessObjects 

  *	If you enter the wrong password when you try to log on to Zero Admin 
  	BusinessObjects, you get the error message: "Your login has been 	
	rejected by the server. Your login may be invalid or disabled.". You 
	could get also the error message: "Unknown error returned by Server".
	If you enter the wrong password three times, you will no longer be able 
	to use your login until your Supervisor has reactivated it. If you get 
	these error messages repeatedly while trying to log in, please check 
	with your Supervisor that you have the correct password and that your 
	login has not been disabled. 

Installation constraint 

  *	To install Zero Admin BusinessObjects through the portal, you 
	must be logged in to your Windows NT4 or Windows 2000 machine as a 
	local administrator. 
  *	For Zero Admin BusinessObjects to function correctly, you must copy the 
  	psapi.dl_ file from the installation CD, in VOL1\CoreMS. Copy the 
  	psapi.dl_ to WINNT\System32, then expand the file by running "expand 
  	psapi.DL_ psapi.DLL" at the MSDOS prompt. 

Logging on to Zero Admin BusinessObjects on an Apache Web Server

  *	To logon to Zero Admin BusinessObjects on a WebIntelligence 2.7.1 
	server using an Apache web server configured in DSO (Native) mode, you 
	must ensure that your default login page is apache.html. To verify that 
	this is the default login page, check that the value for the http 
	server DirectoryIndex is apache.html in the Webi26.conf file. For 
	example: 
    	<Directory /share/webi26/Server/WebIntelligence2.5/http-server>
    	DirectoryIndex apache.html
    	Options -Indexes
    	</Directory>

Universes  

  *	Asynchronous connections are not supported. Since asynchronous 	
	connections do not function within Zero Admin BusinessObjects 
	5.1.x, universe connections in asynchronous mode run in synchronous 
	mode. Please note Customer Support does not give any technical support 
	to the asynchronous mode with Zero Admin BusinessObjects 5.1.x 
	at this time. 

Accessing data from personal data files 

  *	The Microsoft DAO components required to access data from personal data 
	files using Zero Admin BusinessObjects are not part of the Zero Admin 
	BusinessObjects install package. However, if these components have 
	already been installed on the client computer (with other Microsoft 
	products), you will be able to access data from personal files. If 	
	these components are not already on the client computer then you will 
	not be able to access data from personal files. BusinessObjects 
	specifically uses DAO version 3.5. 

Help files 

  *	Help files have been lightened to facilitate downloading Zero Admin 
	BusinessObjects. 

Authentication

  *	It is not possible to log in to Zero Admin BusinessObjects, standalone 	
	mode on a W9x client machine, using NTLM authentication mode. 

------------------------------------------------------------------------
Designer
 
Known Issues 
Limitations  
------------------------------------------------------------------------
 
Known Issues

Adding a Character Constant to the Select Statement of an Object

  *	If you add a character constant to the Select statement of an Object, 
	you should join it with the "||" concatenation symbol not the "+" 
	symbol.
	Example: City.city || 'a' 

Universe revision numbering

  *	The revision number of the universe is not counted correctly each time 
	you save or export the universe.

Authentication

  *	In Designer, you cannot have a dynamic DB connection if NT 
	authentication is enabled.

Automation Object Model

  *	For more information regarding Automation Object Model, see the 
	BusinessObjects SDK Readme.

Miscellaneous

  *	When exporting universes that include characters that are not supported 
	by the repository's connectivity, for example the Euro symbol for 
	Sybase connectivity, the connection may be lost. If this occurs, you 
	should close and then restart Designer to recreate the repository 
	connection. 
  *	When you create a measure object, the aggregation function by default 
	for the measure is Sum. If you select None for this function, incorrect 
	results can be returned if an end user is using multiple data 
	providers. If end users will be using multiple data providers to create 
	reports, you should use Sum as the aggregation function. 
  *	Objects separated by commas are no longer supported for concatenation. 
	A formula with two objects separated by a comma does not take into 
	account the second object. You must redefine the SQL. 

Import Universe with ODBC Connection 

  *	When importing a universe with a List of Values, using an ODBC 
	connection, you may receive the following message: Could not retrieve 
	columns of universe tables. The associated universe connection is not 
	valid. It is possible to use the universe correctly, except when using 
	the 'Refresh Structure' function. 

Limitations

	There is no security setting for Automation features distinct from 
	interface settings in the Supervisor module. Access rights to an 
	Automation object are the same as those for the interface 
	items. 

Limit Execution Time Option

  *	The Limit execution time to option on the Controls tab of the Universe 
	Parameters dialog box is not supported for Oracle connectivities. This 
	option limits the duration of the fetch phase of a query. 

Restrictions on Derived Universes

	Deriving a universe is a powerful feature that simplifies the 
	maintenance burden on your universes. However, it is complex and 
	entails certain restrictions: 
	* Contexts are not inherited in a linked universe. 
	* While carrying out a SQL request on tables of the core universe, the 	
	data is retrieved from the database defined by the connection of the 
	linked universe. 
	* In Designer, after changing a source, it is advisable to close the 
	universe then re-open it in order to initialize the components( List of 
	Values,...) 
	* When you "Include" a core universe, a custom list of values for the 
	core universe is not included in the derived universe. The lists of 
	values for the universe, derived from objects of the Core universe, can 
	be affected by an "Include" or a "Change Source" function on the 
	universe core. We recommend that these values are checked after one of 
	these operations. 

Object Names

  *	You should not create two or more objects with similar names, where the 
	only difference in their names is a special character (".", "&", "#", " 
	", "'", ":", "-" "/", "", "(", ")", "{", "}"). For example, two objects 
	called object1&object2 and object1#object2. This will cause problems 
	when the objects are exported to Excel. 

Universe File Names

  *	To avoid naming conflicts in the repository, we recommend that you do 
	not create universes with the same name and using a different case. For 
	instance, you should not create a Beach.unv, and then a beach.unv. The 
	export now controls the uniqueness of the universe name, independently 
	of the case. However, if you have such universes in your repository, 
	Designer prompts you before overwriting (for instance, Beach.unv by 
	beach.unv). 

Importance of Syntax

  *	You can no longer rename a connection after its creation. 
  *	In general, we recommend you avoid certain characters in object names 
	or in class names such as commas, parentheses, less than and greater 
	than symbols. 
  *	When defining external strategies in Storaen.txt for instance, remember 
	that parameter names are also case-sensitive. 
  *	When you use an external strategy, we recommend that you check that no 
	spaces have been inserted in table or column names. An external 
	strategy can support spaces in the Qualifier or Owner column. 
  *	In order to avoid problems with databases on export time, if you enter 
	a long description for an object, we recommend that you use Ctrl+Enter 
	to make a carriage return instead of space characters. 

External strategies

  *	If you use an external object strategy to create an alias, the alias 
	does not correspond to a table in the database. If you try to access 
	the properties (using the Edit Join dialog box) for a join between a 
	table and the alias, an error will be generated. You need to manually 
	create the alias to access the Edit Join dialog box. 

Alias tables

  *	When you create an alias with Designer, the name length limit is 110 
	characters. However, certain RDBMS, for example Informix and DB2 are 
	limited to 18 characters. When you create your universe, you need to 
	use the rules of your RDBMS when naming tables and aliases. 

List of Values

  *	When you customize a list of values, a file with a .lov extension is 
	created in the \UserDocs\UniverseName folder or 
	\UserDocs\RepositoryName\DomainName\UniverseName folder. If you intend 
	to distribute your universe using a floppy disk or the file system, you 
	should ensure that you copy the .lov files with the .unv files. 
  *	LOV queries do not use aggregate-aware functions.  If an @aggregate-
	aware object is defined, the default LOV query is built with the first 
	argument in the @Aggregate_Aware function. 
  *	To display the complete list of values of an object you must select all 
	the values. 
	Workaround: You can display all the list of values for an 
	object by:
  	Typing this formula in the Where clause of the object:
  	Table.Field IN @Prompt('Message (type all for all 
	values)','A','MyClass\MyObject',multi,free) 
	or
  	'all' in @Prompt('Message (type all for all 
	values)','A','MyClass\MyObject',multi,free)
  *	You cannot run a query if the SQL sentence exceeds the allowed limit of 
	65536 characters. 

Miscellaneous 

  *	Custom Format: you have to select a category before you can add a 
	custom format in the Number tab of the new Object Format dialog box in 
	Designer. 
  *	If you have Business Objects Designer installed on the same machine as 
	a WebIntelligence server the customized list of values cannot be taken 
	into account when you launch Zero Admin Business Objects from a client 
	machine.

------------------------------------------------------------------------
Supervisor
 
Known Issues
------------------------------------------------------------------------

Known Issues

User Access 

  *	Important:  Two supervisors should avoid working on a repository at the 
  	same time. If this happens the operations of one supervisor may overwrite 
  	the operations of the other; however, if these supervisors have a strong 
  	knowledge of the repository structure multiple edits shouldn't over-write 
  	or conflict with each other. 

Upgrading a Repository 

  *	When you upgrade a repository from version 4.x to 5.x, you may 
	encounter problems with some user restrictions that have been set in 
	Supervisor. You must reset these restrictions in the upgraded universe. 

Monitoring Broadcast Agent 

  *	Adding Broadcast Agents into the Broadcast Agent Manager:

	When using the Administration tool you may add Broadcast Agent Servers 
	to be monitored within the Broadcast Agent Manager module. When you 
	click on "Monitor one more Broadcast Agent" you may provide a username 
	with a supervisor profile. This allows you to monitor the Broadcast 
	Agent(s) of your group. However, if your group contains subgroups you 
	cannot monitor the Broadcast Agent(s) for the subgroups, even if you 
	created them.
	Workaround: Copy the supervisor into the all of the subgroups. 

Import Users 

  *	This feature allows any Supervisor to quickly import user and group 
	definitions from a text file, modifying or even deleting existing ones. 
	Because this information is so sensitive, you must be careful to use it 
	in the proper way, ensuring that unintentional duplications or 
	overwrites do not occur. To limit access to this feature, the General 
	Supervisor can switch the "Import Users" security command off for the 
	whole company (by disabling it at the root level). This way, only 
	General Supervisors will be able to use it by default and it can still 
	be enabled specifically for selected Supervisors. 
  *	In an import file for batch creation or modification of users and 
	groups and their properties, you might change the name of a user or 
	group. If you refer to the new name of the user or group in another 
	command later in the same import file, it will not work, because the 
	file is read before any changes are made, and the name will therefore 
	not yet have changed; it will not be recognized and an error message 
	will appear. However, you can still use the old user name to manipulate 
	the user. We recommend that you run a separate import file to rename 
	users and groups after other modifications to your user/group 
	configuration. 

Print

  *	When printing information on your repository configuration by means of 
	the Print command on the File menu, results can be inaccurate if a user 
	has multiple instances with different rights to the same universe. The 
	printed result depends on the order of instances shown in the list in 
	the Groups and Profiles tab of the User Properties dialog box:
	- If the instance at the top of the list has access to the universe, 
	the printed results will indicate that the user has access to the 
	universe
	- If the instance at the top of the list does not have access to the 
	universe, the printed results will not indicate that the user has 
	access to the universe
	This is true of all options of the Print command, including Print in 
	Table Format. 

Print Resources by User/Group Definition 

  *	When printing information on the resources in your repository by means 
	of the Print command on the File menu with the Resources by User/Group 
	Definition option, extra blank lines are printed when the Applications 
	customization option is selected. 

Print in Table Format 

  *	When printing information on your repository configuration in table 
	format by means of the Print command on the File menu with the Print in 
	Table Format option, the operation can be very lengthy and consume a 
	very high proportion of memory resources if your repository 
	configuration is highly complex (for example, if there are very many 
	groups, subgroups, and multiple instances). 

Document domain deletion 

  *	When as General Supervisor you delete a document domain using the 
	Repository Management dialog box (called by choosing the Repository 
	command on the Tools menu), the deletion may be incomplete. After 
	deleting the document domain, open the Repository Management dialog box 
	again and click Scan to run a Scan and Repair of the repository to 
	complete the deletion cleanly. 

------------------------------------------------------------------------
BusinessQuery
 
General Information 
Known Issues 
Limitations
------------------------------------------------------------------------
 
General Information

  *	You can have multiple version installations (5.1 or 5.0 and 4.1) of 
	BusinessQuery on the same computer. 
  *	BusinessQuery version 5.1 does not require a Path environment variable. 

Known Issues

General Known Problems

Query

  *	The Supervisor cannot hide BusinessQuery commands. 

BusinessQuery menu with Windows XP

  *	The BusinessQuery menu may not appear with Windows XP. This problem can 
  	occur even if "BusinessQuery 5.1" is selected in the Microsoft Excel 
  	Add-Ins dialog box (Tools > Add-Ins). To correct this problem, you can 
  	execute a Detect and Repair operation in Microsoft Excel by selecting 
  	Help > Detect and Repair, and then restarting Microsoft Excel.

Limitations

BOMain.Key in BusinessQuery 4.1 for Excel 

  *	BQY files created with a bomain.key in BusinessQuery 4.1 or 5.0 can 
	only be opened with BusinessQuery 5.1 if the BusinessQuery 5.1 security 
	domain is named BOMain.key. 
  *	Problems may occur when changing the BusinessQuery add-in (4.1 to 5.0, 
	5.0 to 4.1, 4.1 to 5.1, 5.1 to 4.1, 5.1 to 5.0, 5.0 to 5.1). 
	After adding, removing or changing a BusinessQuery add-in, close Excel 
	and re-open it, then load BusinessQuery. 

Known Problems due to Excel

  *	When you remove a name in an Excel Sheet, Excel does not refresh the 
	list of names, that's why in the Query Panel, when you create a 
	condition using the operand "Select An Excel Name," the name you 
	deleted is always displayed. If you select it and run the query, Excel 
	will crash. 
  *	When you remove a query directly via Excel using the "delete" command, 
	Excel 8.0 becomes unstable. Please use the "Remove" command of 
	QueryDirector to correctly delete queries. 
  *	Once you select File>Exit in Excel, BusinessQuery is unloaded even if 
	you cancel the File>Exit command in Excel. To reload BusinessQuery, you 
	must click on the Load menu item. 
  *	You cannot run a query with Excel if the SQL sentence exceeds the 
	allowed limit of 65536 characters.

------------------------------------------------------------------------
OLAP Essbase Access Pack
 
Installation Issues 
Known Issues
------------------------------------------------------------------------
 
Installation Issues

Configuration Support

  *	For information on configurations currently supported in Business 
	Objects 5.1.9 / WebIntelligence 2.7.5, refer to the Business Objects 
	Product Availability Report Web Site (PAR). 
	The Product Availability Report (PAR) contains detailed up-to-date 
	information on supported: 
	* products and languages 
	* operating systems 
	* web and application servers 
	* connectivities 
	* browsers 
	* printers 

Known Issues

Compatibility with other versions of BusinessObjects 

  *	Using this version, you can open documents created with any 4.x version 
	of BusinessObjects. You may have problems editing and refreshing a 
	document created with a 4.1.3 version without the CSP 31. 

Linking different data providers using a custom sorted dimension 

  *	An application crash might occur in a multiple data provider report if 
	you link the different data providers with a custom sorted dimension 
	(such as the dimension 'Year'). 

Essbase API Related Issues 

  *	If the server does not respond to the connection request, 
	BusinessObjects waits for Essbase client timeout. 
  *	During a drill operation or a loading of the Database Outline, an 
	application crash might occur if the local machine resources are low. 
  *	The Essbase report script command '{DECIMAL 2}' applied to numbers 
	greater than or equal to 1e+198 causes an application crash in 
	esscsln.dll. 
  *	If you have defined a filter with 'None' access on a dimension in the 
	database, the Essbase report script returns the value '#Missing' for 
	this dimension, whereas '#NoAccess' is returned when the Hyperion 
	Essbase Excel Add-In is used. 
  *	If you modified the Dynamic Members definition on your server, the 
	changes will be taken into account in the OLAP Panel only if you put 
	these members in the Grid by drilling or put a level. 

Connection Related Issues

  *	If the server connection is broken during the data fetch phase, the 
	Panel is reset in the OLAP Panel. 
  *	An application crash might occur if you select a server without 
	databases. 

Add/Remove Panel Related Issues 

  *	Before you add (or remove) a member by drag and drop, you must set the 
	focus on the target in the available members tree list. If you do not, 
	the operation is undone. 

Report Related Issues 

Data Provider

  *	The '#OlapAll' reserved value used by BusinessObjects to designate the 
	aggregated value returned from the server does not appear in a report, 
	even though it is available in the Filters dialog box (Filters command, 
	Format menu). However, '#OlapAll' does appear when you export data to 
	other file formats, for example, to Excel. 

Report

  *	If you define an alerter on the time dimension with a condition such as 
	greater than 'Jun,' then the highlighted months are selected on the 
	first alphabetical sort letter. That means Mar, May, Nov, Oct, Sep will 
	be selected. 
  *	When you use a measure-tagged dimension as a filter, the elements of 
	this dimension will appear as columns in the report and not as 
	sections. 
  *	If you want to change the query in a report, reload the OLAP Panel. To 
	be sure to generate a correct report, select the "Display the new data 
	in a new report" option in the Modified Data Provider dialog box. 
  *	Ranking applied on ServerValue( ) returns erroneous values. 
  *	Some variable names are not updated when you change the alias table. 
  *	If you applied filters in the report and change the alias table you're 
	using, you will get an empty report. The filters definitions are not 
	changed (i.e., the filters are applied using the previous values); 
	therefore you need to change the filters definitions. 
  *	Some cells might contain #SYNTAX after you edited a Data Provider or 
	removed dimension elements. 
  *	You are not prompted for the user password when you select the 
	Automatic Refresh option. You'll have to enter this password when the 
	first refresh is done. 
  *	Applying a filter on the ServerValue in the Slice and Dice Panel might 
	not work. To work around this issue, apply the filter via the filter 
	button in the Report toolbar. 
  *	When a report with a table alias name containing parentheses is 
	refreshed, the error message DMA0007 is returned. 

Change Source

  *	An application crash might occur when you try to apply a "Change Source 
	on an OLAP document" whenever you use a version of BusinessObjects 
	without OLAP Essbase access.

------------------------------------------------------------------------
OLAP Express Access Pack
 
Installation Issues
Known Issues  
Limitations 
------------------------------------------------------------------------ 

Installation Issues

Configuration Support

  *	For information on configurations currently supported in Business 
	Objects 5.1.9 / WebIntelligence 2.7.5, refer to the Business Objects 
	Product Availability Report Web Site (PAR). 
	The Product Availability Report (PAR) contains detailed up-to-date 
	information on supported: 
	* products and languages 
	* operating systems 
	* web and application servers 
	* connectivities 
	* browsers 
	* printers 

Known Issues

Compatibility with other versions of BusinessObjects 

  *	Using this version, you can open and work with documents created with 
	any 4.0.x version of BusinessObjects. You cannot edit and refresh a 
	document created with a 4.1.3 version without the CSP 31. 

Databases designed with Oracle OLAP applications

  *	The Express OLAP Access Pack looks for certain dimension properties 
	(see list) to identify the Express tables that define the STANDARD and 
	DEFAULT hierarchies. This is the standard design for Oracle Express 
	databases designed with Oracle Express OLAP tools, such as Oracle 
	Express Administrator. If the Express OLAP Access Pack does not find 
	these properties, it looks for hard-coded tables made from the 
	concatenation of the dimension-id and the names of these properties.
	Databases designed with Oracle OLAP applications such as Oracle 
	Financial Analyzer (OFA)/Oracle Sales Analyzer (OSA) may have different 
	designs that are not supported. 
	The Express DBA must ensure that the tables that the Express OLAP 
	Access Pack looks for exist in the Express database. The list of 
	dimension properties follows:
	"idcode"
	"parentrel"
	"depth"
	"hierdim"
	"leveldim"
	"leveldepth"
	"leveldesc"
	"hierdefault" 

Running Queries in Personal Oracle Express 6.3

	You cannot run queries using Personal Oracle Express 6.3. You need to 
	create a local Oracle Express server. To do this:
	1. Select Oracle Express Server 
	The Select a Connection panel appears.
	2. Enter a connection name, for example 'personal' and click Edit. 
	The Edit Connection to Oracle Express Server dialog box appears.
	3. Select Express Server 6 from the Server version drop-down list.
	4. Select ncalrpc from the Transport drop-down list.
	5. Type the name of the machine on which you installed Personal Express 
	6.3 in the Host text box. Click OK.
	6. Leave the User Name and Password text boxes empty. Click Next.
	7. Select the database you want to access to
	8. Click in the Password text box, but do not enter any text.
	9. Click Finish. 
	You are now connected to Personal Oracle Express 6.3 and can create a 	
	query.

Limitations

Express SNAPI / RSNAPI

  *	If, during a request, Personal Express does not respond, then 
	BusinessObjects will freeze. You will have to stop the application 
	using CTRL+ALT+DEL. 
  *	If during a request, Oracle Express Server does not respond, you will 
	have an infinite loop of general error messages. You will have to stop 
	BusinessObjects using CTRL+ALT+DEL. 
  *	You cannot attach a database on Personal Express if it is already 
	attached by another product (Oracle Express Administrator or Oracle 
	Express Analyzer). 
  *	If BusinessObjects fails during a request on an Oracle Express Server 
	5.0.x (with RPC daemon), then the instance server is not closed. The 
	server administrator has to stop it. 
  *	If a connection between BusinessObjects and an Oracle Express Server 
	5.0.x is already established, BusinessObjects will stop when you try to 
	establish a second connection if the RPC daemon is no longer running. 

Unix

  *	Database names are case-sensitive under Oracle Express Server on UNIX. 
	
OLAP Panel

  *	BusinessObjects does not support Oracle Express number formats. For 
	example, BusinessObjects does not restrict the number of decimal 
	digits, whereas Oracle Express does. 
  *	The format for date and number measures in the Grid and in the report 
	is defined in the Windows Control Panel (Regional Settings). 
  *	BusinessObjects uses the default Oracle Express hierarchy. If it does 
	not exist, use the "STANDARD" hierarchy. 
  *	Characters are translated from OEM to ANSI for Personal Express. For 
	Oracle Express Servers (5 or 6) no translation is made. Therefore, if 
	you need to translate characters for a server you can add in the 
	BO/OraExp/Busobj.ini file the entry for your server: 
	SERVERCHARSET=OEM 
  *	BusinessObjects does not support dimensions with no values. 
  *	BusinessObjects does not support variables defined with zero 
	dimensions. 
  *	BusinessObjects does not support Oracle Express relations. 
  *	Non-visible objects are not displayed in the Database Outline. 
  *	The pop-up menu can take a long time to appear when you click the right 
	mouse button in the Grid. 
  *	It is possible to add a measure in the Grid, even if it is a measure 
	that should not be added; for example a measure whose dimensions have 
	no values or unsupported values. This can occur when there is already a 
	measure in the Grid. 
  *	In some databases created without the Oracle Express Administrator, 
	hierarchies might be flattened and the "Long labels" option might not 	
	work. 
  *	On some Express databases, it is not possible to read the Express Long 
	Name. 

Add/Remove Panel

  *	Before you add (or remove) a member by drag and drop, you must set the 
	focus on the target in the available members tree list. If you do not, 
	the operation is undone. 

Report

Data Provider

  *	BusinessObjects might fail if you generate a very large report, 
	depending on your swap disk size. You can calculate the maximum number 
	of cells you can retrieve: one cell takes an average of 300 bytes. To 
	know the number of cells you are going to retrieve, use the Warn if 
	number of cells exceeds option in the OLAP Panel Option. 
  *	The '#OlapAll' reserved value used by BusinessObjects to designate the 
	aggregated value returned from the server does not appear in a report, 
	even though it is available in the Filters dialog box (Filters command, 
	Format menu). However, '#OlapAll' does appear when you export data to 
	other file formats, for example, to Excel. 
  *	When you edit or refresh an existing OLAP data provider on a database 
	whose outline has been modified or whose tags have been changed, you 
	need to be aware of the following: 
  *	If you define an automatic refresh for a data provider (using the 
	Automatic Refresh available in the Data Manager), do not try to 
	activate the View Data button, the Refresh button or the Edit Data 
	Provider button during the data provider refresh. 
  *	Filters on values that have been modified in the Outline are deleted 
	from the OLAP Panel. 
  *	If the changes to the Outline affect dimensions or measures that were 
	placed in the Grid, the OLAP Panel is unavailable. 

Report

  *	If you define an alerter on the time dimension with a condition such as 
	greater than 'Jun,' then the highlighted months are selected on the 
	first alphabetical sort letter. That means Mar, May, Nov, Oct, Sep will 
	be selected. 
  *	If you want to change the query in a report, reload the OLAP Panel. To 
	be sure to generate a correct report, select the "Display the new data 
	in a new report" option in the Modified Data Provider dialog box. 
  *	Ranking applied on ServerValue( ) returns erroneous values. 
  *	Some variable names are not updated when you change to long, short or 
	value labels. 
  *	If you applied filters in the report and change the labels you're 
	using, you'll have an empty report. The filters definitions are not 
	changed (i.e., the filters are applied using the previous values); 
	therefore you need to change the definitions yourself. 
  *	Some cells might contain #SYNTAX after you edited a data provider and 
	removed dimension values. 
  *	You are not prompted for the database password when you select the 
	Automatic Refresh option. You'll have to enter this password when the 
	first refresh is done. 
  *	Applying a filter on the ServerValue in the Slice and Dice Panel might 
	not work. To work around this issue, apply the filter via the Filter 
	button in the Report toolbar. 
  *	Measures of date and text type are interpreted as dimensions 
	(BusinessObjects terminology) when inserted in a document microcube. 
	When you insert a measure of date type in the down edge and then run 
	the query, the resulting report is a very big crosstab (in fact, if a 
	measure was inserted in the body, it will be aggregated). 
  *	An application crash might occur if you try to apply a Change Source on 
	an OLAP document whenever you use a version of BusinessObjects without 
	OLAP Express access.

------------------------------------------------------------------------
IBM DB2 OLAP Access Pack
 
Installation Issues  
Known Issues 
------------------------------------------------------------------------
 
Installation Issues

  *	For information on configurations currently supported in Business 
	Objects 5.1.9 / WebIntelligence 2.7.5, refer to the Business Objects 
	Product Availability Report Web Site (PAR). 
	The Product Availability Report (PAR) contains detailed up-to-date 
	information on supported: 
	* products and languages 
	* operating systems 
	* web and application servers 
	* connectivities 
	* browsers 
	* printers 

Known Issues

IBM DB2 API Related Issues 

  *	If the server does not respond to the connection request, 	
	BusinessObjects waits for IBM DB2 client timeout. 
  *	During a drill operation or a loading of the Database Outline, an 
	application crash might occur if the local machine resources are low. 
  *	The IBM DB2 report script command '{DECIMAL 2}' applied to numbers 
	greater than or equal to 1e+198 causes an application crash in 
	esscsln.dll. 
  *	If you have defined a filter with 'None' access on a dimension in the 
	database, the IBM DB2 report script returns the value '#Missing' for 
	this dimension whereas '#NoAccess' is returned when the IBM DB2 Excel 
	Add-In is used. 
  *	The IBM DB2 Grid API release used to retrieve data supports 254 columns 
	and 16370 lines. The Grid API uses scripts whose size cannot exceed 
	32Kb. If the OLAP Panel contains a huge amount of values, generated IBM 
	DB2 script size may exceed 32kb; in this case, BusinessObjects will 
	display an error "The query cannot be executed because it is not 
	possible to generate a script for it." However the script will be split 
	when you set members as filters, therefore we suggest the following 
	work around:
  *	If you modified the Dynamic Members definition on your server, you must 
	enter these members into the Grid by drilling if you want them to be 
	displayed in the OLAP panel or put a 
	level. 
  *	Use drill-down and drill-up instead of drag and drop.
  *	Avoid unbalanced structures.
  *	Set members as filters.
  *	Select level from view by level 

Connection Related Issues

  *	If the server connection is broken during the data fetch phase, the 
	Panel is reset in the OLAP Panel. 
  *	An application crash might occur if you select a server without 
	databases. 

Add/Remove Panel Related Issues 

  *	Before you add (or remove) a member by drag and drop, you must set the 
	focus on the target in the available members tree list. If you do not, 
	the operation is undone. 

Report Related Issues 

Data Provider

  *	The '#OlapAll' reserved value used by BusinessObjects to designate the 
	aggregated value returned from the server does not appear in a report, 
	even though it is available in the Filters dialog box (Filters command, 
	Format menu). However, '#OlapAll' does appear when you export data to 
	other file formats, for example, to Excel. 

Report

  *	If you define an alerter on the time dimension with a condition such as 
	greater than 'Jun,' then the highlighted months are selected on the 
	first alphabetical sort letter. That means Mar, May, Nov, Oct, Sep will 
	be selected. 
  *	When you use a measure-tagged dimension as a filter, the elements of 
	this dimension will appear as columns in the report and not as 
	sections. 
  *	If you want to change the query in a report, reload the OLAP Panel. To 
	be sure to generate a correct report, select the "Display the new data 
	in a new report" option in the Modified Data Provider dialog box. 
  *	Ranking applied on ServerValue( ) returns erroneous values. 
  *	Some variable names are not updated when you change the alias table. 
  *	If you applied filters in the report and change the alias table you are 
	using, your report appears empty. The filters definitions are not 
	changed (i.e. the filters are applied using the previous values); 
	therefore you will have to change the filters definitions. 
  *	Some cells might contain #SYNTAX after you edited a Data Provider or 
	removed dimension elements. 
  *	When you select the Automatic Refresh option, you are prompted only 
	once for your User's password. 
  *	Applying a Filter on the ServerValue in the Slice and Dice Panel might 
	not work. To work around this issue, apply the filter via the Filter 
	button in the Report toolbar. 

Change Source 

  *	An application crash might occur when you try to apply a "Change Source 
	on an OLAP document" whenever you use a version of BusinessObjects 
	without OLAP IBM DB2 access. 

Known Restrictions 

  *	An application crash might occur in a multiple data provider report if 
	you link the different data providers with a custom sorted dimension 
	(such as the dimension 'Year').

------------------------------------------------------------------------
BusinessObjects OLAP Connect
 
General Information 
Known Issues
------------------------------------------------------------------------

General Information

Product status

  *	This version of BusinessObjects MDX Connect is a production release. 
  *	This version of BusinessObjects BW Connect is a production release. 
  *	This version of BusinessObjects WL Connect is a production release. 

Data providers

  *	For information on configurations currently supported in Business 
	Objects 5.1.9 / WebIntelligence 2.7.5, refer to the Business Objects 
	Product Availability Report Web Site (PAR). 
	The Product Availability Report (PAR) contains detailed up-to-date 
	information on supported: 
	* products and languages 
	* operating systems 
	* web and application servers 
	* connectivities 
	* browsers 
	* printers 

Upgrade to BusinessObjects OlapConnect 5.1.7

Support status 

	Reports created with BusinessObjects BW Connect released with 
	BusinessObjects 5.1.1, BusinessObjects 5.1.2 and BusinessObjects 5.1.3 
	are supported provided that reports are refreshed (Edit and Run) in 
	order to enable 5.1.7 new features. 
	Compatibility between BusinessObjects OlapConnect 5.1.7 and previous 
	versions of BusinessObjects OlapConnect 
	BusinessObjects OlapConnect 5.1.7 is not compatible with previous 
	versions of BusinessObjects OlapConnect and cannot co-exist within the 
	same deployment environment (either on the client or the server).

BW Connect Installation

	It is recommended that you create a connection to SAP BW based on the 
	saplogon.ini file. Please refer to the Section 'SAP BW Connection 
	Considerations', on page 33 of the User's Guide.
	BW Connect does not require the entire SAP BW front-end to be installed 
	on the desktop, only the SAP ODBO components from the SAP GUI. 
	Note: for compatibility purpose, it is important to always use the SAP 
	ODBO components that come from the same SAP BW front-end patch. 

Known Issues

BusinessObjects MDX Connect, BusinessObjects BW Connect, and BusinessObjects WL
Connect

  *	The following error message appears when the file oawReport.ocx is 
	installed incorrectly: 
    	"429: ActiveX component can't create object." 
	To fix this problem, you need to manually register the file.  To do 
	this: 
	1. Click Start, Run 
	2. Enter regsvr32 "c:\program files\business objects\businessobjects 
	5.0\oawreport.ocx" 
    	If you have installed Business Objects in another location, you need to 
	enter that path.  
	The following message appears: 
	"DllRegisterServer in [installation path] \businessobjects 
	5.0\oawreport.ocx succeeded."

Column order

  *	If updating the report changes the structure of the report, columns may 
	be reordered. 

Sorts

  *	A custom sort on an OLAP Connect report is lost when members are added 
	or subtracted.

InfoView

  *	A "Save and Close" document cannot be refreshed in InfoView.  

BusinessObjects MDX Connect

Attributes

  *	If you add attributes from different levels of the same dimension to 
	the same report, values for the highest dimension level attributes may 
	be false or not displayed. 

Nested Dimensions

  *	The performance of queries with nested dimensions can be improved by 
	changing the sort option to "Use natural sort order" for each 
	dimension. This only applies to queries that do not contain ranks or 
	filters.

BusinessObjects BW Connect

Connection

  *	InfoCube names or technical names containing quotes or double quote 
	characters and names that are longer than 30 characters are not 
	supported. 

Prompt

  *	The error message "Some metadata could not be found in cube. Report 
	will be modified to exclude missing members and dimension" may appear 
	when refreshing a report that displays a prompt - with "single members" 
	as prompt type and "All members in dimension" as possible members - 
	that already had a previous selected value. The workflow will continue 
	correctly by clicking OK.

InfoView

  *	There are no prompts when refreshing a report accessing to a QueryCube 
	with SAP BW Formulas or SAP BW Hierarchy variables. The last values 
	selected in Full Client are used for the refresh. 
  *	An "automation exception error" might occur when entering an incorrect 
	Sap BW login or password or when refreshing a report that contains a BW 
	Connect data provider with prompts and a Universe data provider with 
	prompts. 
  *	When refreshing a report that contains a prompt, the prompt list of 
	values contains only the last value selected. 

Memory Leaks

  *	You might encounter memory leaks when you create a large number of 
	reports in one session or when you have a prompt filter with a large 
	list of values. If so, close and reopen the application. 

Filter Attributes

  *	"An error occurred during the execution of the query" is displayed when 
	executing a query that contains a filter on an attribute (only when 
	using 2.0b client). 

BCA

  *	A "Save and Close" document cannot be refreshed using BCA. The BCA 
	Console displays a message indicating that refresh has failed. 

Manual entry for Prompt (SAP BW 3.0b version)

  *	"Use Member Validation" does not work with Alphanumeric code.

Change Source
  *	This feature is not supported for QueryCubes having Hierarchy type BW 
	variables. 

SAP ODBO extension limitations

Member Filters on the Filter Axis

  *	Only one member per dimension may be selected to filter dimensions left 
	on the Filter Axis. Ranks and Sorts on the Filter Axis are not 
	supported. 

Connection

  *	BusinessObjects BW Connect always shows the technical names of 
	databases, not their descriptions, even when the Show Technical Names 
	option is unchecked. 

Other limitations

  *	Server calculations, time options, default member features, and split 
	hierarchies are not supported. 

SAP BW variables

  *	Several variables on the same dimension is not supported. The error 
	message "The selected cube contains unsupported mandatory variables. No 
	query can be processed" is displayed when trying to access a cube that 
	contains such a dimension.
  *	No values are retrieved in the report with Formula "Price" variable  
	without "Default value".
  *	BusinessObjects BW Connect processes only SAP BW variables defined for 
	Characteristic value. 
  *	Above BW variables are supported by BusinessObjects BW Connect provided 
	that: 
  *	They are used in the 'Free Characteristics', 'Rows', or 'Columns' areas 
	of SAP Business 

Explorer and Analyzer query definition panel. 

  *	They are not used in the 'Filter' area of SAP Business Explorer and 

Analyzer query definition panel. 

  *	If you embed a BW variable in a Key Figure, you must make sure that the 
	dimension referred to by the variable is available in the QueryCube 
	definition so that BW Connect can populate the prompt. 
  *	BusinessObjects BW Connect requires that SAP BW variables be populated 
	only by user entry. 
  *	Whenever you use an SAP BW variable, an SAP BW prompt is activated. 
	This prompt requests user entry. The SAP BW prompt replaces the 
	BusinessObjects prompt. 
  *	SAP BW variables only allow the selection of member values. Therefore, 
	a selection such as "All Company codes" is not allowed. The same 
	restriction applies for levels. 
  *	If an SAP BW variable exists for a dimension, restrictions on the 
	variable have priority over any restrictions for the dimension itself.  

BusinessObjects WL Connect

Prompts

  *	You may encounter difficulties if you create a report using the "Range 
	of members" prompt type.

------------------------------------------------------------------------
Broadcast Agent 5.5
 
Known Issues 
------------------------------------------------------------------------
 
Known Issues

Broadcast Agent Administration 

  *	If you uninstall and then reinstall Broadcast Agent on the server(s), 
	for example when upgrading, the definitions of named Broadcast Agents 
	and the tasks sent to them are preserved in the repository. However, 
	you must restart the scheduler(s) manually, using the Business Objects 
	Services Administrator. Starting a scheduler is described in the 
	Broadcast Agent Administrator's Guide, Chapter 3.
  *	WARNING: If you enter an invalid password: After three failed attempts 
	to enter the General Supervisor or Supervisor password, the General 
	Supervisor or Supervisor login will be disabled. Ensure that you define 
	at least one backup General Supervisor account in your repository to 
	enable recovery from this situation.
  *	When connecting to the Business Objects Services Administrator from the 
	cluster manager machine itself, do not enter the TCP-loopback address, 
	i.e. 127.0.0.1 (localhost). If you do, connection will fail. You need 
	to use a Fully Qualified Network Address (FQNA) to connect to the 
	Business Objects Services Administrator.

Business Objects Services Administrator and Microsoft Internet Explorer Java
Console option 

  *	When using the Microsoft Internet Explorer browser to access the 
	Business Objects Service Administrator (Administrator Tool), you must 
	have the "Java console" option disabled in Internet Explorer (disabled 
	is the default setting). To ensure this option is disabled: In Internet 
	Explorer, select View, Internet options, and click on the "Advanced" 
	tab. Scroll down to the section labeled Java VM, and make sure that the 
	Java Console option is not checked.
	If you attempt to run the Administrator Tool with this option set 
	incorrectly, it may cause unpredictable effects. 

WebIntelligence User Interface

  *	With Internet Explorer 4.0.1 SP2, when you send or publish a document 
	to Broadcast Agent from WebIntelligence, and the document contains a 
	prompt, you must enter the value of the prompt before entering the 
	scheduling frequency. If you enter the frequency first, it may not be 
	preserved correctly during the prompt entry process. 

Scheduler

  *	If the database hosting the repository shuts down unexpectedly while a 
	Scheduler is accessing the repository, the Scheduler may not respond 
	when the database restarts. In this case, you must stop and restart the 
	Scheduler. You can do this using the Business Objects Services 
	Administrator as described in the Broadcast Agent Administrator's 
	Guide, chapter 3. 
	If database corruption has occurred, you may also need to use 
	Supervisor to run a Scan and Repair operation on the repository 
	database, as described in the Supervisor's Guide.
  *	When using the Auto-shutdown Scheduler on Windows 2000 the Scheduler 
	may encounter problems.
	Workaround: Using the Admin Tool, click Refresh. Your Scheduler is re-
	launched. 

Document in Drill Mode 

  *	When you retrieve and open a full-client document that was sent to 
	Broadcast Agent in Drill mode, the Drill bar does not appear. Click on 
	Analysis / Drill and then click on any column to view the Drill bar. 

VBA Dialog or Input Boxes 

  *	If you export a document to the repository containing VBA dialog boxes 
	or input boxes triggered by an event, the document will not display 
	correctly to WebIntelligence users, and cannot be refreshed using 
	Broadcast Agent. 

Miscellaneous 

  *	OSAgent Port value - This value is crucial to the correct operation of 
	the software, and you must supply this number during installation. Its 
	value must be unique on the sub-net where you are installing the 
	software. To find out how to select an appropriate value, see the 
	Installation and Update Guide or the Broadcast Agent Administrator's 
	Guide.
  *	If a Scheduler gives the error message "Cannot login to the 
	repository - Current server login is invalid", this indicates that the 
	Broadcast Agent password (set using Supervisor, in the Group Properties 
	dialog, Broadcast Agent tab) has been changed since you set up the 
	Scheduler. You must enter the new password in the Business Objects 
	Services Administrator, under Broadcast Agent Manager, in the Scheduler 
	settings dialog, in the parameter labeled "Password". 
  *	When deploying Business Objects server products with the "Use 
	BusinessObjects user name and password" database security option 
	checked, ensure that you also set each universe to "Disconnect after 
	each connection". This option is in Supervisor. Select the Tools menu, 
	then Connections, Edit, Advanced tab. 

Using Variables with the Distribute via Web Server option 

  *	When you send a report containing one or more variables to Broadcast 
	Agent using the "Distribute via web server" option, the generated HTML 
	file may contain some unnecessary white space or empty lines. You can 
	avoid this by using the Trim function when displaying variables in 
	these reports, for example,, Trim(MyVariable).

------------------------------------------------------------------------
Installer
 
General Information
Known Issues 
Upgrade Information 
------------------------------------------------------------------------

General Information

Configuration Support

  *	For information on configurations currently supported in Business 
	Objects 5.1.9 / WebIntelligence 2.7.5, refer to the Business Objects 
	Product Availability Report Web Site (PAR). 
	The Product Availability Report (PAR) contains detailed up-to-date 
	information on supported: 
	* products and languages 
	* operating systems 
	* web and application servers 
	* connectivities 
	* browsers 
	* printers 

Miscellaneous

  *	PDF files should be removed from your computer before installing a 
	Service Pack. Failure to do so will result in two different PDF 
	versions in the Online Guides folder. 
  *	The installation of the server products or the administration tools 
	modifies the system path. In some configurations, the path is too long 
	and the variable WISYS cannot be read, so the products cannot be 
	launched.
	On Windows98, check in the autoexec.bat file that the path is correct 
	and move it if necessary to the beginning.
	On Windows NT and 2000, check the environment variables to make sure 
	WISYS is correct and move it to the beginning if necessary. 
  *	Two folders, Freeware and Microsoft , are accessible on the CD but are 
	not installed via Setup if you choose a Master installation, as none of 
	the files included in those directories is needed. However, if you want 
	users to have access to these directories, you have to manually copy 
	the two directories once the master installation is done. 
  *	Before installing the server products, make sure that you have stopped 	
	all applications and all services running on the machine; otherwise the 
	program may not be able to proceed with the installation of some dlls, 
	or other system files. 
  *	When installing the WebIntelligence modules, part of the configuration 
	is carried out on the web server. During this phase, the status bar of 
	the Setup program seems to freeze while copying the file nsconfig.exe 
	even though the installation is running. As soon as the configuration 
	of the web server is finished, the status bar continues to reflect the 
	remaining copies & tasks. 
  *	Once the Desktop products are installed, you can view the Documentation 
	(.pdf format) from the Help menu only if you have Acrobat Reader 
	installed. If you do not have Acrobat Reader on your machine, you can 
	install the Reader from http://www.adobe.com. 
  *	If you are installing a service pack update of BusinessObjects 
	products, double-click the SETUP.EXE file in the SETUP folder of the CD-
	ROM. 
  *	If during installation of Enterprise Server Products you change the 
	default location of any installation folder to a remote machine, you 
	must make sure that, on the machine hosting the server products, the 
	wiorb and wimanager modules run on a local administrator account which 
	is granted the "Act as part of the operating system" right.
	To create the account, you must be an administrator of your domain. 
	Proceed as follows:
	1. From the Start bar, choose Programs => Administrative Tools (Common) 
	=> User Manager for Domains
	2. From the User Manager window, create a new user and add the user to 
	the Administrators group.
	3. Select the user and, on the Policies menu, click User Rights.
	4. In the User Rights dialog box, select Show Advanced User Rights.
	5. In the list of user rights, choose "Act as part of the operating 
	system" and click Add.
	6. Under List Names From, select the domain and click Show Users.
	7. Under Names, choose the user and click Add, then OK.
	8. Under Grant To, select the user and click OK.
	To run the wiorb and wimanager modules on this account, do the 
	following for each:
	1. On the Windows Control Panel, double-click Services.
	2. Choose the WebIntelligence module (wiorb or wimanager).
	3. Click Startup.
	4. In the Service dialog box, select Logon As: This Account.
	5. Enter the user name and password for the service and click OK. 
  *	The latest Rapid Deployment Templates (RDTs) can now be downloaded from 
	the Online Customer Support web site by your identified Business 
	Objects support contact. For more information about Online Customer 
	Support, please see the main Business Objects web site 
	(http://www.businessobjects.com) "Services/Support" section. 

Known Issues

Upgrading to Service Pack 7 or Greater 

  *	When you upgrade your Business Objects servers to Service Pack 7 or 
	greater, you must also upgrade all BusinessObjects 5.1.x clients that 
	connect to those servers. Because the communication between the client 
	and the server was optimized in BusinessObjects 5.1.7, client versions 
	prior to Service Pack 7 cannot communicate with Business Objects 
	servers later than Service Pack 7. Refer to the Deploying 3-tier 
	BusinessObjects guide for more information. 

Downloading Zero Admin BusinessObjects 

  *	When downloading Zero Admin BusinessObjects on Windows 2000, if you 
	have user rights only, the Business Objects shortcut is not created 
	(Start\Programs\BusinessObjects 5.1). You must launch Business Objects 
	through Windows Explorer. 
  *	Zero Admin BusinessObjects is not supported on Windows 98, 1st edition. 
	Universal Drill-through Services 
  *	If Universal Drill-through Services is not selected during the first 
	round of WebIntelligence setup, installing it as an additional 
	component does not prompt for a port number and therefore defaults to a 
	NULL value. If you decide to install UDS after WebIntelligence setup is 
	completed, please follow these steps to assign a port number: 
	1. Locate and open the following file: <Install 
	Path>Server\WebIntelligence 2.5\Config\setup.txt  
	2. Add a five digit port number to replace NULL value in 
	DTS_Port_ID=Null (i.e. DTS_Port_ID=20060) 
	3. Copy the five digit number into the following registry location: 
	HKEY_LOCALMACHINE\Software\Business Objects\DTS\1.0\Port 

Installation 

  *	When you install Business Objects products on Windows 98 and select BCA 
	Service Administrator, which is not selected by default when you choose 
	a Custom installation, the following error is displayed: Error occurred 
	while installing file C:\PROGRA~1\BUSINE~1\SERVER\WEBINT~1.5\JRE\LIB\
	jvm.jcov.txt. (INS0018). Click Skip and then the installation proceeds 
	without any problem.  
  *	Your anti-virus may detect that some BusinessObjects files are infected 
	by a virus without indicating the name of the virus. This is due to the 
	fact that the file compression system used by Business Objects may not 
	be recognized by the anti-virus. 
  *	If you plan to install BusinessQuery for Excel for OLAP Services, you 
	should avoid installing it on the same machine on which you installed 
	your OLAP data sources. This may generate problems. 
  *	The COMCTL32.DLL version (stored in the System folder of the Windows 
	installation folder) must be equal to or greater than version 4.71 to 
	run any BusinessObjects application. 
  	* When performing an installation from the CD, the installer 
	automatically updates COMCTL32.DLL if the version of the file is not 
	appropriate. 
  	* When performing a master installation, we advise you to copy the 	
	CoreMs folder in the master installation folder. 
	The CoreMs folder contains 40COMUPD.EXE, which lets you overwrite the 
	COMCTL32.DLL file. 
	* To install the correct version, run 40COMUPD.EXE before, during or 
	after the installation (you can browse to the CoreMs folder when the 
	installer is looking for 40COMUPD.EXE and a message dialog box appears 
	asking you to ask to insert the BODisk disk). 
	After copying a new version of COMCTL32.DLL, you must relaunch Windows. 
  *	The following error is stored in the Windows Event Viewer when you 
	install WebIntelligence on the NES 3.0 server: 
  	* Application.log 
	* Source: Perflib 
  	* Description: The Open Procedure for service "https3.0" in DLL 
	"sctr.dll" failed. Performance data for this service will not be 
	available. Status code returned is DWORD 0. 
  	* This error message is always generated in this case of installation 
	but can normally be disregarded. 
  *	The following error is stored in the Windows Event Viewer when you 
	install WebIntelligence on the Microsoft IIS 4.0 server: 
  	* The server was unable to add the virtual root '/wi/wiadmin' for the 
	directory "C:\Program Files\Business Objects\Server\WebIntelligence 
	2.5\Server\Classess\bo\w2\adm" due to the following error: The system 
	cannot find the path specified. The data is the error code. 
  	* This error can normally be disregarded. The virtual directories are 	
	correctly created and are usable. 
  *	In certain cases, the Business Objects installer might not update the 
	file MFC42.DLL and delete the existing one.
	However, the installer will install MFC42.DLL if the file does not 
	exist on the machine being installed. You should therefore reinstall. 
	MFC42.DLL is installed correctly.
	Note that the lack of MFC42.DLL means that Windows system dialog boxes 
	that can be called from the installer, for example to see users of NT 
	domains when installing Enterprise Server Products, are not available. 
  *	Visual Basic Applications (VBA) is not installed on Windows NT terminal 
	Server Platforms.
	On the Windows NT Terminal Server platform where Microsoft Visual Basic 
	for Applications is not already installed, the Visual Basic 
	Applications(VBA) module is not installed correctly.
	You need to delete the incorrectly installed dll and help files, then 
	copy the dll and help files from a correct installation to the 
	c:\program files\common files\microsoft shared\vba folder. 
  *	The installation of BusinessObjects 5.1 involves two CDs. By default, 
	the installer installs the files in the language of the operating 
	system. If you are installing a language other than the operating 
	system language, or more than one language, you will be asked to insert 
	the second CD and go to the following folder: \Online Guides\XX, where 
	XX is the language folder. The language folder mentioned in the message 
	is that of the operating system language. However, the installer may 
	actually be attempting to install another of the languages. You must 
	look in the status bar at the bottom of the screen to see which 
	language the installer is trying to install, and go to the 
	corresponding folder on the second installation CD. 
  *	There are two installation CDs for Business Objects products, CD1 and 
	CD2. The contents of CD1 are in a folder called Vol1. The contents of 
	CD2 are in a folder called Vol2. If you copy the contents of the 
	installation CDs to a network drive, you must copy them inside their 
	respective folders. After you copy to a folder called, for example, 
	Installation, on a network drive, you should have the folder 
	Installation/Vol1/[contents from CD1] and the folder 
	Installation/Vol2/[contents from CD2].

Master Installation 

  *	When you have chosen Master Setup in the setup wizard, avoid using the 
	Back button. In particular, if you choose Master Setup, then later 
	change your mind and use the Back button to choose Standalone Setup, 
	you may not be able to install the Standalone Setup. If you find 
	yourself in this situation, please exit the Setup wizard and start 
	again. 
  *	When defining the location of the ShData directory, we recommend that 
	you select a directory other than the default location; otherwise you 
	would have to give read/write rights on the whole BusinessObjects 
	directory. By defining the ShData directory in a different location, 
	you will be able to maintain the whole BusinessObjects directory as 
	read-only, and only have the ShData directory as read-write. 
  *	In the case of a master installation, if you plan to install the Demo 
	Kit or the EFashion Kit, from the Utilities section, you need to have 
	the Microsoft ODBC package installed as well, from the Data Access 
	section. 
  *	When updating a Master Setup, if multimedia products such as the 
	BusinessObjects Quick Tour were part of the existing Master Setup, then 
	when you install the new version, a dialog box will appear twice (one 
	right behind the other) informing you that "Setup cannot find the 
	folder MULTIMEDIA_DIR. Please locate this folder by clicking on the 
	Browse button." It is not necessary to locate the folder. Click Cancel 
	in each of these dialog boxes to continue the installation. 
  *	When running the products from a shared installation, you won't be able 
	to access the pdf files from the Help menu within the applications. We 
	suggest you open the files from the Online Guides directory, in the 
	master directory. 
  *	In the case of a master installation, you cannot choose the minimal 
	type, if you do not plan to run all subsequent installations in this 
	mode, as the pdf files and the help are not installed. 

Upgrading from a Master Setup

  *	If you currently have Business Objects products 5.0 standalone client 
	installed from a master installation and you want to update to Business 
	Objects products 5.1 standalone client installed from a master 
	installation, you must first de-install your Business Objects products 
	5.0 standalone client installation. Then you can launch the setup 
	wizard from the Business Objects products 5.1 master installation 

Uninstalling Zero Admin BusinessObjects

  *	On Windows 2000, if you have user rights only, do not delete the 
	default Business Objects folder stored in C:\Program Files as this 
	cancels your right to later reinstall Business Objects in this folder. 
	To reinstall Business Objects you must select a folder for which you 
	have write privileges or ask your administrator to relaunch AllowBO51-
	26-W2000.exe. 

Authentication 

No Authentication mode 

  *	When WebIntelligence runs in "No Authentication" mode, BusinessObjects 
	documents (*.rep files) cannot be viewed or edited with any viewer. 
  *	In "No Authentication" mode, user options are not kept from one session 
	to another. 

Security 

  *	If you are using Secure Socket Layers protocol (SSL) with your HTTP 
	server, and using digital certificates as a security method, you may 
	get a ReportViewer error if the appropriate Certificate Authority's 
	certificate is not in the browser certificate store. If this occurs, 
	you must import the certificate by means of a certificate server or the 
	certificate management function of your web browser. For more 
	information on how to do this, see the online help of your web browser. 

Obsolete system DLLs 

  *	On Citrix (or any platform with terminal services), the system .dll 
	file mfc42.dll may be obsolete since system .dll files are not copied 
	to the folder Windows\System. The supported version is at least 
	4.21.73.03. This file is generally installed with Microsoft Office. 
	This problem may also occur with other system .dll files. 

Oledb.sbo file

  *	During the installation an error message is displayed stating that the 
	oledb.sbo file cannot be found. To install the Oledb.sbo file, click 
	Browse and select the Oledb folder.
	For a master installation, you must also update the setup.inb file 
	which you can find at Master Installation\Setup 5.0\setup.inb.
	In the setup.inb file: 
	1. Scroll to the CLASS = OLEDB Core section and add "Oledb" to the end 	
	of the Disk parameter. 
  	2. Scroll to the CLASS = MS SQL Server OLEDB Driver Invisible section 
	and add "Oledb" to the end of the Disk parameter. 

Upgrade Information 

  *	When you upgrade to WebIntelligence 2.7, the audit database is not 
	automatically updated. 
	Enter the following SQL statements to update your audit database 
	manually:
	insert into OBJ_A_APPLICATION (A_APPLI_N_ID, A_APPLI_C_NAME) VALUES ( 
	6, 'BusinessObjects ZA' );
	insert into OBJ_A_APPLICATION (A_APPLI_N_ID, A_APPLI_C_NAME) VALUES ( 
	7, 'WebIntelligence 2.6' );
	insert into OBJ_A_EVENT_NAME (A_EVNAM_N_ID, A_EVNAM_C_NAME) VALUES ( 
	39, 'Upload Agnostic Document' );
	insert into OBJ_A_OBJECT_TYPE (A_OTYPE_N_ID, A_OTYPE_C_NAME) VALUES ( 
	19, 'SQL Value');
	update OBJ_A_EVENT_NAME
	set A_EVNAM_C_NAME = 'Publish'
	where A_EVNAM_N_ID = 8;
	update OBJ_A_EVENT_NAME
	set A_EVNAM_C_NAME = 'Download Agnostic Document'
	where A_EVNAM_N_ID = 33;
	update OBJ_A_EVENT_NAME
	set A_EVNAM_C_NAME = 'BusinessObjects ZA started'
	where A_EVNAM_N_ID = 34; 
  *	To install Business Objects 5.x Desktop Products on a machine where 
	there is an existing installation of BusinessObjects 4.x while keeping 
	the existing installation, install the 5.x release to a different 
	installation folder than the 4.x release. The default installation 
	folder of the 4.x release is "BusinessObjects" the default installation 
	folder of the 5.x release is "Business Objects" in two words. 
  *	As the 5.0 and 5.1 versions use the same registry entry, the two 
	versions cannot be used at the same time on the same machine. 

------------------------------------------------------------------------
Connectivities
 
General Information  
Documentation  
Limitations 
 
------------------------------------------------------------------------

General Information 

Configuration Support 

	For information on configurations currently supported in Business 
	Objects 5.1.9 / WebIntelligence 2.7.5, refer to the Business Objects 
	Product Availability Report Web Site (PAR).
	The Product Availability Report (PAR) contains detailed up-to-date 	
	information on supported: 
	* products and languages 
	* operating systems
	* web and application servers 
	* connectivities
	* browsers 
	* printers 

New IBM Product Nomenclature 

  *	IBM recently renamed their products.  The readme now reflects these 
	nomenclature changes. Server names are now: 
	AS/400 is now the iSeries 
	AIX servers are now the pSeries 
	Mainframes are now the zSeries 
	NT servers are now the xSeries 

Restrictive Connections 

  *	A restrictive connection is a special type of connection intended to 
	protect data access. The Administrator who wants to force the user to 
	enter data account access parameters should define a restrictive 	
	connection.  
	This connection type is using the BusinessObjects @Variable function 
	BOUSERPROMPT to ensure that the user are prompted to enter the database 
	login parameters when trying to access the data and refresh the report. 
	Refer to the section "Defining restrictive connections" in the 
	Designer's Guide for more information.

Documentation

	All database access guides are available in pdf format on the CD; 
	however, only IBM DB2, Oracle, Informix, Microsoft SQL Server, Sybase, 
	Oracle Rdb, Shadow Direct, Star SQL, Red Brick, and Teradata are 
	provided as printed guides.

Limitations

Overview 

IBM DB2 UDB 
IBM DB2/390 (zSeries) 
IBM DB2/400 (iSeries) 
Informix 
MS Access 
MS OLE-DB 
MS SQL Server 
Neon Systems Shadow Direct 
ODBC 
Oracle 
Oracle Rdb 
Red Brick  
StarSQL 
Sybase ASE  
Sybase ASIQ 12 
Teradata

Overview 

	BusinessObjects does not restrict RDBMS (Relational DataBase Management 
	System) data types. Thus, you can generate a query in which you have, 	
	for example, an Oracle Long type in the ORDER BY. This may cause an 
	RDBMS (Relational DataBase Management System) error on execution. 
  *	If a Long Binary object is included in a query, BusinessObjects will 	
	automatically fetch data row by row. 
  *	If the date format of your Windows Setting is set to mm/dd/yy, then all 
	year values will be displayed in the current century (e.g.: 03/12/01 
	will be equal to 03/12/2001 even if the real value is 03/12/3001). 
  *	If you apply a condition on money data types, you cannot fetch data 
	when you use a list of values. To select these types, you must use the 
	operand "Type a new constant" and enter the exact value. Both money and 
	smallmoney data types are accurate to one ten-thousandth of a monetary 
	unit, but BusinessObjects rounds values up to two decimal places for 
	display purposes. Therefore, a value equal to 2.894 becomes 2.89 in the 
	list of values. 
  *	You should avoid selecting the Use asynchronous mode option when you 
	create a connection for a universe that is accessed from 
	WebIntelligence or BusinessObjects 5.i. The Cancel Query feature would 
	not work. 
  *	When exporting a BusinessObjects document to an Excel file, you should 
	not specify an SQL reserved word as the name of the Excel file, for 
	example date.xls or select.xls. If you do, the export fails. 
  *	If you export a query to Excel, open the Excel file in Excel 97 and 
	save it in Excel97&5.0/95WorkBook format, then modify the query and re-
	export it to the Excel file, an "Export Done!" message is displayed but 
	the Excel file is not updated. 
  *	When you have a Shared installation, if you remove a BusinessObjects 
	driver and do not delete the chkmidw.ini file from C:\Program 
	Files\Business Objects\Data Access 5.1, the Check Middleware dialog box 
	will be displayed when you install another driver even if the 
	"Middleware Check" check box is not selected in the Setup Wizard. Note: 
	Check middleware results are shown only in English. 
  *	Unicode database (such as UTF8) is not supported with Business Objects 
	V5.x/WebIntelligence 2.x. 
  *	In Zero Admin BusinessObjects, data from a BLOB type field is 
	returned line by line during the fetch phase. 
  *	The repository database constraints (NOT NULL) are only created during 
	the creation, update, or upgrade of the BusinessObjects repository. 
	These are the only operations that can change the number of constraints 
	over time. Except from these operations, the number of database 
	constraints of the repository tables will remain unchanged. 
  *	The use of the BOUNDARY_WEIGHT_TABLE parameter in the PRM file is only 
	supported for DB2 and Teradata platforms.
  *	The description and the possible values for the Max_InList_Values 
  	parameter in each database guide are incorrect. The corrected version is 
  	the following:
	Description: Allows you to increase the number of values you may enter in 
	a condition when you use the IN LIST operator. This limit is either set by 
	how many values a database can accept in a IN LIST condition or simply by 
	the size of the SQL generated.
	The possible values are:
	No parameter Specifies that you may enter up to 99 values when you create 
	a condition using the IN LIST operator.
	X Specifies that you may enter up to X values when you create a condition 
	using the IN LIST operator

IBM DB2 UDB

  *	Currently the Cost Estimate option does not work with IBM DB2 UDB. 
  *	If you use databases that have commas as decimal separators, you must 
	enter the following parameter into the (GENERAL) subsection of the 
	[RDBMS] section of all DB2 .prm files: DECIMAL_COMMA=YES 
  *	If you want to access data via the Free-hand SQL editor, you must 
	uncheck the Enable deferred prepare option in the Compatibility tab of 
	the CLI/ODBC Settings - Advanced Settings dialog box.

IBM DB2/390 (zSeries)

  *	If you select the Export to RDBMS (Relational DataBase Management 
	System) command option, you may get an error message. If you do get an 
	error message, the application tried to create the table in a database 
	to which you do not have the appropriate rights. 
  *	If you create a condition in the Query Panel with a Date type object, 
	the Structured Query Language (SQL) syntax may generate an error if its 
	SQL definition just contains a date. To avoid generating an error 
	message, you should create an object whose SQL syntax includes both 
	date and time. 
  *	Currently the Cost Estimate option does not work with IBM DB2/390 
	(zSeries). 
  *	If you use databases that have commas as decimal separators, you must 
	enter the following parameter into the (GENERAL) subsection of the 
	[RDBMS] (Relational DataBase Management System) section of all DB2 .prm 
	files: DECIMAL_COMMA=YES 
  *	To create a repository you have to use the Custom repository create 
	mode in order to not have the security domain on the same Tablespace as 
	the universe and document domains.
  *	Objects using the count(distinct) function cannot be displayed in list 
	of the value panel in Designer.
  *	Repository creation relies on the DB2MVS.SQL file for DB2/390. You are 
	welcome to edit this file and allocate specific size for large table 
	such as OBJ_X_DOCUMENTS. Recommended table space type is "segmented".

IBM DB2/400 (iSeries)

  *	Please note that the following IBM fixes are mandatory on the IBM 
	iSeries (iSeries) V5R1 system: 
	1. V5R1 Cumulative Package, Version TL02036 (released at the beginning 
	of Feb/2002)  
	2. V5R1 DB Group PTF, version 6 (released 01/30/2002)  
	3. PTF SI02593 (Not included with the other fixes. It needs to be 
	ordered individually.) 

	4. Client Access /400 (the latest version) 
  *	If you use databases that have commas as decimal separators, you must 
	enter the following parameter into the (GENERAL) subsection of the 
	[RDBMS] section of all DB2.prm files: DECIMAL_COMMA=YES 

Informix

  *	You should avoid creating a Business Objects repository with Supervisor 
	on an ANSI Informix IDS or XPS database. You should create the repository 
	on a non ANSI database. This only applies to the repository. There is no 
	problem with data account access. 
  *	You can access stored procedures with Informix Connect as long as they 
	do not include input parameters. 
  *	You should not enter a value greater than 32000 in the 
	RecommendedLenTransfert parameter (i.e. informix.sbo file). If you do, 
	you may encounter problems while exporting your document. 
  *	When creating the database for the repository, you must select the 
	Buffered (safer) option from the Logging mode list in the New Database 
	dialog box. 
  *	When you create a universe, table alias names cannot contain more than 
	18 characters. 
  *	The recommended option for creating a WebIntelligence connection to 
	Informix is to select the Disconnect after each transaction option on 
	the Advanced tab of the Informix-Connect dialog box. If you do not and 
	you create a report that contains an InList operator with a prompt, and 
	you select the Refresh when opened option when you save the report, you 
	will get an error message when you open the report. 
  *	The asynchronism feature is not supported with the current driver. 
  *	When you parse a join between tables that contain 50 or more columns, 
	the following error message is displayed: The number of DESCRIBED 
	columns is greater than the allocated space. However, the query will 	
	work. 
  *	When you create a connection in Supervisor, if you select Use 
	BusinessObjects user name and password on the Login tab of the 
	connectivity dialog box, the OK button may be grayed out. To avoid this 
	problem you should select Use BusinessObjects user name and password 
	before you enter any other connection parameters. 
  *	The Datetime datatype is supported only in a SELECT statement. Datetime 
	is not normally supported in a WHERE clause. If you use a DATETIME 
	column in a WHERE clause, an error message appears. In Designer, you 
	can prevent the use of DATETIME in a condition for an object as 
	follows: 
	1. Double-click an object in the Object Browser. 
	The Edit Properties of Object dialog box appears. 
	2. Click the Advanced tab. 
	The Advanced page appears. 
	3. Clear the Condition checkbox in the Can be Used In groupbox. 
	4. Click OK 
  *	In Designer, you can use the following workaround to use the Informix 
	Datetime datatype in a WHERE clause for each object using a DATETIME 
	column: 
	1. Double-click an object in the Object Browser 
	The Edit Properties of Object dialog box appears. 
	2. Click the Advanced tab. 
	The Advanced page appears. 
	3. Type 'YYYY-MM-DD HH:MM:SS.000' in the Database Format textbox. 
	4. Click OK. 

MS Access

  *	If you encounter problems using the Open DataBase Connectivity (ODBC) 
	Driver Manager 3.0 with the MS Access driver, install the ODBC Driver 
	Manager Update located in the Microsoft folder on the CD-ROM. 
  *	After upgrading your MS ODBC driver from 3.51.171300 to 4.00.xxxx, some 
	objects measures or queries based on MS Access queries no longer work. 
	This is a Microsoft issue. Workaround: Change the double quotes to 
	single quotes around the string characters in the Access query.
  *	When you run a Business Objects query with MS Access, you may receive 
	an Out of Memory error. This can be overcome by upgrading the Microsoft 
	Jet Driver. Refer to the Microsoft article Q239114 at www.microsoft.com 
	for more details.
	Note: starting with Microsoft Data Access Components (MDAC) version 
	2.6, MDAC no longer contains the following Jet components:
	* Microsoft Jet 
  *	Microsoft Jet OLE DB Provider 
  *	ODBC Desktop Database Drivers. 

MS OLE-DB

  *	The audit functions are not supported with this driver.  
  *	Unicode Character Strings are not supported (nchar, nvarchar, ntext). 

MS SQL Server

  *	If you want to view currency, date and time values in the columns of 
	the Designer Table Browser, you need to ensure that on the Create a New 
	Data Source to SQL Server wizard, the "Use regional settings when 
	outputting currency, numbers, dates and times" check box is not 
	checked. 
  *	BusinessObjects 5.1 supports MS SQL Server NVARCHAR datatypes. The 
	Quick Design Wizard in Designer will not automatically create on object 
	from a column that contains MS SQL Server NVARCHAR datatypes. To query 
	an MS SQL Server NVARCHAR datatype, you must manually create a Long 
	text object in Designer based on the column that contains the NVARCHAR 
	datatype. 
  *	In Designer, if you select the View Column Values command, you cannot 
	display the column values for a column that contains NVARCHAR 
	datatypes. 
  *	When you create the data source to access Broadcast Agent, its 
	definition and its name must be identical to the one you used to create 
	the repository in Supervisor.
  *	In a universe, when an object is created against one of the 'Small 
	Money' data fields using an OLE DB connection with SQL server, the 
	objects is parsed incorrectly. This does not affect query execution; 
	the results are displayed correctly. Workaround: Use an ODBC connection 
	to avoid this parsing error. 

Neon Systems Shadow Direct 

  *	Building Combined Queries (using the operators Union, Intersect or 
	Minus") is not supported. 

ODBC

  *	With ODBC (Open DataBase Connectivity) Driver Manager 3.x, we do not 
	support File DSN. 
  *	The data source name should not be more than 33 characters. If the name 
	is longer than 33 characters it will not be listed in the drop-down 
	list box when you go to create a connection in Designer or Supervisor.

Oracle 

  *	Euro character:  For those browsers using single-byte characters, the 
	Euro character is displayed correctly using Oracle middleware when the 
	following settings are in place:
	Browser: 
	* Is Windows Internet Explorer or Netscape.  
	* Uses Codepage 1252 that supports the Euro character (the encoding 
	setting should be 'Western' or 'Western European'). 
	Middleware (UNIX or Windows): 
	* NLS_LANG must contain language_territory.WE8MSWIN1252; (WE8MSWIN1252 
	representing the Oracle codepage that works with Codepage 1252 in the 
	Windows browser)  
	Database (UNIX or Windows): 
	* Must be created with the Codepage that supports the Euro character. 
	The SQL syntax should be: create database ... charset codepage; 
	Examples: WE8ISO8859P15, WE8MSWIN1252. A complete list is available at 
	the following link:
	http://downloadwest.oracle.com/otndoc/oracle9i/901_doc/server.901/
	a90236/appa.htm#956722 
  *	The following synonyms are not retrieved when you use the standard 
	Designer strategies: Public synonyms, Recursive synonyms (synonyms 
	pointing to other synonyms) and Synonyms granted using roles. To avoid 
	this problem, use an external strategy. 
  *	Ensure that your client middleware NLS configuration corresponds to the 
	National language Support (NLS) database, as well as your Windows 
	Regional Settings. These parameters define your charset (supported 
	characters) date, and number formats. If you do not have the same 
	parameters on the database client middleware, or Windows Settings, 
	BusinessObjects does not retrieve correct results. Possible problems: 
	numbers rounded off or dates and local characters badly retrieved. 
  *	In the oracle.sbo file if you set the RunInit parameter to 0, the 
	InitDateFormat is ignored and the date format of your current session 
	is equal to the database parameter value. If formats are different, 
	queries on dates may fail and return no data. 
  *	The Data Access driver does not allow you to access Java stored 
	procedures or relational-objects on Oracle. 
  *	BusinessObjects 5.1 supports Oracle CLOB (Character Large Object) 
	datatypes. The Quick Design Wizard in Designer does not automatically 
	create an object from a column that contains Oracle CLOB  datatypes. To 
	query an Oracle CLOB datatype, you must manually create a Character 
	object in Designer based on the column that contains the CLOB datatype. 
	The Select statement must contain the following function: 
	dbms_lob.substr(name of column,number of characters returned,position 
	of first character). This works on SQL*Net 2.3 and Net8. 
	In Designer, you cannot display the column values for columns that 
	contain CLOB datatypes using the View Column Values command. 
  *	Oracle Binary Large Object (BLOB) datatypes are not supported. 
  *	Installing the version Oracle 8.x or higher Application Development Kit 
	installs an Object Request Broker (ORB) file that conflicts with the 
	Business Objects ORB file. If you want to install the Application 
	Development Kit, you should delete the environment variable CLASSPATH. 

Oracle Rdb 

  *	Warning: When you are migrating a Business Objects 4.1 repository to a 
	BusinessObjects 5.1 repository, users should not be connected to the 
	repository database. 
  *	Document Agent Server should also be disconnected from the repository 
	database. 
  *	The repository Migration Tool is only supported from Oracle ODBC Driver 
	2.10.17.00 for Rdb to Oracle 8.1.7. 
  *	To use the Oracle Rdb driver v3.x, you must add the following text inside 
	the Network Layer section of the odbc.sbo file: 
	
	[Oracle ODBC Driver for Rdb] 
	DriverLevel=1 
	ArrayFetch=1 
	Driver Name=Oracle [OR][Dd][Bb][C]* 
	SQL External File=Rdb 
	SQL Parameter File=rdb 
	InputDateFormat={\d 'yyyy-mm-dd'}
  *	The possible values of the OUTERJOINS_COMPLEX parameter are the following:
	Y Specifies that the database supports outer joins with complex joins 
	N Specifies that the database does not support outer joins with complex 
	joins. 
	The activation of this parameter allows the selection of "Outer join" in the 
	case of complex joins, for example joins that use the AND and LIKE operators. 
	Note: When you select Outer join, you must still edit the join manually in 
	the SQL Join Expression box.

Red Brick 

  *	The repository migration does not work with Red Brick Access Pack 
	2.0.2. To migrate the repository, use Red Brick Access Pack 1.0.8. 

Star SQL 

  *	An invalid date format can be returned when using StarSQL. The 
	workaround is to change array fetch to "1" and use function SQLFetch() 
	instead of SQLExtendedFetch().

Sybase ASE 

  *	If you create a query whose definition contains NUMERIC or DECIMAL 
	columns with NULL values and IMAGE or TEXT columns, the database 
	returns random values instead of NULL. This problem applies to Sybase 
	Open Client 11.1 or higher. To fix this problem, select the CONVERT 
	function in the object definition to replace all NUMERIC or DECIMAL 
	datatypes to INTEGER. 
  *	If you want to create an object whose object name is the Euro symbol, 
	install the Euro Converter module provided by Sybase. 
  *	On Sybase Adaptive Server 11.5 and 11.9.2, the stored procedure 
	sp_proc_columns (which lists the parameters of a stored procedure) 
	returns results which are missing the column_type column. This causes a 
	discrepancy in the results returned when you run the 
	SQLProcedureColumns function. To avoid this problem, you should install 
	the server EBF8517 patch which you can get from Sybase. 
  *	When you create a connection in Supervisor, if you select Use 
	BusinessObjects user name and password on the Login tab of the 
	connectivity dialog box, the OK button may be grayed out. To avoid this 
	problem you should select Use BusinessObjects user name and password 
	before you enter any other connection parameters. 

Sybase ASIQ 12 

  *	You need to install the Sybase and Generic ODBC Data Access Packs to 
	access the Sybase Adaptive Server IQ 12 ODBC driver. 
  *	Stored procedures are not supported. 
  *	Connections with asynchronous mode are not supported. 
  *	The login name is not case sensitive (whereas password is). You can log 
	on with either <user_name> or <USER_NAME>. 
  *	You cannot export an agnostic document with a document name length 
	exceeding 12 characters. 
  *	The database you create to store the BusinessObjects repository has to 
	be non-case sensitive. 
  *	The use of '!=' and 'ANY' or '=' and 'ALL' operators in a query 
	condition is not supported by Sybase ASIQ and generates an error code 
	DA0005 in BusinessObjects. 
  *	The configuration file SIQ12en.PRM now contains the same functions as 
	the SYB12EN.prm. 

Teradata 

  *	To enable Designer to recognize a TIMESTAMP column, you must create the 
	table using the following syntax: 
	create table object1(obj_N TIMESTAMP WITH TIMEZONE) 
	insert into object1 values(TIMESTAMP 'yyyy-mm-dd hh:mm:ss')
	If your date columns are stored as TIMESTAMP datatypes then you must 
	change the InputDateFormat value in the default section of the 
	Teradata.sbo file to: 
	TI\ME\STA\MP 'yyyy-mm-dd HH:mm:ss'
	If your date columns are stored as DATE datatypes, but few columns are 
	TIMESTAMP datatypes, then leave the InputDateFormat as \d 'yyyy-mm-dd', 
	and apply TI\ME\STA\MP 'yyyy-mm-dd HH:mm:ss' database object format to 
	these specific objects in Designer (i.e. Advanced tab of the Edit 
	Properties of Object dialog box).
	You can find the Teradata.sbo file at: C:\Program Files\Business 
	Objects\Data Access 5.0\Teradata\Teradata.sbo.
	If you use this object in BusinessObjects, you must create the 
	following date format:
	yyyy-mm-dd hh:mm:ss
	and apply it on the cell that displays this object.
  *	The following is a list of the OLAP functions that are currently 
	supported: 
	V2R3 OLAP Functions: Teradata Extensions: CSUM, MAVG, MDIFF, MLINREG, 
	MSUM, QUANTILE, RANK 
	V2R4 OLAP Functions: ANSI SQL-99 (New for Service Pack 7): RANK, 
	PERCENT_RANK 
	An example of SQL-99 syntax: 
	SQL=RANK() OVER (PARTITION BY ($*) ORDER BY ($*)) 
	Where the evaluation context $  * needs to be hardcoded when defining 
	objects in the Designer. 

------------------------------------------------------------------------
BusinessQuery SDK
 
Documentation 
Limitations 
------------------------------------------------------------------------
 
Documentation

See the directory Business Objects 5.0\Read Me\BQSDK for more information.

Limitations

	Once installed, this product can only be accessed by licensed 
	BusinessQuery SDK partners, and requires an additional key.

------------------------------------------------------------------------
InfoView/WebIntelligence
 
General Information
Installation Issues
Known Issues 
Limitations
InfoView
Web Servers Notes
Browsers Notes
Universal Access Java Applet
------------------------------------------------------------------------

General Information

Removed previously implemented fix 

	The following customer cases that were previously fixed with the 
	Business Objects 5.1.4 / WebIntelligence 2.7 release were in fact not 
	bugs in our product. By actually implementing them, it has caused 
	various regressions in our product. 
	Bug Number: 1052246 
	Vantive Case(s): 302297148, 302299109, 302300760, 302300803, 
	302301216, 302303822, 302304099, 302304790, 302305595, 302306030, 
	302307448, 302307760, 302312619 
	In a WebIntelligence report that contains sections, some unnecessary 
	HTML is generated. 
	Bug Number: 1049527 
	Vantive Case(s): 302272466, 302299924 
	In InfoView, when displaying in HTML a full client document, the cells 
	that use data as char contain too many spaces at the end of the data. 
	For the Business Objects 5.1.8 / WebIntelligence 2.7.4 release, the fix 
	that was previously implemented for each case was removed. 

Viewing charts in the PG32 graphic library 

	The PG32 graphic library for WebIntelligence is new in Service Pack 6; 
	it enhances display and orientation of charts. This causes a lot of new 
	behavior in charts; the following are new changes compared to previous 
	versions of Service Pack 5.1/2.7: 
  *	The PG32 graphic library in WebIntelligence has large, blank spaces 
	between charts. 
  *	In bar charts, values on the X-axis appear vertically if too many 	
	appear; if there are only a few X-axis values, then they will appear 
	horizontally.  This behavior is different than in previous Service 
	Packs, where values always appeared horizontally regardless of the 
	number of values. 
  *	In the PG32 graphics library, the data list in the legend is sometimes 
	incomplete by default. You must change the display to a larger graph to 
	view all values in the legend. 
  *	There is a behavioral change for Line and Bar charts. In previous 
	Service Packs, values appeared in the Y2 axis without lines. Effective 
	Service Pack 6, a double horizontal line now appears in the Y2 axis, 
	which corresponds with the values. 
  *	The color in the Pie chart and Donut chart has "rotated" in the new 
	PG32 graphic library in Service Pack 6. 
  *	In Radar Line charts, the Y-axis appears vertically, unlike in previous 
	Service Packs where it appears horizontally. 
  *	True Type Fonts are used in 3D Bar charts.  The size of the font 
	depends on the size of the chart.  If the chart is too large, some data 
	on the Z-axis does not appear. Resizing the chart does not display more 
	values. 
  *	Modifications to fonts and attributes do not function correctly. For 
	example, if you set the underline option, it is not applied in your 
	results. 

Getting Started with WebIntelligence Sample Documents

  *	For users to be able to follow the Getting Started with WebIntelligence 
	tutorial, you must do the following: 
	1. Using Supervisor, create a user profile with both the user name and 
	password as Student. 
	2. Allow the Student profile access to the following: 
	* Full WebIntelligence functionality 
	* Viewing BusinessObjects documents 
	3. Select the following six sample documents located on the product CD 
	in the WebI_Tutorial folder. 
	The sample files are named:
	lesson1.wqy
	lesson2.wqy
	lesson3.wqy
	lesson4.wqy
	lesson5.wqy
	lesson6.wqy
	4. Copy the documents to the Student user storage folder on the server, 
	located by default at: 
	C:\Program Files\Business Objects\Server\WebIntelligence 
	2.5\Storage\user\Student
	5. Select the BusinessObjects file, Efashion.rep, from the following 
	folder: 
	C:\Program Files\Business Objects\BusinessObjects 5.0\UserDocs 
	6. Copy this .rep file to the same Student user storage folder: 
	C:\Program Files\Business Objects\Server\WebIntelligence 
	2.5\Storage\user\Student 
	These documents will now appear in the Personal Documents list when you 
	log into InfoView as Student.

Customizing Parameters

  *	When downloading data from InfoView to CSV files it is now possible to 
	change the decimal or field separating characters by creating a file 
	wiqtinit.txt in the WebIntelligence repository.
	To do this:
	1. Follow this path: < Installation repository of 	
	WebIntelligence>\Server\WebIntelligence 2.5\wiqt\Bin. 
	2. Create a text file and call it wiqtinit.txt 
	3. The file should have the following structure:
	[INIT]
	DecimSep=<Decimal separator>
	ListSep=<Field Separator> 
	4. Save the file. 
	5. Reboot the WebIntelligence server or WIQTManager to register your 
	changes. 
	The <Decimal separator> characters can have the values: period (.) or 	
	comma (,).
	The <Field Separator> characters can have the values: comma (,) or 
	semicolon (;).
	Note: Do not use the identical values for both the Decimal and Field 	
	separators at the same time.

Customizing Login Error Messages

  *	The ModifyWebIMsgs.html file contains instructions on how to perform 	
	this modification and is included in the first level of the Freeware 
	folder of volume1 of the Product CD. The executable files are found 
	within the InfoView folder located in the Freeware folder.

Activate Fix for Bug #1055345

  *	To activate the fix for Bug 1055345, which forces the shutdown of 
	WIStorageManager, WIQT, WIGenerator, WIDispatcher, and BOMgr when CORBA 
	shutdown does not work correctly, you must do the following:
	Add a new key (a string value) for each process with its value in 
	seconds in the Windows registry.
	HKEY_LOCAL_MACHINE/SOFTWARE/Business Objects/Shared/Administration 
	Services/5.0/ <Name of the process>
	Name of the key: WaitForCompletionTime=600
	The default values (in seconds) are as follows:
	- 900s for WIGenerator, WIDispatcher, WIStorageManager, BOManager 
	(tunable)
	- 300s for WIQT (hard coded - cannot be modified)

Issue Related to the Fix Implemented for Bug #1080486

  *	With Service Pack 9, if you publish a full client document with the option 
	"Store HTML in document", your document may display a bit differently in 
	WebIntelligence. Before Service Pack 9, the display of such documents was 
	done by WIQT. Now, this task is done by the BusinessObjects processes. 
	Depending on your server tuning and the ratio of such documents in your 
	repository, it may have a significant impact on your server activity, as 
	the BusinessObjects processes are mono task. To avoid an overload of the 
	BusinessObjects processes, you may want to increase the "Max. number of 
	busy processes" and "Max. number of loaded processes" parameters of the 
	BOManager. 
	Note: The first time you access the document from the server, you may 
	experience a slow response time.
 
Installation Issues

  *	You should uninstall all previous versions of Business Objects products 
	before installing WebIntelligence on the same server.  See Installation 
	guide for further instructions. 
  *	When you uninstall WebIntelligence without stopping the services, you 
	might have two WIClusterManager.exe (for a Cluster Manager) or two 
	WIClusterNode.exe (for a Cluster Node) in the task manager. The 	
	uninstall will continue without any problem. 
  *	If you want to use BOManager on your WebIntelligence server, you must 
	configure a printer driver on that server. 
  *	The web server should be first stopped before installing 
	WebIntelligence on a Netscape server, then restarted after 
	installation. 
  *	When you activate the BOManager trace while the BOManager is running, 
	the latter may generate core files.
	Workaround: Stop the BOManager Module before activating the trace and 
	restart it. 
  *	You can install WebIntelligence in several languages, but can only use 
	one language at a time. You can use the Admin tool to switch from one 
	language to another. Then stop and restart WebIntelligence. 

Updating to a Service Pack

  *	When you update to a Service Pack, users must clear their Cache or 
	Temporary Internet files folder before they log on and launch 
	WebIntelligence. Otherwise they cannot download the new WebIntelligence 
	applets. 

Installing WebIntelligence in a folder other than C:\Program Files
  *	If you install WebIntelligence on a folder other than C:\Program Files, 
	ensure that the System account on the machine has Full Control rights 
	on the WebIntelligence installation folders. 

Known Issues 

Separator in prompts

  *	In WebIntelligence 2.7, only the semi-colon is supported as a separator 
  	between data types in a prompt. 

Number length limitations in WebIntelligence documents

  *	In WebIntelligence, the maximum value possible when doing 
	calculation/data display within a thin client Report is 2147483648. If 
	the value is greater, you will get a negative value. 

Using two prompts with the same name 

  *	The ActiveX Query Panel and Light Java applet let you enter two or more 
	prompts with the same name instead of displaying the error message 
	"Empty or duplicate prompts in query conditions. This is not allowed in 
	a query".  

Drag and drop in Netscape 4.7 on Windows 2000-SP2 Client 

  *	On Windows 2000-SP2, if you are using the Netscape 4.7 browser, you may 
	experience difficulties when you drag and drop an object to the Query 
	Panel in the Full Java applet.
	Workaround: Double click on the object instead of doing a drag and 
	drop. 

Euro symbol on MacOS 

  *	On the MacOS operating system, the Euro symbol is not displayed 
	correctly in WebIntelligence reports. 

Documentation 

  *	In Chapter 9 of the WebIntelligence System Administrator's Guide, 
	although WebIntelligence 2.6 and WebIntelligence 2.7 have the same 
	product ID number, all references and examples refer to WebIntelligence 
	2.7. 

Internal Trace 

   *	There is a performance issue during system traces when the log file 
  	reaches the size limit. The most recent trace content is copied at the 
  	beginning of the log file, which slows down the server. The following 
  	new parameter has been added to the BOMgr_diag.ini file to improve 
  	performance during system traces: RenameLogFile. 
	The default value of this parameter is 0. If you modify this parameter's 
	value to 1, the existing trace log is backed up to the BOMGR_DIAG.bak file 
	when the size limit is reached, and a new log file is created. If the 
	BOMGR_DIAG.bak backup file already exists, it is overwritten. 
 
Port Translation 

  *	When carrying out port translation, the wrong port number is generated. 
	This can cause problems in deployments with the Cisco LocalDirector. 

Starting 

  *	It takes longer to log in if a user belongs to several groups. 

Opening 

  *	Occasionally, when opening a My InfoView page with one or more frames 
	defined as a document, you will get an error in the frame or frames. 
	This is less likely to occur when using a Netscape browser. 

Standard HTML Viewer 

  *	If your repository is overloaded, you may encounter problems when 
	viewing BusinessObjects documents with prompts in Standard HTML. You 
	should scan and repair your repository in order to make it work 
	correctly. 

Scheduler 

  *	If the database hosting the repository shuts down unexpectedly while a 
	Scheduler is accessing the repository, the Scheduler may not respond 
	when the database restarts. In this case, you must stop and restart the 
	Scheduler. You can do this using the Business Objects Services 
	Administrator as described in the Broadcast Agent Administrator's 
	Guide, chapter 3. If database corruption has occurred, you may also 
	need to use Supervisor to run a Scan and Repair operation on the 
	repository database, as described in the Supervisor's Guide. 

Table Formatting 

  *	If you increase the table spacing, the spacing color remains the 
	default color yellow, even if you change the cell color. 
  *	If you change the table borders in BusinessObjects and apply any 
	further formatting, these changes do not carry over to the HTML version 
	of the document. Only one standard border type displays in HTML. See 
	bug ID 1045318. 

Drill Mode 

  *	Default hierarchies do not function correctly in WebIntelligence drill 
	mode. 

WebIntelligence Unresponsive

  *	In a WebIntelligence cluster, if user requests (Login, Display 
	Documents..) are not processed, this may be because when 
	WebIntelligence is running and an Application Server or a web server is 
	restarted, the default WIAPIBroker on which the WIBean objects reside 
	may be stopped. The osagent located on the Cluster Manager activates 
	WIAPIbroker on another Cluster Node of the cluster. If this Cluster 
	Node does not host WIBean or WICOM objects, WebIntelligence will not 
	respond to user requests. Workaround: Use the Administrator to disable 
	all WIAPIBroker modules on machines that do not host WIBean or WICOM 
	objects. 

Documents 

General 

  *	If you publish a Corporate document with Zero Admin Business Objects or 
	BusinessObjects you cannot open the document in WebIntelligence during 
	the same session. You receive the following error message: Internal 
	error bolightsrv error BOL #130 Unable to open this document, not 
	authorized.
	Workaround: Logout and login again.
	or
	Ask your Supervisor to enable your Real Time User Rights 
  *	When naming a document do not exceed the maximum amount of characters 
	allowed by the operating system. 

BusinessObjects 

  *	You cannot publish, save or send a BusinessObjects document with an 	
	embedded password from the documents list in expand mode. 
  *	BusinessObjects documents cannot be viewed in PDF and standard HTML 
	format with the Apache web server in CGI mode.
	Workaround: You may encounter this problem if you have reconfigured 	
	your Apache web server from CGI to DSO or DSO/SSL mode or vice-versa. 
	Empty the cache <Webi install directory>/WIData/Storage/docs/Document 
	before you restart the web server, otherwise you will not be able to 
	open your documents. 
  *	If you refresh a BusinessObjects document that contains several data 
	providers with the refresh option disabled you will receive the 
	following error message:
	Internal error bolightsrv error BOL #109 Error during refresh 
	(mariac.product.businessobjects.com)
	This message is incorrect and should in fact be:
	Internal error bolightsrv error BOL #109 unable to refresh the DP, 
	select 'Refreshable option' (mariac.product.businessobjects.com). 

Document in Drill Mode 

  *	When you retrieve and open a BusinessObjects document which was sent to 
	Broadcast Agent in Drill mode, the toolbar does not appear. Click on 
	Analysis/Drill and then click on any column to view the toolbar. 

Security Issues 

  *	If you choose to create a category when uploading a document, the 
	browse field appears empty when you return to the upload page. You must 
	browse for the document again. 
  *	Documents created in BusinessObjects 4.1 and saved as HTML cannot be 
	refreshed from WebIntelligence 2.7 if InfoView is configured to view 
	them as Standard HTML.
	Workaround: Configure InfoView to use the ActiveX viewer to view and 
	refresh documents saved as HTML.
  *	When you open a .doc, .xls, or .pdf document, the Microsoft or Acrobat 
	toolbar does not appear.
  *	When the Supervisor security command "Send to other groups" is checked 
	but not "Send to other users", the user is able to send documents to 
	all users.

InfoView

General

  *	You cannot access another InfoView portal through My InfoView.
  *	You cannot upload files with size 0 Kb. You receive the message "File 
	name and/or path is invalid".
  *	With a CGI Mode Web Server, you must use Basic Authentication on both 
	the Web Server and WebIntelligence for the following components to 
	function correctly:
        Netscape Plug-In Document Viewer
        ActiveX Document Viewer
        ADE Document Viewer (for use with WebIntelligence SDK).
  *	National Language Support (NLS) characters are not supported on 
	Netscape Browsers for login name and password.
  *	Asynchronous connections are not supported. Since asynchronous 
	connections do not function within WebIntelligence 2.7, universe 
	connections in asynchronous mode run in synchronous mode. Please note 
	Customer Support does not give any technical support to the 
	asynchronous mode with WebIntelligence 2.7 at this time.

ActiveX Report Viewer

  *	You may encounter problems when printing BusinessObjects documents in 
	enhanced document format with some HP Printer drivers.
  *	The printer driver you use with BusinessObjects must be installed on 
	the server to ensure you get the same rendering with the ActiveX Report 
	Viewer as with BusinessObjects. If you don't have the correct driver 
	installed on the server you can check the Print as BusinessObjects 4.1 
	option when creating the document with BusinessObjects to have a better 
	rendering with the ActiveX Report Viewer.
  *	Before downloading the latest Netscape plugin, you must first delete 
	the old one from your browser cache.
  *	If you set the "Display properties" setting to 256 colors on Windows 98 
  	and then create a WebIntelligence in Active X, the Active X panel becomes 
  	white. 

Documents

  *	You cannot open BusinessObjects documents simultaneously in 
	BusinessObjects and InfoView.
  *	When "Edit Document" rights are disabled for a user in Supervisor, a 
	user cannot change the View Documents settings in the InfoView options 
	page. The default setting of "Optimized for my Browser" is used. If a 
	change is required, it must be made in the master.txt file 
	(view_settings variable).
  *	You cannot display a BusinessObjects document that is set to refresh on 
	open if it contains a prompt for password.
  *	You cannot display the same non-Business Objects document in more than 
	one pane, even if the document is named differently for each pane.

Publishing or scheduling

  *	You can only view one value at a time when changing the prompt values 
	of a multi-prompts document in the Scheduling page.

Uploading Documents

  *	You cannot upload PowerPoint documents in WebIntelligence. 
  *	You cannot open an uploaded HTML document if it contains references to 
  	other external files such as images or other HTML files.

WebIntelligence

  *	When WebIntelligence is configured in BusinessObjects standard 		
	authentication mode and the web server in basic authentication mode, 	
	users are given access to WebIntelligence even if they click Cancel in 
	the login dialog box.
	Workaround: Make sure that WebIntelligence and the web server are both 
	configured in the same authentication mode. Therefore, if 
	WebIntelligence is configured in BusinessObjects standard 
	authentication mode, the web server should not be configured in basic 
	authentication mode.

Documents 

  *	Your "Page Setup" options are not registered fully in WebIntelligence 
	unless you click "Print Preview" and save the document. 

Browser 

  *	QuickBrowserCheck indicates VM1518 when VM1520 is installed. 
  *	National Language Support (NLS) characters with a Macintosh browser 
	(Netscape 4.7) are not supported when publishing. 
  *	You may get incorrect dates on Macintosh for lists and documents. 

Logging into WebIntelligence in a Netscape Browser

  *	With a Netscape browser, if you log out of WebIntelligence and log in 
	again without closing the browser, the Authentication Failed. Retry? 
	message may be displayed. You should ignore this message and continue 
	to log in. 

Security Commands 

  *	When the Supervisor security command "Send to other groups" is checked 
	but not "Send to other users", the user is able to send documents to 
	all users. 

Miscellaneous 

  *	If the date does not display properly in WebIntelligence, make sure 
	that the regional date setting in Windows appears as "yyyy". 
  *	If you increase the table spacing, the spacing color remains the 
	default color yellow even if you change the cell color. 
  *	You may not open a refresh on open BusinessObjects document that 
	contains prompts, if the user has a prompt restriction on the prompted 
	object used in the document. 
  *	Group and User with same name is not supported. 
  *	The Create footer calculations option on crosstabs and financial tables 
	does not work in WebIntelligence. 
  *	When you drill a report with a condition and then change the condition, 
	you receive the error message No data to fetch. This is because the 
	previous condition value was not cleaned up. To make it work, you must 
	create a wiqtinit.txt file in the wiqt folder and enter inside the file:
	[INIT]
	DeleteAllFilters=y. 
	Repository Restriction
	During setup it is possible to identify the directory location of the 
	BOMain.key file. UNC is not supported in identifying the location of 
	this file.
	However, if UNC was already chosen in the setup, you can change it in 	
	the following manner: 
  *	Change setup config on each machine to set a Local directory for Local 
	Datas. 
  *	Copy .key file in Cluster Manager machine. 
  *	Restart the Cluster Manager and all the Cluster Nodes. The 
	synchronization feature then maintains the proper .key files throughout 
	the cluster. 

BusinessQuery Documents 

  *	Refresh on Open does not work for BusinessQuery documents in 
	WebIntelligence. 
  *	If you try to refresh a BusinessQuery document in InfoView, you will 
	receive the following error; "This page is empty". If your user rights 
	allow it, you may edit the document and run a new query to display 
	updated information. 

WebIntelligence Documents 

  *	You receive an error when trying to open a WebIntelligence document 
	with a name that matches the maximum amount of characters allowed for a 
	document name. 
  *	When you drill down a level and then refresh a document that contains a 
	prompt, if you select a prompt value other than the value you selected 
	when you drilled down (i.e. if you try to drill out of the cube), a 
	blank screen or No data to fetch error message may be displayed because 
	WebIntelligence did not delete the document filter created when you 
	selected the initial prompt value.
	This may be because one of the commands Work in Drill Mode, Run and 
	Refresh documents or Do not always regenerate SQL is disabled. You 
	should ask your General Supervisor for rights to all of these commands. 
  *	When viewing WebIntelligence charts, the legend may overlap the chart 
	itself if the font used in the legend is too large.  See bug ID1050743. 

BusinessObjects Documents 

  *	When opening a BusinessObjects document with an embedded password in 
	Standard HTML format, no password is required.  You will, however, 
	receive an error if you try to refresh the document. 
  *	One cannot publish, save, send a BusinessObjects document with an 
	embedded password from the document lists in expand mode. 
  *	With Netscape 4.7 and Internet Explorer 5x, selecting certain paper 
	size options in the Page Setup dialog box causes problems.
	In the Page Setup menu, the Printer button does not work in Netscape 	
	4.7. 
  *	When a context has been modified in a universe, if you attempt to 
	refresh a BusinessObjects report based on the context in 
	WebIntelligence, the Contexts of <Query_Name (Universe_Name)> dialog 
	box will not be displayed. This is because the SQL in the query is not 
	updated. You must first refresh the query in BusinessObjects and export 
	the refreshed report to the repository. 
  *	The BOMGR0060 not authorized to open this document may be displayed 
	when you attempt to open a BusinessObjects document that has been 
	published or sent during your current session. To resolve this problem, 
	you should log out and re-log into WebIntelligence. 

Printing

  *	Some PLC printer drivers do not support scaling of documents so 
	changing the scaling factors in the Page Setup dialog box is ignored. 

Authentication 

  *	Security protocol Kerberos (used by Windows 2000) is not a supported 
	authentication method for WebIntelligence Server 2.7. 

Limitations

  *	The "Save password" function only works when Basic authentication is 
	set for both the web server and WebIntelligence. This functionality is 
	not supported for BusinessObjects standard authentication, which is the 
	current specification. 
  *	When connecting to the Business Objects Services Administrator from the 
	server machine itself, do not enter the TCP-loopback address, i.e. 
	127.0.0.1 (localhost). If you do, connection will fail. You need to use 
	a Fully Qualified Network Address (FQNA) to connect to the Business 
	Objects Services Administrator. 
  *	Only standard multi-processor configurations (with up to four 
	processors) are supported for WebIntelligence. 
  *	You cannot manage a BusinessQuery document in InfoView if the universe 
	that was used to create it has changed. 
  *	When viewing documents in PDF format, you must have the following 
	platform vs. browser compatibility:  On Win 98 and Win NT 4.0 client 
	platforms, Acrobat 4.0 viewers are compatible with IE 5.x. 
  *	You cannot save InfoView user options on the server if the user name 
	and/or password contains special characters:\ /   *	?: " < > | . 
  *	It is highly recommended that the WebIntelligence server be used 
	strictly as a server and not as a client. For example, you should not 
	use the busobj.exe installed with WebIntelligence as BusinessObjects 
	Reporter. If you do, BOManager will close down busobj.exe at its own 
	discretion such as while you're editing a full client document.

Aggregation of duplicated values in a WebIntelligence query

  *	Before WebIntelligence 2.7.4, when joining a data set from multiple SQL 
	statements, any duplicated value from the data set is joined with the 
	value or values from the other data set. Any joined measure value with 
	a duplicated value is aggregated, as often as there are duplicated 
	values. This occurs when the duplicated value is projected in a single 
	value. 
	Starting with WebIntelligence 2.7.4, WebIntelligence keeps only an 
	instance of the value of the measure for the entire set of projected 
	duplicate values. On previous service packs, the workaround "Don't 
	fetch duplicate row" by default may be used for the report. See bug ID 
	1070702. 

InfoView Query Panel limited to 256 objects in WebPanel

  *	In WebIntelligence, the InfoView Query Panel cannot have more than 256 
	objects in the WebPanel. 

Administration

  *	On a Microsoft Windows server a maximum of 50 users can refresh a 
	BusinessObjects document simultaneously. 

Setup
  *	After uninstalling WebIntelligence, you must reboot your server in 
	order to complete the process. 
  *	WebIntelligence will not start if the memory attributed to the 
	Environment variables is too short. (i.e. WebIntelligence variable not 
	taken into account because it is not loaded). 
  *	Removing Data Access in the server side will remove it from the client 
	because they are shared by these two modules. 
  *	You must disable Frontpage Extension in IIS in order to be able to 
	display Microsoft Word documents created in Office2000. 
  *	If your repository is on Informix, the wimanager and wiorb services 
	must be started with the user name and password of the person who 
	installed WebIntelligence. 

Browser

  *	A Netscape Browser cannot display a long list or long document when 
	accessing IIS Server with HTTPS protocol. The message "End of I/O 
	Channel" will pop up during the transfer of a long HTML document (e.g. 
	if you have more than 50 documents in your Corporate Documents List 
	when displayed in Expanded Mode). 
  *	When you open an agnostic document, check OLE server to fit the 
	document in the frame. 
  *	National Language Support (NLS) characters are not supported on 
	Netscape Browsers for login name and password. 
  *	National Language Support (NLS) characters are not supported on 
	Macintosh browser (Netscape 4.7) when publishing. 
  *	You may get incorrect dates on Macintosh for lists and documents. 
  *	If you click Cancel when downloading a BusinessObjects document from 
	InfoView, the browser freezes for a moment.  This is an Internet 
	Explorer bug. 

Queries 

  *	You cannot run a query if the SQL sentence exceeds the allowed limit of 
	65536 characters. 

WebIntelligence and other products

  *	For WebIntelligence 2.7 (or below), we recommend that you install 
	WebIntelligence software on dedicated servers. WebIntelligence is not 
	supported when it is installed on a server with databases, 
	repositories, and other non-operating system products. Web servers can, 
	however, be installed on the same server. 
  *	When you open a .doc, .xls, or .pdf document, the Microsoft or Acrobat 
	toolbar does not appear. 

"Business Objects Standard" authentication method under IIS 4.0 

  *	If you chose the "BusinessObjects Standard" Authentication method, when 
	running WebIntelligence 2.7 under IIS 4.0, the IIS4.0 password 
	authentication parameter must be set to "Allow anonymous" in IIS4.0 
	manager. 

My InfoView 

  *	You cannot access another InfoView portal through My InfoView. 
  *	You cannot display the same agnostic document in more than one pane; 
	even if the document is named differently for each pane. 
  *	You cannot display a BusinessObjects document that is set to refresh on 
	open if it contains a prompt for password. 
  *	You cannot display a website that contains code which causes it to 
	always appear in front. 
  *	You cannot upload files with size 0 Ko. Get message "File name and/or 
	path is invalid" 

Security Limitations 

  *	If you choose to create a category when uploading a document, the 	
	browse field appears empty when you return to the upload page. You must 
	browse for the document again. 

BusinessObjects 5i 

  *	You cannot upgrade BusinessObjects 5.0, or any version previous to 5.0, 
	through the InfoView portal with the light version of BusinessObjects. 
	
Automatic Web Server configuration

  *	Possible problem with automatic configuration of Microsoft IIS4 
  	If during installation you chose automatic configuration of the 
	Microsoft IIS4 Web server, it is possible configuration will not have 
	been correct. If you encounter any problems, refer to the Installation 
	& Updating Guide, Appendix A, "Configuring Web Servers for Windows NT" 
	and check that the virtual directory and associated permissions are 
	correct. 

Stopping WebIntelligence

  *	When you stop WebIntelligence, Java Runtime Environment (JRE) may not 
  	stop automatically. If ever that is the case, you should stop JRE 
  	manually 
	
InfoView

ActiveX ReportViewer 

  *	You may encounter problems when printing BusinessObjects documents in 
	enhanced document format with some HP Printer drivers. 
  *	The printer driver you use with BusinessObjects must be installed on 
	the server to ensure you get the same rendering with the ActiveX Report 
	Viewer as with BusinessObjects. If you don't have the correct driver 
	installed on the server you can check the Print as BusinessObjects 4.1 
	option when creating the document with BusinessObjects to have a better 
	rendering with the ActiveX Report Viewer. 
  *	Before downloading the latest Netscape plugin, you must first delete 
	the old one from your browser cache. 

WebIntelligence Document Viewers and Web Servers Using CGI Mode 
  *	The ADE Server module, which controls the document viewers within the 
	WebIntelligence cluster, must reside on a Windows NT server. If the 
	cluster's web server is being used in CGI mode, however, this can limit 
	the functionality of the viewers. For the Netscape plug-in, ActiveX, 
	and ADE (for use with WebIntelligence SDK) document viewers to work 
	correctly, you must use Basic Authentication for both the web server 
	and your WebIntelligence system. 

Inbox documents 

  *	When a user has opened a BusinessObjects document in the InfoView 
	Inbox, the document cannot be opened simultaneously in BusinessObjects. 
	InfoView options page and Edit Documents user rights 
  *	When Edit Document rights are disabled, a user cannot change the View 
	Documents settings in the InfoView options page.  The default setting 
	of Optimized for my Browser is used.  The changes have to be made in 
	the master.txt file on the view_settings variable value. 

BusinessQuery Documents 

  *	If you try to open a BusinessQuery document with a prompt that has been 
	sent to Personal Documents with BusinessObjects and saved as *.bqy file 
	in My InfoView, you may get this message: "Can not open this file".  
	This occurs if the query is not supported by InfoView. 

Download as PDF 

  *	If you click Download while viewing BusinessObjects in My InfoView 
	using the PDF viewer, the PDF plug-in appears in your browser.  Click 
	the browser's Back button to return to the InfoView session. 

Changing prompt values when publishing or scheduling 

  *	You can only view one value at a time when changing the prompt values 
	of a multi-prompt document in the Scheduling page. 

Windows 2000 Plug-in support 

  *	The Web page that lets you download the Netscape Plug-In references 
	Windows NT4 as a supported platform, but not Windows 2000. You can 
	nevertheless download the Plug-In and use it with WebIntelligence on 
	the Windows 2000 platform. 

Web Servers Notes

  *	SSL communications are not supported on the standard Apache package. 
  *	If you install Apache in CGI mode without the DSO option and you try to 
	view BusinessObjects documents in PDF or standard HTML format, you may 
	receive the following error message: Page cannot be found.
	Workaround: Click Refresh. 
  *	If you try to download the Netscape Plug-in you may receive the 
	following message: Could not load the plug-in for the MIME type 
	'application/x-Report-Viewer'. Make sure enough memory is available and 
	that the plug-in is installed correctly. This problem will not occur 
	when Apache does not include DSO support.
	Workaround: Quit and restart Netscape Communicator.
  *	To configure WebIntelligence 2.7.5 with SiteMinder, you must create 
  	environment variables on the web server.
	For the "HTML form-based" solution of SiteMinder with Microsoft IIS, 
	create the following environment variables and set their values as 
	follows: 
	"SSO_Support"="1" 
	"SSO_HTTP_Header"="HTTP_SM_USER"
	For SiteMinder with iPlanet, create the following environment variables 
	and set their values as follows: 
	"SSO_Support"="1" 
	"SSO_HTTP_Header"="sm_user"
	For the custom header solution on other web servers, create the following 
	environment variables and set their values as follows: 
	"SSO_Support"="1" 
	"SSO_HTTP_Header"="custom_header"   

Browsers Notes

  *	For the Load into Spreadsheet function (or "Download" when viewing the 
	document) in Internet Explorer for users with Excel installed: 
	In your Microsoft browser, you need to add the following information in 
	View/Options/Programs/File Types:
	For Microsoft Excel Comma Separated Values File:   extension:   CSV.
	Content Type:  text/csv
	Open with:  Excel 
  *	Certain patches for updates of Microsoft Internet Explorer 6 can make 
	download of the full and light Java applets from the Business Objects 
	server impossible if JVM (Java Virtual Machine) 3805 is used. There is 
	no problem if JVM 3810 is used. Therefore you should use JVM 3810 with 
	Microsoft Internet Explorer 6. 

Universal Access Java Applet

	The Universal Access Java applet for InfoView and WebIntelligence 
	contains accessibility features that are compliant with Section 508 of 
	the 1998 U.S. Rehabilitation Act.
	Information about the accessibility features are contained in the 
	Appendices A in the InfoView User's Guide and the WebIntelligence 
	User's Guide.
	Note:  The Universal Access Java Applet is only available in English.

Installation Notes

  *	A specific JDK level and configuration is required. Please refer to 
	Installation and Update Guide. 

Limitations

  *	WebIntelligence OLAP is not available via the Universal Access Java 
	applet. 
  *	Charts are not available to screen readers.  This includes bar, line, 
	surface, area, pie, volume, doughnut, polar, and simple scatter charts. 

Known Issues

Jaws

  *	When tabbing to an object in the Universal Access Java applet, Jaws 
	will read the previous object title, as well as the current object 
	title. This issue is due to a problem in the Freedom Scientific's 
	software that will be addressed in the next maintenance release of 
	Jaws. 

InfoView

  *	Compliancy tests were successfully performed in InfoView and 
	WebIntelligence using the following technology: 
  *	Jaws 4.0.2 screen reader, the only screen reader currently supporting 
	Java 
  *	Compliancy tests were successfully performed in ONLY InfoView using the 
	following technology: 
  	* IBM Home Page Reader 3.02 
	* Window Eyes 4.2 
	* Zoomtext 7.0 
 
Browser Notes

  *	Due to a limitation in Internet Explorer, the status of the Java 
	virtual machine in the Configuration detail panel cannot be made to 
	comply to the 508 standard. The status, determined by a Java applet, is 
	only indicated by color, which cannot be interpreted by accessibility 
	tools. 
  *	For the best results, the following browser is recommended:
   	- Microsoft Internet Explorer 5.5

------------------------------------------------------------------------
WebIntelligence for OLAP Data Sources
 
General Information 
Installation Issues 
Known Issues
------------------------------------------------------------------------
 
General Information

Product Status 

	The installation of the WEBINTELLIGENCE OLAP access is integrated with 
	the installation of WEBINTELLIGENCE. See the Installation and Update 
	Guide for complete instructions on installing WEBINTELLIGENCE.
	The Installation and Update Guide includes information on installing 
	both Business Objects Enterprise Server Products and Business Objects 
	Desktop Products. WEBINTELLIGENCE OLAP components are installed when 
	Explorer and the appropriate OLAP Access Pack are installed on the 
	server within the Business Objects Enterprise Server Products 
	installation. The client requires only an Internet Explorer web 
	browser. You do not need to install any additional Business Objects 
	software on the client.

Documentation 

	Please see "WebIntelligence Guide for OLAP Data Sources" 
	(WebIOLAPUser26en.pdf) and "WebIntelligence OLAP Administration and 
	Universal Drill-through Services Guide" (DrillThroughAdmin26en.pdf) for 
	additional information on this product.

Installation Issues

	This installation guide is specific to this version of the product and 
	should not be used as a general guide for WebIntelligence installation. 
	For additional installation guide, please see Chapter 5 "Information 
	for Administrators" of the "OLAP Documents" in WebIntelligence help. A 
	separate guide for OLAP data sources is also included in the product in 
	the help section of the OLAP connectivity in WebIntelligence. 

	WebIntelligence OLAP is only tested to run on a cluster manager.

Configuration Support

  *	For information on configurations currently supported in Business 
	Objects 5.1.9 / WebIntelligence 2.7.5, refer to the Business Objects 
	Product Availability Report Web Site (PAR). 
	The Product Availability Report (PAR) contains detailed up-to-date 
	information on supported: 
	* products and languages 
	* operating systems
	* web and application servers 
	* connectivities
	* browsers 
	* printers 

Middleware Installations

	Important: Please make sure that Essbase middleware (Essbase 5.0.2 P14) 
	is installed prior to running the WEBINTELLIGENCE Setup Wizard. Follow 
	the installation instructions from the database vendor.

UDS Designer Installation Issues

  *	It is recommended that you do not install UDS Designer on the 
	WEBINTELLIGENCE server. 
  *	Windows 98 is not supported for UDS Designer installation.
  *	If you are installing UDS Designer on Windows NT server 4.0 SP6, it may 
	not function properly as it is not a supported platform for a desktop 
	product. If you have to install UDS Designer on this platform, use this 
	workaround:
	In the above scenario; after the installation is completed, launch UDS 
	Designer and try connecting to your OLAP data. If you receive Run-Time 
	Error 429, it means that you must perform some manual registrations:
	1) Find ATL.DLL in your system 32 folder and register the dll.
	2) After ATL.DLL is properly registered, find DTSMAPDATA.dll in 
	\Business Objects\BusinessObjects 5.0 folder and register the file.
	How to register (or re-register) a DLL or OCX file
	To manually register or re-register a DLL use the program RegSvr32 in 
	the system32 folder of WinNT with the following command:
	RegSvr32.exe <path> filename of DLL or OCX
	Where <path> is the path to the folder containing the DLL or OCX.

Known Issues

  *	Client browsers must have the Java Virtual Machine (JVM) installed. 
	Failure to do so may cause a Java "error on page" message. The Java 
	Virtual Machine is an Install on demand component of Internet Explorer.
  *	When a user is required to change password at first logon onto an OLAP 
	server, there is no interface to enable this feature. Users are 
	required to change their OLAP server password prior to establishing 
	connections in WebIntelligence.
  *	Dimensions with thousands of children may cause an error in displaying 
	values when drilled down. You may move the dimension and then filter 
	the dimension in the member selection dialog.
  *	The maximum number of columns allowed in a report is set to 256 columns.
  *	The maximum number of Rows allowed in a report is set to 1000 rows.
  *	During heavy network traffic time, some reports may open with errors or 
	produces blank page, try to click the Back button on your browser and 
	try again to login or perform the operation.
  *	Please ensure that IIS is installed prior to installation, otherwise 
	you are required to re-install the product.
  *	It is important to verify that the OLAP middleware is installed prior 
	to the WebIntelligence installation process. If OLAP middleware is 
	installed after the installation is completed, you are required to re-
	install OLAP access.
  *	The Universal Drill-through Service (WebIntelligence DTS Manager listed 
	in Services directory) is set to automatically start as a service 
	provided it is installed during the WebIntelligence installation. Make 
	sure that the service is running prior to activating the UDS feature. 
	This service requires a stop and start every time a map is modified, 
	added or replaced (UDMs) in the data folder. 
  *	Download as .csv, opening from the current location may cause an error 
	if there is a macro in the XlStart directory. Save the .csv file and 
	then open it.
  *	Under certain circumstances the WebIntelligence session times out even 
	though users are active in an OLAP report. The loss of session can 
	cause a user to lose their OLAP report work. Workaround: Modify the 
	default session timeout in WebIntelligence manager.
  *	If a connection to Microsoft OLAP server fails, please check the IIS 
	settings as described in the Technical Notes section on 
	Security/Authentication Issues and make sure that a valid domain user 
	with local administrative rights is logged into the WebIntelligence 
	server and has access rights to the database and cubes. 
  *	Java.io.IOException Error in UDS  
	Case 1: If you run a web server on a port other than port 80 (in 
	default web site properties). When you try to get a dialog box you will 
	get the java.io.exception error. Solution: Change the port to 80
  	Case 2: Invalid map in Data folder. In some cases if the UDS is unable 
	to translate the map or the map is not correct, this error message is 
	displayed 
	Solution: Make sure that the map is valid

Essbase/DB2OLAP Servers

  *	Essbase 5.0.2 run time client patch 14 is highly recommended as 
	middleware. 
  *	Make sure that the Essbase client and server versions are compatible. 
  *	Create an ESSBASE.CFG File in Essbase/DB2OLAP Server. 
  *	Using an editing program, create a file named ESSBASE.CFG in your 
	ARBORPATH \BIN directory, and include one setting on each line. 
	Note: If you have the ESSBASE.CFG, you may add the settings to the 
	existing file. The above settings are case sensitive; please make sure 
	that you have the following values set as shown (one setting on each 
	line):
	Setting Name		Recommended Value
	AGENTDELAY 		35
	AGENTTHREADS 		55
	SERVERTHREADS 		60
	__SM__BUFFERED_IO 	TRUE

	The above Settings were tested with the following Essbase server 
	configuration:
	* Windows NT4.0 with Service Pack 6 
	* 800Mhz Processor
	* 1GB Memory
	* Essbase API 6.0/P3 
	* DB2 OLAP 7.1/P3 
	How to confirm the first three settings:
	* Launch Essbase/DB2OLAP server application manager and log as an 	
	administrator.
  	* Click on Server in the menu/information. 
  	* Click on Essbase Config tab and ensure Global ESSBASE.CFG settings 
	are listing above specified values. 
	How to confirm __SM__BUFFERED_IO is set to TRUE:
	* Open the application's log file (for example, SAMPLE.LOG) 
	* Search for "I/O"  
	* For the default setting, it will say, "Using direct I/O..." 
	* For the buffered setting (TRUE), it will say using "Using buffered 
	I/O..." 

SAP BW Connectivity

	The SAP BW server name can be different than the actual machine's name. 
	When creating a connection to a SAP BW server, make sure that the 
	machine name is not entered as the Server name in "Create OLAP Data 
	Source" page.
	Please note that when creating a new connection for SAP BW in "Create 
	OLAP Data Source" page, the SAP server name is case sensitive and 
	connection may not succeed if they differ from the actual server name.

SAP- BW Connectivity Middleware and MDAC

	It is highly recommended that you install MDAC 2.6 RTM and SAP 
	middleware for SAP connectivity. There have been compatibility issues 
	in installing a combination of MDAC 2.7 and SAP middleware that results 
	in WebIntelligence OLAP issues.

Security/Authentication Issues

	Please read WebIntelligence documentation on the install process and 	
	security issues.
  *	When installing on Windows 2000, make sure that to edit the OLAP folder 
	directory security to an anonymous user account with a valid Domain 
	name\username and password. User should have local administrator 
	rights. It is recommended that you use the same user name and password 	
	as the one used during the installation of the product as 
	BUSINESSOBJECTS 

Manager in step 9 of the setup.

  *	User login fails if total number of Essbase ports exceeds your licensed 
	copies. 

Differences Between OLAP Servers

	WebIntelligence for OLAP data sources attempts to provide a uniform 
	interface across each of the OLAP servers to which you can connect. 
	However, because of differences in the way that each of the vendors has 
	implemented their servers, some differences in the interface remain.
	For a detail list of Essbase/DB2OLAP server limitations and 
	restrictions, please see 
	"WebIntelligence Guide for OLAP Data Sources" (WebIOLAPUser26en.pdf).

Modifying Drill Down Limit

	You are able to limit the number of drill down operations in the 
	reports to increase performance. 
	This value is to be set by WebIntelligence administrator. It limits the 
	number of drill down operations allowed in an Essbase / DB2OLAP 
	reports. The number of drill down operations has direct impact on the 
	performance of server and response time.
	If you need to enable this feature, find the following file:
	<Target Installation Folder>\Business Objects\Server\WebIntelligence 
	2.5\Config\Setup.txt 
	Add the following, case sensitive, text to the file and save:
	drill_limit=12
	Where 12 is the number of desired drill down for each report.
	Optimizing Performance in Essbase or IBM DB2OLAP Reports
	When creating an Essbase or DB2OLAP report, to optimize the performance 
	and prevent possible error message during analysis of the report, it is 
	highly recommended that you modify a file after the installation of the 
	Essbase and or DB2OLAP as an OLAP Access pack.
	1. Make sure that installation is successful by creating a sample 
	report connecting to an Essbase or DB2OLAP server.
	2. Close WebIntelligence.
	3. Final the following file: \Business Objects\Server\WebIntelligence 
	2.5\http-server\OLAP\global.asa. 
	Open the file with a text editor.
	4. Copy and paste the following to the top of the script above "<SCRIPT 
	LANGUAGE=VBScript RUNAT=Server>" section:  
	<OBJECT RUNAT=Server SCOPE=Application ID=reportInstance 
	PROGID="O@WEss.ActiveX.1" > 
	</OBJECT>
	5. Locate the " Sub Application_OnStart()" section in the script.
	6. Copy and paste the following to the end of the script right before 
	"End Sub": 
	dim bOn 
	bOn = reportInstance.Connected()
	7. Save and replace the file to the same location.
	8. Stop and start the Default Web Site in IIS. 
	Please note that the above modification is only applicable if you have 	
	installed Essbase and or DB2OLAP as an access pack. If you decide to 
	uninstall providers and select MDX Connect or SAP BW to replace them, 
	you are required to undo the above changes, as the above changes 
	require Essbase and/or DB2 OLAP access pack installed on the server.

Activating Universal Drill-through Services (UDS)

	Important Note: If Universal Drill-through Services is not selected 
	during the first round of WebIntelligence set up, installing it as a 
	separate component does not prompt for a port number and therefore 
	defaults to a NULL value. If you decide to install UDS as a separate 
	install after WebIntelligence set-up is completed, please follow these 
	steps to assign a port number:
  *	Find and open the following file: <Install Path>Server\WebIntelligence 
	2.5\Config\setup.txt 
  *	Add a five digit port number to replace NULL value in DTS_Port_ID=Null 
	(i.e. DTS_Port_ID=20060) 
	Please note that a valid port number may not exceed 65000. 
  *	Copy the five digit number into the following registry location: 
	HKEY_LOCALMACHINE\Software\Business Objects\DTS\1.0\Port 
	Universal Drill-through Services is set to manual start in NT services 
	and you are required to start it prior to using it. To start UDS, open 
	the Services console, right click "WebIntelligence DTS Manager" and 
	select Start.

Universal Drill-through Services Samples CD 

	To obtain a copy of the Universal Drill-through Services Samples CD 
	(containing OLAP cubes, relational databases, universes and target 
	documents), please contact your Business Objects representative.

UDS Mapping Files

	When you perform drill-through, if the UDS Server does not use the new 
	translation maps in the "..\Business Objects\BusinessObjects 5.0\Data\" 
	directory or does not use the updated version of a existing translation 
	maps, follow one of the following workarounds:
  *	Stop and restart the following Windows Service: "WebIntelligence DTS 	
	Manager"
  *	If the previous solution doesn't work, you may have two (or more) 
	translation maps in the ".\Business Objects\BusinessObjects 5.0\Data\" 
	directory for the same combination of source data source and target 
	data source. In this scenario the UDS Server will use the first one 
	loaded to perform the translation. To fix this issue, keep only one 
	translation map for the combination of source data source and target 
	data source in the "..\Business Objects\BusinessObjects 5.0\Data\" 
	directory. When done, you have to reload the translation 
	maps.
	Contact your Business Objects representative for additional help. A 
	sample relational database and related universes along with sample 
	target reports will be provided to activate the feature.

IIS Authentication In Windows 2000 Servers

	To make sure that the "OLAP" folder in IIS has appropriate anonymous 
	user:
	* In OLAP properties dialog, select Directory Security tab.
	* Click Edit button in Anonymous access and authentication control.
  	* In Authentication Method dialog, check the anonymous access check box.
	* Click on Edit button for Account used for anonymous access.
	* In Anonymous User Account dialog, enter a valid Server administrator 
	account.
  	* Before selecting a username and password, ensure that the user has 
	administrative rights on the server and is a member of the domain with 
	access rights in MSOLAP server databases. 
	This is usually the administrator of WebIntelligence server. 
	In this particular example the above user has been assigned as the 
	anonymous user. This is the user that will be used for all resources 
	that the Web Application requires (for example, temp files, registry 
	access, and in the case of MS Analysis Services - it is used to gain 
	access to the OLAP Server).

"Update UDS" Feature in UDS Designer

	There is an icon in the tool bar with the caption of "Update the UDS". 
	When clicking on this icon, you are able to update the UDS services on 
	any server.
	You are required to input the WebIntelligence server name and the UDS 
	port number in that server. Once all the server information is 
	provided, upon clicking on the Update button, it reloads the Data 
	folder that contains translation maps. This remote feature is to 
	replace the required step to stop and start of the WebIntelligence DTS 
	Manager after adding or modifying a map in the data folder. You may 
	save the map directly onto the WebIntelligence server, data folder from 
	a remote client where you have UDS Designer installed. Then update the 
	server to activate the saved map. 
	You are no longer required to stop and start the WebIntelligence DTS 
	Manager in the NT services.

UDS Designer OLAP Data Sources & Middleware

	In order to create translation maps in UDS Designer you will require a 
	connection to an OLAP data source. Select the appropriate OLAP Access 
	Pack during the setup (MDX Connect, Essbase, DB2 OLAP Server). 
	Depending on your choice of OLAP provider, prior to installing the OLAP 
	Access pack; you are required to install the appropriate and compatible 
	middleware.

UDS Designer Installation Issues

  *	It is recommended that you do not install UDS Designer on the 
	WEBINTELLIGENCE server. 
  *	Windows 98 is not supported for UDS Designer installation.

Registering (or Re-registering) a DLL or OCX File

	To manually register or re-register a DLL use the program RegSvr32 in 
	the system32 folder of WinNT with the following command:
	RegSvr32.exe <path> filename of DLL or OCX
	Where <path> is the path to the folder containing the DLL or OCX.

UDS Designer Known Issues

  *	Ensure that *.UDM files saved are not Read-only files; otherwise file 
	access and modifications will cause errors.
  *	Terminating the application by clicking on X button or shutting down 
	the computer while UDS Designer is running may cause an error. 
	Workaround is to save the map, close the application and then shut down 
	the computer.
  *	When logging to the universe for the first time in UDS Designer, a 
	BusinessObjects application is launched in background. Simply close the 
	background application and proceed with the UDS Designer.
  *	Replacing a dimension, updating a hierarchy or a level is not supported 
	in this version of UDS Designer.
  *	Maps created or edited manually may cause an error when trying to open 
	with UDS Designer for further modifications.
  *	UDS Designer is not checking for validity of the Maps saved, if you 
	select to save an incomplete map to use in with the drill-through 
	feature, you may not succeed in activating the UDS server.
  *	The optimized screen area size to display UDS Designer is 1024 by 768 
	pixels, reducing the size may cause some interface issues. UDS Designer 
	dialog does not resize.
  *	Opening the sample maps provided in sample CD might cause an error, as 
	you may not have the identical server, database and cube to match the 
	sources.
  *	UDS Designer is currently listed as "MapDeveloper" in the 
	BusinessObjects 5.1 folder and in the start menu.
  *	When opening a saved map, if the target universe is missing or renamed, 
	UDS Designer will not prompt for universe selection and it leaves the 
	universe target section blank. You may select a universe after it is 
	loaded and associate it with the map.
  *	Connections to Microsoft OLAP servers require NT authentications; make 
	sure you login to Windows using a valid domain username with rights to 
	MS OLAP server.

------------------------------------------------------------------------
International Version
 
General Information 
Documentation
------------------------------------------------------------------------
 
General Information 

Configuration Support
  *	For information on configurations currently supported in Business 
	Objects 5.1.9 / WebIntelligence 2.7.5, refer to the Business Objects 
	Product Availability Report Web Site (PAR). 
	The Product Availability Report (PAR) contains detailed up-to-date 
	information on supported: 
	* products and languages 
	* operating systems
	* web and application servers 
	* connectivities
	* browsers 
	* printers 

BusinessObjects

  *	For the German version, the user must avoid using the verkettung 
	(concat) function in version 4 when creating a user-defined object, 
	because it has been changed to verketten in version 5. To work around 
	this issue, the user needs to go into the PRM file and change 
	verkettung to verketten. 

Documentation 

Acrobat Reader 

  *	Acrobat Reader 4.0 does not display accented characters correctly. To 
	display accented characters, you must have Acrobat Reader 4.05 
	installed. 

------------------------------------------------------------------------
Business Objects 5.1.9 / WebIntelligence 2.7.5
 
Enhancement Requests

Broadcast Agent

Bug Number: 1081761
Enhancement Request Number: 22606
Vantive Case(s):302380254 
You are now allowed to change the rights of a txt file sent 
using Broadcast Agent to a UNIX platform.

Bug Number: 1087352
Enhancement Request Number: 27196
Vantive Case(s):302462733 
You are now able to publish a BusinessObjects document that 
has Broadcast Agent scheduled jobs.

WebIntelligence

Bug Number: 1078110
Enhancement Request Number: 15711
Vantive Case(s):302381059; 302430024; 302438860 
Cell content appears on the next page when a cell displays 
large number of characters.

Bug Number: 1084516
Enhancement Request Number: 16310
Vantive Case(s):302402716; 302448921 
A user is now able to print a BusinessObjects document from an 
ActiveX viewer on any network printer available on a server. 
Additionally, a user can now print a document without having 
to display it.
                  
The following guides have been updated for Business Objects 5.1.9 / 
WebIntelligence 2.7.5.

General

  *	What's New for Service Pack 9 Guide
	The "What's New" documents is updated to reflect the new 
	and improved features in Service Pack 9, as well as 
	enhancements requested by users. The first section of this 
	document details new enhancements to specific Business Objects 
	applications. The second offers a major new update on 
	performance enhancements.

Deployment and Server Products

  *	Broadcast Agent Administrator's Guide
  	Updated. 
  	
  *	Deployment Guide
	Updated. 
	
  *	Installation and Update Guide
  	Updated. 

  *	Supervisor's Guide
	Updated to include information on the "Save Document" 
	property. 

  *	WebIntelligence System Administrator's Guide
	Updated to include information on new UNIX parameters for 
	configuring Broadcast Agent, and new parameters that can be 
	set in the Administrator.

Query, Reporting and Analysis Products

  *	BusinessObjects User's Guide
	Updated to include information on macros, scripts and lists 
	of values. 

  *	Express OLAP Access Pack Users Guide
	Updated to include additional installation and configuration 
	information. 
	
  *	Designer's Guide
	Updated to include information on forcing generation of the 
	+ sign in outerjoin SQL generation for Oracle, and working 
	with lists of values. 

  *	InfoView User's Guide
	Updated. 

  *	WebIntelligence User's Guide
	Updated to include information on the document list separator. 

Database Access

  *	Generic ODBC Access Guide
	Updated. 

  *	IBM DB2 Database Guide 
	Updated.  

Troubleshooting

  *	Error Message Guide
	Added error messages BOMGR0160 and LOV0003. 

  *	Troubleshooting With WICorbaPing
	Updated. 

Customer Cases fixed in Business Objects 5.1.9 / WebIntelligence 2.7.5
 
The following customer cases have been fixed in Business Objects 5.1.9 / 
WebIntelligence 2.7.5.

Auditor

Bug Number: 1054680
Vantive Case(s):302330004 
After installing Auditor 5.1 for UNIX, if you run the 
exportDocument script you receive bad syntax.

Bug Number: 1068955
Vantive Case(s):302385879; 302387534 
Solaris 2.6 is not listed in the Auditor Administrator's Guide 
as a supported platform except in the Browser section.
 
Broadcast Agent

Bug Number: 1038165
Vantive Case(s):302160934 302414056 302419136 
302419394  
The VBA function ExportToRDBMS does not work with Broadcast 
Agent when you export the results of a data provider to  
an RDBMS over a shared connection.

Bug Number: 1042111
Vantive Case(s):302188536; 302190658; 302215812; 
302258389; 302305445; 302339453; 
302400432; 302421490; 302439218; 
302463483  
When publishing a BusinessObjects report to Corporate, the 
overwrite mode turns itself off when the Scheduling time is 
changed.

Bug Number: 1055296
Vantive Case(s):302328887; 302401298; 302401336; 
302402651; 302403009; 302404710; 
302439596; 302475516; 302476160; 
302478037   
Daylight Saving Time does not change scheduled times 
automatically, so jobs run one hour later than scheduled.

Bug Number: 1062229
Vantive Case(s):302351491 
Different schedulers sometimes take the same tasks to schedule 
resulting in a multiplication of scheduled tasks.

Bug Number: 1071962
Vantive Case(s):302393461 
On UNIX,  when you run a  task with a BusinessObjects document 
that contains a tab name with double quotes, and 
the document is meant to be distributed by a web server, the 
task fails. Broadcast Agent should return the error "Export 
as HTML failed" but instead, it returns the error "Maximum 
Duration Reached."

Bug Number: 1079662
Vantive Case(s):302405741 
Scheduled Broadcast Agent reports printing to the same print 
queue, using the same name for .ps files results in the files 
being overwritten.

Bug Number: 1081400
Vantive Case(s):302406141; 302416156; 302438991; 
302476542   
In BusinessObjects in the three tier mode, a scheduling time 
difference occurs when a job is scheduled in Broadcast Agent 
on client machine that is in a different time zone than the server.

Bug Number: 1083636
Vantive Case(s):302419222 
When the Broadcast Agent File Watcher option is selected, the 
task runs only once.  This needs to be documented in the 
Broadcast Agent Administrator's Guide.

Bug Number: 1083723
Vantive Case(s):302426461; 302485753 
A BusinessObjects report printed via Broadcast Agent in 
WebIntelligence 2.7 on an AIX platform has incorrect fonts.

Bug Number: 1083949
Vantive Case(s):302430164; 302454338; 302464329;    
 302467683; 302488905; 302497625    
BcsScdul.exe abruptly stops after awhile because of problems 
related to database access.

Bug Number: 1084830
Vantive Case(s):302440826; 302473701; 302474985 
When sending a document to the Broadcast Agent on Daylight 
Saving Time (summer) to be run on Standard Time (winter), the 
task will be run twice for the first occurrence.

Bug Number: 1086743
Vantive Case(s):302448990; 302457137; 302459719; 
302462448; 302462736; 302463288; 
302474239; 302477873; 302478720; 
302480967; 302484911; 302490145; 
302491086; 302493772; 302495012; 
302496732; 302497230; 302499488; 
302510017; 302512820; 302513728 
The Scheduler panel appears and has to be killed.  This slows 
down the server.

Bug Number: 1087544
Vantive Case(s):302463350 
When you create a new document and schedule it with Broadcast 
Agent, the batch ID in the OBJ_M_MAGIC_ID table increases 
by two instead of one when the job is executed.

Bug Number: 1090101
Vantive Case(s):302474877; 302476223; 302476278;    
302476981;302480199; 302511525    
After Daylight Savings Time, when jobs are scheduled from 
WebIntelligence to run within the next hour of current time, 
the scheduled time changes to the preferred hour plus one hour.

Bug Number: 1090242
Vantive Case(s):302424970 
An error occurs when a report is sent via Broadcast Agent with 
the 'Distribute via web server' option activated.

Bug Number: 1094793
Vantive Case(s):302465077 
Deployment guide should give more details on how to run 
BOManager interactively.

Bug Number: 1096198
Vantive Case(s):302504042; 302505931; 302510232 
When you publish a BusinessObjects report to a distribution 
list via InfoView the following error is returned: 
'Distribution Failed. (BCAG0370) 
- Cannot get distribution list. (BCAG0420)'

BusinessObjects

Bug Number: 1048850
Vantive Case(s):302264698 
A general protection fault is generated when a cell is empty 
in the Body and in the last line, while "In CurrentPage" in a 
Crosstable.

Bug Number: 1050451
Vantive Case(s):302282066; 302344618; 302377310;   
302420838; 302493311    
When the decimal separator is set to "," in the Regional 
Settings, BusinessObjects generates SQL that causes an error 
against DB2 UDB 7.1.

Bug Number: 1052822
Vantive Case(s):302296700 
A general protection fault occurs when formatting a table.

Bug Number: 1055087
Vantive Case(s):302333575; 302410104; 302450288 
When a BusinessObjects report with Page function is saved as 
.txt or .rtf the page number appears as -1.

Bug Number: 1055333
Vantive Case(s):302332611; 302349852; 302374099 
FreeHand SQL shared connections disappear when opening 
multiple sessions of BusinessObjects.

Bug Number: 1055430
Vantive Case(s):302332619 
Graphs are not displayed in HTML format in InfoView when 
adding a cell at the beginning of a document with the "Read as 
HTML" option and position set to "left and top" margin.

Bug Number: 1056204
Vantive Case(s):302320672; 302345168; 302428674 
Prompts for existing BusinessObjects reports using SQL7 server 
can disappear when you change the connection for the target 
universe to point to the same data source using a different name.

Bug Number: 1056642
Vantive Case(s):302348205 
When you use the ALT-Tab keys when entering a string into a 
cell, you can experience formatting problems in the cell, and 
in certain conditions, the report automatically closes.

Bug Number: 1057063
Vantive Case(s):302348243; 302367025; 302429357;  
302462997   
BusinessObjects may crash during Slice and Dice and Ranking if 
you apply a filter before applying a rank.

Bug Number: 1058384
Vantive Case(s):302354635; 302392781; 302465919 
When you group variables in BusinessObjects when the 'Unused 
Values Only' option is not selected, a general protection 
fault occurs.

Bug Number: 1060765
Vantive Case(s):302349390; 302361670; 302375167; 
302380090; 302382038; 302416224; 
302416228; 302438496; 302440591; 
302444478; 302454227; 302454952 
On Windows XP, when you refresh a report with prompts, the 
List of Values (LOV) button is grayed out.

Bug Number: 1061399 
Vantive Case(s): 302421963;  302361729    
Tables sometimes cover (join together with) other tables in 
multi-table reports where the tables are set to repeat the header 
on every page. 

Bug Number: 1063224
Vantive Case(s):302363338; 302439515; 302497348 
When saving a BusinessObjects report in HTML, the generated 
HTML contains an empty table.

Bug Number: 1069257
Vantive Case(s):302386787 
Usage of the 'DBDSN' variable should be more documented in the 
Generic ODBC data access guide.

Bug Number: 1069891
Vantive Case(s):302385823; 302441614 
BusinessObjects Japanese crashes when the IsNull() function is 
used in a block hidden by the Hide Block option.

Bug Number: 1071679
Vantive Case(s):302381602; 302439131; 302459681; 302481336;  
302512715     
An attempt to enter multiple values in a multi-valued prompt 
sometimes produces the error "Attempt to enter multiple values 
in a mono value variable. (VAR0001)".

Bug Number: 1075849
Vantive Case(s):302408191; 302411134; 302411999; 
302420942; 302425564; 302429975; 
302436323; 302451144; 302452517; 
302460545; 302474278; 302483553; 
302488072; 302489079; 302497915; 
302509802  
Cell contents are truncated when a report is saved as PDF.

Bug Number: 1076045
Vantive Case(s): 302452956
In BusinessObjects, when you manually insert a string into an 
object set as date, a general protection fault is produced.

Bug Number: 1076806
Vantive Case(s):302411439 
When you switch to another application under Windows XP while 
parsing the SQL of a query, all Query Panel buttons remain 
grayed out even after the parsing has finished.

Bug Number: 1076887
Vantive Case(s):302407634 
The Installation and Update Guide needs to indicate the 
resolution of error HTTP 404 error (the page cannot be found) 
that users get when they try to log into InfoView using Apache 
1.3.19 or 1.3.27.

Bug Number: 1077279
Vantive Case(s):302413264; 302426527 
If a report is first saved in landscape format in 
BusinessObjects and then saved as PDF, HTML links do not work 
in the PDF file.

Bug Number: 1077303
Vantive Case(s):302409771 
If a query based on a stored procedure is refreshed after the 
data types of stored procedure columns are changed, the data 
type changes are not reflected in the report.

Bug Number: 1077538
Vantive Case(s):302416220 
Keyboard shortcuts do not work in the BusinessObjects Query 
Panel.

Bug Number: 1078137
Vantive Case(s):302416623; 302432331; 302453141;  
302487623    
The error "R6025 - pure virtual function call" appears when 
opening some reports.

Bug Number: 1078534
Vantive Case(s):302421736 
Crosstabs are truncated when printed in A3 format from 
BusinessObjects 5.1.7.

Bug Number: 1078691
Vantive Case(s):302421317 
The BusinessObjects documentation did not explain that the "Do 
Not Generate SQL Before Running" option would prevent 
SQL regeneration as long as the result objects were not 
modified.

Bug Number: 1078762
Vantive Case(s):302420828; 302424494; 302450179 
BusinessObjects crashes when some version 5.1.5 reports are 
opened using version 5.1.7.

Bug Number: 1079265
Vantive Case(s):302384745; 302393442; 302409515; 
302411123; 302425025; 302438167; 
302442073; 302445340  
BusinessObjects hangs when you try to send or schedule a 
report to Broadcast Agent and Microsoft applications are open 
under Windows XP.

Bug Number: 1079422
Vantive Case(s):302458512; 302491965 
SQL is not regenerated when query objects are changed and the 
"Do not generate SQL before running" option is checked.

Bug Number: 1079444
Vantive Case(s):302423224 
Long label names do not appear in reports created on Oracle 
Express.

Bug Number: 1079614
Vantive Case(s):302424923 
In the rpseccom.htm and rpseqseccom.htm files in Freeware, 
code number 93 is no longer present.

Bug Number: 1079636
Vantive Case(s):302420846 
The decimal symbol does not appear in currency values in OLAP 
Connect running against Microsoft OLAP when the decimal 
symbol is set to a comma.

Bug Number: 1079909
Vantive Case(s):302426336 
SQL generation error occurs when the "-" symbol is used in 
conjunction with SUM.

Bug Number: 1079997
Vantive Case(s):302481088 
If you create a BusinessObjects OLAP report with prompts in 
which you selected Use Table as alias and then publish it, 
the report aliases are not displayed correctly in InfoView.

Bug Number: 1080172
Vantive Case(s):302429034 
If a report name contains the "[ " or "]" character, the VBA 
Editor cannot be launched.

Bug Number: 1080245
Vantive Case(s):302428860 
WHERE clauses are sometimes duplicated in the generated SQL 
when the universe contains a WHERE clause and the report 
contains a condition.

Bug Number: 1080363
Vantive Case(s):302428065 
When a report contains a tab named PRN, BusinessObjects 
crashes when attempting to save the report in HTML format.

Bug Number: 1080679
Vantive Case(s):302429819; 302469500; 302482322;   
302508297; 302510526    
When a crosstab break format is set to break on a new page, 
only the first page data is shown.

Bug Number: 1080953
Vantive Case(s):302433112; 302467418 
The table body is sometimes split from the table header when 
text in the table takes up less than one page.

Bug Number: 1081607
Vantive Case(s):302413936; 302452353 
BusinessObjects truncates Informix usernames with more than 8 
characters.

Bug Number: 1082040
Vantive Case(s):302460926; 302478510 
Results of calculations involving numbers with more than 7 
digits are truncated when working with BusinessObjects 
free-hand SQL against Oracle 8.9203 or higher.

Bug Number: 1085037
Vantive Case(s):302442773 
If you add a description to a condition object in Designer and 
then hide the condition object, the description for this 
hidden condition object that was previously added to a 
BusinessObjects report is not displayed.

Bug Number: 1085275
Vantive Case(s):302440332 
After you have used the -var command to refresh a report, the 
Values button in the prompt dialog box is grayed out.


Bug Number: 1085324
Vantive Case(s):302433783; 302458414; 302468698;    
302483589; 302485125; 302506302    
BusinessObjects returns a random number of rows when used with 
Teradata ODBC driver 3.02.00.11.

Bug Number: 1085628
Vantive Case(s):302424399 
BusinessObjects crashes when opening a full client document.

Bug Number: 1085699
Vantive Case(s):302453842; 302460299; 302482606 
Query Panel keyboard shortcuts that worked in earlier versions 
no longer work in 5.1.7 and 5.1.8.

Bug Number: 1086153
Vantive Case(s):302435324 
When creating a calculation for a condition through the 
Complex Condition Wizard, the data objects are not displayed 
when you reach the "Synchronize your Calculation" step.

Bug Number: 1086493
Vantive Case(s):302448740; 302466084 
If you apply a break with the option 'Start a New Page' 
selected, some data disappears from the report.

Bug Number: 1087322
Vantive Case(s):302461054 
In BusinessObjects, a duplicate row is added when the array 
fetch size is set to the same number as the number of rows 
that must be retrieved.

Bug Number: 1087328
Vantive Case(s):302462258 
BusinessObjects crashes when you add a free-standing cell and 
then enter a formula inside this cell.

Bug Number: 1087761
Vantive Case(s):302466272; 302476946; 302478310;     
302487727; 302489944; 302501028;     
302501457       
When you create a query in BusinessObjects that should return 
a result set of more than 65535 records, the first time 
you run the query, you only get 65535 records back. All the 
records are returned if you refresh the report. This behavior 
is repeated every time you close and rerun BusinessObjects.

Bug Number: 1088031
Vantive Case(s):302446809 
In BusinessObjects 5.1.7 if you click Print Preview, it takes 
several minutes to render the page.

Bug Number: 1088572
Vantive Case(s):302450172; 302476381 
If you remove a data provider from the Data Manager and then 
click OK, BusinessObjects crashes.

Bug Number: 1088875
Vantive Case(s):302471354 
In the Data Manager, when you use linked universes (core and 
derived universe) on two domains, the link between two Data 
Providers disappears after you change the universe definition 
and refresh the report. If the queries are performed with 
objects coming from the derived universe, the link does not 
disappear.

Bug Number: 1089130
Vantive Case(s):302460373; 302462621; 302470340; 
302471558; 302472215; 302488773; 
302490521; 302491474; 302493325; 
302493717; 302495335; 302495763; 
302497373; 302498902; 302506323; 
302507732; 302508261; 302508377 
After upgrading to BusinessObjects 5.1.8, reports that use 
Microsoft Excel as a data provider cannot be refreshed.

Bug Number: 1090605
Vantive Case(s):302481006; 302484937; 302495917;  
302503263    
If you create a cell in a report, format the cell so that 
"wrap text" is applied and then save the report to HTML, the 
text is no longer wrapped.

BusinessObjectsConnect BW

Bug Number: 1076889
Vantive Case(s):302412899 
It is not possible to change the OLAP data source from BW 
Server 2.0B to BW Server 3.x.

Bug Number: 1088400
Vantive Case(s):302462166; 302472149 
The Query Panel reappears instead of the query result when you 
run a SAP query that uses the lowest hierarchy level.

BusinessObjectsConnect MDX

Bug Number: 1069895
Vantive Case(s):302379725 
Error OLC0025 appears when you apply an attribute filter on a 
hierarchy.

BusinessQuery

Bug Number: 1069054
Vantive Case(s):302388403; 302388818 
In BusinessQuery an issue has been noted when refreshing a 
query after a universe that has been exported has 
been updated. You must edit the query to use the newest 
version of the universe.

Bug Number: 1084268
Vantive Case(s):302440936 
BusinessQuery hangs when changing worksheets and one worksheet 
has the name "#BusinessQuery#".

Bug Number: 1090998
Vantive Case(s):302444224 
Erroneous information is present in the BusinessQuery section 
of the readme.

BusinessQuery MD

Bug Number: 1079847
Vantive Case(s):302408677 
When a BusinessQuery 5.1.5 report is displayed in version 
5.1.6, not all rows are displayed.

Designer

Bug Number: 1057057
Vantive Case(s):302349532; 302433976; 302484442 
When you change a table name in a universe, the table name is 
not changed in the subselect FROM clause for an object or 
predefined condition.

Bug Number: 1059749
Vantive Case(s):302353474; 302372813; 302432046;   
302440474; 302505908    
When you change the value of ColSort in the target RDBMS SBO 
file, the modified value is not applied to tables that are 
already inserted in Structure pane.

Bug Number: 1070123
Vantive Case(s):302379366; 302391467; 302427662;  
302456816    
If you cancel importing universe by pressing the ESC button, 
the following message appears: "You must close this universe 
before importing it".

Bug Number: 1075747
Vantive Case(s):302406617 
In Designer, objects are grayed out when the universe contains 
a large number of objects (for example 14000 objects).

Bug Number: 1076078
Vantive Case(s):302398369 
The "Allow users to edit this List of Values" option for list 
of values does not apply to a personal list of values. The 
personal LOV is not exported and remains on the local machine. The 
user always has access to the personal LOV, even when the 
"Allow users to edit this List of Values" option is cleared.

Bug Number: 1077233
Vantive Case(s):302414433 
BusinessObjects does not respond when a report is refreshed if 
the UNION parameter in the DB2400EN.PRM file is set 
with no value (turned off). This forces two queries to be 
generated.

Bug Number: 1079263
Vantive Case(s):302424174; 302431605 
An unhandled exception error occurs when an object that 
contains quotes in the column name is parsed. This applies 
to connections using OLEDB data providers.

Bug Number: 1082937
Vantive Case(s):302437523 
In the Designer's Guide, the mention of the number of rows 
fetched by a query has been corrected to the numbers of
rows viewed at any one time when viewing table values.

Bug Number: 1085964
Vantive Case(s):302448216; 302456121; 302461346;    
302468538; 302475322; 302495396    
When you change the owner for a table in a universe, the owner 
name in object properties for objects built on the table is 
incorrect. Applies to Oracle.

Bug Number: 1086445
Vantive Case(s):302454353; 302511227 
MAX_INLIST_VALUES parameter is not defined correctly in the 
Database Access guides nor is the description for the 
In List operator in the BusinessObjects User's guide.

Developer Suite

Bug Number: 1048534
Vantive Case(s):302256821; 302384826 
The BusinessObjects SDK ConvertTo method of the DataProvider 
class considers commas as field separators when used 
to export to a .csv file.

Bug Number: 1053330
Vantive Case(s):302311864; 302356597 
If you are using Windows NT authentication to login to 
WebIntelligence, you should not be able to login to 
WebIntelligence if previously you did not log on to your machine 
with your NT login.

Bug Number: 1053558
Vantive Case(s):302315134 
If you publish a full client document to WebIntelligence in 
which you selected the Refresh Document When Opening option, 
"Refresh options" should not appear when you try to save the 
exported document in WebIntelligence.

Bug Number: 1054320
Vantive Case(s):302325020 
The Receive Method of the Documents class is badly defined in 
the BusinessObjects SDK Reference guide and online help.

Bug Number: 1056884
Vantive Case(s):302347150 
If you decide to publish a WebIntelligence document with the 
option "Scheduled Refresh" selected, the default refresh date 
is a month behind the current date.

Bug Number: 1062869
Vantive Case(s):302362014; 302393179; 302490976 
When refreshing a full client document using a Visual Basic 
(VBA) macro or application, the ActiveX Report Viewer 
component fails to display all the report pages of a full 
client document.

Bug Number: 1068841
Vantive Case(s):302383876; 302399337; 302428622;   
302447030; 302473797    
If you open a BusinessObjects or WebIntelligence document in 
the custom MyInfoView welcome page, a system exception 
is thrown.

Bug Number: 1070161
Vantive Case(s):302372525 
With WebIntelligence JSP, if you selected "Standard HTML 
format" as viewing mode and BusinessObjects as editing mode, 
you get a blank page in Zero Admin BusinessObjects when you 
edit a full client document which contains one or more prompts 
and which has the Refresh Document When Opening option 
selected.

Bug Number: 1073924
Vantive Case(s):302401401 
On WIBean, it is not possible to leave a blank value in the 
enterValue method of the WIPrompt class.

Bug Number: 1075133
Vantive Case(s): 302399872 
If you use the BusinessObjects SDK Load method of the 
DataProvider class, you receive the following message: "Cannot 
get DataProvider"

Bug Number: 1076652
Vantive Case(s):302409307; 302413051; 302463830 
The docViewREPZB.asp sample does not detect or upgrade Zero 
Admin BusinessObjects.

Bug Number: 1076902
Vantive Case(s):302412970; 302418012; 302418317;     
302423671; 302431474; 302444924;     
302448692       
If you use WebIntelligence ASP to access a full client 
document and try to view it through the PDF viewer using 
Acrobat 6.0, Acrobat starts but nothing is displayed.

Bug Number: 1076922
Vantive Case(s):302408956; 302443924 
WebIntelligence ASP does not allow overwrite of former 
versions of ActiveX Report Viewer.

Bug Number: 1076961
Vantive Case(s):302414373 
In WebIntelligence ASP, the Upload link is not deactivated 
when the "Push Document" security command is disabled in 
Supervisor.

Bug Number: 1077159
Vantive Case(s):302409928; 302415458 
In WebIntelligence ASP, WasValueSelected of the WIPrompt class 
is correctly set only when a single value is selected from 
the List of Values (LOV).

Bug Number: 1077404
Vantive Case(s):302415183 
In WebIntelligence JSP, personal categories are not created 
correctly.

Bug Number: 1078160
Vantive Case(s):302419920; 302422613 
The WIBean getName method of the WIDataProvider class does not 
return the name of the data provider of a full client 
document saved as a personal document.

Bug Number: 1078464
Vantive Case(s):302420714 
When using the ActiveX Web Panel through the WebIntelligence 
ASP sample in SSL mode, you are not redirected to 
the correct URL location.

Bug Number: 1080604
Vantive Case(s):302431063 
In a Visual Basic (VBA) macro if you add 
"Application.Interactive = False" with a Document_Open() 
method, this crashes BusinessObjects.

Bug Number: 1084839
Vantive Case(s):302447670
Nested prompts do not work correctly when the "Automatic 
refresh before use" property is selected.

Bug Number: 1085033
Vantive Case(s):302449277 
The WIBean getDPResult function of the WIDocument class does 
not retrieve the names of the data providers in the right 
order nor does it display the data that corresponds to each 
data provider.

Bug Number: 1091090
Vantive Case(s):302474286; 302479021 
When you display a full client document in the ActiveX Report 
Viewer using the WebIntelligence JSP sample of Developer 
Suite 5.5.8 deployed on WebSphere 5.0.2 AIX, the URL address 
in the browser is wrong.

Bug Number: 1093627
Vantive Case(s):302492215 
In InfoView, if a user clicks quickly a couple of times the 
Show List of Values button when filling a condition prompt, an 
empty List of Values list is displayed.

InfoView

Bug Number: 1045274
Vantive Case(s):302222956; 302230727; 302312692;  
302429623    
The error message BOMGR0160 needs to be documented in the 
Error Message Guide.

Bug Number: 1056340
Vantive Case(s):302339795 
When opening a BusinessObjects report in pdf format in 
WebIntelligence on a UNIX platform, '#Alerter' appears instead 
of the month.

Bug Number: 1062463
Vantive Case(s):302363802; 302401062; 302422067;  
302488821    
In InfoView, an Excel file, saved as .html, uploaded to 
Corporate Documents returns a blank page when retrieved.

Bug Number: 1080631
Vantive Case(s):302425519 
The InfoView User's Guide needs to state that in InfoView, you 
are not able to select the start and expiration time when 
scheduling a document on an hourly, daily, weekly or monthly 
interval. The expired time is "12:00 AM" by default.

Bug Number: 1087109
Vantive Case(s):302461536; 302467840; 302468967; 
302472885; 302501932; 302502734; 
302504375; 302509867  
A BusinessObjects report could not be opened in 
WebIntelligence 2.7.4 on a Solaris platform.

Bug Number: 1092655
Vantive Case(s):302483021 
When users are required to change their password at their 
first login in InfoView in the ASP mode, there is a timeout if 
they do not change it quickly enough.

Bug Number: 1093300
Vantive Case(s):302484598; 302493172 
The "Publish document" option in WebIntelligence fails when 
the document domain name contains a space.

BugNumber:1093889
VantiveCase(s): 302477644;302509576 
A WebIntelligence error is displayed when opening a BusinessObjects 
report in InfoView. This happens when the application is returning 
the storage token.

Setup

Bug Number: 1078144
Vantive Case(s):302419220 
The Deployment Guide and the "windows2000.txt" file contain 
incorrect information on access to the Windows registry keys.

Bug Number: 1079653
Vantive Case(s):302423448 
When you run wsetup for WebIntelligence 2.7.3 on HPUX 11.0 
with Apache 1.3.27, and you select DSO in the Apache 
configuration, you may receive the following error message:
"/usr/lib/dld.sl: Unresolved symbol: ap_ctx_get (code)  from 
/opt/bo/webi273/Server/WebIntelligence2.5/http-server/bin/
mod_hsal1.3.27.so Syntax error on line 3 of 
/usr/local/apache_1.3.27/conf/webi26.conf: Cannot load 
/opt/bo/webi273/Server/WebIntelligence2.5/http-server/bin/
mod_hsal1.3.27.so into server: Unresolved external ./apachectl start: 
httpd could not be started".

Bug Number: 1088987
Vantive Case(s):302469657 
The licensing information documented in the Installation and 
Update Guide is inconsistent.

Bug Number: 1091547
Vantive Case(s):302477864 
The Installation and Update guide for Windows contains 
incorrect information on upgrading to a new service pack.

Supervisor

Bug Number: 1077875
Vantive Case(s):302415798; 302420704; 302490004;  
302499947   
When you run a scan and repair in Supervisor, the trigger 
files deleted.

Bug Number: 1079730
Vantive Case(s):302396089; 302429175 
Supervisor can delete documents in a disabled domain and link 
universes to a user that doesn't belong to a group with 
access to those universes.

Bug Number: 1080020
Vantive Case(s):302428649 
On the BusinessObjects CD, the Vol1/Freeware/repostry.htm file 
in the repository column lists the OBJ_M_ACTOR.M_ACTOR_N_ENDING  
and M_ACTOR_N_CNTDOWN as being only supported on BusinessObjects 4.1.

Bug Number: 1083734
Vantive Case(s):302413747 
The Scan and Repair function in Supervisor deletes BCA file 
watcher and Distribution paths from obj_m_genpar.

Bug Number: 1086185
Vantive Case(s):302440255 
In the Supervisor's Guide the definition for the Save Document 
property needs to be clarified.

WebIntelligence

Bug Number: 1047006
Vantive Case(s):302330494; 302356020 
A predefined list of values that contains the quote(') symbol 
does not work in WebIntelligence.

Bug Number: 1051202
Vantive Case(s):302285866; 302317450 
WebIntelligence 2.6.2 on UNIX Sun Solaris 7: The errors 
"#ERROR" or "#Syntax" appear on cells when viewing a 
BusinessObjects report in InfoView.

Bug Number: 1051490
Vantive Case(s):302283868; 302291193; 302375883 
When you click on the View Prompts button of the scheduling 
options, the text box beside the prompt remains empty.

Bug Number: 1052405
Vantive Case(s):302296703 
On UNIX platforms in previous versions, the WIORB launches the 
WIClusterManager before it is initialized, resulting in 
unnecessary traces in the WIClusterManager.log.

Bug Number: 1052836
Vantive Case(s):302301831; 302419680 
BusinessObjects returns an error message when you modify a 
universe, export it to the repository and then refresh 
the document in InfoView.

Bug Number: 1052864 
Vantive Case(s): 302321498; 302305305 
If you create a 3D chart in WebIntelligence and apply a 
logarithmic scale to an axis, you don't see the value change. 

Bug Number: 1060273
Vantive Case(s):302350874 
There is no logical way to include HTML in a .rep file when 
saving, publishing or sending it via WebIntelligence.

Bug Number: 1060388
Vantive Case(s):302348737 
WebIntelligence on Sun Solaris and IBM AIX (German only): The 
customized format of the "*.csv" file resulting 
from a downloaded WebIntelligence report does not work.

Bug Number: 1062515
Vantive Case(s):302366144; 302398073; 302506034 
When formats are applied in WebIntelligence, an incorrect 
number format with negative values is returned.

Bug Number: 1064255
Vantive Case(s):302369560 
The Check Browser function displays an unsupported Java 
Virtual Machine (JVM) version.

Bug Number: 1066118
Vantive Case(s):302375715 
When viewing a BusinessObjects document drilled to the lowest 
level, the web browser crashes when viewing the report in 
full.

Bug Number: 1066197
Vantive Case(s):302376590
You are unable to drill on certain sections when the options 
"Repeat on every page" and "Start a new page for each 
section" are set to YES.

Bug Number: 1067917 
Vantive Case(s): 302377464 
If WebIntelligence is deployed on Windows 2000, you are not able 
to retrieve a full-client document in PDF format.  

Bug Number: 1068062
Vantive Case(s):302382138 
On Windows platforms in previous versions, once the WIQT 
inactive time is reached, documents with prompts are 
displayed without the prompt label in InfoView.

Bug Number: 1068485
Vantive Case(s):302386616 
In a prompt report with "show as index" the left navigation 
bar is hidden.

Bug Number: 1068637
Vantive Case(s):302383832; 302413018 
When opening a Web Intelligence Document with Section headings 
in an Index frame, the "OpenDocument"
function causes an Error in the Index frame.

Bug Number: 1070048
Vantive Case(s):302389149  
It is not possible to trace WIOrb under UNIX though the option 
does exist in the WItraceCtl utility.

Bug Number: 1070956
Vantive Case(s):302394816 
On UNIX platforms in previous versions in the Administration 
Console, the WITraceCtl displayed the location of log 
and error file creation incorrectly. The WITraceCtl displays 
the WIData/log directory as the location, when the correct 
location is $WI/Setup.

Bug Number: 1071292
Vantive Case(s):302396842 
When viewing a sectioned report in Enhanced Document Format, 
sometimes the sections tree does not display the selected section 
when the "Row by Row autofit" option is selected.

Bug Number: 1073076
Vantive Case(s):302364336 
In the French version of WebIntelligence (running on a 
French-language operating system), a runtime error appears 
when sending or publishing a report with a scheduled refresh 
and your computer's date/time is set to Winter time.

Bug Number: 1073247
Vantive Case(s):302393439 
Empty prompts do not work.

Bug Number: 1073534
Vantive Case(s):302438753 
Error WI058 appears when moving reports between repositories 
and user has access to more than one universe.

Bug Number: 1074573
Vantive Case(s):302341425; 302494858 
The Audit facility lists the user as "unknown" for certain 
events even after the user logs in and is authenticated.

Bug Number: 1075628
Vantive Case(s):302408156; 302412849; 302421463; 
302423962; 302424869; 302429719; 
302444882; 302445758; 302456819; 
302459197; 302462233; 302464027; 
302466517; 302467133; 302471056; 
302473773; 302476698; 302494103 
Sun Solaris and IBM AIX: Corporate and Personal document lists 
are not sorted in alphabetical order.

Bug Number: 1076100
Vantive Case(s):302410984 
UNIX: When a BOManager process doesn't respond, freezes, or 
dies for an unknown reason, the OAD launches more than 
one BOManager instances when the server is highly stressed.

Bug Number: 1076105
Vantive Case(s):302396380; 302399142; 302410985;   
302439003; 302459562    
The BOManager process crashes due to a problem with the BOL 
"release session."

Bug Number: 1076128
Vantive Case(s):302401932; 302408110; 302410897;   
302438204; 302480071    
The last refreshed time in the Corporate Documents is 
incorrect when you set the time zone to "(GMT -05:00) Indiana 
(East)".

Bug Number: 1076206
Vantive Case(s):302410865; 302432441; 302443730;    
302464217; 302471828; 302507126    
On Solaris, some sections are missing when viewing 
BusinessObjects documents in Enhanced Document Format or in 
ActiveX.

Bug Number: 1076334
Vantive Case(s):302393820 
When you install iPlanet application server after 
WebIntelligence, then run wupdate and select the iPlanet web 
server, it removes the gxlib library reference from the 
LD_LIBRARY_PATH environment variable. As a result, you can not 
start the web server.

Bug Number: 1076791
Vantive Case(s):302404488 
Refreshing a WebIntelligence report that contains OpenDoc 
objects, with Drill Mode enabled, opens the report without 
frames instead of within the normal frameset.

Bug Number: 1077006
Vantive Case(s):302413793 
The document name is lost as a result of any document action 
done in InfoView after a WIQT process timeout.

Bug Number: 1077101
Vantive Case(s):302406721 
Users can only drill on a report for which they no rights if 
the universe is not on the server.

Bug Number: 1077545
Vantive Case(s):302394394 
When navigating multiple reports containing the OpenDoc 
feature, in PDF view format, the following system error 
occurs:
"Error during shut-down of BusinessObjects server process." 
(BOMGR0050)

Bug Number: 1077607
Vantive Case(s):302417367 
Line feed in the description field does not work when a 
WebIntelligence document is published as a corporate document.

Bug Number: 1077980
Vantive Case(s):302410942; 302457867 
On the Solaris platform in previous versions, when a Broadcast 
Agent Scheduler starts, the WIAPIBroker does not start, 
and a general CORBA exception (SDK exception 19001) is 
returned.

Bug Number: 1077989
Vantive Case(s):302411470; 302443310; 302463963;   
302500785; 302510798    
Downloading BusinessObjects documents (*.rep) via InfoView 
causes the libhttpd.ep process to take up 1GB of memory.

Bug Number: 1078058
Vantive Case(s):302422803 
Sun Solaris: InfoView Corporate document lists are not sorted 
correctly.

Bug Number: 1078143
Vantive Case(s):302419690 
The In List command comma list separator is not documented in 
the WebIntelligence User's Guide.

Bug Number: 1078182
Vantive Case(s):302416627 
Setting the WEBI_PROXYTIMEOUT system variable on the server to 
a value lower than the proxy timeout causes performance problems 
when opening and refreshing documents in InfoView.

Bug Number: 1078184
Vantive Case(s):302412539 
IBM AIX (en_US locale): InfoView Corporate document lists are 
not sorted correctly.

Bug Number: 1078291
Vantive Case(s):302413790 
A user who is not allowed to see LOVs but tries to build a 
query with LOVs, only receives "Error2" in the task bar 
instead of an explanatory error message.

Bug Number: 1078399
Vantive Case(s):302416276; 302421851 
InfoView on Sun Solaris: When viewing a BusinessObjects 
document (.rep) in InfoView, with the view format option 
"Optimized for my browser" enabled, the section map tree does 
not display correctly on reports.

Bug Number: 1078528
Vantive Case(s):302418370; 302457584; 302471692 
When refreshing a report that contains prompt for a query that 
has just been saved and closed, the following error message 
appears:  "HTTP/1.0 200 OK Content-Type: text/html".

Bug Number: 1078765
Vantive Case(s):302419226 
The limitation on the number of objects per Y-axis documented 
in the WebIntelligence User's Guide is incorrect.

Bug Number: 1078824
Vantive Case(s):302487921 
WebIntelligence on Mac/OS 10 and Netscape 7.02: when you 
click "Create Documents" in InfoView and then 
select a universe, an error is generated.

Bug Number: 1079112
Vantive Case(s):302362492; 302378941; 302405849; 
302411479; 302416666; 302418019; 
302428060; 302432022; 302441072; 
302443872; 302449156; 302454548; 
302460203; 302464509; 302502406 
In previous versions, an unhandled exception can cause the 
BOManager process to delete %SystemDriver%\boot.ini and/or 
%SystemRoot%\system32\drivers\*.*  files.

Bug Number: 1080448
Vantive Case(s):302418626; 302443698; 302454413;  
302471524   
In previous versions, the Audit facility logged abnormal 
entries in the OBJ_A_EVENT_LOG table.

Bug Number: 1080486
Vantive Case(s):302429217; 302462700; 302476225 
A full client report does not refresh automatically when it 
opens in the HTML viewer.

Bug Number: 1080518
Vantive Case(s):302476879 
InfoView on UNIX: The "Insert Break" and "Start a New Page" 
options do not work on WebIntelligence reports when viewed 
in PDF or Enhanced View (ActiveX) format.

Bug Number: 1081068
Vantive Case(s):302428371 
On the Solaris platform in previous versions, the client 
system time is not displayed correctly when jobs are scheduled 
in InfoView.

Bug Number: 1081122
Vantive Case(s):302439087  
When viewing reports in InfoView, in HTML view format, the 
following error message is sometimes generated: "Internal 
error: Thread exception" (BOMGR0100)

Bug Number: 1081236
Vantive Case(s):302429954; 302443070; 302448073;  
302478463   
WebIntelligence on Sun Solaris: The DocumentDate() function 
returns the following value for date: 01-January-1901

Bug Number: 1081450
Vantive Case(s):302433619; 302456666 
On Windows 2000 Server in previous versions, clicking the BCA 
Parameters button or the User activity button in the 
Administrator displayed a blank page.

Bug Number: 1081523
Vantive Case(s):302431222; 302435786 
The temporary key files related to 3-tier BusinessObjects 
(Zero Administration BusinessObjects) sessions are not 
deleted from the C:\Program Files\Business 
Objects\BusinessObjects 5.0\Temp\cache directory.

Bug Number: 1081535
Vantive Case(s):302434442 
When viewing BusinessObjects documents (*.rep) in InfoView, a 
thin white line appears above the titles on reports.

Bug Number: 1082292
Vantive Case(s):302390868; 302435273; 302458383;   
302459287; 302508445    
In previous versions, duplicate values for A_EVLOG_N_ID were 
logged in the OBJ_A_EVENT_LOG table.

Bug Number: 1082578
Vantive Case(s):302440641 
InfoView allows you to enter malicious scripts in some input 
fields.

Bug Number: 1082823
Vantive Case(s):302438534 
When using the ActiveX viewer: When you remove objects and add 
different objects to the Query Panel, and then click 
"Save" and "Close", the wrong object is displayed on the Query 
Panel although the SQL statement is correct.

Bug Number: 1083541
Vantive Case(s):302438445; 302462782; 302462903;  
302508858    
The connection to the repository never closes. This results in 
multiple open sessions on the database.

Bug Number: 1083799
Vantive Case(s):302429853 
On UNIX platforms in previous versions, the "Busbj error BOL#5 
No open Document" is displayed when the BOL times out.

Bug Number: 1083811
Vantive Case(s):302472188 
BOManager becomes quite unstable during low stress testing.

Bug Number: 1083867
Vantive Case(s):302444817; 302458149; 302465222; 
302477915; 302489854; 302500877; 
302501489   
UNIX: When using the ActiveX viewer to view BusinessObjects 
documents (*.rep) in InfoView, the "Page break" option is 
not applied correctly to sections on reports.

Bug Number: 1084036
Vantive Case(s):302441970 
When a report is scheduled in Broadcast Agent to a file 
watcher file, the report remains indefinitely in 'Waiting' 
status.

Bug Number: 1085302
Vantive Case(s):302445102 
On the SUN platform in previous versions, an internal 
bolightsrv error (BOL #109) is displayed when a 
BusinessObjects document with a date prompt is refreshed.

Bug Number: 1085862
Vantive Case(s):302452937; 302455094; 302463087; 
302465958; 302469715; 302471456; 
302472527; 302488546; 302496929; 
302502208; 302512195  
When you use InfoView to refresh a BusinessObjects report 
(*.rep) that contains prompts, and select values that include 
the ampersand symbol ("&"), no data or partial data is returned.

Bug Number: 1086027
Vantive Case(s):302429170 
In previous versions, the BOManager generates a BOMGR10480 
CORBA Exception when BOLight processes crash during 
OpenDocument/ImportDocument.

Bug Number: 1086954
Vantive Case(s):302421611  
System traces cause performance issues as size of the log file 
reaches the limit. 

Bug Number: 1087069
Vantive Case(s):302457323; 302459163; 302487767 
If you run a report containing prompts, switch to drill mode 
and then run the report once again, the values that you enter 
in the prompt dialog box are not saved and in fact you are 
prompted to enter new values.

Bug Number: 1087456
Vantive Case(s):302457352 
Axis label values, on grouped bar charts, display horizontally 
and overlap with each other.

Bug Number: 1087485
Vantive Case(s):302462383; 302470000; 302478471;  
302495865   
If you open a published corporate WebIntelligence document set 
for drill mode, you receive a BusinessObjects report viewer 
error.

Bug Number: 1087913
Vantive Case(s):302459030 
When using Informix SDK 2.70, InfoView returns a bolightsrv 
error  BOL #5 (No open document) on the second or 
third refresh of BusinessObjects documents.

Bug Number: 1088734
Vantive Case(s):302461631 
In a WebIntelligence report, document links do not work.

Bug Number: 1089213
Vantive Case(s):302472190 
If you refresh in WebIntelligence a report that uses Visual 
Basic for Applications as its data provider, you receive an 
error message.

Bug Number: 1090122
Vantive Case(s):302461322 
In the WebIntelligence System Administrator's Guide, the 
information on auditing Business Objects modules is 
incomplete.

Bug Number: 1090128
Vantive Case(s):302472875; 302476915; 302487358; 
302488018; 302497165; 302498573; 
302504972; 302508382  
If you create a cell in a report, format the cell so that 
"wrap text" is applied and then save the report to HTML, the 
text is no longer wrapped.

Bug Number: 1090308
Vantive Case(s):302471799 
In InfoView, if you try to view a full client document in 
Acrobat PDF format, you receive an error message.

Bug Number: 1090323
Vantive Case(s):302453581 
WICorbaPing doesn't accept the argument -OAlocalIPC 0.

Bug Number: 1095680
Vantive Case(s):302486014 
The WIQT process dies during retrieval of large amounts of 
data via the ActiveX viewer.

Bug Number: 1099166 
Vantive Case(s): 302517058; 302515190 
If you publish a Business Objects report in which you selected 
the Store HTML in document option, the report crashes when 
you open it in WebIntelligence JSP.   

Zero Admin BusinessObjects

Bug Number: 1061158
Vantive Case(s):302360639 
In previous versions, when you installed Zero Admin 
BusinessObjects under WIJSP, the VBA package was not 
automatically deployed on the client machine (if the package 
is not already installed). The problem has now been 
resolved by modifying the docViewREPZB.jsp and newDocZB.jsp 
files: <param name="Language" value="EN">
</param> changed to <param name="SessionLanguage" 
value="EN"></param>

Bug Number: 1076877
Vantive Case(s):302408771; 302418053 
When you login to WebIntelligence, and select to view 
BusinessObjects documents with BusinessObjects, then open 
a BusinessObjects report and refresh it, your system freezes 
if the report contains 1000, 2000 or 3000 bytes sent by 
InternetWriteFile.

Bug Number: 1077362
Vantive Case(s):302398304; 302406872; 302410411; 
302415893; 302425864; 302432827; 
302433074; 302445388; 302453918; 
302475602; 302489231; 302492486; 
302493043; 302493969; 302494766; 
302497490; 302506721; 302507202 
In previous versions when using SiteMinder, the presence of a 
cookie with no value in the HTTP communication while opening 
a Full-Client document in Zero Admin BusinessObjects can 
generate an unhandled exception in the ActiveX and cause 
Internet Explorer to crash.

Bug Number: 1078675
Vantive Case(s):302419447 
The ampersand  "&" in the name of a BusinessObjects report 
that is saved as a personal document in BusinessObjects in the 
three tier mode is lost.

Bug Number: 1081854
Vantive Case(s):302436445 
Supervisor does not offer a no way to restrict access to 
disabled documents found using the Find Files option in 
BusinessObjects.

Bug Number: 1082341
Vantive Case(s):302437920 
A WebIntelligence document that has the double byte space in 
the description is not displayed correctly in the Personal 
documents list of BusinessObjects in the three tier mode.

Bug Number: 1083784
Vantive Case(s):302445773; 302461701; 302465574;    
302479601; 302504311; 302509683    
When you try to send a Zero Admin BusinessObjects report to an 
email recipient more than once, nothing is sent 
and when you try to close the application, you receive an 
unhandled exception error.

Bug Number: 1084103
Vantive Case(s):302430273; 302438981; 302445143; 
302446177; 302455404; 302479399; 
302480631; 302483980; 302486746; 
302506814  
When you apply a break to a BusinessObjects report and select 
'Start a New Page' option, the report loses data and blank 
pages appear.

Bug Number: 1085093
Vantive Case(s):302441913; 302477086; 302479742;  
302492267   
When you open a BusinessObjects report on a Windows XP system, 
and try to display the list of values in a prompt, 
your system freezes.

Bug Number: 1086548
Vantive Case(s):302471302; 302472995; 302473000;  
302508081   
Zero Admin BusinessObjects running on Informix AIX causes wiqt 
logout core dump issue.

Bug Number: 1088293
Vantive Case(s):302461032 
When you select a Zero Administration BusinessObjects document 
to save as HTML on a directory or system drive that 
does not have enough space, you do not receive an error 
message.

Bug Number: 1088915
Vantive Case(s):302465637; 302476979; 302480517;   
302481177; 302484924    
Zero Admin BusinessObjects freezes for an extended period when 
you run a large query, press ESC, then select to display 
partial results.

Bug Number: 1089121
Vantive Case(s): 302452956
When you cancel a Zero Admin BusinessObjects query from AIX, 
your system freezes while the query is performing row 
retrieval.

Bug Number: 1090057
Vantive Case(s):302474122; 302490037 
When a user's password is modified in Zero Admin 
BusinessObjects launched from the desktop, and the 
WebIntelligence session times out or is ended via the 
Administration Console, the user's account is disabled.

