BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

Transcription

1 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes BusinessObjects Enterprise XI R2 Fix Pack 3.8

2 Copyright 2008 Business Objects, an SAP company. All rights reserved. Business Objects owns the following U.S. patents, which may cover products that are offered and licensed by Business Objects: 5,295,243; 5,339,390; 5,555,403; 5,590,250; 5,619,632; 5,632,009; 5,857,205; 5,880,742; 5,883,635; 6,085,202; 6,108,698; 6,247,008; 6,289,352; 6,300,957; 6,377,259; 6,490,593; 6,578,027; 6,581,068; 6,628,312; 6,654,761; 6,768,986; 6,772,409; 6,831,668; 6,882,998; 6,892,189; 6,901,555; 7,089,238; 7,107,266; 7,139,766; 7,178,099; 7,181,435; 7,181,440; 7,194,465; 7,222,130; 7,299,419; 7,320,122 and 7,356,779. Business Objects and its logos, BusinessObjects, Business Objects Crystal Vision, Business Process On Demand, BusinessQuery, Cartesis, Crystal Analysis, Crystal Applications, Crystal Decisions, Crystal Enterprise, Crystal Insider, Crystal Reports, Crystal Vision, Desktop Intelligence, Inxight and its logos, LinguistX, Star Tree, Table Lens, ThingFinder, Timewall, Let There Be Light, Metify, NSite, Rapid Marts, RapidMarts, the Spectrum Design, Web Intelligence, Workmail and Xcelsius are trademarks or registered trademarks in the United States and/or other countries of Business Objects and/or affiliated companies. SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries. All other names mentioned herein may be trademarks of their respective owners. Third-party Contributors Business Objects products in this release may contain redistributions of software licensed from third-party contributors. Some of these individual components may also be available under alternative licenses. A partial listing of third-party contributors that have requested or permitted acknowledgments, as well as required notices, can be found at:

3 Contents Chapter 1 About these Release Notes 11 Chapter 2 Updates for BusinessObjects Enterprise XI R2 FixPack Show rows with empty dimension values was not working properly...14 Clicking the Cancel button in the progress bar when uninstalling Live Office FP, then inserting a Live Office object may cause an unspecified error...14 Chapter 3 Updates for BusinessObjects Enterprise XI R2 FixPack When scrolling on Voyager crosstab loading or processing message appears...16 CR Page Server terminates while refreshing Crystal Reports...16 Saving a Crystal Report with NO DATA saves parameter values after setting the datasource location...18 Chapter 4 Updates for BusinessObjects Enterprise XI R2 FixPack Updates for BusinessObjects Enterprise XI R2 FixPack Live Office returns internal error message after uninstalling client FixPack Web Intelligence reports that use Oracle as data source display only six decimal digits...20 Chapter 5 Updates for BusinessObjects Enterprise XI R2 FixPack Updates for BusinessObjects Enterprise XI R2 FixPack Ability to disable Export to Excel property without disabling other options...22 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes 3

4 Contents Chapter 6 Updates for BusinessObjects Enterprise XI R2 FixPack Updates for BusinessObjects Enterprise XI R2 FixPack Null values are not considered when multiple data providers are used in a single report...24 Web Intelligence report displays differently with the interactive viewer.24 Extended Daylight Savings Support: Australian Eastern Daylight Time, Australian Central Daylight Time and Tasmania...24 OLAP Security issue...25 Merging dimensions between two queries...26 Voyager reports do not open after uninstalling...26 Chapter 7 Updates for BusinessObjects Enterprise XI R2 FixPack Updates for BusinessObjects Enterprise XI R2 FixPack New check box Share prompt across queries in Crystal Reports...30 Tomcat memory issue...31 Overlap of text in Structure View in WebIntelligence...31 New and modified strings not yet translated...31 Chinese characters in PDF format...32 Chapter 8 Updates for BusinessObjects Enterprise XI R2 FixPack Updates for BusinessObjects Enterprise XI R2 FixPack Extended Daylight Savings Support: New Zealand and Western Australia...34 Impossible to refresh a Desktop Intelligence document in Infoview with a specific macro...35 The View Query Right...35 Voyager support for Essbase MetaRead security...35 Error in InfoView when browsing through cube BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

5 Contents Chapter 9 Installation 37 Silent installation options for reduced Desktop Intelligence installation...38 Installing BusinessObjects Enterprise in a 64-bit environment...38 BusinessObjects Enterprise Support in a 64-bit Environment...40 Installing on Windows bit operating system...41 Set Analyzer with 64-bit Windows Vista...41 MS SQL Server bit Native Client...41 The license key is not added to the CMS during installation...42 MetaDataPlugin InfoObject permissions...42 The fonts.xml file is corrupted during installation...42 Uninstalling Live Office results in a self-repair action in other BOE applications...43 The domain property of the dsws.properties is not updated with the CMS name and port number during installation...43 Uninstalling as part of the service pack sometimes causes an error to appear when opening the CMC in Java...44 Chapter 10 Deployment 45 Deploying desktop.war to a different location...46 Deploying BusinessObjects Enterprise applications on the IBM WebSphere application server...46 Using the desktop.war file in a distributed UNIX deployment of Performance Management XI R2 SP Error while setting up EPM servers on a different machine than the CMS and.net WCA...47 The PMDT is not migrating metric conditions...48 Security message appears in the Tomcat SSL mode...48 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes 5

6 Contents Chapter 11 Developer 51 In VS2003 WebApplication designtime and runtime, the toolbar and charts show up as a red X...52 Chapter 12 Data Access 53 Configuring SQL generation parameters for a universe in the Data Access Guide...54 Locked resources parameter in the Data Access Guide...55 REVERSE_TABLE_WEIGHT parameter in the Data Access Guide...55 RPT files with Oracle ODBC connections...55 Teradata driver Unicode settings for a Solaris platform...56 OLAP Intelligence connection not available with reverse proxy...56 No preview of NCHAR and NVARCHAR in Netezza...57 Chapter 13 BusinessObjects Enterprise 59 Incomplete documentation about scheduling events...60 BusinessObjects in 2-Tier mode session disappears if report execution is longer than WISESSION parameter...60 Exporting a query to a TXT file results in an unwanted decimal separator.60 Chapter 14 Desktop Intelligence 63 All REP sub-reports appearing in the same PDF...64 Chapter 15 Reporting 67 New window appears, despite the use of the command swindow=same.68 Chapter 16 InfoView 69 Search Indexing Program in InfoView BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

7 Contents Chapter 17 Information OnDemand 71 You can now access Information OnDemand from InfoView...72 Chapter 18 Web Intelligence 73 Web Intelligence help pages missing...74 Faulty cell display...74 For User with administrator rights, View SQL is disabled...74 Drill up does not work in the Firefox2 browser...74 Drag and drop in reports does not work in the Firefox2 browser...75 The NoFilter function does not work with block or quick filters...75 No database ranking for HP Neoview...75 The wrong error message appears when a user without correct access rights tries to schedule a Web Intelligence report...75 Not able to retrieve a prompt while rescheduling a Web Intelligence instance in History...76 Turning to a pie chart from a report with more than ten objects crashes the report server...76 Chapter 19 Crystal Reports 77 Arabic does not appear correctly using Oracle Client...78 Unable to create a Crystal report after deploying Adhoc.war application in WebLogic application server...78 HP NeoView problems in Crystal Reports...79 An Ad hoc filter placed on a universe date field should generate a date prompt instead of a datetime prompt...79 Chapter 20 Performance Management 81 Analytics...82 Gauge analytics...82 Analytics are not available using SharePoint BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes 7

8 Contents Problems with editing and viewing analytics without IE6 SP1 patches.82 Unable to create analytics based on a universe query that uses the measures with BEGIN_DATE and END_DATE prompts over a HP Neoview 2.2 connection...82 Applications...84 Deleting a subject from Set Architect causes errors in the Performance Management repository...84 An HTTP 500 error in Performance Manager My Goals...84 Set Analysis...84 Predictive Analysis models do not work with Sybase ASE Performance Management documentation...85 Chapter 21 Designer 87 Designer SQL generation parameters...88 Chapter 22 Voyager 89 Users are not allowed to view Voyager documents in InfoView...90 Chapter 23 Business Question 91 Error when trying to open a report from an encyclopedia link...92 Reports do not reflect InfoView preferences...92 Chapter 24 Live Office 93 In Live Office, you cannot create folders directly under the BOE Public folder...94 Chapter 25 Web Services 95 Working with Drill: Handling document reference in the CallbackScript BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

9 Contents Chapter 26 Auditing 97 New Auditing database 'document path' event detail...98 Chapter 27 Troubleshooting HTTP Errors 99 Troubleshooting HTTP 404 errors Resolving HTTP 500 errors Chapter 28 Business Objects Information Resources 103 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes 9

10 Contents 10 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

11 About these Release Notes 1

12 1 About these Release Notes These Release Notes contain important information about this product release, including the following: installation notes, details regarding known issues with this fix pack, and important information for product users. Business Objects recommends you read the entire document before installing your Business Objects software. Please also visit the Business Objects support web site for additional notes and information that may become available following the release of this document. These release notes include all issues that were documented for BusinessObjects XI Release 2 Service Pack 3 as well as all new issues included in all FixPacks from 3.2. For acknowledgements of third party contributors and applications, in addition to related license information, see 12 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

13 Updates for BusinessObjects Enterprise XI R2 FixPack 3.8 2

14 Updates for BusinessObjects Enterprise XI R2 FixPack Show rows with empty dimension values was not working properly "Show rows with empty dimension values" was not working properly The property "show rows with empty dimension values" was not working properly. It now works as designed, and if there are null values they won't be displayed unless this property has been checked. Clicking the Cancel button in the progress bar when uninstalling Live Office FP, then inserting a Live Office object may cause an unspecified error Clicking the Cancel button in the progress bar when uninstalling Live Office FP, then inserting a Live Office object may cause an unspecified error This is caused because the following files are not registered: crystal_addin_framework.dll cr_module.dll webi_module.dll core_module.dll ce_module.dll You can register those dll files to work around this issue. 14 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

15 Updates for BusinessObjects Enterprise XI R2 FixPack 3.6 3

16 Updates for BusinessObjects Enterprise XI R2 FixPack When scrolling on Voyager crosstab loading or processing message appears When scrolling on Voyager crosstab loading or processing message appears By default, the Voyager crosstab retrieves 60 rows and 40 columns (2400 cells) of data. This balances the rate at which data is retrieved and limits the frequency by which the data is fetched from the OLAP server. There are scenarios where administrators may wish to custom configure the number of rows and columns requested by a crosstab before another request from the server is required. For example, users may prefer to wait longer to fetch data but then be able to view more data without having to make more data requests. Another example is where the shape of the data favours vertical scrolling over horizontal scrolling. In this case it may be preferable to retrieve 120 rows and 20 columns, which is still 2400 cells and thus offers the same balance. You can change the number of rows and columns that are fetched by modifying the sdk-faces-config.xml file which is installed into the [install location]\program Files\Business Objects\Tomcat\webapps\busi nessobjects\enterprise115\desktoplaunch\web-inf\sdk-faces-con fig.xml To modify the scrolling values: 1. Search for the ScrollingConfiguration element. 2. Adjust the value properties of the managed-property crosstabrowfetchsize and crosstabcolumnfetchsize. 3. Save the file to the same location. CR Page Server terminates while refreshing Crystal Reports This issues applies to Crystal Reports that are created on BVM with Teradata that have more than This is an workaround fix. Teradata ParseSQL function which is used for parsing escape seqence in SQL statements will cause core dump at multiple thread situation. To change the querybuilder resource file make, it does not build escape string such as d{''}, oj{} in SQL statement so that customer can 16 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

17 Updates for BusinessObjects Enterprise XI R2 FixPack 3.6 CR Page Server terminates while refreshing Crystal Reports 3 set "NoScan=Yes" in ODBCINI to avoid core dump in Teradata ParseSQL funciton. NoScan=[ Yes No ] (Default = No) This option is used to enable/disable parsing of SQL statements by the driver. In Windows, this option is called "DisableParsing". When NoScan is Yes - the parser in the driver is bypassed and the SQL statement is sent directly to Teradata. This option should not be set when the SQL statement contains ODBC-specific syntax. Setting this option while using ODBC-specific syntax in the SQL statement results in Teradata Database reporting errors. When NoScan is No - the parser in the driver is not bypassed and SQL statements are sent to the parser. Also by bypassing the ParseSQL function of Teradata ODBC driver, the SQL statement of execute store procedure clause need to be rebuilt. Disable CALL To EXEC Conversion=[Yes No] (Default = No) This option implements the CALL statement with an escape clause, {CALL <name>(..)}. When Disable CALL To EXEC Conversion is No, the ODBC Driver for Teradata considers the {CALL <name>(..)} statement as the SQL for MACRO execution, and converts the above statement to an EXEC <name>(..). When Disable CALL To EXEC Conversion is Yes, the ODBC Driver for Teradata does not convert {CALL <name>(..)} statements to EXEC, and considers the statements as CALL statements for Stored Procedure Execution. Parsing the SQL is mandatory for this CALL statement with escape clauses to work. Hence, on Windows, the Disable Parsing option should not be selected. On UNIX, the NoScan option should not be selected. Since the teradata ODBC is not able to cope up with the multiple thread situation this fix is meant to workaround that issue and setting NoScan=Yes is needed for this to work. This would work for crystal reports and NoScan=Yes should be set for DSN used by crystal reports. BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes 17

18 Updates for BusinessObjects Enterprise XI R2 FixPack Saving a Crystal Report with NO DATA saves parameter values after setting the datasource location Saving a Crystal Report with NO DATA saves parameter values after setting the datasource location Command Table and Stored Procedure parameters have changed to match regular Crystal Reports parameter behavior and do not save their values with the report unless the Save Data with Report option is set to true. Previously, Command Table and Stored Procedure parameter values were incorrectly saved with the report even if the user had chosen not to include Saved Data. 18 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

19 Updates for BusinessObjects Enterprise XI R2 FixPack 3.5 4

20 Updates for BusinessObjects Enterprise XI R2 FixPack Updates for BusinessObjects Enterprise XI R2 FixPack 3.5 Updates for BusinessObjects Enterprise XI R2 FixPack 3.5 This chapter describes known issues with BusinessObjects Enterprise XI Release 2 FixPack 3.5. There is one new item added for FixPack 3.7 that exists since FixPack 3.5. There are two updates to FixPack 3.3. Live Office returns internal error message after uninstalling client FixPack3.5 To avoid the internal error with Live Office after uninstalling BusinessObjects XI Release 2 Client FixPack 3.5, you must run the gacutil /i command on the following binaries: BusinessObjects.DSWS.LiveOffice.dll CrystalDecisions.Windows.Forms.dll CrystalDecisions.Shared.dll For example, launch the command line and type: gacutil /i BusinessOb jects.dsws.liveoffice.dll Web Intelligence reports that use Oracle as data source display only six decimal digits In BusinessObjects Enterprise XI Release 2, Service Pack 3, when Oracle database is the report data source, even if value has more than six decimal digits, only six decimal digits display in the Web Intelligence report. This issue is fixed in FixPack BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

21 Updates for BusinessObjects Enterprise XI R2 FixPack 3.4 5

22 Updates for BusinessObjects Enterprise XI R2 FixPack Updates for BusinessObjects Enterprise XI R2 FixPack 3.4 Updates for BusinessObjects Enterprise XI R2 FixPack 3.4 This chapter describes known issues with BusinessObjects Enterprise XI Release 2 FixPack 3.4. Ability to disable Export to Excel property without disabling other options Two new rights have been added in the CMC for Web Intelligence documents to control the ability of users to save a Web Intelligence document in Excel or PDF Format: Export Report s Data (Excel) Export Report s Data (PDF) These rights work in conjunction with the Export the reports Data right for the Web Intelligence document. If the Export the reports Data right is granted, then the user will be able to save the document in both Excel and PDF Formats. To disable either one or both of the formats, you can: Deny Export the reports Data, this will disable both saving to Excel and PDF format. Deny "Export the reports Data", then grant either: "Export Report's Data (Excel)" to allow only Excel format or, "Export Report's Data (PDF)" to allow only PDF format. In Java Report Panel (JRP), the Excel and PDF option will be displayed for a report which has either one or all the formats disabled, an error message will be displayed when the user tries to save in the denied format. In Fix Pack 3.4, the error message displays only in English. 22 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

23 Updates for BusinessObjects Enterprise XI R2 FixPack 3.3 6

24 Updates for BusinessObjects Enterprise XI R2 FixPack Updates for BusinessObjects Enterprise XI R2 FixPack 3.3 Updates for BusinessObjects Enterprise XI R2 FixPack 3.3 This chapter describes known issues with BusinessObjects Enterprise XI Release 2 FixPack 3.3. Null values are not considered when multiple data providers are used in a single report In Web Intelligence documents, null values were not considered when multiple data providers were used in a single report. As a result, these values would not appear in reports instead of appearing blank. This issue was a regression which appeared in SP3 and has been fixed in FixPack 3.3. Web Intelligence report displays differently with the interactive viewer When a Web Intelligence document is created by aligning separate tables or cells so that they touch each other, the cells may be appear misaligned when the document is viewed with the HTML Viewer or the Interactive Viewer. This behavior is due to an HTML limitation, and there is no known workaround. If the document is viewed in PDF format, the alignment is correct but the thickness of the borders between adjacent tables is increased. The workaround for this is to eliminate cell borders when aligning tables. Extended Daylight Savings Support: Australian Eastern Daylight Time, Australian Central Daylight Time and Tasmania In Australia, the State governments of New South Wales, Victoria and Tasmania and the Australia Capital Territory (ACT) legislated in 2007 to extend and align the start and end dates of daylight saving time (DST) for 24 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

25 Updates for BusinessObjects Enterprise XI R2 FixPack 3.3 Updates for BusinessObjects Enterprise XI R2 FixPack the Australian Eastern Standard Time (AEST) time zone and Tasmania time zone. As of 2008, Australian Eastern Daylight Time (AEDT) begins at 2:00 am AEST on the first Sunday in October; and ends at 3:00 am AEDT, on the first Sunday in April. Tasmania now also aligns its daylight saving dates with Australian Eastern Daylight Time start and end dates. In addition, the State government of South Australia (SA) is to trial a pilot extension to Australian Central Daylight Time (ACDT) in 2008 to align South Australia start and end dates with the above states. ACDT now ends 3:00am ACDT, on the first Sunday in April 2008; and begins 2:00am Australian Central Standard Time, on the first Sunday in October A final decision on whether to keep the extended period is to be made after this 2008 trial ends. See Your BusinessObjects Enterprise XI system may not reflect Daylight Saving Time during the extended start and end DST periods for Australian South Eastern States or during the trial extended DST period for South Australia. The problem is fixed by applying this BusinessObjects Fix Pack in addition to the operating system and Java time zone patches from your OS and Java runtime vendors. In Crystal Reports, an affected area is the Crystal Reports formula function 'CurrentCEUserDateTime' and its related special field 'Current CE User Time Zone'. In this Fix Pack, Crystal Reports has been updated to return string values that comply with all the above Australian daylight saving changes OLAP Security issue For security reasons, starting from FixPack 3.3 existing Voyager connections with user specified logon need to be refreshed before they can be edited. This is done automatically when a connection is used through Voyager. If a connection with user specified logon has not been refreshed through Voyager, upon editing you will receive an error regarding the connection to the underlying cube. To work around the problem, re-enter the password for the user specified logon. BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes 25

26 Updates for BusinessObjects Enterprise XI R2 FixPack Updates for BusinessObjects Enterprise XI R2 FixPack 3.3 Merging dimensions between two queries If you have two queries in a Web Intelligence report where a dimension is synchronized between the two queries and you create a variable with count function on the dimension of an individual query, it returns the count of the merged query results if the variable appears in a table cell. If the variable appears in a free cell, the result returns the count of the individual query results. To force the variable to return the count of the individual query results in a table cell, do one of the following: Select the Extend merged dimension values check box in the "Document Properites" tab Remove the synchronization For example, if you have two queries synchronized on the dimension [State], there are five rows from query 1 results, and 10 rows from the merged query results. You add the formula "count( [query1].[state])" in a table cell, it returns 10. When you add the same formula in a free cell, it returns 5. You then select the option Extend merged dimension values or remove the synchronization and the formula results returns 5. This fix applies to BusinessObjects Enterprise XI R2 FixPack 2.8, FixPack 3.3, and Service Pack 4. For any prior version without this fix, the variable returns the count of the individual query results regardless of how you set the "Extend merged dimension values"option. Voyager reports do not open after uninstalling After uninstalling BusinessObjects Enterprise XI R2 FixPack 3.3 or later, existing Voyager reports do not open and new reports cannot be created because there are no available connections. For security reasons, existing voyager connections with user specified logon need to be refreshed before they can be edited. This is done automatically when a connection is used through Voyager. If a connection with user specified logon has not been refreshed through Voyager, upon editing you will receive an error regarding the connection to 26 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

27 Updates for BusinessObjects Enterprise XI R2 FixPack 3.3 Updates for BusinessObjects Enterprise XI R2 FixPack the underlying cube. To work around the problem, reenter the password for the user specified logon. If you decide to uninstall this patch, note that any Voyager connection that has been refreshed either automatically or manually will no longer function. Voyager workspaces based on these connections will also be affected and require recreation. Business Objects highly recommends that you do not uninstall this patch. Workaround: Reinstall the FixPack. BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes 27

28 Updates for BusinessObjects Enterprise XI R2 FixPack Updates for BusinessObjects Enterprise XI R2 FixPack BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

29 Updates for BusinessObjects Enterprise XI R2 FixPack 3.2 7

30 Updates for BusinessObjects Enterprise XI R2 FixPack Updates for BusinessObjects Enterprise XI R2 FixPack 3.2 Updates for BusinessObjects Enterprise XI R2 FixPack 3.2 This chapter describes known issues with BusinessObjects Enterprise XI Release 2 FixPack 3.2. New check box Share prompt across queries in Crystal Reports A new check box "Share prompts across queries" has been added in the Crystal Reports Query Panel. This new check box allows the user to be prompted only once if there are multiple prompts with the same definition. For example, Query A has three prompts: Country Region City Query A is linked to Query B, which has three prompts: Country Region Zip Code Without selecting the "Share prompts across queries" check box: When Query A is run, users are prompted for Country, Region, and City. When Query B is run, users are prompted again for Country and Region as well as Zip Code. If the "Share prompts across queries" check box is selected: When Query A is run, users are prompted for Country, Region, and City. When Query B is run, users are prompted only for Zip Code. Limitation: If the prompt definition is modified, the name of the prompt will change during resynchronization the next time the report is opened for scheduling or viewing. If references were made to the prompt name (like in a select clause), the new name is no longer recognized, and the report will no longer work. 30 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

31 Updates for BusinessObjects Enterprise XI R2 FixPack 3.2 Updates for BusinessObjects Enterprise XI R2 FixPack Workaround: The report needs to be opened in Crystal Reports Designer and all references to the prompt name updated with the new name. Note: The "Share prompts across queries" check box did not exist in FixPack 3.1. However, the shared prompt functionality was added as the default behavior for all new reports created with FixPack 3.1. Starting from FixPack 3.2, users have a choice of whether or not to activate this feature. Tomcat memory issue Known issues with Tomcat and BusinessObjects Enterprise include the following: When several web applications are deployed in the same Tomcat instance, an "out of memory" error may occur in the Tomcat logs, and the process may terminate unexpectedly. Workaround: Increase the maximum permanent generation size to 128M by adding -XX:MaxPermSize=128M in the JVM options in the Tomcat configuration. Overlap of text in Structure View in WebIntelligence When you create a section in a WebIntelligence document using the Java Report Panel, if you display the document in Structure View, the text "End of section on: <section name>" will overlap the table. This issue will be fixed in the next FixPack. New and modified strings not yet translated Some user interface strings and error messages added or modified to fix issues in this FixPack may not yet be translated and may appear in English. These texts will be translated for the next FixPack. BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes 31

32 Updates for BusinessObjects Enterprise XI R2 FixPack Updates for BusinessObjects Enterprise XI R2 FixPack 3.2 Chinese characters in PDF format The Tahoma font does not support the use of Chinese characters in PDF format. To display Chinese characters in a sans serif font for delivery to PDF format, install the font Arial Unicode MS, which will be used as the default font. If Arial Unicode MS is not installed, Tahoma will be used by default and the characters will fail to be displayed. 32 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

33 Updates for BusinessObjects Enterprise XI R2 FixPack 3.1 8

34 Updates for BusinessObjects Enterprise XI R2 FixPack Updates for BusinessObjects Enterprise XI R2 FixPack 3.1 Updates for BusinessObjects Enterprise XI R2 FixPack 3.1 This chapter describes known issues with BusinessObjects Enterprise XI Release 2 FixPack 3.1. Extended Daylight Savings Support: New Zealand and Western Australia Background: in April 2007 the New Zealand Government announced an update to the Time Act of 1974 which extends both the start and end dates of daylight saving time (DST). In 2007, daylight savings time will start one week earlier (2:00 A.M. on the 30th September 2007) and will end two weeks later (3:00 A.M. on 6th April 2008) than past years. In Western Australia, the State Government has introduced daylight saving time for a three-year trial period starting December In 2007 and 2008, daylight saving will begin at 2am Western Standard Time on the last Sunday in October, and end at 2am Western Standard Time (3am summer time) on the last Sunday in March the following year. A referendum will be held in 2009 to decide whether this should become permanent in Western Australia. See Impact: your BusinessObjects Enterprise XI R2 system may not reflect Daylight Saving Time during the extended start and end DST periods for New Zealand or during the new DST period for Western Australia. The problem is fixed by applying this BusinessObjects Fix Pack in addition to the operating system and Java patches from your OS and Java runtime vendors. In Crystal Reports, an affected area is the Crystal Reports formula function CurrentCEUserDateTime and its related special field Current CE User Time Zone. In this Fix Pack, Crystal Reports has been updated to return string values that comply with the above changes to New Zealand and Western Australian Daylight Saving Time. 34 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

35 Updates for BusinessObjects Enterprise XI R2 FixPack 3.1 Updates for BusinessObjects Enterprise XI R2 FixPack Impossible to refresh a Desktop Intelligence document in Infoview with a specific macro If you have document with Macro having "applicationinteractive=true" in the code, you will experience a problem viewing the document in Infoview. Workaround: do not set applicationinteractive=true in Macro for the document which is viewed in Infoview. The View Query Right The "View SQL" right is newly added at the Web Intelligence Application level in XI R2 SP3. This right allows an administrator to control a user to view a SQL statement in the Web Intelligence Query Panel or not. Even when the right is set to "Disable", it will work only during the creation of a new Web Intelligence document. Once the document is saved, a user can view the SQL statement in edit mode. This issue will be addressed in the next FixPack. Voyager support for Essbase MetaRead security Voyager supports connections to Essbase cubes that have MetaRead permissions defined on members. Voyager respects the restrictions put in place by such permissions, by limiting the members that users can see in the metadata explorer and member selector. Any cells containing data that have been restricted by MetaRead permissions, such as data for all ancestors of a restricted member, appear as NULL cells (blank by default). This means that the default view of data is often blank, because the default member selection consists of the top level parent members. You can see data by changing your member selection to members that don't have restricted descendants. BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes 35

36 Updates for BusinessObjects Enterprise XI R2 FixPack Updates for BusinessObjects Enterprise XI R2 FixPack 3.1 Error in InfoView when browsing through cube There is a connection pool to keep track of connections. When a connection is deleted from a workspace it is not deleted immediately but instead remains in the connection pool for 2 minutes. This provides better performance if you wish to reconnect. After this pause the deleted connection is destroyed by the connection monitor. Consequently, if Voyager alerts you that there have been structural changes to the cube, you must log off and wait for 2 minutes to avoid errors. This ensures the connection is removed from the connection pool before trying again. 36 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

37 Installation 9

38 Installation 9 Silent installation options for reduced Desktop Intelligence installation Silent installation options for reduced Desktop Intelligence installation The client tools silent installation allows you to deploy only the tools you select, for example, Desktop Intelligence. The following silent installation parameters were added to the BusinessObjects Enterprise XI R2 SP3 client installation: NO_Samples allows you to exclude Xtreme databases from the Client Tools Install. NO_Templates allows you to exclude Visual Studio 2005 templates. NO_Log disables the installation logging. NO_Webhelp excludes the WebIntelligence online help, InfoView Guide, and administrator guides from the installation as these are not required in a standalone Desktop Intelligence installation. Each installation parameter, when set to 1 in a silent installation command, excludes a significant component from the installation of BusinessObjects Enterprise XI R2 SP3. When you use them all, the installation footprint of the BusinessObjects Enterprise Client Tools is reduced to approximately 390 MB. When used separately: NO_Samples offers approximately 100 MB of size reduction. NO_Templates offers approximately 10 MB of size reduction. NO_Log provides 50 MB of size reduction. NO_Webhelp offers approximately 200 MB of size reduction. Each parameter can be used independently of or in combination with the other silent installation parameters. Installing BusinessObjects Enterprise in a 64-bit environment The steps for Installing BusinessObjects Enterprise on a 64-bit Operating System are the same as installing on a 32-bit Operating system. Refer to 38 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

39 Installation Installing BusinessObjects Enterprise in a 64-bit environment 9 the BusinessObjects Enterprise installation documentation (Windows or Unix) for detailed instructions. Note: BusinessObjects installations run in 32-bit compatibility mode in a 64-bit environment. 1. Install BusinessObjects Enterprise XI Release 2 Service Pack 2. Note: The installer does not allow you to install to a directory that has parentheses "(" or ")" in its name. As a result, the default directory, \Program Files (x86)\business Objects, is invalid. Instead, BusinessObjects Enterprise should be installed in the \Program Files\Business Objects directory. 2. Log on to Central Management Console. 3. In the "Users" page, reset the administrator password. 4. In the "License Keys" page, enter a valid license key. 5. In the "Servers" page, select the BusinessObjects Enterprise servers and enable them. Note: If you are using Live Office, creation of Web Intelligence reports is not currently supported in InfoView on a 64-bit Linux Operating System. 6. If necessary, import sample universes and/or sample Crystal Reports into your BusinessObjects Enterprise system. 7. If you are using Crystal Reports and the database server is Microsoft SQL Server 2005, ensure that you have the latest version of SQL Server 2005 Feature Pack installed to obtain the latest 64-bit Microsoft SQL Server Native Client. After installing the driver, you should set up your Microsoft SQL Server 2005 data source using the 32-bit ODBC Administrator. Note: The ODBC DSNs displayed in the Report Creation Wizard are only 32-bit ODBC DSNs. If you have a 64-bit database server, ensure that you have installed the 32-bit ODBC data access driver that is supported by your database server. If you have a 64-bit Oracle OLE DB data source in your deployment, install the 32-bit Microsoft OLE DB Provider for Oracle. BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes 39

40 Installation 9 Installing BusinessObjects Enterprise in a 64-bit environment 8. Install BusinessObjects Enterprise XI Release 2 Service Pack 3 to update your BusinessObjects installations. BusinessObjects Enterprise Support in a 64-bit Environment The following operating system/chipset combinations are supported for BusinessObjects Enterprise and Crystal Reports installations: Windows 32-bit on 64-bit AMD/Intel chipset Windows 64-bit on 64-bit AMD/Intel chipset Linux (Red Hat and SUSE) 32-bit on 64-bit AMD/Intel chipset Linux (Red Hat and SUSE) 64-bit on 64-bit AMD/Intel chipset Sun SPARC 64-bit: supported for BOE* IBM AIX RISC 64-bit: supported for BOE* HP-UX on PA-RISC 64-bit: supported for BOE* Note: *The data access drivers used by BusinessObjects Enterprise and Crystal Reports must also be 32-bit, but the database server software, operating system, and chipset can be what the database vendor supports. On 64-bit Windows, you cannot mix 32-bit and 64-bit executables, so it is not possible to use the 64-bit DB drivers. Note: On 64-bit Windows, there is a 32-bit ODBC Administrator and a 64-bit ODBC Administrator. Also, there are 32-bit ODBC registry and 64-bit ODBC registries. If you set up a data source (DSN) using the default 64-bit ODBC Administrator, that DSN will not appear for 32-bit applications. The name of the ODBC Administrator application is called odbcad32.exe for both 32-bit and 64-bit versions. On 64-bit Windows, the ODBC Administrator is located in the following locations: 64-bit ODBC Administrator: %SystemRoot%\system32\odbcad32.exe 32-bit ODBC Administrator: %SystemRoot%\SysWOW64\odbcad32.exe 40 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

41 Installation Installing BusinessObjects Enterprise in a 64-bit environment 9 Installing on Windows bit operating system When you install BusinessObjects Enterprise XI R2 Service Pack 3 on a Windows bit operating system with.net 1.1, and then open.net InfoView or.net CMC running off of IIS, you receive a 'Service Unavailable' error. In 64-bit Windows operating systems, 64-bit processes can only load 64-bit DLLs, and 32-bit processes can only load 32-bit DLLs. By default, IIS6 on 64-bit Windows runs with 64-bit W3WP.EXE processes, but.net Framework 1.1 as ASP.Net implemented through 32-bit ISAPI DLLs, so the W3WP.EXE processes for IIS6 cannot load the DLLs for ASP.Net. To fix this issue, run the following command to force IIS6 to run W3WP.EXE as a 32-bit application in WOW64 (32-bit compatibility) mode: CSCRIPT C:\Inetpub\AdminScripts\adsutil.vbs SET W3SVC/App Pools/Enable32bitAppOnWin64 1 You need to restart IIS6. Use the following command: NET STOP W3SVC /y & NET START W3SVC Set Analyzer with 64-bit Windows Vista Full Client Set Analyzer does not work with the 64-bit version of Windows Vista. MS SQL Server bit Native Client MSSQL Server bit Native Client is not supported on 64-bit platform. BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes 41

42 Installation 9 MetaDataPlugin InfoObject permissions The license key is not added to the CMS during installation When you install BOE XI R2 SP3 on a 64-bit operating system, a valid license key is not added automatically to the Central Management Console in CMC > License Keys. Workaround: 1. Log on as an administrator to the Central Management Console. 2. Go to CMC > License Keys. 3. Add the license key. MetaDataPlugin InfoObject permissions If you are upgrading from BusinessObjects Enterprise (BOE) XI R2 SP2 to BOE XI R2 SP3, you may encounter an issue with the permissions associated with the MetaDataPlugin InfoObject. In BOE XI R2 SP2, only administrators were assigned view rights on the MetaDataPlugin InfoObject. As of BOE XI R2 SP3 everyone has view rights set for this InfoObject. Therefore if you are installing BOE XI R2 SP3, and migrating the objects from your BOE XI R2 SP2 Central Management Server (CMS), you may have a problem accessing the MetaDataPluginInfoObject. Workaround: 1. Delete the MetaDataPlugin InfoObject from the CMS using the BOE SDK. 2. Restart the CMS. The fonts.xml file is corrupted during installation In the Solaris version of Voyager, an error occurs when you click the "Print to PDF" icon from a Voyager workspace. This happens because during the installation of BOE XI R2 SP3, the fonts.xml file you customized in a previous BOE installation is overwritten. 42 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

43 Installation Uninstalling Live Office results in a self-repair action in other BOE applications 9 Workaround: All files that are overwritten during installation are stored in a located in the base folder {$INSTALL_DIR}/patch/sp3/backup. Restore fonts.xml from this backup and use it to replace the installed version in the following location: [$INSTALL_DIR]/bobje/enterprise115/ solaris_sparc/com/businessobjects/ multidimensional/services Uninstalling Live Office results in a self-repair action in other BOE applications In Windows, launching applications like Crystal Reports, Business View Manager and OLAP Intelligence, after uninstalling Live Office, starts a self-repair action for review After you uninstall Live Office and then launch either Crystal Reports, Business View Manager or OLAP Intelligence, a configuration screen appears with the following message: "Please wait while Windows configures BusinessObjects Enterprise XI Release 2" Caution: Do not select Cancel. The configuration process takes approximately five minutes to complete, and then the respective application, as well as other applications will launch without any problem. The domain property of the dsws.properties is not updated with the CMS name and port number during installation BOE XI R2 SP3 does not automatically update the domain property. If the Central Management Server (CMS) in not running on default CMS port, you need to update it. BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes 43

44 Installation 9 Uninstalling as part of the service pack sometimes causes an error to appear when opening the CMC in Java Workaround: Enter the port number with the CMS name in the domain property of the dsws.properties file, then redeploy the dswsbobje.war file. Uninstalling as part of the service pack sometimes causes an error to appear when opening the CMC in Java After uninstallation using BOE XI R2 SP3, an HTTP Status 404 error may appear when you try to launch the Central Management Console using Java. If this happens, try the following: Wait for Tomcat to redeploy the war file. If the problem persists, manually restart Tomcat. As a last effort manually redeploy the war files. 44 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

45 Deployment 10

46 Deployment 10 Deploying desktop.war to a different location Deploying desktop.war to a different location To deploy desktop.war to a location other than the default location, remove the following files: aa-browsercheck.html aa-quickbrowsermenu.html from the following directory: <Business Objects Install Dir >\BusinessObjects Enterprise 11.5\java\applications Deploying BusinessObjects Enterprise applications on the IBM WebSphere application server Business Objects recommends the following best practices for deploying BusinessObjects Enterprise applications on the IBM WebSphere Application Server. Deploy your BusinessObjects Enterprise system by using one of the following methods: the WebSphere installation tool wdeploy script manually In each case, it is highly recommended that you deploy the WAR files in the order listed: Webcompadapter jsfadmin jsfplatform admin infoview (desktop.war) adhoc 46 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

47 Deployment Using the desktop.war file in a distributed UNIX deployment of Performance Management XI R2 SP3 10 styles analysishelp dswsbobje afhlep Using the desktop.war file in a distributed UNIX deployment of Performance Management XI R2 SP3 If you install BusinessObjects Enterprise, without the Performance Management components, on one directory and then install Performance Management, without the BusinessObjects Enterprise components in a DIFFERENT directory, the desktop.war present in the Performance Management directory is the updated desktop.war that contains both BusinessObjects Enterprise and Performance Management. Because of this, you cannot log into Performance Management. Workaround: Redeploy to the BusinessObjects Enterprise Tomcat directory the deskop.war in the Performance Management directory. Error while setting up EPM servers on a different machine than the CMS and.net WCA An "initconfig file doesn t exist" error is returned when you log into InfoView where there is an Expand installation on a secondary server in an environment with the following configuration: Primary machine CMS cache server job server Java.Net WCA Secondary machine processing server BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes 47

48 Deployment 10 The PMDT is not migrating metric conditions performance management servers pointing to the primary machine To avoid the error, do the following: 1. Create a folder named "Performance Management 11.5" under the BusinessObjects installation directory on the machine where.net WCA is installed, and not on the box on which the performance management servers are installed. 2. Manually deploy the war files, copying from the machine on which EPM is installed. 3. Copy the Initconfig.properties file to the Performance Management 11.5 folder. The PMDT is not migrating metric conditions In Windows, the Performance Management Deployment Tool is not migrating metrics correctly, and the condition in the target system is set to none. This occurs for all metrics created off a specific universe. If you refresh the metric there is no filter applied and the resulting data for the metric is not correct. Workaround: Move the conditions and filters from the universe to the same class/subclass as the measure. Security message appears in the Tomcat SSL mode In Windows, the following browser security message appears: "This page contains both secure and nonsecure items. Do you want to display the nonsecure items?" In the following situations: when viewing a Crystal Reports report in Java and ActiveX Viewer in a new full screen browser window while displaying dashboard analytics in Flash mode in InfoView with Apache Reverse Proxy server 48 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

49 Deployment Security message appears in the Tomcat SSL mode 10 This happens when the Secure Socket Layer (SSL) mode is activated in Tomcat, and the Use Macromedia Flash when available option is activated in InfoView Preferences > Performance Management. This is a bug in Internet Explorer ( Workaround: You need to change an Internet Explorer setting: 1. In Internet Explorer, go to Tools > Internet Options > Security. 2. Select the appropriate zone for the server. If you don t know the exact zone, contact your network administrator. 3. Click Custom Level. 4. Under "Miscellaneous", enable "Display mixed content". BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes 49

50 Deployment 10 Security message appears in the Tomcat SSL mode 50 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes

51 Developer 11

52 Developer 11 In VS2003 WebApplication designtime and runtime, the toolbar and charts show up as a red X In VS2003 WebApplication designtime and runtime, the toolbar and charts show up as a red X In Windows with.net, when you use VS2003 WebApplication designtime, the toolbar show up as red X's. In runtime, the toolbar and charts show up as red X's.The folder and files of crystalreportviewers115 do exist and its path is correct. BusinessObjects Enterprise XI R2 SP3 patch installer does not alter IIS metabase settings. Workaround: 1. Delete the virtual directory of crystalreportviewers115 in the IIS. 2. Recreate it with the same name, and point to the following path: [BusinessObjects installation directory]\common\3.5\crystalreportviewers Run iisreset in the command prompt. 52 BusinessObjects Enterprise XI R2 FixPack 3.8 Release Notes