I'm unsure where this post actually belongs, so here it is in general.

Yesterday I upgraded our Sage from 2022.x to 2023, the process went fine throughout the several machines including the server.

However afterwards it was noted that all of our companies are extremely slow to open. I tested on the server itself and the time to open was just fine on that local instance.

Thinking that I had potentially missed something firewall or network related we tested with the firewall off on both sides to no avail. I contacted Support chat and was told that they aren't responsible and don't have the port information for the application...smh(do better). I continued on looking and did manage to nail down the ports and application requirements through a packet capture and online resources.

The required ports and applications are open( to the best of my knowledge)

The server is a windows 2016 machine with 16GB of ram and resides on a raid 10(4 drive) array and an intel i7, the OS is on a ssd raid 1, highly unlikely to be OS or hardware related. I did however run benchmarks to ensure that disk writes, disk latency, cacheing were all working as expected, and they were.

I have reviewed the sage connection manager configurations, tried increasing the pool size to 512 from 128, this had no impact towards the problem so it was reverted. Likewise I confirmed the port within the firewall and even attempted changing the port number, again the changes reverted after not seeing a change.

I did speak with Sage yesterday(tier 2 support) and the gentleman was very knowledgeable and pleasant to deal with. He did try to elude to this being network related however moved passed that once I showed via wireshark and other methods that the network is not blocked nor modified from before the upgrade to now. He did escalate for a callback monday evening, however I am still trying to resolve this so have moved forward to here.

We have multiples of companies, I have run scans on the companies, migrated them to local to test, likewise copied fresh db's over to have the same problem. The connection is maintained through a Domain Controller via smb2, the response time from host-client is appx 2ms. The wait time on stream is upwards of 30 seconds before initial stream closure(which fwiw doesn't FIN, the stream appears to just stop, the majority of said stream is actually PSH traffic, which I thought a bit suspicious but don't stare at streams all day so likely don't know what I'm on about)

I have a test machine that I'm able to uninstall/re-install etc, the majority of standard troubleshooting has been done and still this problem is just glaring at me.

Is there something I am missing here or can anyone offer any input/advise to try please? I've marked this as ODBC but I suspect it's more mysql related.