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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Management Reporter + Legacy + Data Mart migration issues

(0) ShareShare
ReportReport
Posted on by

Here is our scenario:

Our ManagementReporter database exists on a server with SQL Server 2008 (no TDE) with a default port & Windows Server 2008 R2, and is being moved to SQL Server 2012 (yes TDE), non-default port, & Windows Server 2012 R2.

When installing Management Reporter on the new App server, we have run into an issue that appears unsolvable when reaching back to the new SQL server 

We can configure the Services and Legacy GP + Data Mart ERP integrations well-enough, however, we receive the following error under the "Service" logs.

Error retrieving company information for Dynamics GP GL Adapter. The connection to the Microsoft Dynamics GP database failed. The server name and user credentials are required.
Component: Microsoft.Dynamics.Integration.Common.TraceLog

Event Viewer shows the same thing.

We have followed the instructions here :https://community.dynamics.com/gp/b/dynamicsgp/posts/how-to-move-your-management-reporter-2012-database-to-a-new-server , running the master key drop, reset/certificate drop. but we continue to receive this error.

I don't have the ability to access the old master key from the previous server (still running though).

Alternatively, we can create a new Management Reporter database during installation, but if we do that, we lose the Report Library (I understand we can export/import the building blocks).

So far, there appears to be no way of moving the report library to the new MR database, and no matter what, the SA credentials and Server Name doesn't appear to be passed into several MR tables that hold credentials/connectors, as they are both encrypted, and set in read-only XML.

I have narrowed down the connections to the following tables:

dbo.Reporting.ControlCompanyIntegration
dbo.Connector.Adapter
dbo.Connector.MapCategoryAdapterSettings
dbo.Reporting.ControlConfiguredIntegration
dbo.Reporting.ControlCompany

But it seems the SA credentials aren't getting to where they need to be.

It's very clear that the "Management Reporter 2012 Application Service" is the key to updating the credentials and replacing the references to the old server with the new server, but no matter what, unless we lose the report library, we can't get MR running without errors.

Does anyone have any ideas that might help?

*This post is locked for comments

I have the same question (0)

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans