Symptom
Review of logs show the following messages :
*OBServiceManager* log:
----------------------
20140414T160151.832|1|OBMO.exe ( Exited after immediately ) Retry count set to 1|||||5076
20140414T160151.832|1|GenericExeController.SetRegistryServiceStatus ServiceName: OBMO, ServiceStatusStopped|||||5076
20140414T160157.822|1|GenericExeController.SetRegistryServiceStatus ServiceName: AMP, ServiceStatusStarted|||||788
20140414T160159.822|3|Waiting for stop event to be created(10) - IMO_STOP_EVENT_MLSRV_WRAPPER|||||4812
20140414T160209.823|3|Waiting for stop event to be created(20) - IMO_STOP_EVENT_MLSRV_WRAPPER|||||4812
20140414T160219.825|3|Waiting for stop event to be created(30) - IMO_STOP_EVENT_MLSRV_WRAPPER|||||4812
20140414T160220.825|1|GenericExeController.SetRegistryServiceStatus ServiceName: MlsrvWrapper, ServiceStatusStarted|||||4812
20140414T160221.807|3|GetThreadState - Event handles not avaliable. This is OK during shutdown or stopping. IMO_STOP_EVENT_OBMO_SERVICES|||||4620
20140414T160221.808|1|GenericThreadController detected service process for service 'OBMOTHREADS' was not running. Restarting it...|||||4620
...
...
20140414T160237.154|1|Service stopped because the following child services either could not be started or failed to keep running. |||||2552
20140414T160237.154|1|OBMO.exe|||||2552
Windows Application Event Viewer show the below error :
Service stopped because the following child services either could not be started or failed to keep running.
OBMO.exe
Read more...
Environment
SAP Mobile Platform 2.3.3
Operating System : Microsoft Windows Server 2008 Standard SP2
Product
Keywords
OBMO.exe Exited after immediately SMP 2.3.3 , KBA , MOB-SUP-RT , SUP Runtime , Bug Filed
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview