No ratings

Unable to start K2 Connect on clustered server




Symptoms


When attempting to start the K2 connect service on one of the two servers in the cluster we get the following error:
"K2 Connect Server failed.
Time out has expired and the operation has not been completed"

Looking in the Event Viewer the following is logged:
"Service cannot be started. System.Data.SqlClient.SqlException: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_ApplicationInstanceComponents_Destinations". The conflict occurred in database "K2Connect", table "dbo.Destinations", column 'ID'.
The statement has been terminated.
at SourceCode.ServiceObjectModel.Server.Runtime.Service.ConnectClientRegistration.GenerateConnectInterfaces()
at SourceCode.ServiceObjectModel.Server.Runtime.Service.ServiceObjectModelServerService.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)"

Diagnoses


The specific error can be caused if the Default K2 connect destination has not been set correctly in K2 connect Administration.


Resolution

Client deleted and recreated the destination configuration in K2 connect Administration on the affected server and the service could be started successfully.

Please see the following KB article for additional information on Default Destinations: http://help.k2.com/kb000345





Labels: (1)
Version history
Last update:
‎08-27-2021 05:10 PM
Updated by:
Contributors