App Control: Parity server service crashing after server upgrade

Products

• Carbon Black App Control (formerly Cb Protection)

Issue/Introduction

• Console not loading with "Network error while trying to communicate with Cb Protection Server"
• 0KB or 1KB file size for C:\Program Files (x86)\Bit9\Parity Server\Configlist\Configlist.xml.egk
• Multiple .DMP files in C:\Program Files (x86)\Bit9\Parity Server\Support
• ParityServer.exe crashing repeatedly seen in the Windows System events

  Faulting application name: parityserver.exe, version: 8.1.10.3, time stamp: 0x5ef6517a
  

Environment

• App Control Server: 8.1.0 - 8.1.10

Cause

ParityServer.exe is unable to import the OpenSSL library file "Libeay32.dll' needed to encrypt the configlist files

Resolution

Please upgrade to Server Version 8.5+ as the affected binaries causing the issue are no longer used. 

If an upgrade is not possible, in some cases the following steps can allow the server service to become stable again. 

1. Login to the CB Protection Server and download the fixed "Libeay32.dll" from the CB Vault
2. Stop both the CB Protection Server and Reporter services
3. Backup the existing Libeay32.dll in the folder

C:\Program Files (x86)\Bit9\Parity Server

4. Replace the Libeay32.dll with the newly downloaded one
5. Start the Cb Protection Server and then the Reporter service 

Additional Information

• Once the file is replaced you may still receive the "Network error while trying to communicate with Cb Protection Server" for 5-10 minutes after services are started
• The timestamp of the confilist files will update when they are successfully re-built in this folder:

C:\Program Files (x86)\Bit9\Parity Server\configxml