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 :
Microsoft Dynamics GP (Archived)

Stumped by performance issues with GP2018 installed on client, talking to database on server (Windows 10 vs 7)

(0) ShareShare
ReportReport
Posted on by 12

Hello!  I work in I.T. (support engineer) for a marketing/media company that uses Microsoft Dynamics GP for the financial software. During the 6+ years I've worked here, the Accounting team has gone through several migrations to newer versions with the help of a consulting firm they've used.  Most recently, we upgraded from GP2015 to 2018R2.

The program I'm running into is that performance has gotten absolutely terrible since the Finance folks were upgraded from Windows 7 machines to Windows 10.  We only have 5 - 7 users who are ever in the application at a time, tops.  Typically, only 2 or 3 are using it at the same time.  Everyone has wired gigabit Ethernet connections back to a Windows 2012R2 server on a VMWare ESXi virtual machine, acting as the back end server for their clients.  If I have someone go back to an older Windows 7 laptop and sign in on it, there's a noticeable speed increase over the same GP2018 installation on a new Windows 10 laptop.

I've read some of the common suggestions to improve performance, such as disabling "Windows Defender" anti-virus and excluding certain extensions like .DIC from real-time scans.  All good ideas, but seeing little to no speed improvements after doing that.

If one of us runs GP2018 via a Terminal Server session so they're using the entire thing from the server itself, it runs much better. So this definitely seems to be a performance issue related to the database connections between the client and the server.  Just wondering if there's an optimization or a change with the SQL connectors I should be doing on the Win 10 clients for this?

*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
    RE: Stumped by performance issues with GP2018 installed on client, talking to database on server (Windows 10 vs 7)

    Hi there,

    This is unfortunately a very difficult issue to debug / troubleshoot, as there are so many things that can have changed between the Win7 & Win10 upgrade..

    I agree that usually the full Dynamics GP client should run very smoothly when deployed on the local computers/workstations.. but I almost always recommend my clients to use a Terminal Server to publish the GP application, as we can much better control the environment, and also the TS sits usually much closer to the SQL server where the data resides, which helps avoiding network issues that might come up.

    Where could you start ? maybe setup some wireshark tools to monitor the trafic between the workstations and compare the data between Win7 & Win10 computers.. you might find out that the packet size for the network trafic isn't optimized in W10 and could be the culprit.

    Can you be more explicit on which operations in the GP client are poor in performance ? is it when posting transactions ? is it when running reports ? smartlists ? exporting data from GP ?  Are the dictionaries shared on a network or local (.DIC) ?

    There are so many places that can have an issue with the performance, that it is hard to tell without directly looking at it.

    I've have many clients that are running GP 2018R2 from W10 workstations and they run very well and smoothly.

    Hope this helps.

  • twyrick Profile Picture
    12 on at
    RE: Stumped by performance issues with GP2018 installed on client, talking to database on server (Windows 10 vs 7)

    Thanks for the response!

    I can tell you we have several custom .DIC files that we copy to the Data folder on the workstations, so those shouldn't be getting accessed from the server.

    The sluggish performance pretty much begins as soon as the user logs in with their login/password and selects a company to work in.  There's a long delay getting all of their initial menus fully populated on the screen and ready to go.  Switching screens to run reports or post transactions or any of that seems really "laggy".

    We did wind up publishing GP2018 via Terminal Server and gave our users that alternative to use, and it's much faster.  But we've had some headaches with the Terminal Server sessions too, like one user in particular who seems to constantly have "stuck" TS sessions with solid black screens when she tries to reconnect.  We have the Terminal Server configured to log people out after 15 minutes of inactivity, but that doesn't seem to help in her case. Her session will go idle and sit there indefinitely, until I force a disconnect or a logoff (depending on the situation, sometimes I can only force a disconnect -- and other times, both options are present to choose from), from the server.

    I should probably mention, too, that we use a 3rd. party product called PaperSave which has a GP client.  That definitely adds more time to the whole login process, since the PaperSave plug-in launches and has to establish a cloud connection before GP goes to the main menu, ready to run.  Nonetheless, we had this installed under Windows 7 too and the sluggishness I'm seeing now is just much more than the delays I already know that program added.

    You may be onto something about the network packet size not being optimized? I'm suspicious that Win 10 has different defaults for that than Win 7 did over the erthernet adapters?

  • Suggested answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on at
    RE: Stumped by performance issues with GP2018 installed on client, talking to database on server (Windows 10 vs 7)

    Hi @twyrick,

    Would you be able to  create a copy of the DYNAMICS.SET launch file on a Win10 client and remove the PaperSave GP add-on to check if this is what's causing the delays.. ?

    Usually Microsoft would suggest in such situations to proceed by elimination and remove all un-necessary add-ins from the launch file and start the client with a bare minimum GP config (usually around 18-20 modules in the DYNAMICS.SET)

    I've see customers that have up to 35-40 modules setup when including most of the GP modules and a lot of 3rd-party ISV products. That can be a lot of pressure to the starting client.

    One of my clients is running a launch file with 27 modules and the start of GP is under 50 secs from their TS / Citrix server..

    I've my own demo system running off an Azure VM with 2018R2 and 22 modules installed, and GP starts within 20 secs into the home page and ready to work.

    Have you timed some of your GP starts from different locations (i.e. SQL server, TS server, W7 & W10 workstations) to compare facts, not just impressions ? I had to do this exercise once to show Microsoft that there was really an issue with some configuration, but you need some factual data, and not just once.. but repeatable values.

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…

Abhilash Warrier – Community Spotlight

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

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans