IBM Cognos 8 Business Intelligence

PowerPlay

README

Product Information
This document applies to IBM Cognos 8 Version 8.4 and may also apply to subsequent releases. To check for newer versions of this document, visit the IBM Cognos Resource Center (http://www.ibm.com/software/data/support/cognos_crc.html).

Copyright
Copyright 2008 Cognos ULC (formerly Cognos Incorporated). Cognos ULC is an IBM Company. Portions of Cognos ULC software products are protected by one or more of the following U.S. Patents: 6,609,123 B1; 6,611,838 B1; 6,662,188 B1; 6,728,697 B2; 6,741,982 B2; 6,763,520 B1; 6,768,995 B2; 6,782,378 B2; 6,847,973 B2; 6,907,428 B2; 6,853,375 B2; 6,986,135 B2; 6,995,768 B2; 7,062,479 B2; 7,072,822 B2; 7,111,007 B2; 7,130,822 B1; 7,155,398 B2; 7,171,425 B2; 7,185,016 B1; 7,213,199 B2; 7,243,106 B2; 7,257,612 B2; 7,275,211 B2; 7,281,047 B2; 7,293,008 B2; 7,296,040 B2; 7,318,058 B2; 7,325,003 B2; 7,333,995 B2. Cognos and the Cognos logo are trademarks of Cognos ULC (formerly Cognos Incorporated) in the United States and/or other countries. IBM and the IBM logo are trademarks of International Business Machines Corporation in the United States, or other countries or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. Cognos does not accept responsibility for any kind of loss resulting from the use of information contained in this document. This document shows the publication date. The information contained in this document is subject to change without notice. Any improvements or changes to the information contained in this document will be documented in subsequent editions. U.S. Government Restricted Rights. The software and accompanying materials are provided with Restricted Rights. Use, duplication, or disclosure by the Government is subject to the restrictions in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer clause at DFARS 252.227-7013, or subparagraphs (C)(1) and (2) of the Commercial Computer Software - Restricted Rights at 48CFR52.227 as applicable. The Contractor is Cognos Corporation, 15 Wayside Road, Burlington, MA 01803. This document contains proprietary information of Cognos. All rights are reserved. No part of this document may be copied, photocopied, reproduced, stored in a retrieval system, transmitted in any form or by any means, or translated into another language without the prior written consent of Cognos.

Table of Contents
Chapter 1: IBM Cognos 8 Business Intelligence PowerPlay Server Readme

Review the Readme Updates 5 Review the Fix List 5 Limitations 5 Installation and Configuration Limitations 5 PowerPlay Limitations 6 Migration Limitations 6 Drill Through Limitations 7 Installation and Configuration Known Issues 7 Error After Installing PowerPlay Administration With Existing PowerPlay Server Installation 7 Migration Known Issues 7 Migration of Upfront Reports Fails Due to Missing Data Source 7 Upfront Report Created Using the Save As Command in PowerPlay Web Fails to Run After Migration 8 Empty Folder Named "cubes" Created After Migrating from IBM Cognos Connection 8 Starting the Series 7 Migration Service Returns an Error 8 Unable to Run PowerPlay Studio Report Opened in Report Studio 9 Custom View Migrated from Personal NewsBox Appears as a Broken Link 9 Custom View Migrated a Second Time Appears as a Broken Link 9 Migration Errors when Cube or Folder Name Contains Certain Japanese Characters 10 Error Message not Clear when Migrating Upfront Content from a Series 7 Distributed Installation Environment 10 "Bad Address" Error Appears in Migration Assistant on AIX 10 Scheduled Migration Tasks Fail with Communication Error 11 Problems Migrating Reports with Internal Path Names Exceeding 255 Characters 11 Problems Migrating Cubes with non-ASCII Characters on UNIX 11 Unable to Migrate Reports on UNIX when Path Names Contain Certain European Characters 13 Missing Brackets in Bookmark Conversion Utility Script Function 13 PowerPlay Known Issues 14 Report Viewed from Output Versions List Always Opens in Cognos Viewer 14 Continuous Prompting for Data Source Selection When Running a PowerPlay Report 14 Error When an Agent Runs a PowerPlay Report 14 Report Output Versions are not Accessible from View Run History for PowerPlay Reports 15 PowerPlay Administration Activities Do Not Appear in the PowerPlay Audit Logs 15 Index

17

Readme 3

Table of Contents

4 PowerPlay

Chapter 1: IBM Cognos 8 Business Intelligence PowerPlay Server Readme

This Readme contains late-breaking information about known issues, including installation issues, limitations, and deprecation notices. The documentation included in this release is current as of October 2008.

Review the Readme Updates

The Readme Updates document contains issues that arise after the product is released. We recommend that you review the Readme Updates.

Steps
1. Go to the IBM Cognos Resource Center (http://www.ibm.com/software/data/support/cognos_ crc.html). 2. Click Documentation. 3. Navigate to the Readme Updates for your product.

Review the Fix List

The fix list is a list of the known issues that were addressed in this release. We recommend that you review the fix list.

Steps
1. Go to the IBM Cognos Resource Center (http://www.ibm.com/software/data/support/cognos_ crc.html). 2. Click Documentation, then click Troubleshoot. 3. Navigate to the fix list for your product.

Limitations
The following limitations exist for this release.

Installation and Configuration Limitations

The following limitations affect the installation or configuration of IBM Cognos 8 PowerPlay.

Readme 5

Chapter 1: IBM Cognos 8 Business Intelligence PowerPlay Server Readme

Installing IBM Cognos 8 PowerPlay With IBM Cognos 8

In a distributed IBM Cognos 8 environment, you must install PowerPlay components on all computers. If the IBM Cognos 8 environment uses a computer with an operating system that is not supported for IBM Cognos 8 PowerPlay then IBM Cognos 8 PowerPlay Server is not supported in this environment. For example, if you have IBM Cognos 8 BI Server application tier components installed on both an HP Itanium server and on a Windows server, you can not install IBM Cognos 8 PowerPlay into this environment. To review an up-to-date list of environments supported by IBM Cognos products, such as operating systems, patches, browsers, Web servers, directory servers, database servers, and application servers, visit the IBM Cognos Resource Center (http://www.ibm.com/software/data/support/cognos_crc. html).
nba

PowerPlay Limitations
Administration
Command line administration options are not supported.

Data Sources
Like IBM Cognos Series 7, for PowerPlay Client we recommend that you use cubes on the same operating system and with the same encoding as used for building the cube. IBM Cognos PowerCubes are the only supported data source. 3rd party OLAP data sources are not supported.

IBM Cognos 8 Features

Integration with IBM Cognos Go! components is not complete. Watch rules are not supported for PowerPlay reports.

Samples
Sample cubes and reports are available on the IBM Cognos 8 Business Intelligence Samples CD.

Migration Limitations
Source Content
We recommend that you do not migrate more than 1500 objects at one time.

6 PowerPlay

Chapter 1: IBM Cognos 8 Business Intelligence PowerPlay Server Readme

Drill Through Limitations

Administration
Some administration settings may not work. You can not hide a report used as a drill through target.

Transformer
Drill through targets that use non-English character sets are not supported.

Dynamic Filtering
Drill through with dynamic filtering to reports created in Analysis Studio is not supported.

PowerPlay Studio
Drill through based on multiple cell selections is not supported. Select a single cell for drill through.

Installation and Configuration Known Issues

The following known issues exist for installation and configuration.

Error After Installing PowerPlay Administration With Existing PowerPlay Server Installation
When you install PowerPlay Administration on top of an existing PowerPlay Server installation, and then click on the PowerPlay tab in IBM Cognos Administration, the following error may appear Unable to process the document, the target is not valid or the target was not received. To access PowerPlay Administration, you must uninstall and reinstall PowerPlay Server including the PowerPlay Administration component. We recommended that you back up important files to ensure no data is lost during the reinstallation process. For more information about backing up files, see the IBM Cognos 8 PowerPlay Installation and Configuration Guide.
595925

Migration Known Issues

The following known issues exist for migration.

Migration of Upfront Reports Fails Due to Missing Data Source

Reports published to Upfront that have an empty field for the data source information are not migrated. The migration task contains errors that it cannot find the related data source for the reports. To work around this problem, republish the report from PowerPlay Enterprise Server.
595881

Readme 7

Chapter 1: IBM Cognos 8 Business Intelligence PowerPlay Server Readme

Upfront Report Created Using the Save As Command in PowerPlay Web Fails to Run After Migration
A Series 7 PowerPlay report that is created using the Save As command in PowerPlay Web fails to run after migration. The following error appears in the migration task history: MGD-msg-0479 Cube mapping entry was not found for the following source mapping: Your Cube Name This causes an error in the migration task and, although the report appears in the Cube Mapping page of the Migration Assistant and you can migrate it, the report does not run because the package link is unavailable. This is because the Upfront data source information points to the original report instead of to the data source. The Upfront data source information for the original report published from PowerPlay Enterprise Server correctly points to the data source. To work around the problem, do one of the following: Include the original report in the migration task. In IBM Cognos Connection, click the Set properties button for the report and set the package link to the correct package.

598428

Empty Folder Named "cubes" Created After Migrating from IBM Cognos Connection
After performing a migration with IBM Cognos Connection as the migration source, an empty folder named "cubes" is created in the migrated content location. Objects are migrated successfully and the package related to cube references was migrated to the PowerPlay folder. You can safely remove the empty folder.
588104

Starting the Series 7 Migration Service Returns an Error

Starting the IBM Cognos Series 7 migration service returns an error message. If the migration service is started from Windows Services, the following message appears: The IBM Cognos Series 7 Migration Services on Local Computer started and then stopped. If the migration service is started by running the migs7service_config -config command, the following error message appears: Failed to load csx file. This problem may occur if the cer5.csx file is missing from the S7_install/bin directory. To resolve the problem, create the cer5.csx file by reapplying the configuration setting.

Steps to Reapply the Configuration Setting

1. In Configuration Manager, open the current configuration. 2. In the Components tab, select the root node.

8 PowerPlay

Chapter 1: IBM Cognos 8 Business Intelligence PowerPlay Server Readme 3. From the Actions menu, click Apply Selection. 4. If the cer5.csx file is not created in the bin directory, reinstall PowerPlay Enterprise Server. 5. Start the Series 7 migration service.
575218

Unable to Run PowerPlay Studio Report Opened in Report Studio

When running a PowerPlay Studio that was opened in Report Studio using the Open with Report Studio command, an error like the following appears: OP-ERR-0182 Invalid parameter '[T2549(non zero-suppressed on row)]' provided for 'filter' at position '1' for 'dataItem="T2549(zero-suppressed on row)"'. This problem occurs when a parameter in a data item expression is of numeric type but the expected type is memberset. This may occur if the report contains a calculation to which zero suppression was applied. To resolve the problem, in Report Studio, change the parameter's type from numeric to memberset. For example, the first parameter in the following expression is of numeric type. filter([T2549(non zero-suppressed on row)],((tuple([cubes/0406Great Outdoors].[Years].[Years]. [Years]->:[PC].[@MEMBER].[CONVERSION_DATE]) <> 0) and (tuple([cubes/0406Great Outdoors].[Years].[Years].[Years]->:[PC].[@MEMBER].[CONVERSION_DATE]) is not null))) Changing the first parameter to the following changes its type to memberset. member([T2549(non zero-suppressed on row)],'','',hierarchy([cubes/0406Great Outdoors]. [Locations].[Locations]))
607951

Custom View Migrated from Personal NewsBox Appears as a Broken Link

A custom view migrated from a personal NewsBox appears as a broken link in IBM Cognos Connection. The custom view's icon is also missing. The migration process does not support migrating custom view reports saved to a personal NewsBox that were created from reports that are also located in a personal NewsBox. Although such custom view reports are migrated, they appear as broken links. To resolve the problem, move the original report to a public NewsBox. When you migrate the contents of the public NewsBox and the personal NewsBox, the custom view is successfully migrated. Note: Ensure that you include the cube that the report references in the migration task.
604119

Custom View Migrated a Second Time Appears as a Broken Link

When migrating the same custom view of a report a second time, the link is broken in IBM Cognos Connection. To resolve the problem, do one of the following:

Readme 9

Chapter 1: IBM Cognos 8 Business Intelligence PowerPlay Server Readme Remove the migrated reports from the first migration and redo the migration. Use cut and paste to move the migrated reports to a new folder and redo the migration.

605492

Migration Errors when Cube or Folder Name Contains Certain Japanese Characters
When migrating a report that references a cube whose name is the Japanese Shift-JIS codepoint 0x8150, 0x815C, 0x815F, 0x8160, 0x8161, 0x817C, 0x818F, 0x8191, 0x8192, or 0x81CA, you may encounter the following error messages: MGD-msg-0482 Unable to create the following path in IBM Cognos 8: MGD-msg-0413 The following messages are returned from IBM Cognos 8: MGD-msg-0480 Invalid cube mapping. The target path does not exist or cannot be created. Source: /cubes/Japanese//, target location: /content/folder[@name="??????"]/folder[@name="PowerPlay"]/ folder[@name="cubes"]/folder[@name="Japanese"]/folder[@name="" where "??????" represents "Migrated Content" in Japanese. In the last error message above, a folder already exists that is similar to the target path that could not be created. The existing folder is named U+FFE0 (full-width cent sign), and the migration task is attempting to create a folder named U+00A2 (cent sign). Both are potential Unicode renderings of the Shift-JIS codepoint 0x8191. To resolve the problem, rename or delete the existing folder with the similar name and redo migration.
609798

Error Message not Clear when Migrating Upfront Content from a Series 7 Distributed Installation Environment
When migrating Upfront content from a Series 7 environment where PowerPlay Enterprise Server services and Upfront services are on two different computers, the migration fails if the PowerPlay Enterprise Server services are stopped. The following error message appears: MGD-msg-0440 A communication error has occurred with <host name> on port <port number>. Verify that the Series 7 migration server name and port number are correct. The error message does not clearly indicate that the PowerPlay Enterprise Server could not be contacted.
607029

"Bad Address" Error Appears in Migration Assistant on AIX

When running the Migration Assistant on AIX, one of the following error messages appears: Bad Address A memory address is not in the address space for the process. To resolve the problem, obtain and install the fileset for APAR IY76141 on the Series 7 server. Then reboot your computer. 10 PowerPlay

Chapter 1: IBM Cognos 8 Business Intelligence PowerPlay Server Readme

608227

Scheduled Migration Tasks Fail with Communication Error

When more than one migration task is scheduled to run at the same time, one task fails. The following error appears in the failed task's run history details: MGD-msg-0440 A communication error occurred with host <host name> on port <port number>. Verify that the Series 7 migration server name and port number are correct. To work around the problem, schedule the migration tasks to run in sequence.
609713

Problems Migrating Reports with Internal Path Names Exceeding 255 Characters
When migrating Upfront content, if the number of characters used for the folder name and report name exceeds 255 characters, the migration fails. The following error appears: S7S-err-0813 Exception encountered parsing IBM Cognos Deployment Manager errors and warning from file: UNEXPECTED INTERNAL ERROR: CDM dump is missing the "PPES.packletLocation" property. PowerPlay Enterprise Server may also generate a core file in the S7_install/bin/ directory. When path names exceed 255 bytes in length, the IBM Cognos Series 7 PowerPlay Enterprise Server process may overflow a buffer. In particular, you may want to check the length of your paths in the PPSRoot directory. For example, S7_install/ppserver/PPSRoot/... You are most likely to encounter this problem on UNIX UNIX usually permits path names of 1023 or more bytes. Windows limits path names to 260 bytes when using the APIs that PPES uses. when using a multi-byte language such as Japanese A single character can occupy two or more bytes. Consequently, path names can reach the 255 byte limit with fewer characters. To work around the problem, contact the IBM Cognos Resource Center for a software update to address bug 603523. Alternatively, you can avoid the problem by selecting to migrate only NewsBoxes containing reports with path names that are less than 255 characters in length. Or rename the report and NewsBox names so that they use less than 255 bytes.
603523

Problems Migrating Cubes with non-ASCII Characters on UNIX

If the IBM Cognos Series 7 PPES service is using a non-ASCII path name to access a PowerCube and the IBM Cognos 8 server is running in a locale that uses a different character set, then the IBM Cognos 8 server is unable to locate the referenced PowerCube on disk. For example, the PPES service is using a Japanese name encoded in Shift-JIS using the Solaris locale ja_JP.PCK and the IBM

Readme 11

Chapter 1: IBM Cognos 8 Business Intelligence PowerPlay Server Readme Cognos 8 server is running in the locale ja_JP.UTF-8. As a result, the migration of reports that depend on the PowerCube fails with error messages like the following: MGD-msg-0424 IBM Cognos 8 is unable to create the following data source: cubes/Japanese/<Japanese characters> MGD-msg-0422 MigDeploy Exception: MGD-msg-0432 Invalid data source parameters. The path to the physical cube is not specified. The procedure to work around the problem depends on whether you want to use the same or different locale setting in IBM Cognos 8 as in IBM Cognos Series 7. If you want to use the same locale setting in IBM Cognos 8 as in Series 7, set language environment variables to match those used when starting Series 7 PPES.

Steps to Set Language Environment Variables

1. Set the LANG, LC_ALL, and if applicable, LC_CTYPE environment variables to match those that were used when starting IBM Cognos Series 7 PPES. For example, LANG= ja_JP.UTF-8. 2. Launch c8_install/bin/cogconfig.sh. 3. Restart the IBM Cognos 8 service. 4. Redo the migration. If you want to use a different locale setting in IBM Cognos 8, make a copy of the PowerCube under the locale's encoding. Note that you will probably need to use a custom shell or other file-copy utility because entering file names using two separate encodings at a shell command prompt may not work.

Steps to Copy the PowerCube Under a Locale's Encoding

1. Copy the PowerCube .mdc file on disk from its name under the old locale's encoding to its new name under the new locale's encoding. For example, to move the file "cubes/Japanese/Japanese characters.mdc" from ja_JP.PCK to ja_JP.UTF-8, copy the file named "/cubes/Japanese/\x93\xfa\x96{\x8c\xea\x82\xcc\x83L\x83\x85\x83u.mdc" to the new filename "/cubes/Japanese/\xe6\x97\xa5\xe6\x9c\xac\xe8\xaa\x9e\xe3\x81\xae\xe3\x82\xad\xe3\x83\ xa5\xe3\x83\x96.mdc" 2. Redo the migration.
609468

12 PowerPlay

Chapter 1: IBM Cognos 8 Business Intelligence PowerPlay Server Readme

Unable to Migrate Reports on UNIX when Path Names Contain Certain European Characters
An error occurs when migrating reports with path names that contain certain European characters on UNIX. The error occurs when the migration source is IBM Cognos Connection, and the reports were published to IBM Cognos 8 in the following way: 1. The source PPX reports are created under the Windows-1252 encoding. 2. The reports are transferred, using FTP, to UNIX running in the French locale fr_FR.8859-15 or the German locale de_DE.8859.15. 3. In one of the locales in the previous step, the PPES service is started. 4. The reports are inserted in PPES and then published to IBM Cognos 8. The migration error occurs if the path name contains one of the following characters: 0xA4 (euro symbol) 0xA6 (S caron) 0xA8 (s caron) 0xB4 (Z caron) 0xB8 (z caron) 0xBC (OE) 0xBD (oe) 0xBE (Y umlaut)

An error message like the one below appears in the run history details or the migration log: S7S-err-0646 Exception caught: 93 (__privateGetProperty) ppes_bridge.py: 72 (__privateEncode) /dap ./lib/python2.5/encodings/iso8859_15.py: 12 (encode) To work around the problem, open the PPX report in a text editor and modify the encoding from Windows-1252 to the same encoding used by the PPES service. For example, change the encoding to ISO-8859-15.
609944

Missing Brackets in Bookmark Conversion Utility Script Function

In the Migration and Administration Guide, topic Run the Bookmark Utility as a Server, the code mentioned in step 5 of Steps to Allow Users to Change Bookmarks to IBM Cognos 8 is missing two brackets. As a result, the code will not execute properly. Use the following code instead:
function custom1() { var tparent = self.window; if (typeof(topparent) == "undefined"){ tparent = parent; } else {

Readme 13

Chapter 1: IBM Cognos 8 Business Intelligence PowerPlay Server Readme

tparent = topparent; } var bkmURL = tparent.location.href; var bkmCGIURL = "<bookmarkcgi URL>"; if (bkmURL.indexOf('?') != -1) bkmCGIURL += bkmURL.substr(bkmURL.indexOf('?')); tparent.location.href = bkmCGIURL; }

PowerPlay Known Issues

The following known issues exist for PowerPlay.

Report Viewed from Output Versions List Always Opens in Cognos Viewer
When you view a saved PowerPlay report output version, it will always open in Cognos Viewer, even if the properties are set to PowerPlay Studio Viewer. To view the report in PowerPlay Studio Report Viewer, run the report interactively from the IBM Cognos Connection folder using Run with options.
609597

Continuous Prompting for Data Source Selection When Running a PowerPlay Report
A report author can create a report based on a package that uses more than one PowerCube data source connection. When you run this type of report using the Run in the background option from the advanced Run with options, you will repeatedly be prompted to select a data source and you will not be able to run or cancel the report. You must end your browser session to cancel the attempt to run the report.
606173

Error When an Agent Runs a PowerPlay Report

If you have not been authenticated to the appropriate namespace prior to running the agent that runs a PowerPlay report based on a package with a secured data source, you will be prompted for authentication information. After entering your credentials the following error appears. RSV-SRV-0042 Trace back:RSReportService.cpp(791): RSException: CCL_CAUGHT: RSReportService::process()RSReportServiceMethod.cpp(239): RSException: CCL_RETHROW: RSReportServiceMethod::process(): asynchWait_RequestRSReportServiceHelper.cpp(831): RSException: CCL_THROW: RSReportServiceHelper::absoluteAffinityError() To run the report without errors, log on to the appropriate namespace before you run the agent.
605964

14 PowerPlay

Chapter 1: IBM Cognos 8 Business Intelligence PowerPlay Server Readme

Report Output Versions are not Accessible from View Run History for PowerPlay Reports
After a PowerPlay report is run and the output saved, the View run history option is available on the Perform an action page. However, unlike output for other IBM Cognos 8 studios, you can not access Report outputs or Options from the View run history details page. You can access saved report outputs using the View report output versions option.
598000

PowerPlay Administration Activities Do Not Appear in the PowerPlay Audit Logs

PowerPlay administrative activities, such as adding or removing cubes, are no longer logged to the PowerPlay audit log files or to the PowerPlay tables in the IBM Cognos 8 audit database. These actions are now performed outside of PowerPlay administration and written to the cogipf_action table in the IBM Cognos 8 audit database.
591326

Readme 15

Chapter 1: IBM Cognos 8 Business Intelligence PowerPlay Server Readme

16 PowerPlay

Index
A
administration limitations, 6 settings may not work, 7 auditing not supported in admiinistration, 6

J
Japanese characters troubleshooting migration problems with cube or folder names, 10

L
limitations, 5 logging not supported in admiinistration, 6

B
bookmark conversion utility script, 13

C
cubes report cube mapping limitations, 6 custom views appear as broken links when migrated a second time, 9 appear as broken links when migrated from personal NewsBoxes, 9

M
migration custom views migrated a second time appear as broken links, 9 custom views migrated from personal NewsBoxes appear as broken links, 9 empty folder named ubescreated, 8 errors when cube or folder names contain certain Japanese characters, 10 error when migrating Upfront content from a Series 7 distributed environment, 10 known issues, 7 limitations, 6 memory address error appears in Migration Assistant on AIX, 10 migrating cubes with non-ASCII characters on AIX, 11 problems migrating reports with long names, 11 reports created using Saved As command do not run, 8 tasks scheduled to run at same time fail, 11 unable to migrate reports on UNIX when path names contain certain European characters, 13 Upfront reports with no data source information not migrated, 7

D
data sources limitations, 6 drill through administration settings may not work, 7 limitations, 7 dynamic filtering administration settings may not work, 7

F
failed to load csx file troubleshooting, 8 fix list, 5

I
IBM Cognos 8 Transformer administration settings may not work, 7 IBM Cognos Connection empty folder named ubes created after migration, 8 installation and configuration limitations, 5

O
open with Report Studio cannot run report, 9

Readme 17

Index

P
PowerPlay reports running in Report Studio returns error, 9 PowerPlay Studio administration settings may not work, 7

not migrated when data source information missing, 7

R
readme updates, 5

S
samples limitations, 6 Series 7 distributed environment migration error when PPES services are stopped, 10 Series 7 migration service error when starting, 8

T
troubleshooting bookmark conversion utility script, 13 custom views migrated a second time appear as broken links, 9 custom views migrated from personal NewsBoxes appear as broken links, 9 empty folder named ubescreated after migration, 8 error when migrating Upfront content from a Series 7 distributed environment, 10 error when starting Series 7 migration service, 8 memory address error appears in Migration Assistant on AIX, 10 migrating cubes with non-ASCIII characters on AIX, 11 migrating reports with long names, 11 migration errors when cube or folder name contains certain Japanese characters, 10 running PowerPlay report opened in Report Studio returns error, 9 scheduled migration tasks fail, 11 unable to migrate reports on UNIX when path names contain certain European characters, 13

U
Upfront reports created using Save As command fail to run after migration, 8

18 PowerPlay