Try to add server by manually giving username/password... also look EAS logs to see more details on error
And if its just for essbase cube migration from 9.3.1 then there are many other ways to achieve this...
In case it wasn't clear, I am adding manually an Essbase 9.3.1 server to a 184.108.40.206.500 EAS Console. I wasn't aware there are other ways to add the server in such a scenario.
The logs show only a MAXL error:
[2014-06-25T11:45:10.654+01:00] [EPMServer0] [ERROR]  [oracle.epm.essbase.eas] [tid: 27] [userId: <anonymous>] [ecid: 0000KRIcHLS6YNk6wzbe6G1JedWl00004d,0] [APP: EAS#220.127.116.11] Failed to get MaxlConnection
Hence my question - Is this a bug? Can anyone replicate this?
1 person found this helpful
I just tried with .501 (Essbase svr/rtc/eas) and it is still the same... cannot connect to an 18.104.22.168 essbase server any longer
Hi, I am experiencing exactly the same. A fresh 22.214.171.124 environment with sample apps in Essbase. I installed patch set 500 (17529887) then all 501 patches essbase EAS APS today, and I cannot add an essbase server from another environment (126.96.36.199) to migrate from. Adding the ess.svr says just like Alin said above, as soon as you click the + sign to open up that server, get the message about no connection. MaxL and EssCMD both work between the servers. But I want to add the old essb.svr in the new EAS so that I can simply migrate 25 essb.apps/DBs with all their objects. It must be a bug in both patches 500 and 501 EAS.
so is the correct workaround to leave p500 HSS/all products and p501 installed for essb svr/cli and for APS, but to roll back 501 of EAS server and console ? back to 188.8.131.52.00 version of EAS ??
at a Swiss customer onsite, 9 July 2014. (win2008 platform, also with HFM/FR loads of post 500 patches on).
Yes either don't patch EAS to after to the migration or rollback 500/501, also log it with Oracle because the more this issue is raised the quicker a patch to fix it will be available.
There is no other workaround that I'm aware of. As John said, roll back patches, migrate (make sure you've cleared java cache and use the "old" console) and then apply .501 and log the bug with Oracle.