Symptoms

Diagnoses

Resolution



We started by killing the K2 blackpearl service, this allowed the setup manager to complete, and identify other issues, mostly configuration files that were pointing to the C drive instead of the installed location on the D drive. (multiple IIS configurations were pointing to the c drive causing problems because K2 was installed on the D drive)

There were also issue with the K2 DB at least one stored procedure was missing, so a repair was run to fix this issue and once that was completed some XML in one of the configuration files (web.config) was also fixed K2 started and was working as expected.