Symptoms

The K2 Blackpearl environment has upgraded to 4.6.11 from 4.6.9. The update of Blackpearl is successfully. Before installing K2 Connect 4.6.11, the previous installed K2 Connect 4.6.9 was running without any issue. After upgrading K2 Connect to 4.6.11, the SAP Connection is tested successfully. However, it cannot get the 4.6.11 K2 Connect Service to start.
 

Diagnoses

When logging as the K2 Service Account and opening the K2 connect Admin tool, K2 connect's machine key is not displayed. This explains why the K2 Connect service is not started. The behavior is usually indicated that the K2Service/Admin account doesn't have full DB permission to K2 Connect database or the K2 service account has no full permission to Connect folder (C:Program Files (x86)K2 connect).
 

Resolution

Granting K2Service/Admin account full DB permission to K2Connect database allowed the K2 Connect admin tool to pull back the machine key. After providing the license key, the K2 Connect service was able to started.