Financial Close Management (FCM) Service Not Starting In Multi Node Environment BEA-141151
(Doc ID 2792612.1)
Last updated on OCTOBER 07, 2021
Applies to:Hyperion Financial Close Management - Version 18.104.22.168.250 and later
Information in this document applies to any platform.
- Multi Node Environment.
- FCM server installed on a different server.
- When trying to start FCM server in Weblogic console receiving an Error:
For server FinancialClose0, the Node Manager associated with machine <machine name> is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
3. When starting FCM server from command line \Oracle\Middleware\user_projects\domains\<domain name>\bin>startManagedWebLogic FinancialClose0 output showing:
<Jun 14, 2021 7:51:17 AM CDT> <Notice> <WebLogicServer> <BEA-000358> <Started WebLogic Independent Managed Server "FinancialClose0" for domain "Domain_Name" running in Production Mode>
<Jun 14, 2021 7:51:17 AM CDT> <Warning> <JMX> <BEA-149510> <Unable to establish JMX Connectivity with the Adminstration Server AdminServer at <JMXServiceURL:null>.>
<Jun 14, 2021 7:51:20 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Jun 14, 2021 7:51:20 AM CDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document