Losing connectivity to the database (DB) or attempting to connect to the database timing out is what the user sees. Behind the scenes, this means that the DB has become very busy for some reason. Figuring out that reason might be a challenge.

In one customer instance, we found that they had inadvertently changed the date of the GW3 machine by a drastic amount. Again, this was a mistake on their part, but it was done. The GW3 DB purging logic took over and said "oh... I have a lot of records that I need to get rid of". It then used all of its resources to delete old database records. Normally, on a regular basis, this happens after the maximum database time length in small chunks, like one hour at a time and the user never notices the impact. Some GW3 bundles come licensed for 60 day limits on the DB to keep the cost of the bundle lower. You can easily see that if the PC date were moved ahead by one month or more, that GW3 would see that it had a large amount of housekeeping to do.

We are taking steps for future releases to help protect the user from these type of mistakes.