Symptoms

Issue 1 - K2 Service takes 3 minutes to start.
Issue 2 - K2 for SharePoint configuration - Logged Error: Deployment Error: Authorization Failed
 

Diagnoses

We found that the client was exposing all SMO's to endpoints and also that there was security settings setup specifically for the environment and SMO in workspace
 

Resolution

Resolution1
The reason why the K2 Service is taking so long to start is because of the following line in the K2HostServer.exe.config
smoServices enableEndpoints="true"

This goes and creates endpoints for your smartobjects.
http://help.k2.com/onlinehelp/k2blackpearl/devref/4.6.4/webframe.html_k2_smartobject_services_introduction.html

When we changed this to false. the service started immediately. However you are using endpoints. so we changed it to back to true again.

Regarding the Endpoints, you will need to specify the endpoint statically in the following stack







You could try and add your endpoints here.
http://help.k2.com/onlinehelp/k2blackpearl/userguide/4.6.4/webframe.html_walkthrough_create_managed_endpoint.html

and

help.k2.com/onlinehelp/k2blackpearl/devref/4.6.4/webframe.html_configuration2.html

This should expose only the endpoints you need.


Resolution2

We resolved the issue by performing the following steps:
-Remove all security settings in SmartObjects > Security > SmartObjects Administration
-Set the default environment to Development to match the web.config for the smartforms > Designer > workflow -Remove security setting for Development Environment
-Remove all security for the following SmartObjects in SmartBox > Security
--SmartBox Administration
--FormsImage
--K2 Process Field Management
--PDF File
--SharePoint Integration Settings Events
--SharePoint Integration Workflows Events