Sinch Community

Hey,  I would like to share info around this topic to share the problem.  The case is that database replication script was written for disaster recovery use cases, but can of course be used in this kind of actions as well. But the main problem with the script is that components it's using are deprecated by Microsoft. Earlier those were part of Microsoft SQL Server.    Now I cannot remember what was the component, but can find it out if needed. Also one of Sinch Contact Pro partners were trying to take the script to modern day some time ago, but right now I don't remember the results. Will check with the partner.  Br, Jukka ... View more

Hi Glenn,   thanks for your answer. We now installed Sinch Contact Pro on an Azure SQL Managed Instance with SQL authentication. There were a lot of changes to do in installation script in regards to SQL authentication, but for Azure SQL Managed Instance we had to comment only the line with Simple recovery model at Monitoring Database. Our first tests didn't show any problem, but during our advanced tests we realized that we are not able to save some settings in System Configurator. We always get a MSDTC error message in Agent Server logfiles and therefore saving was aborted. How did you handle these errors?   Thanks. BR, Thomas ... View more

Contact Pro has no Spring4Shell dependency. We are not using the component. BR, Jukka ... View more

Hi Jukka,   that's really great news. Thanks for your help.   Best regards, Thomas ... View more

Hi Thomas,  Good that you asked and here is the answer shortly from onprem point of view:  FP18 dependency for log4j has been replaced in the hotfix with our own logging solution and we are no more using log4j in Contact Pro Hotfixes for FP17 and older contains actions recommended by Apache in this document and logging is using log4j In other words we recommend customers upgrading to latest release or minimum to apply hotfix to mitigate the problem.  //Jukka ... View more