8/14/2010

FRx to Management Reporter Migration

If you are looking to migrate from FRx to Management Reporter, There is an inbuilt migration wizard in Management Reporter to do the same. I don’t need to specify the steps involved in the migration process as it has been covered in much detail elsewhere on the blogosphere. Here is a perfect link to accomplish the same.

FRx 6.7 to Management Reporter Migration

However, Hold on before running the wizard if you are on Management Reporter RTM edition. If you are running Management Reporter RTM edition for Dynamics GP 2010, you’d run into an error that says 'Windows Authentication is not supported for Microsoft Dynamics GP’. I heard this occurs even if you choose SQL Authentication. If you observe the event logs, it might be like this

  Message: Microsoft.Dynamics.Performance.Reporting.DataProvider.Service.DirectLinkException: Windows Authentication is not supported for Microsoft Dynamics GP ---> Microsoft.Dynamics.Performance.DataProvider.GeneralLedger.GLConnectionException: Windows Authentication is not supported for Microsoft Dynamics GP
   at Microsoft.Dynamics.Performance.DataProvider.Core.TraceManager.Publish(Exception sourceException, Boolean throwException)
   at Microsoft.Dynamics.Performance.DataProvider.GeneralLedger.GP.GLProvider.HandleConnect(EntitySettingCollection settings, CredentialCollection credentials)
   at Microsoft.Dynamics.Performance.DataProvider.Core.SourceSystemProvider.Connect(EntitySettingCollection settings, CredentialCollection credentials)
   at Microsoft.Dynamics.Performance.DataProvider.Core.SourceSystemConnection.Open()
   at Microsoft.Dynamics.Performance.DataProvider.Core.SourceSystem.CreateConnection(SourceSystem system, EntitySettingCollection settings, CredentialCollection credentials)
   at Microsoft.Dynamics.Performance.DataProvider.Core.SourceSystem.Connect(EntitySettingCollection settings, CredentialCollection credentials)
   at Microsoft.Dynamics.Performance.DataProvider.GeneralLedger.GLSystem.Connect(Guid providerTypeId, EntitySettingCollection settings, CredentialCollection credentials)
   at Microsoft.Dynamics.Performance.Reporting.DataProvider.Server.DirectLinkService.GlConnect(Guid providerTypeId, EntitySettingCollection settings, StoredCredential credential)
   --- End of inner exception stack trace ---
   at Microsoft.Dynamics.Performance.Reporting.DataProvider.Server.DirectLinkService.GlConnect(Guid providerTypeId, EntitySettingCollection settings, StoredCredential credential)
   at Microsoft.Dynamics.Performance.Reporting.DataProvider.Server.DirectLinkService.ConnectInternal(Guid entityId, StoredCredential credential)
   at Microsoft.Dynamics.Performance.Reporting.DataProvider.Server.DirectLinkService.<>c__DisplayClassa.<Connect>b__5()
   at Microsoft.Dynamics.Performance.Reporting.DataAccess.Server.SecureService.<>c__DisplayClassb`1.<SecureExecute>b__a()
   at Microsoft.Dynamics.Performance.Common.Service.ServiceBase.BaseExecute[T](Func`1 executor)
Component: Microsoft.Dynamics.Performance.Reporting.DataProvider.Server.DirectLinkService
User: DEMOGP\managementreporter

Currently, This is identified as a bug in MR RTM and there is a workaround suggested to get away with this issue

1.      Uninstall MR RTM

2.      Install MR Beta (Server Components and Migration Wizard - https://mbs.microsoft.com/fileexchange/?fileID=0843903d-3544-49f5-af37-3e80ccd0384b

3.      Perform the migration using the beta

4.      Export reports into .tdbx.

5.      Uninstall MR Beta

6.      Reinstall MR RTM

7.      Create companies in MR and then import in reports from the .tdbx file.

(Source: Dynamics GP Forum)