Save parameter reports, saved to a different domain than the My Report created from a Reporting Object, will fail to run successfully when the My Report and the Reporting Object the My Report was created from are located in a different domain than the Save Parameter report. To ensure that you are able to run your Save Parameter reports created from My Reports, save the Save Parameter report to the same domain as the My Report you are creating it for.

Editing a Master File or .ftm file with the Text Editor in the Data Servers folder in the Managed Reporting Applet environment truncates the file. It is recommended that you edit these files using Developer Studio or you can edit them directly with an editor available to you, such as Notepad or Textpad.

This issue is resolved in the Developer Studio Data Servers environment. However, the behavior still appears when editing files using the Managed Reporting Applet.

When using the MR Administrator tool to create a custom role, an HTTP message specifies that the role name already exists.

As of Version 7 Release 7, the new Managed Reporting roles (MR Security Object Management, MR Group Authorization Manager, and No Privileges) are not fully implemented for Active Directory (AD) authorization. When Managed Reporting security is configured for Active Directory External Authorization, an HTTP 500 error occurs when an MR Administrator selects one of the new 77 Managed Reporting roles. All other Managed Reporting roles are functional with Managed Reporting security configured for Active Directory authorization.

The following special characters are not supported in the URL for HTML reports:

• <
• >
• /

The following are known issues when using the Alert Wizard in WebFOCUS Managed Reporting:

• When using the MR Applet Alert Wizard to create an alert test using the text editor, the Java console contains the following error:

  "IBIResfile: String named: 'EditorFrameWidth' is missing from the resource file"

  This error does not have any impact on the user being able to use the text editor to create or edit the alert test.

• When editing the Alert Wizard with the Text Editor, the title bar of the Text Editor displays as Procedure Viewer Alert Test and Procedure Viewer Alert Event. In addition, the save dialog box displays WebFOCUS Developer Studio in the title bar.

The following are known issues with Managed Reporting migration:

• My Reports that are not based on Reporting Objects and contain -INCLUDE statements incorrectly have the internal flag roname=value added to the MRFLAG string for the My Report entry in the Managed Reporting user .htm file within the Managed Reporting repository. Due to this flag being added, the My Report will not run from the MR Applet User Interface. The My Report will run from the BI Dashboard interface.

  This problem can be corrected by manually editing the .htm file of the user in the MR Repository and removing the roname=value reference from within the MRFLAG= value.

  The following is an example of a Custom Report with roname=value to delete:

  <!--IBIMR_FOLDER--> 
  <P><A HREF='#.olapcustomreports' MRFLAG='none'>Custom Reports</A> 
  <LI><A HREF='admin/cars.fex' MRFLAG='myreport,rassist,roname=mrv/ carmilea.fex'>Cars</A>
  <!--/IBIMR_FOLDER-->

• As of Version 7 Release 7.02, National Language characters in the worp_users directory names get corrupted during the Unicode Migration Load process if the native language of the target operating system is different from native language of the operating system being migrated. This may cause files to appear missing after the migration load step. A workaround for this issue is to archive the worp_users directory using an archive utility that supports Unicode and then unarchive it in the new WebFOCUS environment.

As of Version 7 Release 7, when using an IE Version 7 or 8 browser, if you click Change Password from the MR_login.jsp or MRlogon.htm page, the page becomes blank and does not display the desired change password page. This issue is specific to IE 7 and IE 8 and does not occur with Firefox browsers.

A alternative is to click Tools in the IE 7 or IE 8 browser main menu, select Internet Options from the drop-down menu, click the Languages button at the bottom of the General tab, select the desired language, and click OK. This refreshes the page and displays the desired change password page.

When logging on to Managed Reporting using the mrlogon.htm (Managed Reporting Logon) page, the initial page of the Managed Reporting Applet opens in a smaller frame than it should. When you log out, the logoff page opens with corrupted frames. If you attempt to log on from the logoff page, an IE error message is displayed. It is recommended that you log on to Managed Reporting from the mr_login.jsp page, as shown in the following URL:

http://hostname[:port]/wf_context_root/login/mr/mr_login.jsp

where:

hostname[:port]

Is the host name and optional port number (specified only if you are not using the default port number) where the WebFOCUS Web application is deployed.

wf_context_root

Is the site-customized context root for the WebFOCUS Web application deployed on your Application Server. The default value is ibi_apps.

A Managed Reporting Publish form published outside of the MR Repository that runs against a secure WebFOCUS Reporting server displays a message that includes the following:

The following error has occurred while processing this form: (WFC 32033) Error occurred, rc=32033 
Please contact your administrator for assistance.

After clicking OK in the message dialog box, the publish form displays without dynamic list values. This issue occurs whether or not you provide valid reporting server credentials.

The contents of a Managed Reporting Publish file that is a Standard Report cannot be saved to a new HTML file in the Data Servers area.

The following are known issues related to the MR Applet:

• In Java 1.6.0_10+, when using the MR Applet Text Editor EDIT/FIND option to locate a string, the find does not highlight what is being searched for.

  Java 1.6.0_10 added a feature that allows it to offload some of the rendering of graphics to DirectX through a pipeline. This pipeline has shown problematic with a number of video card drivers, most significantly affecting those cards made by ATI.

  For the video card drivers that are impacted, this problem causes a number of rendering and display issues and can trigger a spike in CPU usage.

  Solution: Upgrade your video card driver to a version that is not impacted by this problem or disable Java usage of DirectX.

  To get the latest version of your video card driver, visit your video card or computer manufacturer Web site.

  To disable Java use of DirectX for rendering, do the following:

  1. Navigate to your Java Control Panel. This can be done by clicking:
     • Start Menu, Control Panel, and then selecting Java.

       or

     • Start Menu, Settings, Control Panel, and then selecting Java.
  2. Click the Java tab and click View.
  3. Double-click on the runtime settings box for each version of Java you have installed that is above release 1.6.0_10 and insert the following text:

     -Dsun.java2d.d3d=false

  4. Click Ok, then Apply, followed by Ok to close the dialogue.
  5. Close and reopen any open Web browsers.

  For more details on this setting, see the Java release notes at:

  http://www.oracle.com/technetwork/java/javase/6u10-142936.html

  Or the following thread:

  http://stackoverflow.com/questions/848481/problem-with-painting-in-java-swing-app-in-java-1-6

  When using the Internet Explorer browser configured to use Sun JVM version 1.5.0_11 and the Managed Reporting Applet User Interface, the following errors are seen in the Sun Java Console. No impact to the functionality of the Managed Reporting Applet User Interface has been identified.

  java.lang.NullPointerException: peer  
     at sun.awt.windows.WCanvasPeer.create(Native Method)  
     at sun.awt.windows.WComponentPeer.<init>(Unknown Source)  
     at sun.awt.windows.WCanvasPeer.<init>(Unknown Source)  
     at sun.awt.windows.WPanelPeer.<init>(Unknown Source)  
     at sun.awt.windows.WToolkit.createPanel(Unknown Source)  
     at java.awt.Panel.addNotify(Unknown Source)  
     at ibi.mra.IBIMRADmin1.init(IBIMRADmin1.java:8072)  
     at sun.applet.AppletPanel.run(Unknown Source)  
     at java.lang.Thread.run(Unknown Source)

  This issue is listed in Sun Microsystems JDK 1.5.0_11 Release Notes under bug ID 6178323 at:

  http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6178323

  The bug report information specifies this is a permanent change. WebFOCUS programming will review this issue and work to handle the error appropriately.

• When using the IE Browser with Sun JVM 1.5, the MR Applet may sporadically close when closing a reporting tool (Report Assistant, Graph Assistant, Reporting Object tool). This problem does not occur with an IE browser configured to use Sun JVM 1.4 or Sun JVM 1.6. Information Builders has not been able to identify the cause of this problem due to its sporadic nature. When the MR Applet unexpectedly closes, the Sun JVM creates a dump file on the user desktop with the following file name: hs_err_####.log (where #### is a series of numbers). If you experience this problem, please report it to Information Builders Customer Support Services with the Sun JVM dump file and reproduction information.

When the browser Back button is selected while viewing a report that was run from an HTML-based reporting tool, the message Processing WebFOCUS Request appears, but the report is not successfully rerun. Close the browser window and run the report or graph request again. The HTML-based reporting tools affected include Report Assistant, Graph Assistant, Power Painter, and Advanced Graph Assistant.

In Managed Reporting, if you run a My Report that is a Saved Parameter report and the parameter value applied is not the parameter value you saved, contact your Managed Reporting Administrator or Developer. Confirm that the saved parameter report is based on a Reporting Object that specifies default values for the parameter using the –DEFAULT command in the Reporting Object Other component. The –DEFAULT command should not be issued in the Reporting Object Other component for parameters that can be saved by the Saved Parameters feature because the –DEFAULT in the Reporting Object Other component is issued after, and overrides, the –DEFAULT in the Saved Parameter report.