My Oracle Support Banner

MaxL Crashes/Generates Empty Script When Encrypting a MaxL Script Not Working After applying Essbase Patch Set Update (PSU) (Doc ID 2175115.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Hyperion Essbase - Version and later
Generic Windows


After applying the Essbase PSU, there are multiple issues when trying to encrypt a MaxL script depending on where MaxL is run from:

The following examples are from a Windows environment.  

MaxL run on the Essbase Server from the \Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin directory:

Generate keys is successful:

startMaxl.bat -gk

Essbase MaxL Shell 64-bit - Release 11.1.2 (ESB11.
Copyright (c) 2000, 2016, Oracle and/or its affiliates.
All rights reserved.

Public Key for Encryption: 923,2377741337
Private Key for Decryption: 1620300947,2377741337

MaxL Shell completed

When the command to encrypt the MaxL script is run, MaxL (essmsh) crashes and an empty script, file.mxls, is created: startMaxl.bat -E Test.mxl 923,2377741337

Running a previously encrypted MaxL script also crashes Maxl (essmsh): startmaxl.bat -D Test.mxls 50929109,907225463

MaxL Run from a Client System, not on  Essbase Server  will not crash but generates an empty script, Text.mxls.



 Applied Essbase PSU.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.