"OLAP_error(1020051): Maximum number of rows processed[250000] exceeded[394321]"

This is on Essbase version 11.1.1.3

By default the Max Rows setting for Analytic Provider Services is set to 5000.

If we exceed this limit, will get the below error
"OLAP_error(1020051): Maximum number of rows processed[250000] exceeded[394321]"

So increase the Max Rows settings by doing the following: 

1. Open the \APS\bin\essbase.properties file. 
2. Locate the setting: 
service.olap.dataQuery.grid.maxRows=5000. (we can set service.olap.dataQuery.grid.maxRows=0(no limit))
3. Increase the setting. Microsoft Excel has limits as specified below. 
4. Save the file and restart the Analytic Provider Services server. 

For Excel 2003, there is a limit of 65535 rows. 
For Excel 2007 with version 11.x of SmartView the limit is 1,048,576 rows (but this is dependent on system memory). 

"OLAP_error (1042017):Network error

This is on version 11.1.1.3.500

Got the below error while performing the retrieval through SmartView.

"OLAP_error (1042017):Network error: The client or server timed out waiting to receive data using TCP/IP. Check network connections. Increase the NetRetryCount and/or NetDelay values in the essbase.cfg file. Update this file on both client and server. Restart the client and try again". 

By seeing this error we have increased NetRetryCount and NetDelay values as below
NetRetryCount 1000
NetDelay 600 

Restarted services and performed the retrieval but issue is still not resolved.
When we check logs found that it has generated exception file(log00001.xcp).

From the XCP file and the application log file found that sufficient server threads were not available for the users to connect to the database.

So added the below setting to Essbase.cfg file and restarted Essbase service for the changes to take effect.

SERVERTHREADS 50

After this performed the retrieval and got another error
OLAP_error (1023134): Request grid size is more than allowed limit [10000000]. Increase it using the config setting MAX_REQUEST_GRID_SIZE 

Added the below setting to essbase.cfg file and restarted Essbase service for the changes to take effect
MAX_REQUEST_GRID_SIZE <ApplicationName> 100000000

Issue has been resolved after making these changes in Essbase.cfg file.

"Cannot connect to the provider because: The request timed out. Contact your administrator to increase netRetryCount and netRetryInterval

This is on version 11.1.1.3

Increased netRetryCount and netDelay in Essbase.cfg
NetDelay 2000
NetRetryCount 6000 

Increased the timeout and network settings in the \Hyperion\Products\Essbase\aps\bin\essbase.properties file:

netRetryCount=600 TO 6000
netConnectRetry=3 TO 30
netDelay=200 TO 2000
netSocketTimeOut=200 TO 20000

But still getting the error "Cannot connect to the provider because: The request timed out. Contact your administrator to increase netRetryCount and netRetryInterval 

Implemented the below steps to resolve this issue

i) Add the Provider server details under the provider servers tab and the Essbase server as a standalone server in EAS console.

ii) Implement the below in both APS and Essbase server:

1. Open the Windows Registry.

2. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCPIP\Parameters.

3. Add new
DWORD Value named "TcpTimedWaitDelay"
Select "decimal" radio button, type in 30.

The default value forTcpTimedWaitDelay is 2 minutes. This is how long it will take for a TCP/IP port that was used by the network for a connection to be released and made available again. 30 seconds is the minimum allowed by Microsoft

4. Add new
DWORD Value named MaxUserPort
Select "decimal" radio button, type in 65534.

The default value forMaxUserPort is 5000. This determines the highest port number TCP can assign when an application requests an available user port from the system.

5. Add new
DWORD Value named MaxFreeTcbs
Select decimal radio button, type in 6250.

The default value for MaxFreeTcbs is 2000. This determines the number of TCP control blocks(TCBs) the system creates to support active connections. Since each connection requires a control block, this value determines how many active connections TCP can support simultaneously. If all control blocks are used and more connection requests arrive, TCP can prematurely release connections in the TIME_WAIT state in order to free a control block for a new connection

6. Re-start the machine.

7. Re-start the Hyperion Services including the Analytic Provider Services Service.

iii) On the client machine, update/add the following registry keys:

1. Open the Registry, Start -> Run -> Regedit.

2. Locate the following section:

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

3.Create the following new DWORD keys with decimal values:

ReceiveTimeout=480000

KeepAliveTimeout=180000

ServerInfoTimeout=180000

In this example, the ReceiveTimeout setting is 8 minutes. The KeepAliveTimeout and ServerInfoTimeout settings are 3 minutes. Set these to greater than the longest running request.

4. Restart the machine for the new settings to take effect. 

Now "Cannot connect to the provider" issue has been resolved.

ASO Cube Spreadsheet Extractor Error

We got this issue on ASO cube which is having huge data.

Getting the below error while trying to connect through SmartView.

"OLAP_error (1020004): An error [1130203] occurred in Spreadsheet Extractor"

Checked the Essbase Log and Application log
In Application log we found 

Info(1020089) Ignoring span Hybrid Analysis option. Spanning into Hybrid Analysis Relational Source has been disabled. See the essbase.cfg file

Info(1020055) Spreadsheet Extractor Elapsed Time : [29.734] seconds

Error(1013289) Command [SpreadsheetOperation] failed due to memory allocation failure

Increased the Java Heap size for APS as below:

1. From "Start" ->run->regedit and enter.

2. In the registry look for the HKEY_LOCAL_MACHINE->Software->Hyperion Solutions->aps->HyS9aps

3. For this node you should see several keys, several are jvmoptions.

4. Locate the Xmx and -Xms which are the maximum and minimum heap respectively.

NOTE: You can also change or add the stack size setting -Xss here as well.

5. These can be changed by right-click-> and select modify.

6.For both Xms and Xmx, modify the value as 1024m

Now the values are 
JVMOption10 REZ_SZ -Xms1024m
JVMOption11 REZ_SZ -Xmx1024m
JVMOption12 REZ_SZ -Xss256m
-Xss1024m. 

7. After changing these settings you will need to stop and start the Hyperion Analytic Provider Server windows service.

Now tried with the retrieval using Smart view, we are not getting this error.

Changing RDBMS Server for Hyperion Essbase

Take the backup of old databases and restore in new database server

Navigate to \Oracle\Middleware\user_projects\epmsystem1\bin

Run resetConfigTask.bat to release the configuration with old RDBMS server

Navigate to Oracle/Middleware/user_projects/epmsystem1/bin and run the

epmsys_registry.bat to generate report (to check the details of Hyperion Products and RDBMS information)

Run the EPMSystemConfiguration with new Database Server name.

Check reg.properties file whether this updated the RDBMS server or not.

reg.properties file will be located under \Oracle\Middleware\user_projects\epmsystem1\config\foundation\11.1.2.0

Restart the EPMSystem

To check whether Essbase is running or not run the below command through Command Prompt

\Oracle\Middleware\user_projects\epmsystem1\bin>opmnctl status

Places where changes happened

Table Name : dbo.HSS_COMPONENT 
In this table in two places updated old server name with new server name

Table Name : dbo.HSS_COMPONENT_PROPERTY_VALUES 

In this table in 3 places updated old server name with new server name

Updated reg.properties file with new RDBMS server name

Now i have changed RDBMS server successfully and everything working fine.

The expression must be of type 'string' - Alias issue in Essbase Studio

Encountered this issue while creating alias(new binding)

Reason : Due to different data type in Binding expression(expression must be of type 'String')

Converted binding expression to String using the below

'abs'(connection : \'TestingStudio'::'AgentInfo.dbo.EssbaseTestLoad'.'AgentId').toString

Now i have successfully created a new binding.

ORA-12638: credential retrieval failed

Got this error while connecting to Oracle Database

This looks like entered wrong password, but actually its not.

Problem will be the Oracle server is not configured to support Windows authentication
or The credentials used to login are not sufficient to allow to login to the server.

Workaround
Goto %Oracle Home%\NETWORK\ADMIN in my case it is 
C:\app\prathap\product\11.2.0\dbhome_1\NETWORK\ADMIN

Open sqlnet.ora file and modify 
SQLNET.AUTHENTICATION_SERVICES= (NTS) to
SQLNET.AUTHENTICATION_SERVICES= (NONE)


It worked for me.