Hi all,
I have a test upgrade we are doing to 2025 on a Windows 2019 Server and the system is is just crawling. 7-10 seconds to open a task.
It's the same on the server or workstation.
I worked through the performance KB and checked settings, adjusted the NIC, etc.
It's running on hyper-V and has pretty killer level specs. Networking checks out fine too.
So I used the trusty sysinternals tool to see whats happening - I took a proc monitor 'capture' of both the client and workstation to see where the delay was. from the client POV there's a TCP request that goes in and has a 3-4 second delay in the response from the server.
what I found interesting is on the server, the bulk of the load time seems to be the sage server is reading through the data files. The reads to C:\Sage100 are very very fast and take up only a very small portion of the time. However, the pvxwin32.exe process on server is also reading from the UNC path over SMB and that's very slow. If I sum up the time spend on the UNC path - in a 7 second capture, 3.09 seconds were just reading from the UNC.
SOTA.ini, the shortcut, the server, etc are all pointed at the C:\, I have no idea why sage would need to try to access the share drive on advanced!
"2:25:35.3051028 PM","pvxwin32.exe","12040","ReadFile","C:\Sage\Sage100_2025\MAS90\MAS_System\SY_Context.M4T","SUCCESS","Offset: 8, Length: 248","0.0000075"
vs
"2:25:35.2831818 PM","pvxwin32.exe","12040","ReadFile","\\sage2025v2\sage\Sage100_2025\MAS90\MAS_System\SY_Context.M4T","SUCCESS","Offset: 64,000, Length: 31,744, Priority: Normal","0.0328000"
Am I configuring something wrong? Is it normal for the sage server to be reading from the UNC and not the local drive?
Any other ideas would be great...
------------------------------
Calvin Morrison
Operations Manager
Kissinger Associates, Inc.
215-429-9384
------------------------------