This content has been marked as final. Show 8 replies
are foundation services, "Oracle Process Manager (ohsInstance..)", APS services running.
The three Services you mention are all showing as "Started" under Services:
1) foundation services= "Hyperion Foundation Services - Managed Server"
2) APS services = "Hyperion Provider Services - Web Application"
3) "Oracle Process Manager (ohsInstance..)
I checked the HyS9FoundationServices - sysout log (per an earlier posting by you!). Every 3 hours this is posting a couple of warnings:
<Warning> <JMX> <BEA-149515> <An error was encountered getting the attribute AdminServerListenPort on the MBean com.bea:Name=FoundationService0,Type--ServerRuntime during a call to getAttributes>
<Warning> <JMX> <BEA-149515> <An error was encountered getting the attribute AdminServerHost on the MBean com.bea:Name=FoundationService0,Type--ServerRuntime during a call to getAttributes>
Edited by: user9325875 on 22-Jun-2011 04:42
Can you log into shared services - http://<foundationmachine>:28080/interop/index.jsp and http://<foundationmachine>:19000/interop/index.jsp
Both of these URLs return an Error 404--not found.
This mirrors the Failed messages in the EPM System Diagnostics output since this is the test that the diagnostic undertakes on each of the Web Apps?
If you restart the foundation service and check the two HyS9FoundationServices logs are there no more errors being generated?1 person found this helpful
Thanks, John, for the prompt to check both theHys9FoundationServices log files (I had only checked sysout before.
The salient lines from the logs are below (retyped so there may be minor syntax typos):
Caused By:EPMCSS-00001:Failed to initialize EPM Shared Services Security Instance. Component SYSTEM9/FOUNDATION_SERVICES_PRODUCT/SHARED_SERVICES_PRODUCT is null in the EPM System Registry. Verify EPM Registry Configuration.
Com.hyperion.lcm.common.managerException: Failed to connect to Registry databse. Exception – “com.hyperion.hit.registry.exceptions.RegistryException: com.hyperion.hit.registry.exceptions.RegistryException:
java.sql.SQLException: [FMWGEN][SQLServer JDBC Driver][SQLServer]Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.”
Error: EPM System Security is not initialized properly
1) sysout implies that there is a null files in the System Registry?
2) syserr implies that the log in to the (SQL Server) Shared Services Registry is not trusted using Windows authentication? (Yet the "Installation and Configuration Guide" specifically suggest Windows authentication? I found a similar posting [see under the dotted line below] related to Remote Desktop but I am not running this.)
Do you think the issue in (1) causes (2) as a side effect rather than due to Windows authentication?
If (1) is the primary cause, is the best course to reconfigure by:
a) exit EPM System Configurator
b) delete the reg.properties file, located in user_projects/epmsystem1/config/foundation/188.8.131.52.
c) start over in Configurator and configure with a clean Shared Services Registry database?
“Thread: 184.108.40.206 Foundation Service Problem
I installed and configured EPM products on Win2008R2 x64 without any errors and all services are up, but shared service is not working properly, there are errors in service logs as below, in syserr service log file , there is a message like this; "Error: EPM System Security is not initialized properly"
So I see Error 404--Not Found message on shared service screen. How can i fix this issue.
We solved the problem via removing "delete temporary folders on exit" check box on win2008 r2 Remote Desktop Session Host Configuration screen.”
The docs are incorrect, in the 220.127.116.11 known issues
Defects - 7127257,7188590
You must use native authentication with Microsoft SQL Server instead of Windows authentication. Both the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide and the Oracle Hyperion Enterprise Performance Management System Installation Start Here state to use Windows authentication.
Spot on, thanks very much John.