"Error 0x80004005: Unspecified Error" returned when starting OpalisActionService service


When attempting to start OpalisActionService service using the Windows Services applet the following error is received:

"Error 0x80004005: Unspecified Error"

The following errors may be captured in the Action Server logs (if using SQL server):

"Cannot open DB connection"
"[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."


The OpalisActionService process is unable to connect to the Database.  This could be due to any of the following reasons:
  1. The database instance is not running.
  2. Hostname provided for database server does not resolve correctly via DNS.
  3. An incorrect database instance has been referenced.
  4. A non-standard TCP/IP port may have been configured for TCP/IP connectivity.
  5. TCP/IP may not be configured as an acceptable binding or an alternative protocol binding may be configured as higher priority causing connections to work from some locations but not others (e.g. local versus remote).
  6. The user account provided does not have permission to access the database.


Correct the problem that is preventing the OpalisActionService process from accessing the database.
  1. Verify database instance is running

    If the database instance is not running then it cannot accept the connections from the OpalisActionService.  When unable to make initial contact with the database, the OpalisActionService is designed to terminate.  This only occurs if connectivity cannot be obtained at service start.  If the Action Server is installed on the same server as the database instance then a failure to start the OpalisActionService at machine startup could be a result of the database instance not having started yet.  This can be resolved by establishing a dependency in the OpalisActionService on the database instance service.

  2. Verify database server hostname

    Check to ensure that the hostname of the database server does not have a typo and validate that the appropriate hostname responds to network traffic (e.g. ping for response and validation that the correct IP responds).

  3. Incorrect database instance

    Check that the appropriate instance is being referenced.

  4. Database instance port

    Validate that the expected port has been configured for use.

  5. Protocol Configuration

    If multiple protocols are in use then protocols other than TCP/IP may cause connectivity to work from some locations but fail from others (e.g. local versus remote).  If multiple protocols are configured on the database server then it may be necessary to explicitly define the protocol to use.

  6. User account permission

    The user account is defined using the Opalis Integration Server Database Configuration utility.  If using Microsoft SQL Server as the database server with Windows Authentication as the selected security provider, then the user account which starts the OpalisActionService service is leveraged.  The configured account must have read and write permissions to the Opalis database.