Hyperion & stuff

Stuff about Hyperion and stuff

EPMA wrong deployment host

I had a scare recently with yet another EPMA issue.  After a load balancing exercise on the Hyperion servers by distributing the components, suddenly EPMA deployment for Essbase apps wouldn’t work anymore.  It returned with HTTP Error 500, bla bla bla.  Previously I had moved EAS and APS from the box running EPMA to another box.  When trying to deploy an Essbase app manually, I noticed that the EPMA deployment host was somehow pointing to the server running EAS.  After several tries of restarting EPMA, reconfiguring Web Server and restarting EAS, I finally decided to reconfigured the old EAS and Web Server running on the same box as EPMA.  Guess what, it worked.  The EPMA deployment host was now back to the right server.  I didn’t think that EAS would be related to Essbase deployment, but I guess it is.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: