Oracle BAM server doesn't start up

Question

Hi, I have a BAM server in a cluster and start up sometimes and not others.
When started shuts down unexpectedly.
Logs files doesn't show errors.
=============================================================================================
startWebLogic.cmd console show a "million" times, stop when shutdown server
"(Warning) (oracle.mds) (BEA-000000) (A call to flushChanges on the current MDSSession does not specify the correct transaction key)"
==============================================================================================
startManagedWebLogic.cmd console show this:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141247]The configuration di
rectory C:\Oracle\Middleware\wlserver_10.3\common\bin\config does not exist and
the admin server is not available.
        at weblogic.management.provider.internal.RuntimeAccessImpl.parseNewStyle
Config(RuntimeAccessImpl.java:200)
        at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(Runtim
eAccessImpl.java:115)
        at weblogic.management.provider.internal.RuntimeAccessService.start(Runt
imeAccessService.java:41)
        at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesMan
ager.java:461)
        at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServ
icesManager.java:166)
        at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
        at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
        at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
        at weblogic.Server.main(Server.java:71)
>
<16/04/2014 11h'07 ART> <Notice> <WebLogicServer> <BEA-000365> <Server state cha
nged to FAILED>
<16/04/2014 11h'07 ART> <Error> <WebLogicServer> <BEA-000383> <A critical servic
e failed. The server will shut itself down>
<16/04/2014 11h'07 ART> <Notice> <WebLogicServer> <BEA-000365> <Server state cha
nged to FORCE_SHUTTING_DOWN>
Thanks!

Answer 1

See the below error :
The configuration directory C:\Oracle\Middleware\wlserver_10.3\common\bin\config does not exist and  the admin server is not available.
It clearly mentions that config.xml file was not found - which is needed for the Admin Server to start. Check in the above location if one exists or not.