Hi  @sirjoe;

Please note that I'm following recent opened ticket, it's still under investigations regarding similar(related) issue and i will revert back to you with proper workarounds.

Follow up with this k2 documentation for other relevant information http://help.k2.com/onlinehelp/k2five/devref/5.2/default.htm#Concepts/AuthConnectStrngs.htm%3FTocPath%3DConcepts%2520and%2520Development%2520Techniques%7CAuthentication%2520and%2520Connection%2520Strings%7C_____0

From my expertise I think this should be resolved at custom third parties integration application,

 https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/connection-strings-and-configuration-files#retrieving-connection-strings-at-run-time

https://docs.microsoft.com/en-us/ef/ef6/fundamentals/configuring/connection-strings

Should you find the above information useful, kindly mark such as "Kudu, Accepted Solution and/or MeToo options", as this will other community members.

Kind regards;

Widson.

Thanks Widson.

I hope to hear from you.

Cheers

Hi  @sirjoe;

I'm still in the lookup, however it's clear that the problem is that the app is looking for the connection string in its app.config rather than the .dll config

Usually this issue is caused when configuration entries for Client Tools and Authoring APIs were migrated from .NET machine.config files to the individual application's config files.

Kindly find attached document that will assist you reconfiguring(rechecking)  log files as a step troubleshooting your situtation.

Will revert back ASAP

Should find the above information useful kindly mark as "Kudo and/or Accepted Solution".

Kind regards;

Widson.