Experience: is what you get soon after you need it.

Experience: is what you get soon after you need it.

Rasul Allah (sal Allahu alaihi wa sallam) said: "Restore the trusts of those who trust you, and deal not falsely with him who deals falsely with you." [Abu Dawud, Tirmidhi]

Search This Blog

Tuesday, May 16, 2017

EPMLCM-13000: Service currently not available.


While importing artifacts using LCM you may run into the below error:

Error:
EPMLCM-13000: Service currently not available.


Issue:
This issue is caused by unpublished Bug 18327819 - LCM IMPORT FAILS WITH "MAX ERRORS THRESHOLD" SET AS "<=100" IN MIGRATION OPTIONS



SOLUTION:
1. Login to Shared Services Console with administrator user.
2. Change the value of "Shared Services - Max Errors Threshold" under Administration->Migration Options to "5000".
3. Attempt to Import or Export artifacts again.





Friday, May 12, 2017

Cannot open file: [\Middleware\user_projects\epmsystem1\tmp\tempfile46694208.txt] Unexpected Essbase error 1030100


Issue:

Cannot Open/load data when Importing Data Using the Essbase Administration Services Console (EAS)

 Unexpected Essbase Error 1030100







Fix:
Rename the data file to .txt extension and then try again

An Unpublished Enhancement Request has been filed to support files with any extension: Bug 23537231

Monday, April 24, 2017

EPMLCM-14000:Error reported from FDM Enterprise Edition. EPMFDM-140291:Export of scripts has failed since system directory could not be found

Error:
EPMLCM-14000:Error reported from FDM Enterprise Edition.  EPMFDM-140291:Export of scripts has failed since system directory could not be found


While cloning using the epm_clone*.sh utility/LCM exports of the FDMEE ,  you may encounter the above error:

root cause:
FDMEE Application root folder was not set correctly. The error "EPMFDM-140291:Export of scripts has failed since system directory could not be found" can occur only when the application root folder is not being set. 

The code where the failure occurred, will execute only when exporting a custom, event, drill script.


Fix:
Set  Application Root folder in the application settings. Under Workflow tab > System Settings > Application Root Folder.

Check if the Application Root Folder is also set in the Application Settings page, for all the applications that are being exported. (Setup Tab > Application Settings > Select the target application in the drop down > Check Application Root Folder entry).

If its a full LCM export, all the Applications in the drop down need to have the App root folder set. It can be set with the same value as in System Settings page.