Wednesday, November 9, 2011

MaxL API Instance Not Active EAS to Essbase connectivity issue

Hi Guys,

Today we faced a very peculiar issue with EAS. Once we restart EAS services on Windows box, the EAS services use to start but when we try to open any Essbase Analytic Server, it use to throw below error message : MaxL API instance not Active. Sometime it use to hang EAS console completely.

We investigated the issue and found that the Environment Variable (ESSLANG and ESSBASEPATH) set on the EAS server was not correct. Value for ESSLANG should be .Latin1@Default and ESSBASEPATH value must point to Essbase Client. This make sense as while connecting Essbase server, EAS looks for Essbase Client to get it connected and hence if the values are not proper, if would not connect with Essbase.

Hope this help when you face a similar problem

Keep Sharing

1 comment:

  1. I found that this error is more and more in hyperion world.
    The thing is that sometimes the ESSLANG is just right, and you have to reinstall de EAS console to getthis problem solved. That did it for me.

    ReplyDelete