And when services were not starting, did you find anything in logs ?
Version is 22.214.171.124
we have encountered below error while starting the Hyperion EPMA Service.
started, but did not
finish initializing itself in the time allotted.
at Hyperion.DimensionServer.Service.Main.StartProcess(String applicationName,
String arguments, String startupEventName, String terminateEventName, String
logFileName, Int32 timeout, ProcessInfo& pi)
serverPort, UInt16 netJniPort)
After increasing DimensionServerStartUpTimeout value in BPMA_server_config.xml file , Hyperion EPMA service has started but taking long time(25min) in QA environment rather than 2 minutes and also we have make the windows service as "Manual" instead of "Automatics" in services.msc.
Please lemme know if you need any further details to find out the root cause.
Quick thing is if possible bounce DB and reboot EPMA host , if not able to bounce DB, just reboot EPMA host.
Also, Did you see any exceptions in EPMA logs or event viewer logs? we need to look at more portion of logs.
Did the same DB patch applied on DEV ?
Did you tried rebooting EPMA server and bounce of DB?
Did you check with DB if they getting any performance hindrance after patch?
Try this out and let me know how it goes:
1. Open in a text editor file BPMA_Server_Config.xml, located in folder:
2. Find in the file the following section:
3.Increase the value from 600 to 6000.
4. Save the modified file.
5. Restart EPMA Dimension Server.
Note: Make sure you have a full backup of your system before making any changes.
we have performed above steps which you have mentioned and after that only the HYperion EPMA service in QA environment is taking approx. 30 minutes rather than 2 minutes.
Oh...I missed to see that update earlier.
So the reported issue is no longer their but you have another issue where starting EPMA service now taking a longer time.
Did you check the DB stats when you are starting EPMA service?
Any update on this??
Are the other components on the EPMA Host are working fine?
DB Connectivity from the server is good?
Is that issue got resolved? We are facing similar kind of issue. It would be great if we get any lead or solution.