Author Topic: WAIT_TIMEOUT for multiple operations / login to PCS  (Read 1406 times)

andy__d

  • EA Novice
  • *
  • Posts: 6
  • Karma: +2/-0
    • View Profile
WAIT_TIMEOUT for multiple operations / login to PCS
« on: July 10, 2025, 07:56:55 am »
Hi, we've been having a few users that have been running into an issue with EA and ProCloud Server: they're seeing regular WAIT_TIMEOUT messages appearing when they're trying to load a model, and when working within a model. We've tried a lot of troubleshooting, and, in the end the only solution that worked was to get them a new laptop from IT (which isn't a solution, just dodging the issue).

The thing is, now I'm getting the issue after my PC was upgraded to Windows 11. It worked perfectly before the update (same PC hardware, same network connection), and it works perfectly on my colleagues machines that were upgraded at the same time (same PCS, same model, same hardware specs, same version of Windows 10 / Windows 11, rolled out through System Center).

When connecting, I will see one or more "WAIT_TIMEOUT" error messages, with different SQL queries listed. If I can get it to load, as I make selections in the object browser, I will get these errors every few operations - which is getting really very irritating.

I do not see these errors working with a local model, and I do not see these errors working with a direct connection to a database - I cloned our model database and tried connecting to it directly, and it operates normally (so, the same model in a JET file works fine, and the same model in a connected SQL server works fine), the issue only appears to happen when I connect through PCS. My colleagues are all connecting to the same PCS without issues, and, when the WAIT_TIMEOUT errors are appearing, the server itself is barely ticking over (1% CPU). We're currently using 16, but I've also tried installing the 30 day trial of 17.1 (which was a good way to test fully uninstalling, deleting the APPDATA/SparxSystems directory, and reinstalling a new Sparx EA instance on my desktop) but I'm still seeing the same issue in 17.1.

Any thoughts on what other troubleshooting steps I could use to try to work out why this is happening and rectify it? It seems this is something that a few other users have seen (there's several WAIT_TIMEOUT errors listed in this forum) - but, those have mostly been associated with specific activities: the closest other thread to what I'm seeing was this one from 2020: https://sparxsystems.com/forums/smf/index.php/topic,43487.msg257547.html#msg257547 - so, it's not a unique issue, but, as I noted, it's happened to 5 other users in our environment over the past couple of years, so I expect it's going to happen again - and we're expanding our user base and want to be prepared and figure out what the mitigation steps are so we can fix it if it reoccurs (without having to get a new laptop) - plus, as I spend a good proportion of my day working in Sparx EA, I want to stop wasting 6000 ms waiting every time this occurs :) - thanks very much for any suggestions or pointers!