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

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / GP 2013 Management Rep...
Microsoft Dynamics GP (Archived)

GP 2013 Management Reporter Issue

(0) ShareShare
ReportReport
Posted on by oscarc619 315

Hello all,

     Last night we installed Windows updates on our 3 GP servers.  One is the application server, one is the management reporter server and the third runs SQL.  After rebooting the servers all seemed to be well.  Late today a couple users reported they could not run Management Reporter within GP.  They got the error "Management Reporter cannot connect to the server"

I logged on to the MR server and noticed the Management Reporter 2012 Process Service was stopped.  I went ahead and started it back up.  I waited a few minutes and noticed it stopped again.  I checked the Service alerts in the MR 2012 configuration console and noticed that when the service started a lot of errors in the form of "System.Data.SqlClient.SqlException (0x80131904): The target principal name is incorrect." and then after quite a few of those I see the service stop.  I didn't set the servers up but in the past we haven't had any issues after rebooting the servers.  Any ideas on what could be going on?  Thanks so much for the help

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Redbeard Profile Picture
    Redbeard 12,931 on at
    RE: GP 2013 Management Reporter Issue

    The likely scenario is the machine was unable to see the Domain Controller, which also functions as the DNS server.

    Shut down all the machines and then restart them in sequence, starting with the Domain Controller, the the file server, SQL Server, reporting server, session central and then the session hosts.

    Here is a link to the full post regarding this problem.

    community.dynamics.com/.../troubleshooting-the-microsoft-dynamics-gp-2013-sp2-web-client-target-principle-name-is-incorrect.aspx

    I would assume it is also possible there are other reasons why the machine running Management Reporter cannot resolve the machine name...  you could also try:

    ipconfig \flushdns

    check firewall settings for windows, which might have changed during an update...

  • oscarc619 Profile Picture
    oscarc619 315 on at
    RE: GP 2013 Management Reporter Issue

    Thanks for the response.  That didn't help in this situation.  After doing more digging around I found that a couple of the SQL service accounts on our SQL server were not correct.  They started it up and were running but it wasn't the NT Service account.  GP worked fine but MR was giving us the error.  Once I cleared it out and added the account MR began talking fine to SQL.  Thanks again for all the help.

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

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

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

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans