Smartview Common issues – Master blog Part-2

Continuation to – Previous blog.

Issue – Decompression Error In Smart View on a Refresh.

Solution – During a large refresh/retrieve, Smart View gives an error “Decompression Failed”.
This error may also occur if the Smart View connection has timed out with the additional message “Grid Operation Failed”. This may be due to Microsoft Windows is timing out the connection. Windows network time outs can be too short for large datasets to retrieve.

If your users have IE 7 installed, the default timeout is 30 seconds. The following two Microsoft articles will assist in increasing the timeout:

Prior to any installation, upgrade or modification, it is advised that a full backup be done of all related environments. This includes servers, file systems, registry keys, repositories and databases within the related environments.

It is strongly recommended to engage your Systems Administrator to assist with the following steps.

The following client side registry keys need to be added:

1. Click Start, click Run, type RegEdit, and then click OK.

2. Locate and then click the following key in the registry:


3. On the Edit menu, point to New, and then click DWORD Value.

4. Type KeepAliveTimeout and then press ENTER.

5. On the Edit menu, click Modify.

6. In the Base panel, ensure that decimal is selected.

7. Type the appropriate time-out value (in milliseconds).  It is recommended that you enter 180000 (3 minutes) or longer if required.

8. Click OK.

9. Repeat steps 3-8 above to add ReceiveTimeout and ServerInfoTimeout per below information:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]\

After making the changes, the client machine must be rebooted.

These registry changes are the recommended settings from Microsoft. In some cases (for example, slower connection speeds), you may need to increase the KeepAliveTimeout if these settings do not work.

Issue – Unable to Perform Essbase Ad-Hoc Analysis in Smart View, Error “Cannot set cube view properties”


When trying to connect from Smart View to Essbase and performing an Ad hoc analysis on Sample/Basic, the following error occurs:

Cannot set cube view properties.  com/essbase/services/olap/main/

The reason being due to JAPI jar version and build number in files ‘ess_es_server.jar’ and ‘ess_japi.jar’ are from an old version and not from

To check the version of the jar files, open the jar files using a zip extractor and go to meta-info\ and verify that the ess_es_server.jar and ess_japi.jar have the correct version.

Replace the following two files with the files contained in the APS patch (11823281):


Issue – In Smart View, When an Alias Table is Selected, the Essbase Grid Dimension Metadata Returned Does Not Match the Metadata in the Alias Table

Solution – In Smart View v11., the Essbase grid C-API now returns grid dimension metadata information. However, the metadata information returned does not match with the user selected alias table.
To reproduce:
1.  In Smart View, connect to SampleU.Basic.
2.  Select to use alias table “GermanNames”.
3.  Retrieve an empty grid.

Expected result: grid meta data dimension names match user selected “GermanNames” – Jahr, Produkt, Markt, Szenario, Umsatze .

Actual result: grid dimension names are in English and not matching user selected “GermanNames” alias table – Year, Product, Market, Scenario, Measures.

The cause of this problem has been identified and verified in unpublished BUG 12875766 – ESSBASE RETURNS GRID META DATA INFORMATION NOT MATCHING SELECTED ALIAS TABLE

Issue – Does Smart View Support the MAC Operating System.

Solution – Microsoft Office 2008 (for Mac OS) is supported only for: Financial Management and Financial Reporting.
This means that you can access HFM and Financial Report Web from a Mac OS via the workspace.

We then also support Office 2008 on Mac for these products, e.g in HFM
web you can export a webform to office. For this functionality Office
2008 on Mac is supported.
Smart View client is currently not supported on Mac.

Enhacement request – Bug 13586818 : MAC OFFICE 2011 SUPPORT FOR SMART VIEW has been filed and is currently under internal review by Development.

At this time only Microsoft Windows is supported for Smart View.

Issue – Submitting #MI From Smart View Without Doing a Refresh is Intermittant

Solution – Versions Smart View , Essbase/APS

We have observed inconsistent behavior while submitting #missing. Sometimes SV allows to submit #missing and sometimes it does not.

The steps are: Prepare the data sheet using Smart View. Refresh the sheet.
Send the sheet to someone who doesn’t have Smart View on their system and edit the data sheet rows with #Missing and ask them to send it back to you .
Now connect to Smart View and try to submit the sheet. You can see the #Missing data is not submitting.

Though submit without refresh is supported, submitting #Missing from Smart View without doing a refresh is not supported at this time.

The problem is with Smart View not identifying #Missing cell as dirty.

Enhancement Request BUG 18131605 – SUBMITTING #MISSING FROM WITHOUT DOING A REFRESH has been submitted.

Issue has been fixed in the next release of Smart View

Issue – Smart View “Undo” Button Is Grayed Out

Solution – Sometimes the “Undo” button is grayed out after doing an Adhoc Query and does not allow users to click Undo to get back to the original view.

The internal Undo buffer had not been generated yet. In order to get the internal undo buffer loaded, run a Refresh when the sheet is first opened.  This process should enable the Undo button.  The Adhoc Query does not load to the “undo buffer”.

Issue – Error “Cannot connect to the provider. Make sure it is running in the specified host/port. Error (503)”

Solution – When running a large query in Oracle Hyperion Smart View, the following error is returned after an extended period of time.

Cannot connect to the provider. Make sure it is running in the specified host/port. Error (503).

When this occurs, the user must close Microsoft Excel and then re-open and re-login to continue working.

Reason being Time to complete large query in Smart View exceeds specified maximum session timeout value.

To resolve this issue modify session timeout settings, specified in mod_wl_ohs.conf on Weblogic Managed server. In the mod_wl_ohs.conf file add if missing or modify the parameters for the WLIOTimeoutSecs and WLSocketTimeoutSecs to be a value greater than the time needed for the query to complete. You must restart the Oracle HTTP Server (OHS) and the WebLogic managed server for the Analytic Provider Services (APS) server for the new setting to take effect.

In our example the user was running a query in Smart View which took longer than 5 minutes to complete. The settings were missing for the APS location handler and the Smart View query was unable to complete.

  1. Shutdown the Essbase server service or process.
  2. Backup the current mod_wl_ohs.conf file. The mod_wl_ohs.conf file can be found on the WebLogic Managed server for your implementation of Analytic Provider Services (APS) at the following location:
    On a Microsoft Windows platform: C:\Oracle\Middleware\user_projects\epmsystem\httpConfig\ohs\config\OHS\ohs_component
    On a Linux\Unix platform: //Oracle/Middleware/user_projects/epmsystem/httpConfig/ohs/config/OHS/ohs_component
    Starting with EPM System it is possible to use a “Shared Location” for your Oracle HTTP Server configuration. If this is being utilized in your implementation you should check in that “Shared Location” for the mod_wl_ohs.conf file instead.
  3. Open mod_wl_ohs.conf in a text editor and add or modify the parameters for the “WLIOTimeoutSecs” and “WLSocketTimeoutSecs” properties within the location section for APS. After modification the relevant section should look like this:
    <Location Match ^/aps>
    SetHandler weblogic-handler
    WeblogicCluster <aps-server-name>:13080
    WLIOTimeoutSecs 1800
    WLSocketTimeoutSecs 1800
  4. Restart the Oracle HTTP Server and the WebLogic Managed server service or process for APS.


Issue – Unable to Install Smartview Extensions and Utilities

Solution – Smartview extension such as “Power Pack MDX Script Library Extension Version:” listed in ( are not installing.

1) Download and save .svext file.

2) Click to Install

3) Nothing happen, extensions not added in the smartview options window

to fix –

1) Go to the explorer (My Computer) and type %appdata%

2) This will bring your user directory.  Navigate to Oracle\SmartView\extensions\bin and confirm that there is a folder containing the extension.

3) If the extension is in the folder but not appearing in Options, it is probably because the browser flagged it as a downloaded file and blocked it.

4) Right click on .svext file and go to properties. On the General tab, there may be a button at the bottom that says “Unblock”.  Click it and press OK.

5)  Then re-run the installer, re-open Excel, and go to the Smart View options to verify that the extension is loaded.









Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s