Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Patch Manager returns Error 1068: The dependency service or group failed to start

Patch Manager returns Error 1068: The dependency service or group failed to start

Updated 02 Jan, 2018


You have disabled TLS 1.0 and 1.1 (© 2018 Microsoft, available at, obtained on November 19, 2018) for both client and server and the Patch Manager server has been rebooted. You then tried to access the Patch Manager MMC console but it returns the following error:

Failed to connect to Application Server



When you tried to start the EWDGS in Service Manager, the following error is displayed:


Error 1068: The dependency service or group failed to start


And when you check the dependency service for Eminentware Data Grid service, it is SQL Server service, which is not started automatically. And when you try to start the MS SQL service you get the following errors in system event logs:

A fatal error occurred while creating an SSL client credential. The internal error state is 10013.


TDSSNIClient initialization failed with error 0x80090331, status code 0x80. Reason: Unable to initialize SSL support. The client and server cannot communicate, because they do not possess a common algorithm. 


  • Patch Manager 2.1.5
  • MSSQL Server on the same Server as PM without support for TLS 1.2




If PM application and DB installed on the same server then enable TLS 1.0 as below

  1. Launch Local Security Policy MMC snap-in on the Patch Manager server
  2. In Local Security Settings, expand Local Policies, and then click Security Options.
  3. Under Policy in the right pane, double-click System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing, and then click Enabled.
  4. Reboot the server.


If your company policy does not allow to enable TLS 1.0 on PM server, then upgrade SQL server to a new version or apply below relevant patches if running SQL server 2014 or below


Note:  PM 2.1.6 has dropped support for TLS 1.0 and supports 1.2, so you are advised to upgrade to PM 2.1.6 and have MSSQL DB that is compatible with TLS 1.2. Refer to this MS KB for details


Last modified