web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Create a second environment for Management Reporter

(0) ShareShare
ReportReport
Posted on by 4,130

Hi,

I'm in the process of upgrading GP 2013 to GP 2016. the new version will be installed on a new server.

already completed the GP portion 

One of  component I need to copy to the new server is Management Reporter

I thought this should be straight forward. here is what I did:

- Backup the MR database from old server and restore it to the new server

- Install MR and set to connect to existing server ( which is the new server)

Is there anything else I need to do to make sure the new MR is not pointing to the old server?

The reason I'm asking is because when I open the console on the old server, it shows some error log related to the deployment on the new server!

Do I miss anything?

Thank you,

  

*This post is locked for comments

I have the same question (0)
  • JoshP Profile Picture
    Microsoft Employee on at

    Hi Alaa,

    The documented steps to move a MR database from one environment to another are logged in the following KB article:

    2744330 Error messages when you restore a Microsoft Management Reporter 2012 database: “The operation could not be completed”

    support.microsoft.com/.../2744330

    Thanks!

  • Alaa Ramadan Profile Picture
    4,130 on at

    Thanks Josh

    Do I have to remove the ERP integration from the current server before backing up the DB?  I do not want to get rid of the current deployment before I make sure the new server is up and running with new MR installation

    Also, Is there any setting in the DB referencing the old server?

  • JoshP Profile Picture
    Microsoft Employee on at

    Hello Alaa,

    The detailed documentation steps in KB 2744330 guide you through the tested process to move a MR 2012 database. This is the recommended process. If you would like to inquire about alternate steps other than what has been documented, please open a support case.

    Thanks!

  • Suggested answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,061 Moderator on at

    HI Alaa,

    I've never removed the original integration, before doing backup & restore of the MR DB to the new server..

    However, when you setup the new MR release on the new server, you'll have to redo that integration, but mostly going to hit the error message not being able to connect to the MR database, and as described in the KB article, this is due to the encryption of the data in the DB. You have to follow the steps to reset the encryption key and provide a new one, by using the SQL script from the KB.

    Be careful if you're at the same time upgrading the CU level, and install a different connector, as it might rename your company ID's with a -curr appended.

    Starting from scratch with a fresh new setup and importing all the definitions is also a good way to get rid of historical reports that are filling your old MR database.. in case you won't keep them. It's a little more work, but sometimes worth of it.

  • Alaa Ramadan Profile Picture
    4,130 on at

    Thank you Beat, I'm more comfortable with the fresh installation approach with exporting the definition from old  to the new deployment

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Dan Liebl Profile Picture

Dan Liebl 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans