This content has been marked as final. Show 3 replies
Is it possible that this outline was created in an older version of Essbase,and has simply been copied from one environment (old essbase) to new environment (new essbase)? I am not sure how to get around that, other than perhaps running the migration wizard in EAS from the old to the new. Or alternatively, can you create a test app, open the outline, and do a file save as into the new test app?
I am just throwing out suggestions as to be honest i have not run into this before.
1. What is the version of Essbase?
2. Are you using EAS thick client or web console ?
3. What is the version of Java on the problematic machine?
Please check the below document:
Essbase Administration Services (EAS) Console Hangs When Trying To Open An Aggregate Storage (ASO) Outline (Doc ID 831173.1)
Contents of the document:
When trying to migrate the outline, Essbase Administration Services just hangs.
Also getting error "Old file format discovered" when trying to open an ASO outline.
Incorrect Java version is being used.
Java version 1.6 is not supported with Essbase version 9.3.1. You must use Java version 1.5.
To correct the version:
1. Stop Essbase and Essbase Administration Services.
2. Remove Java 1.6.
3. Install Java 1.5.