We're getting that "increase netretry..." error in Smartview. I checked the APS log and see the following:

ERROR [WebContainer : 0]: - Exception:
com.essbase.smartview.SmartViewException: Cannot perform cube view operation. 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.

If this error is making it into the APS log, can the problem be between Smartview and APS? BTW -- This is only happening for a few users. Any insights would be appreciated.

Thanks,
Tim

This is an Essbase error code.. Are you on a Windows server (either for APS, Essbase or both?)

Tim Tow
Oracle ACE Director
Applied OLAP, Inc

Essbase and APS are running on the same AIX machine.

I would tend to think the issue is in the APS/Essbase communication, and not between the client and the APS server, due to the Essbase error code.

We see these messages on Windows machines due to limitations in the TCPIP stack default socket configuration. The Windows default configuration sets the 'max' socket number to 5000 (instead of a possible 65530 something) with a socket timeout of 240 seconds. Any TCPIP activity that uses a socket thus has a smaller pool of sockets to choose from and, to compound matters, holds onto the socket for 4 minutes before releasing it. I did a blog post on the details: http://timtows-hyperion-blog.blogspot.com/2007/12/essbase-api-error-fix-geeky.html.

It didn't used to be a problem when computers were slower and couldn't use that many sockets but it is becoming a big deal now. We see similar issues all the time with the Outline Extractor running against big outlines (and making many, many calls to the server in s a short period of time). I don’t know exactly what the Smart View servlet is doing internally but it is conceivable that it is doing many, many calls to Essbase in quick succession.

All of this being said, I don’t know if there is a similar issue with TCPIP configuration on AIX. I may be worth a look.

Tim Tow
Oracle ACE Director
Applied OLAP, Inc

Strangest part is that when we do the identical query on the same network, one machine will get the error and the other will process just fine. Each time, it's the same PC getting the error. So it leads me to believe there's some network setting on the one PC that needs to be adjusted.

I had a similar issue with some of our users as well (while implementing 11x BTW). Found that some users are sitting on different domain from the server so the fix was to update their Hyperion Provider Service URL with the domain they are on in order to communicate with the server.

For example, some users use
http//OMAFINP01:13080/aps/SmartView

and the users with issues use this
http//OMAFINP01.na.COMPANY.com:13080/aps/SmartView

I've been able to recreate the problem on my PC.

Steps:

1. Zoom-in on large dimension works just fine.

2. Set the following registry key to 5000:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ReceiveTimeout

3. Restart Machine.

4. Zoom-in on large dimension and I get the error message back from Smartview after about 5 seconds.

5. Set registry key to 3600000.

6. Zoom-in on large dimension works just fine.

I just hope this fixes the problem on the user's desktop. I found this thanks to the following post: http://www.network54.com/Forum/58296/message/1212599342/Hyperion+figured+out+my+issue

The users having problems were all on IE7. I put the registry entry in there and it worked just fine.

This is their information they sent - I did not go see what the hexadecimal value receommendations are:
"For the timeout issues you are seeing in smartview, can you try adding the following registry changes and rebooting?"

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

"ReceiveTimeout"=dword:00dbba00

"KeepAliveTimeout"=dword:00180000

"ServerInfoTimeout"=dword:00180000

We have almost similar problem when we try to refresh report, after 2min more it gives us error msg : can't list alisas, there's still running process..bla..bla..bla. understand smart view can't display alias, then focus on the timing 2min more and change the netdelay and netretrycount in essbase.cfg and essbase.properties under APS. after the changes and restart, the problem seems gone. you might want to try that as well.