Op Manger Service Fails to Start on Server Reboot

Hello -

I'm running Op Manager v11400 on Windows 2008 R2 using the PostgreSQL database.

Anytime the server running Op Manager is rebooted, the Op Manager service fails to start. The service is set to automatically start and can be started manually immediately after the server boots with no issue.

Each time this occurs, the following item is written to the Application Event log:

      Event ID: 0
      Source: PostgreSQL

      The description for Event ID 0 from source PostgreSQL cannot be found. Either the component that raises this event is not installed on       your local computer or the installation is corrupted. You can install or repair the component on the local computer.

      If the event originated on another computer, the display information had to be saved with the event.

      The following information was included with the event:

      pg_ctl: another server might be running; trying to start server anyway

And the following information is written to the wrapper.log file:

      STATUS | wrapper | 2016/01/31 15:09:20 | Machine is shutting down.
      INFO   | jvm 4    | 2016/01/31 15:09:21 | Interrupt signal received Shutting down OpManager
      INFO   | jvm 4    | 2016/01/31 15:09:21 |
      INFO   | jvm 4    | 2016/01/31 15:09:21 |
      INFO   | jvm 4    | 2016/01/31 15:09:21 | Trying to Shutdown OpManager
      INFO   | jvm 4    | 2016/01/31 15:09:21 | ##########################################################
      INFO   | jvm 4    | 2016/01/31 15:09:21 | Connection to the Database is lost. Trying to reconnect to the Database
      INFO   | jvm 4    | 2016/01/31 15:09:21 | Please Wait ...
      STATUS | wrapper | 2016/01/31 15:10:58 | --> Wrapper Started as Service
      STATUS | wrapper | 2016/01/31 15:10:58 | Java Service Wrapper Professional Edition 64-bit 3.5.15
      STATUS | wrapper | 2016/01/31 15:10:58 |   Copyright (C) 1999-2012 Tanuki Software, Ltd. All Rights Reserved.
      STATUS | wrapper | 2016/01/31 15:10:58 |     http://wrapper.tanukisoftware.com
      STATUS | wrapper | 2016/01/31 15:10:58 |   Licensed to Zoho Corporation Pvt. Ltd. for ManageEngine OpManager
      STATUS | wrapper | 2016/01/31 15:10:58 |
      STATUS | wrapper | 2016/01/31 15:11:00 | Launching a JVM...
      INFO   | jvm 1    | 2016/01/31 15:11:04 | WrapperManager: Initializing...
      INFO   | jvm 1    | 2016/01/31 15:11:21 | taryIconProps {DefaultMenuItem=Status, ApplicationName=OpManager, Menu=[{Id=Status,             DisplayName=&OpManager Status, RunProcess=ShowOpManagerStatus}, {Id=StartClient, DisplayName=Start &Client,                               RunProcess=StartOpManagerWebClient}, {Id=ShutDownServer, DisplayName=Sh&ut Down Server, RunProcess=ShutdownOpManager}],       EnableIcon=images/logo16x16_green.png, DisableIcon=images/logo16x16_gray.png, ToolTipText=ProductName,                                           MainProcess=StartOpManager}
      INFO   | jvm 1    | 2016/01/31 15:11:23 | Windows Server 2008
      INFO   | jvm 1    | 2016/01/31 15:11:24 | application_name OpManager
      INFO   | jvm 1    | 2016/01/31 15:11:24 | startAndRun
      INFO   | jvm 1    | 2016/01/31 15:11:24 | menuName &OpManager Status RunProcess ShowOpManagerStatus
      INFO   | jvm 1    | 2016/01/31 15:11:24 | menuName Start &Client RunProcess StartOpManagerWebClient
      INFO   | jvm 1    | 2016/01/31 15:11:24 | menuName Sh&ut Down Server RunProcess ShutdownOpManager
      INFO   | jvm 1    | 2016/01/31 15:11:24 | setProcessInProgress true
      INFO   | jvm 1    | 2016/01/31 15:11:25 | inside addon check
      INFO   | jvm 1    | 2016/01/31 15:11:50 | Unable to start POSTGRESQL daemon
      INFO   | jvm 1    | 2016/01/31 15:11:50 | Unable to create database Exiting OpManager
      STATUS | wrapper | 2016/01/31 15:11:53 | <-- Wrapper Stopped

It seems to have been like this since we installed the system last summer.

For the time being, I've set the recovery options on the server to "restart" on failure and this seems to at least make sure the service gets restarted in a timely manner. However, I'd really like to get to the root of the problem.

Any thoughts or suggestions would be much appreciated.

Thanks,
Robin H.