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 install error- Unable to obtain the database collation

(0) ShareShare
ReportReport
Posted on by

I hope someone can help with this. Install fails when adding GP Datamart.

Management Reporter install error- Unable to connect to the Dynamics GP database to obtain the database collation.

Thanks,

Kevin

Installing Management Reporter 2012 on SQL 2016, Server 2016 for Dynamics 2016.

  • Dynamics Version: 16.00.0620
  • SQL Version: 13.0.4206
  • Management Reporter Version: 2.12.16000.17
  • Service Account is the Domain Administrator and Display name is not blank
  • Removed and re-installed several times
  • The Server appears slow, could this be a timeout issue?
  • Firewall is turned off and port 4712 has an inbound rule

Deployment Log

11/9/2017 3:54:35 PM - Checking SQL Server version; result: 13.0.4206.0 
 Machine: MAINDC
11/9/2017 3:54:35 PM - Checking SQL Server version; result: 13.0.4206.0 
 Machine: MAINDC
11/9/2017 3:54:35 PM - Checking whether database ManagementReporterDM exists 
 Machine: MAINDC
11/9/2017 3:54:35 PM - Checking whether current user has SQL role sysadmin 
 Machine: MAINDC
11/9/2017 3:54:35 PM - True 
 Machine: MAINDC
11/9/2017 3:54:42 PM - Beginning Dynamics GP data mart integration configuration. 
 Machine: MAINDC
11/9/2017 3:54:42 PM - Database collation is . 
 Machine: MAINDC
11/9/2017 3:54:45 PM -  Unable to connect to the Dynamics GP database to obtain the database collation. Check the GP database connection configuration.
 Machine: MAINDC

Event Log - MR Logger Operational

There was no endpoint listening at http://ServerName:4712/CompanyService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on at

    Hi Kevin,

    Did you checked your SQL server default collation where you GP is setup ?

    According to the installation documentation of GP, that should be SQL_Latin1_General_CP1_CI_AS ..

  • Community Member Profile Picture
    on at

    Yes, the server default collation is SQL_Latin1_General_CP1_CI_AS. Each database has that collation as well.

  • Community Member Profile Picture
    on at

    Yes, the server default collation is SQL_Latin1_General_CP1_CI_AS. Each database has that collation as well. The issue is connecting to SQL - "Unable to connect to the Dynamics GP database to obtain the database collation". Any other ideas?

    Thanks.

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

    I'm out of office today,  but have you checked this thread?

    community.dynamics.com/.../212689

    It's about AX,  but would probably apply too.

  • Community Member Profile Picture
    on at

    Beat,

    That does not look like my issue but I did check the Temp db properties. MR tries to get the Collation from GP or SQL and somehow gets denied. It may be a SQL 2016 issue. I have not had this issue before, but there always seems to be something when installing MR. This is SQL Express, but I do not think that is the issue.

    Thanks,

    Kevin

  • Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on at

    Kevin,

    Let me check this out tomorrow,  as I just upgraded my test VM from SQL 2012 to 2016, though it's the developer version, not express. …

  • Verified answer
    Community Member Profile Picture
    on at

    Thanks.

    I was able to get the Legacy Data Provider to install. I truly think this is a Security issue. SQL was installed as the Domain Administrator and that account was used as the service account for MR. Small one server 4 user shop.

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

    Hi Kevin,

    It is definitely recommended by Microsoft to create a dedicated service account on the domain to run the MR 2012 service on the server.. not use any other existing domain user, and really not the Domain Admin.. that's a bad idea.

    The MR 2012 domain service account doesn't need any special security access, you just need to add it to the SQL Server security to provide him the proper security roles to create and access the ManagementReporterDB database.. that is : db_owner and public (and I checked on my own server, that user is not even db_owner... ).. In fact on the MR2012 setup documentation, Microsoft provides following requirements for the service account:

    -Be a user assigned to the Administrator role. (This is within MR2012 security.. not Windows or SQL)

    -Have an Active Directory® domain account user ID and password.

  • Community Member Profile Picture
    on at

    Hi Beat,

    Thanks for taking the time to respond. I will try using a dedicated service account the next time I have access to their system.

    Thanks,

    Kevin

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