Hyperion Planning - Version 11.1.2.3.000 to 11.1.2.3.501 [Release 11.1]
Information in this document applies to any platform.
Failure of Server APACHE Bridge Internal Processing Error
You may find that Environment 1 has access but Environment 2 does not, or it only has Read access. As an example the /tmp/_wl_proxy/ had permissions defined as 750. If both Environment 1 and Environment 2 are members of the same group change /tmp/_wl_proxy to 770 and try to deploy your application again.
There is no need to restart the services after changing the permissions.
Information in this document applies to any platform.
Symptoms
Hyperion Planning application fails to deploy or redeploy. The following error message is displayed:Failure of Server APACHE Bridge Internal Processing Error
Cause
Directory /tmp/_wl_proxy/ is not accessible for the user account running EPM System services.Solution
Make sure that the user accounts running the Hyperion services have access to /tmp/_wl_proxy/. If you have a couple of the Hyperion environments running on a Unix server make sure that each owner has access to this directory.You may find that Environment 1 has access but Environment 2 does not, or it only has Read access. As an example the /tmp/_wl_proxy/ had permissions defined as 750. If both Environment 1 and Environment 2 are members of the same group change /tmp/_wl_proxy to 770 and try to deploy your application again.
There is no need to restart the services after changing the permissions.
thank you so much. THis solved my issue
ReplyDelete