So you're working on your shiny new upgrade: Oracle EPM / Hyperion 184.108.40.206 through 220.127.116.11. (You want to be on 18.104.22.168 at a minimum, as that's the only path to subsequently jump to higher releases as of this writing).
You attempt a first-time start up of web services, and one or more web services shuts itself down. The problem I'm about to describe existed in 22.214.171.124 and prior, but it still rears its ugly head in 11.2.x from time to time.
Here is the symptom. For ease of discussion, I'm talking about an MS Windows server, but the problem can happen in Linux as well. Flip the slashes and change .cmd to .sh.
Inspect Oracle\Middleware\user_projects\EPM_ORACLE_INSTANCE\diagnostics\logs\services\*-sysout.log for the failed process in question, and discover this text:
(Note: This "services" folder does not exist in Linux and you'll need to crawl through the WebLogic domain's log folders)
What to do here?
Answer: the fix is very simple.
1. Start up your WebLogic Admin Server. There's no service for it (yet! A future post I'll write will discuss the easy way to do it. Don't use the Knowledge Base article to create "beasvc"!)
For now, double-click Oracle\Middleware\user_projects\domains\EPMSystem\bin\startWeblogic.cmd. Leave the DOS command window that pops up alone, and wait until you see the text RUNNING in upper-case. This takes 2-1/2 to 5 minutes, depending upon your server.
This process encrypts the master boot.properties file for your WebLogic Admin Server.
2. Copy the file Oracle\Middleware\user_projects\domains\EPMSystem\servers\AdminServer\security\boot.properties to the Oracle\Middleware\user_projects\domains\EPMSystem\servers\FailedServerName\security\ folder, overwriting the boot.properties file that might exist in that folder. Do this while your AdminServer process is still running in that DOS command window.
3. Restart the failed service in question. Now it sees the encrypted boot.properties file and is able to communicate with AdminServer.
4. Once you've been able to successfully start all web services (Planning Web, HFM Web, EAS Web, etc.) you may hit Ctrl-C in that AdminServer DOS command window to end the process, if you wish to.
Appendix: I've stood up every 11.2.x release released thus far: 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, and now 18.104.22.168 as of this writing. I've hit the issue described herein multiple times, and most recently in 22.214.171.124. If you hit this issue yourself - you did nothing wrong during your config. It just happens sometimes.
Once you fix it, the solution tends to be permanent and I've yet to have to do it a 2nd time in the same WebLogic domain.