Symptoms
Corrupted K2Server Database While Attempting to Add an Additional Server to the K2 Farm.
Diagnoses
While attempting to add an additional server to our K2 staging farm, I accidently used an actual server name, instead of the database server name, this some how corrupted the K2Server database.
23:3: SourceCodeLog.LogMsg: 17:00:10:>> Logged Warning: Workflow Server License key failed to update: Cannot open database "K2Server" requested by the login. The login failed.
Login failed for user 'DENALLIXK2Install'.
23:4: SourceCodeLog.LogMsg: 17:00:10:>> Logged Warning: Unable to create database user DENALLIXK2Service: The server principal "DENALLIXK2Install" is not able to access the database "K2Server" under the current security context.
Resolution
"Turns out the installation account did not have permissions to open the database".
Usually the installation account will need require the 'dbcreator' and 'securityadmin' role on the SQL server. If a single 'K2' database schema/ 'K2HostServer' database in 14 databases schema already exists (in an upgrade/reconfiguration scenario) the installation account will need access to these database(s) via perhaps 'dbowner' or 'dbreader'/'dbwriter'.
