Showing posts with label Management Reporter. Show all posts
Showing posts with label Management Reporter. Show all posts

Wednesday, 5 September 2018

Management Reporter - Couldn't retrieve the list of available databases: The connection attempt failed.

You get the error as seen below when trying to deploy the Management Reporter Data Mart under the "Database GP Connection Information" section.
"Couldn't retrieve the list of available databases: The connection attempt failed."

I experienced it with MR CU16 and other persons have experienced with older versions of MR. 

What to do:
To resolve the Dexterity Shared Components 12 needs to be installed. You can retrieve this from a GP2013R2 install file.

Once installed you can complete the MR Data Mart deployment.

Wednesday, 1 August 2018

Management Reporter - Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only

So you are trying to install Management Reporter
You have installed the services
You are trying to deploy the data mart or the legacy and no matter how many times you put in the sa password you get the error above.

How to fix?
-Use a higher version of Management Reporter. The version you are using is possibly not compatible with your SQL version.

Monday, 4 June 2018

Management Reporter Error - Change Tracking not enabled for tables GL00100, GL00102, etc

So you are deploying Management Reporter Data mart and get the change tracking error.

Now this would result in you having to set each table noted to have change tracking enabled.

Instead of doing this you can -
Go straight to GP,
Admin -> Setup-> Company-> Company, click the Options button, turn off Enable GL Reporting and Turn it back on. This will reset the change tracking and you can proceed.

Some tables your error would note:
GL00100
GL00102
GL00200
GL00201
GL10000
GL10001
GL10100
GL10101
GL12000
GL12001
GL20000
GL30000
GL32000
GL40000
GL40200
MC00200
MC40000
MC40600
SY00300
SY40100
SY40101

Monday, 21 May 2018

MR Deployment Error

MR takes long to complete initialization.

The error below is found in the service deployment log

Sequence contains no elements
--- Exception Dump ---
Caught Exception: [Microsoft.Dynamics.Integration.Service.Tasks.RecordException] Sequence contains no elements
Stack trace:




To resolve execute the below on the Management Reporter database.
MERGE Reporting.ControlCompanyIntegration AS TARGET
USING Reporting.ControlCompany AS SOURCE ON (TARGET.ID = SOURCE.ID)
WHEN NOT MATCHED BY TARGET AND GLEntityID not in ('5F878A3C-5F4C-4806-B786-5CAB52C98F0F')
--Update the “1” as needed based on value in Reporting.ControlIntegrationSource
THEN INSERT (ID, SourceID) VALUES (SOURCE.ID, 1);

Sunday, 16 July 2017

The remote server returned an error: (407) Proxy Authentication Required.

So you are installing Management Reporter Application and Process Service in the environment. Clean install. No reports or anything else exists. Then.... you get the above error! It looks like everything was installed though. :s

What next?
- Remove the Application and Process Service.
-Delete the Management Reporter database in SQL that was just made by the process.
-Go into Internet Explorer and turn off the Proxy Service.
-Re-run the install for the Application and Process Service.
-Voila!

Tuesday, 15 November 2016

Management Reporter Crash when Importing Reports

You click Building Block Groups and go to import some reports, when you navigate to the file and click import everything freezes.

This is an issue caused by a microsoft update. It was resolved in versions of Management Reporter 2012 CU13 and higher. If you are unable to use a version higher then all you have to do is not place your mouse icon into the area where the reports are on the import window.

Hence, just click import, navigate to the location and click select all and then proceed with the import, do not put your cursor in the top window or anything as this is what causes the application to crash. Seems to be some pop up message issue cause by a microsoft windows update.

Monday, 13 June 2016

Management Reporter Database in Suspect Mode

So you check SQL and notice your backups stop running.

Only to notice it is because your MR database is in suspect mode. To resolve the issue i would first suggest, removing MR from the database backup plan and complete your GP backups.

Then run the below script to resolve the MR suspect mode issue. Then create your separate plan for MR backups.

Script:

EXEC sp_resetstatus ManagementReporter;

ALTER DATABASE ManagementReporter SET EMERGENCY

DBCC checkdb(ManagementReporter)

ALTER DATABASE ManagementReporter SET SINGLE_USER WITH ROLLBACK IMMEDIATE

DBCC CheckDB (ManagementReporter, REPAIR_ALLOW_DATA_LOSS)

ALTER DATABASE ManagementReporter SET MULTI_USER

Sunday, 6 March 2016

the microsoft.ace.oledb.12.0 provider is not registered

You receive the above error when running the FRx to MR Migration Wizard.

You must install the "AccessDatabaseEngine_x64"