When K2 is configured to use SQL Server alias and SQL is hosted on a separate machine from the K2 server, the K2 Server service fails to start after upgrade to 5.3, when K2 Configuration Service is up and running.
NOTE: This issue only occurred when you use initial version of K2 5.3 installer (5.0004.1000.1), updated installer (5.0004.1000.2) which addressed this issue is already available for download and old installer has been removed from the portal. You can see information on installer specific fixes in K2 Five (5.3) release notes under "Installer Resolved Items in K2 Five (5.3) (5.0004.1000.2)" section.
When attempting to start the K2 Server service using Services snap-in, you receive a warning message "The K2 Server service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs." as shown on the screenshot below:
When starting K2 Server service in console mode the following error is displayed:
Console output text:
The following error gets logged in the K2 Configuration Service log when attempting to start the K2 Server service:
To resolve this issue you need to perform the following steps:
You can now just download updated 5.3 installer (5.0004.1000.2) where this problem does not occur. Workaround below can still be if you use old 5.3 installation package (5.0004.1000.1). More details about fixes included in updated 5.3 installer can be found in the K2 5.3 release notes under "Installer Resolved Items in K2 Five (5.3) (5.0004.1000.2)" section.
1. Edit appsettings.Production.json configuration file located in [INSTALL DIR]\SourceCode.Configuration.Api" and replace the SQL alias name with the SQL Server name in the K2ConnectionString as shown below:
2. Restart the K2 Configuration Service
3. Start the K2 Server Service.