Sage upgrade from Standard 2018 to Premium 2019 (SQL), performance issues (VMWare)

SOLVED

Hello All,

Does anyone have an issue with performance with just navigating menus, etc with Sage 100 when migrated to SQL? Just doing something simple like opening "Company Maintenance" can take up to 30 seconds. The SQL Server itself and the Sage host server are not slow and the network is also not slow. The servers are all new and the disks the VMware is sitting on are all SSD. All of our other services are fine but only this server seems to have some sort of delay before starting any new window. If you run any Crystal report it will run instantly. 

Thanks for your input,

MFALS

  • 0 in reply to Kevin M

    Hello Kevin,

    Yes all sage folders are excluded on server and on workstations. They also had me change the vmware network card to be vmxnet3 instead of e1000. Neither seemed to have made much of a differennce.

  • 0 in reply to MFALS

    Do you see this speed issue on the server? When you changed the firewall on the one workstation did the speed change? If you only changed the settings on the client machine it could be the server that has the firewall slowing it down. Make sure it is fast on server first then go to the client.

  • 0 in reply to MFALS

    Did testing in MAS90 mode make a difference?

  • 0 in reply to MFALS
    SUGGESTED

    in regard to exclusions and slowness on the server, you might want to exclude common components folder (C:\Program Files (x86)\Common Files\Sage\Common Components) and local workstation Crystal Reports folders (C:\Program Files (x86)\SAP BusinessObjects).

    Also, have you tried launching the Sage 100 shortcut "run as administrator" and also in MAS90 (Standard) mode by launching the PVXWIN32.EXE manually (see Sage Knowledgebase article # 21025  How to run Sage 100 Advanced or Premium in Standard mode or "MAS90" mode?  This could help determine if the Application Server service is an issue.

  • 0
    SUGGESTED

    Do you have PEP turned on?  This can be disabled safely from the Administrator login menu.

  • 0 in reply to Kevin M

    I think you mean DEP? Yes it's as windows services only.

    As far as standard mode is concerned. I tried it today from the client machine and it was the same or slower. 

    I also tried to launch as administrator as someone asked earlier and that did not help. 

    I also just tried to turn off real time protection on the server and launch on the client running directly on the server and it still took 30 seconds to open company maintenance. 

  • 0 in reply to MFALS

    I meant PEP.  There have been a couple instances of problems when the service went down, and if you have a firewall blocking the address I could see how that might slow things down.

    I know Sage won't like me saying this but I disable it on every system I install.

  • +1 in reply to Kevin M
    verified answer

    oh that, the last sage support person turned that off.

    I think I found something that helped. So I went into the server and client network configs and disabled IPv6, added the domain name to the domain suffix and now my menus are loading in about half the time. 15 seconds is still pretty long but i'll take it over 30 seconds. 

  • 0 in reply to MFALS

    15 sec is what I see for the launcher but other menu items would usually be a little faster. So it looks like it was a network issue trying to route to and from the server. Glad you got it to go faster

  • 0 in reply to T-Man

    the 15 sec is to open any menu inside of the app. So it's still slow but it's definitely faster now. Why exactly I don't know without detailed logging from Sage. Support is telling me that they can't do detailed logging and to use perfmon. Not sure how Perfmon is going to give me details of what Sage is doing during the long periods of time.