Symptoms
When attempting to log in to Enterprise Performance management Architect (EPMA) the following error occurs:
Module not found:awb.appcontainer.
This is following by a second error after clicking on 'OK':
(404)Not Found (org.apache.axis.AxisFault)
Clicking on the 'Details' link displays the following:
Trace: com.hyperion.awb.web.common.BaseService.openSession(BaseService.java:112)
Solution
1. Open the IIS Manager.
2. Right-click on “Default Web Site”.
3. Select New > Virtual Directory.
4. Define the following Alias: hyperion-bpma-server.
5. Browse to the following directory: %HYPERION_HOME%\BPMA\AppServer\DimensionServer\WebService .
6. Check the following access permissions:
a. Read
b. Run scripts (such as ASP).
c. Execute (such as ISAPI applications or CGI).
7. Click on “Finish”
8. Right-click on the “hyperion-bpma-server” Virtual Directory .
9. Select “Properties” .
10. On the Virtual Directory tab clear the Application Name and click on “Apply”.
11. On the Documents tab remove all the default content pages and add “-1”.
12. On the Directory Security tab > Authentication and Access Control, click on “Edit” and check “Integrated Windows authentication”.
13. Repair the .NET framework 2.0 software installation (it is required since we uninstalled IIS; consequently it is not properly registered with .NET 2.0).
14. Open the ASP.NET tab of the “hyperion-bpma-server” Virtual Directory and select “2.0.50727” the as ASP.NET version.
15. Restart the EPMA services.
16. Confirm that it is now possible to login to EPMA without error.
It can also be the configuration Issue.
Cause
Configuration issue with Internet Information Services (IIS).
Solution
Check the following points:
Go to IIS:
Start > All Programs > Administrative Tools > Internet Information Services (IIS) Manager
a) In Web Sites > Default Web Site, check the site is running, if not start it (click on the > button).
b) In Web Sites > Default Web Site, right click and select 'Permissions' Check the group IIS_WPG is in the list. If not, add it.
c) In Web Service Extension, check ASP.NET v2.0.50727 is set to Allowed. If not, Allow it.
When attempting to log in to Enterprise Performance management Architect (EPMA) the following error occurs:
Module not found:awb.appcontainer.
This is following by a second error after clicking on 'OK':
(404)Not Found (org.apache.axis.AxisFault)
Clicking on the 'Details' link displays the following:
Trace: com.hyperion.awb.web.common.BaseService.openSession(BaseService.java:112)
Solution
1. Open the IIS Manager.
2. Right-click on “Default Web Site”.
3. Select New > Virtual Directory.
4. Define the following Alias: hyperion-bpma-server.
5. Browse to the following directory: %HYPERION_HOME%\BPMA\AppServer\DimensionServer\WebService .
6. Check the following access permissions:
a. Read
b. Run scripts (such as ASP).
c. Execute (such as ISAPI applications or CGI).
7. Click on “Finish”
8. Right-click on the “hyperion-bpma-server” Virtual Directory .
9. Select “Properties” .
10. On the Virtual Directory tab clear the Application Name and click on “Apply”.
11. On the Documents tab remove all the default content pages and add “-1”.
12. On the Directory Security tab > Authentication and Access Control, click on “Edit” and check “Integrated Windows authentication”.
13. Repair the .NET framework 2.0 software installation (it is required since we uninstalled IIS; consequently it is not properly registered with .NET 2.0).
14. Open the ASP.NET tab of the “hyperion-bpma-server” Virtual Directory and select “2.0.50727” the as ASP.NET version.
15. Restart the EPMA services.
16. Confirm that it is now possible to login to EPMA without error.
It can also be the configuration Issue.
Cause
Configuration issue with Internet Information Services (IIS).
Solution
Check the following points:
Go to IIS:
Start > All Programs > Administrative Tools > Internet Information Services (IIS) Manager
a) In Web Sites > Default Web Site, check the site is running, if not start it (click on the > button).
b) In Web Sites > Default Web Site, right click and select 'Permissions' Check the group IIS_WPG is in the list. If not, add it.
c) In Web Service Extension, check ASP.NET v2.0.50727 is set to Allowed. If not, Allow it.
No comments:
Post a Comment