You’re offline. This is a read only version of the page.
Announcements
Hello All,
I am having problem to login to Management Reporter only user works is SA. All other user is getting the following error.
I have checked the GL entity connection information already and it has correct server ID which is matches to ODBC. I already reset the password for other user including DYNSA but no user able to login and only user is able to login is SA.
Hi Babu,
Since this is Legacy, this error is usually caused by an encryption/decryption mismatch between GP and MR. The 'sa' account should always work because it is not encrypted. You'll want to do the following:
1. On a machine where GP is installed and working, check the ODBC (you will need this for later):
-Open File Explorer.
-Browse to C:\Windows\SysWOW64.
-Run odbcad32.exe.
-Under the System DSN tab, select the GP ODBC and click Configure.
-Take a screenshot of the exact value entered on the Server field. You will need this for later.
2. If you have other installs of GP, check that the Server field matches on those as well. Each of those fields has to be the same because it is used for the encryption of the GP logins.
3. Re-deploy MR legacy:
-Get all users out of Management Reporter and make a backup of the ManagementReporter SQL database.
-Log into the MR server with a network account that is configured as an Administrator in MR and a sysadmin in SQL.
-Start the MR Configuration Console.
-Select the legacy integration from the left under ERP Integrations and click the Remove button at the top-right.
-Click File -> Configure.
-Select the GP Legacy option and click Next.
-Enter the value you confirmed from the GP ODBC into the Database Server field. Enter the text exactly (space and case sensitive).
-Use the ‘sa’ account and select the DYNAMICS database from the drop-down.
-Click Next and Configure.
-Once deployed, select the legacy integration from the left and click the Import button.
-Enter ‘sa’ credentials again.
-Mark the “Skip Import” button next to any companies that aren’t “Already Imported”.
-Click the Import Companies button at the bottom-right.
-You may receive a message for each company saying something about updating the connection string. Click Yes or Ok through all of them.
4. You can now test MR. The ‘sa’ credentials should always work. If the GP credentials fail, you will need to have the user reset and re-encrypt them. This needs to be done from a machine where you verified the GP ODBC field is set exactly like you deployed MR:
-Log into GP with the user account in question.
-Change the GP password.
-Close GP, re-open it, and log in with the new password. Don’t skip this step as this is when it becomes re-encrypted.
-Restart MR Report Designer and test the login again.
Thanks Rachel,
Please note that my problem is not related to adding AD user to MR. I am logged into the test server where MR is installed and logging to GP with user ID SA works fine. Any other user other than SA wouldn't work. Sorry for not explaining this properly. There something to do with GP user login not accepted by MR. Please note that we are not using data mart.
Thanks,
babu
To troubleshoot Management Reporter connection problems you need to select OK to this message and then select Test Connection to get an additional error message. You also need to go to Event Viewer to get additional information on the error. In Event Viewer, select Windows Logs and select Application. Under the Source column, look for Management Reporter Report Designer or Management Reporter Services.
Cause
Cause 1
The Management Reporter Client installed is a different version than the MR Server. See Resolution 1 in the Resolution section.
Cause 2
The user trying to run MR has not been set up as a user in MR and therefore cannot connect. See Resolution 2 in the Resolution section.
Cause 3
The computer is not connected to the domain where Management Reporter is installed. See Resolution 3 in the Resolution section.
Cause 4
The time on the client and server is more than five minutes different (differences in time zones are permitted). See Resolution 4 in the Resolution section.
Resolution
Resolution 1
Check the Management Reporter Client install on the workstation and also check the Management Reporter Server install on the server. To check the version in Management Reporter, select Help, and then selectAbout Management Reporter. The MR Client install needs to be the same version as the MR Server install.
Resolution 2
Set up the user receiving the connection error within MR.
Run MR as a user that is set up as an MR administrator.
In MR select Go and then select Security.
Add the user who is receiving the connection error.
This may help you,
Rachel Gomez
#1
André Arnaud de Cal...
291,359
Super User 2024 Season 2
#2
Martin Dráb
230,370
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
