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

You have disabled TLS 1.0 and 1.1 (© 2018 Microsoft, available at https://docs.microsoft.com, 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.

OR

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.

• System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing (© 2018 Microsoft, available at https://support.microsoft.com, obtained on November 19, 2018) was disabled when you disabled TLS1.0 which caused MSSQL service to failed to start, which is a dependency service required for Eminent Ware Data Grid service to run.

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

https://support.microsoft.com/en-ie/...-version-1-2-t (© 2019 Microsoft, available at https://support.microsoft.com, obtained on April 18, 2019)

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 https://support.microsoft.com/en-ie/...oft-sql-server (© 2019 Microsoft, available at https://support.microsoft.com, obtained on April 18, 2019)

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.