Original MR 2.0 Server – set up of this server and Management Reporter was done at least 6 or more years ago and the application has not been updated since that first time.
Version of the Management Reporter shows as 2.0.1700.66 (SP2) This is the same for both the client and the server as reviewed on the Control Panel >> Add Remove screen
http://db:4712
Service Account : AHFMR\mgmtrpt
Password : unknown (as this was created by an IT staff that is since long departed the company)
New MR 2.1 CU10 Server – set up this server was started less than a week ago
Version 2.1. CU10 of Management Reporter from CU10 disk image downloaded to the AIHSDB server and was then installed on this server
First step was to create a Service Account, and when the IT Staff here saw that there was a Service Account that was already labeled to be to used by Management Reporter, they simply changed the password.
During the installation and configuration of the Management Reporter on the new server
http://aihsdb:4712 (original) http://aihsdb:4713 (final)
We attempted to update the original MR DB that we had created on the AIHSDB server by restoring a backup of the DB Server database. This failed.
We spent a day trying different things to get the AIHSDB server installation to take. Finally, by installing the Service and Process Services without the GP Legacy or DataMart installations we were able to get the installation to work. After the Services were installed, running the Configuration a second time allows us to create the Legacy connector as well the Datamart database.
We have installed the Server on AIHSDB and encountered no errors.
We then went to go back to the original MR installation (DB Server) and to export the Report Definitions from the original MR. This is when we learned that we were locked out.
The error message is that we can not connect to the existing MR Server, do we want to identify a new server. When we click yes – we get the option to enter a new server id. If we attempt to use the original MR Server ID – http://db:4712/ it fails to connect and states that there is no server available.
We have checked the services on the DB Server and they are running – using the new password –
We have not touched the DB Server installation or any of the existing MR Client installations since we started this process as we did not feel we needed to have any interaction with that server. We planned to take a copy of the database and update it as noted in the installation notes for MR CU10. We could not find any thing on the versions we had to update from or too – so, hoping that is not the issue.
We have started and restarted all the servers and there are no issues reported by any other applications regarding access the DB Server – this is a live production server and there are over 40 users reaching this SQL installation and getting no errors – so we find it hard to believe that the IP or ODBC connection might be a challenge. We can still attach to the old GP 2010 software and data on that server from the same client.
This appears only to be related to MR and the MR2012 CU10 installation.
We have discussed in detail with Redbeard (thanks for that Harry) so we need to get much deeper and do so as soon as possible.
*This post is locked for comments