In addition to all of the links below, which are not specific to Windows Server 2019 or to Sage 50 2019 (except for the issue with multiple versions of the MySQL daemon, we had a problem with the Connection Manager memory setting (cache buffer) being too high.   I don't recall the setting that worked, definitely less than 1024 MB.  May have been 128 MB.

https://support.na.sage.com/selfservice/viewContent.do?externalId=11112

https://support.na.sage.com/selfservice/viewContent.do?externalId=21799&sliceId=1&openedFromDocument=true

https://support.na.sage.com/selfservice/viewContent.do?externalId=16375&sliceId=1

Hello Johnny7,

Thanks for reaching out! Our support team advises that both Windows Server 2019 and Sage 50 CA version 2019 products were launched around October 2019. Therefore, Sage 50 CA has not been tested and optimized to work with Windows Server 2019 yet. This doesn't mean it wouldn't work however.

The System Requirements (KB 93522)  for Sage 50 2019, still note that the dedicated servers recommended, include: Windows Server 2016, Windows Server 2012, Windows Server 2012 R2, Windows Server 2008 R2, Windows Small Business Server 2008 R2.

Terminal Services: Windows Server 2016, Windows Server 2012, Windows Server 2012 R2, Windows Server 2008 R2

See these resources for instructions:

You may want to create a support ticket on the portal regarding your issue. Tickets are monitored directly by the technical support team.

Other Helpful Links:

• How do I create and view a Support Ticket via the Sage Partner Portal
• For steps on how to resolve issues with download access, please click here for the KB on the Error: "Service cannot be reached" when navigating on the Customer/Partner Portal
  
  

You can also reach Sage via one of the following methods:

Online chat: www.sagecity.com/resources

 Phone:   1-866-996-7243 during regular business hours, Monday to Friday, 9am to 8pm ET, excluding holidays.

Hope this helps!
Erzsi

Hi, thanks for the responses. I have gone through all of them and nothing has helped.

Hi, is the Connection manager up and running on Server 2019 and it is the same version as the workstation?

if yes, try article 10303

possible install full version of 2019 on server see if sample open, if sample opens on both server and workstation, then for sure is network settings.

hope this helps