Problem: The Unwired Server fails to start even though the Sybase Unwired Server service has started.
Explanation: The Sybase Unwired Server service manages multiple child processes, and its running status does not indicate that the actual system is fully functional. Among these child processes, the most important are OBMO.exe and mlsrv12.exe. If none of these are continuously running or multiple instances are running, it will signify a problem. The most common cause is an environment issue (for example, missing files, cannot connect to CDB or Messaging DB) that prevents these processes from starting.
Solution: First check the Event Viewer application log to see if any errors are reported by "Sybase Unwired Server." Address any reported issues and restart the service. If this does not solve the problem, check the mlsrv_err.log under the logs directory. This log reports issues with the mlsrv process during startup. There are additional log files in the logs\OBServiceManager folder that may have information on the Unwired Server startup issues.
If the problem involves having multiple instances of child processes running, the best way to recover is by restarting the computer.
If for any reason, a forced stop of the Sybase Unwired Server is needed, you must terminate the entire process tree under the process "OBServiceManager."