This error is generic and does not say much and you need to dig deeper into the message logs on the Exchange 2019 Server. What I could see in the logs was