Symptoms

1.
K2 connect for Visual Studio throws error:
Connectionstring not set or access to registry is denied

2.
How do I deploy this changes to Connect Service object?

3.
Received a timeout expired error when attempting to publish these Service Object
 

Diagnoses

 1.
https://www.k2.com/onlinehelp/k2connect/userguide/current/default.htm_How_to_Start_a_new_Project.html?Highlight="Run As Administrator"

2.
1. Deploy directly from Visual Studio

a. By selecting the correct K2 environment in the K2 Object Browser as per:
http://help.k2.com/onlinehelp/K2connect/UserGuide/current/default.htm_Setting_Target_Environment.html?TocPath=Develop|_____3

b. Then selecting the default repository that you had attached in your screenshot.

2. The Service Object can also be deployed by copying the .svd file (service object definition) to the target environment and adding/removing this service object using the K2 Administration tools/K2 Client Console.

3.
Tried increasing the timeout values from below article but was not successful:
http://community.k2.com/t5/K2-blackpearl/Timeout-error-publishing-K2-connect-Service-Object/ta-p/79120

Attempting to Stop and Start the K2 Connect service from the "K2 Service Object Designer" was also not successful and resulted in the timeout error. On the K2 Connect server, we located in the Event Viewer > Windows > Application logs that the K2 Connect license had been expired.
 

Resolution 

1.
Visual Studio will need to be started with the "Run As Administrator" option when developing K2 Connect Service Objects.

2.
Service Object was published directly from Visual Studio.

3.
Requesting a new License key allowed the K2 Connect service to start up successfully as well as allowed the publishing of the Service object without timeout error.