There's a documentation update in 184.108.40.206 that says "After adding an Oracle Essbase server using a cluster name, Oracle Hyperion Provider Services must be running in order to execute a Data Preview on databases on that server." and there was an older bug relating to (I think) a similar problem. But it doesn't sound like you're using cluster names. A long shot, but is Provider Services running on both boxes?
I logged this with Oracle and the following is their response copy/pasted
The issue which you have reported in this SR is a desired behavior. This behavior has been seen in latest versions only 11.1.2.x.
In earlier version we can preview the data of any Essbase server added to any eas console.
But form 11.1.2.x environment this behaviour has been changed.
We did checked with development team on this earlier, and according to development team its a behavior by design.
As dev environment and Prod environment have different registries , the preview data would work if Dev Essbase server added to Dev EAS only. like same holds good for prod or test environments.
As same issue has been reported earlier , we form support has raised a bug with development team after reproducing the issue .
But development team did not accept this as bug as this behavior was by design .
So later we changed this bug to a enchantment request with development team to change this behavior.
Bug 14622693 - PREVIEW DATA ON REMOTE ESSBASE HOST FAIL WHEN CONNECTED FROM EAS
If this enhancement requested gets approved by development team ,Then it would be incorporated in future release.
My thanks also Ted, that is fascinating. I like that they've made it an (sic) "enchantment request".
Must have been a different issue that I encountered.
I'm surprised to hear that Development wouldn't accept this as a bug. I can run a report script against a different server, I can run MDX queries against a different server, I can do anything I like to administer the databases and Essbase instance on that server, but I can't preview data? If this was actually a conscious design choice (rather than an unintended consequence of a different design choice), why not add a comprehensible "Sorry, you can't do this" message in EAS?
With all due respect to Development, as the British say: "Pull the other one, it's got bells on".
Maybe this is related to an issue on reporting tools too. I remember replying another question where user was trying to create a WA report on DEV server and pointing towards Prod Essbase. He was getting the same error and if he manully enter the credentials (WA allows you to enter the credentials if the login fails), same time DEV report works fine.
I was telling him that only possible reason I can give was Essbase somehow treats the DEV user as another user (seems like I was correct )
Well Celvin in that case , More to life than this...: EAS - single sign-on to Essbase using separate Shared Services instances This will help i think ...
Please let me know your thoughts ...