2 weeks ago we upgraded our Windows server where essbase is running from 2003 to 2008 R2. After upgrade users keep receiving the "decompression failed" error when working with Essbase. They currently use client versions 22.214.171.124 and 126.96.36.199.
We have tried to key in the registry settings for connection timeout on the client side to 180000 and later to 900000 ms with no success (http://essbaselabs.blogspot.com/2010/02/smart-view-timeout-settings.html). The "decompression failed" error comes always after session timeout.
It looks like the "decompression failed" error replaced the previously thrown "connection timed out" error.
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:
The last post is correct this is an issue with compression and disabling it will get rid of this message. When the session times out the user will still get an error but the error will not fail decompression.
So if you turn compression off you will get the proper error message but the users will still have to log back in.