Symptoms
K2 server is not running
Diagnoses
Commonly related to host name changes. The old host name is still being referenced in Workspace environmental library env when we deployed the workflow. Pl advise on how to resolve this issue.
Resolution
We were able to fix the original issue with Workflow deployments by renaming all references to the old hostname in the Workspace > Environmental library. However, a new error popped up "System.IO.FileNotFoundException: The dependency file 'D:Program Files (x86)K2 blackpearlBinSourceCode.Workflow.Client.dll' could not be found. The file will not be written to the bin folder" The dll looked to be still referening the older server name and could not find the file or path.
We ran a Full repair on blackpear/SmartFroms and K2 for SharePoint. Workflows are now deploying normally.
