Disconnected Agent Due To WinHTTP Communication Error 12019

Products

• Carbon Black App Control (formerly Cb Protection)

Issue/Introduction

• Agent shows as Disconnected in the Console.
• Disconnected Agent Logs generate a Trace.bt9 file which includes:

  Server Communication: WinHTTP communication error: 12019

Environment

• App Control Server: All Supported Versions
• App Control Agent: All Supported Versions
• Microsoft Windows: All Supported Versions

Cause

Microsoft defines WinHTTP Error [12019] as:

ERROR_WINHTTP_INCORRECT_HANDLE_STATE: 12019
The requested operation cannot be carried out because the handle supplied is not in the correct state.

Typically this is due to the Proxy not allowing the connection.

Resolution

1. Log in to the endpoint and use an administrative command prompt to temporarily stop and unload the Agent:

   cd "C:\Program Files (x86)\Bit9\Parity Agent"
   dascli password <GlobalPassword>
   dascli tamperprotect 0
   net stop parity
   fltmc unload paritydriver

2. Reset the Proxy:

   netsh winhttp reset proxy

3. Load the driver and start the Agent:

   fltmc load paritydriver
   net start parity

4. Wait a few minutes and verify the connection was restored.

Additional Information

• In some cases the WinHTTP error 12017 may also be seen.
• The Agent does not officially support a Proxy and a bypass to the Server Address may be required.