Open Forum

Expand all | Collapse all

GP2018 R2 with Windows server 2019 datacenter

  • 1.  GP2018 R2 with Windows server 2019 datacenter

    Posted Oct 20, 2020 01:29 PM
    Hi!
    We had network issues and recreated our GP SQL server and GP app server.  I have discovered they installed Windows server 2019 datacenter on both the new servers.  We are having issues with users locking up, slow performance and after inserting my .dll for copy/paste intercompany no users could log into GP.  Are these issues that could be caused by having Windows server 2019 installed?  We are trying to decide if we need to recreate these new servers?

    Thanks!

    ------------------------------
    Marilyn Hunter
    BCforward
    Indianapolis IN
    ------------------------------
    Academy - Online Interactive Learning from Experts


  • 2.  RE: GP2018 R2 with Windows server 2019 datacenter

    Posted Oct 21, 2020 08:05 AM
    Hi Marilyn,
    We upgraded from 2010 (and another instance from 2013) and installed the new 2018R2 (modern lifecycle) on 2019 servers as well.  Our SQL Server is 2017 and we have not seen any performance issues like you are describing.  We have seen better performance across the board.  Make sure you are giving the new servers enough memory (I think the SQL server we have 24GB RAM and the app server 16GB RAM).  We generally have 8-10 users logged into the app server at a time without issue.  The issue we have is locking up when we go to print.  We believe that is due to printer drivers (we allow local printers to map through the RDP session) and have been removing that as an issue with static network printers for all users.

    If you remove the .DLL are users able to log in again?  When do you see GP locking up? (I am assuming it is GP locking up and not the entire server or RDP session)

    Thank you.

    ------------------------------
    Dave Magalen
    dmagalen@auroraplastics.com
    IT Manager - Aurora Plastics
    Streetsboro OH
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 3.  RE: GP2018 R2 with Windows server 2019 datacenter

    Posted Oct 21, 2020 12:04 PM
    Thanks for the response Dave.  We have 32GB RAM on the SQL server and 28GB RAM on the terminal server, our GP license is for 17 users.  We are using GP as a published app.  GP locks up randomly and not necessarily during heavy usage.  I had it lock up twice on me when I was the only user in the system and I was clicking to open windows.  It locks up everything to the point I could not even get to task manager and had to have someone sign me out from the terminal server.  GP started working when I removed the .dll and stopped again when I tried putting it back in.  We have also had boxes missing on the displays.  For instance when the print screen comes up to ask where to print or in series post there should be a box to the left of all the options and sometimes the boxes are there and sometimes they are not.  It will not let users check the boxes when they are not there.  If they log out of GP and back in it works.

    I am also seeing some .net errors in the event viewer.  Could those be caused by the server and GP not being compatible?

    At this point I am thinking of upgrading GP.  I don't know if these issues are caused by compatibility issues, but I feel like I need to eliminate that as a possibility.

    Thanks!

    ------------------------------
    Marilyn Hunter
    BCforward
    Indianapolis IN
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 4.  RE: GP2018 R2 with Windows server 2019 datacenter

    Posted Oct 21, 2020 01:42 PM
    So it looks like the server resources should work, even for just one person logged in.  I would not look that direction unless you just get slow response when many users are logged in.

    You should not get .NET errors (we don't see any) so you might be on to something there.  We have 3.5 and 4.7 installed on our app server.  But I would think GP would not have installed without .NET installed.  Having some option windows not open sounds like either those .NET errors are stopping it, or something with the GP app.

    I would make sure both .NET versions are installed and Windows updates are installed.  Then you can install the October 2019 update to bring you up to 18.3.  We are running that on 2019 servers without issues.

    Another step, if you can, is build another app server and point it to the same database and see if a clean install might help.  Maybe something was not right during the install of the app on the existing server.

    Thanks.

    ------------------------------
    Dave Magalen
    dmagalen@auroraplastics.com
    IT Manager - Aurora Plastics
    Streetsboro OH
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 5.  RE: GP2018 R2 with Windows server 2019 datacenter

    Posted 26 days ago


    Thanks for all the information!

    We have tested the upgrade to GP2018.2 and most of our issues are gone on our test server, so I think it was the incompatibility issue.

    I am still curious if anyone knows if the event below could be causing our slowness and lockups.  This is occurring on our app server.  I am being told that since it is listed in the event viewer as "Information" and not warning or error it can be ignored.  But my research leads me to believe this is something that should not happen and needs to be corrected.


    Thanks!


    ------------------------------
    Marilyn Hunter
    BCforward
    Indianapolis IN
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 6.  RE: GP2018 R2 with Windows server 2019 datacenter

    Posted 26 days ago
    I forgot - one other issue.  It appears the copy/paste function from David Lyn does not work with Windows server 2019 and/or GP2018.2 as I cannot get it to work in my test environment either.  Does anyone have a suggestion for what we could replace this with?  We mainly want to copy/paste intercompany transactions in the GL.

    Thanks!

    ------------------------------
    Marilyn Hunter
    BCforward
    Indianapolis IN
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 7.  RE: GP2018 R2 with Windows server 2019 datacenter

    GOLD CONTRIBUTOR
    Posted 26 days ago
    Hi,
    SQL Server memory paging is not something I personally would ignore. It will not stop the server from working, but it will have a performance impact. The impact will depend on the paging file and the speed of the IO that the page file is running from.
    SQL Server paging is usually either an indication the SQL is competing for memory resources on the host or that the capacity of the server is too small for the size of the active components of the database. This leads back to the question of the size of the server and the answer will always lie with how big the database is, how quick the IO is and the size of the typical operations. GP tends to use a large number of cursor based operations, which is best done if SQL can load as much of the requested dataset into memory, for a small database or low volume operation, this will work well with a small amount of memory. The very fact that SQL tells you it is paging, indicates to me that your server memory is too small for your needs, or that you have too many apps in memory at once.
    Just as a side point, new versions of SQL always bring new features and improved functionality and execution plans, which often means that hardware that is good for one version may not cope after an upgrade by just one version. An interesting point is that SQL has been improving the use of memory tables in the last few versions, which means that the use of memory can really help performance if the app supports it and the server has the resources.
    We have five SQL servers running SQL 2017 for 52 GP companies with 990 concurrent users. Each server has 512GB RAM and uses NVME drives and it still takes constant fine tuning to ensure that we run within our performance limits.
    For me, there just is no better performance upgrade for a SQL server than giving it all the memory you can and it will be the most rewarding performance upgrade you can make. Second to that is making you drives (especially temp and system - for paging) as fast as you can.

    Hope something helps.


    ------------------------------
    David Joosten
    IT Executive
    Premier FMCG (Pty) Ltd
    Midrand
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 8.  RE: GP2018 R2 with Windows server 2019 datacenter

    SILVER CONTRIBUTOR
    Posted 24 days ago
    Hi Marilyn,

    Just to be clear on your definitions of servers - If you have a database server (the server running only SQL) separate from your application/app server (the server only running the GP application), you shouldn't be getting this warning. It sounds like you may have a running instance of SQL on your application server That doesn't need to be there.

    You can run GP and SQL on the same box successfully for smaller deployments, but you may want to double-check your architecture and make sure you're not running a SQL instance  on the wrong server.

    ------------------------------
    Jeff Woodard
    Chief Technical Officer
    Transportation Financial Services, Inc.
    West Palm Beach FL
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 9.  RE: GP2018 R2 with Windows server 2019 datacenter

    GPUG ALL STAR
    Posted 21 days ago
    [Frown]  Whomever you had help you do the restore should have their knuckles rapped - several times.  You never change everything up like this to troubleshoot a problem because you end up causing more problems.  They should have replicated your existing/working environment to get you back up and going THEN suggested an upgrade plan.  (Just FYI, but datacenter edition is overkill for Dynamics GP and REALLY expensive in most cases.  Unless you really need it for something else, it's probably just a cost you don't need.)

    The other thing that is a big no-no is to change the OS, SQL Server version AND software at the same time - again because if something goes sideways you don't have a clue where to look to solve it.  From my 25 years experience, you want some time between upgrading each piece to make sure you have everything critical working before you alter one more variable.

    From what it sounds like, that .dll is fairly important to your day-to-day efficiencies.  But a .dll is an executable library reference that is built to link to other libraries.  They usually have to be rebuilt from version to version as the various libraries change.  And sometimes the libraries are NOT compatible from one OS to another.  If at all possible, I'd try to find someone with a developer platform who can look at the original then recompile for your current environment.


    ------------------------------
    Blair Christensen
    Database Administrator
    Oppenheimer Companies, Inc.
    Boise Idaho GPUG Chapter Leader
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 10.  RE: GP2018 R2 with Windows server 2019 datacenter

    Posted 20 days ago
    I am overwhelmed by the massive amount of very valuable information that everyone has provided.  It is amazing to me that so many people spent quite a bit of time composing long, comprehensive responses.  While I have 22 years experience with GP, I do not have little technical knowledge on the server side, other than SQL itself.  I do know to check version compatibility, but unfortunately the servers were built and connected to another program that has the GP server name hardcoded in about 50 places before I realized what they did.  (Don't even get me started on that issue). That forced me into a hurried upgrade to GP2018.2, which is definitely not the way I like to do them, but it was the only viable option.  Fortunately that fixed most of our issues and there were no issues after the upgrade.  So if anyone is reading this trying to determine if GP2018R2 works with Windows Server 2019 the answer is a definite NO.

    Our DBAs have no experience with GP and from what I understand it is a different beast than many other programs in SQL.  Which is why I appreciate all the server information provided that I have passed on to my team.  We do have a developer on our team, so I will get with him to see if he can adjust the .dll to work with our new server.  Since one response indicated the memory paging really was an issue, the server team worked on the terminal server and while I am not sure what they did I know it included installing updates.  Whatever they did, those issues also went away.

    In summary I feel like we are now running GP in a stable environment and so appreciate all the valuable information provided. Thanks for helping me through my panic!

    ------------------------------
    Marilyn Hunter
    BCforward
    Indianapolis IN
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 11.  RE: GP2018 R2 with Windows server 2019 datacenter

    GPUG ALL STAR
    Posted 19 days ago
    Marylin,
    I'd definitely second @Blair Christensen on the DLL issue you're runing into that could slow down or break your GP client.  A DLL is a very specific code that was written and compiled with a specific (more or less) Windows Version and libraries in mind.. Just putting it onto a brand new Windows server in a complete different version is like shooting for the stars and hopping you'll get something back.. I've seen this in my past that customers wanted to take with them old add-ons from older GP versions (2010, 2013) that used to work just fine and bring them on the latest greatest Windows & GP versions, and it would simply fail or cause weird things.
    You may want to look into some other ISV add-ons that support current GP releases to replace that Intercompany copy/paste feature..  Free tools that where developped years ago for GP tend to not be maintained (hence why they were free) and putting your business processes on them is quite a risky bet. ​

    ------------------------------
    Beat Bucher
    Business Analyst, Dynamics GP SME
    Montreal QC/Canada
    @GP_Beat http://www.gp-geek.com
    Montreal QC GPUG Chapter Leader
    MBS MVP (2015-2018)
    All-Star 2013
    ------------------------------

    Academy - Online Interactive Learning from Experts


If you've found this thread useful, dive deeper into User Group community content by role