Hi all,
I currently have a delicate situation with Management Reporter after an upgrade. We upgraded a customer from GP2013 to 2018. The GP 2018 was moved to a new SQL instance. We also did the upgrade of Management Reporter to the new SQL instance. They are using the legacy system, so I upgraded the MR database and recreated the ERP integration in Management Reporter console. I was able to connect to MR Report Designer using my new SQL credentials. Last Friday, we shutdown the old SQL server, because everything seemed running well. Today users were getting errors trying to log on Management Reporter. What I have noticed is that the 2 MR services (Application Service and Process Service) were still using a connection to the old SQL server. The ERP integration though, was connected to the new instance. I recreated the 2 services, now everything runs well. My issue is that last week the client made some validation in MR so see if all the data was correct after the upgrade. They validated data, before and after the upgrade. I would like to know if the data they have validated last week may be wrong because the services were not pointing at the new SQL instance. I'm not sure if the Application Service and Process service were looking at the right database.
Thank you
*This post is locked for comments