Sage 300 RemoteApp Sessions Freezing

One of our clients using Sage 300 2014 through RemoteApp on Windows Server 2012 has been experiencing occasional session freezes. It happens to several different users (the ones who work in Accpac the most), but not everyone.  It most often (but not always) happens when the Print button is clicked to print a Crystal form or report. The client has two locations. This happens at both locations, but at one, they tell us that if they wait a few minutes, they can resume work. At the other location, where freezes occur more often, someone with the Admin password (usually me) has to force the user's Accpac session to close, using that function in the Current Users screen. The client has two beefy servers, one dedicated to SQL Server, the other dedicated to Sage 300, both hosted at Rackspace. We have other clients with the same setup (but not at Rackspace) who have no such issues. We have so far not been able to pin this down. Any ideas?  Thanks.

Parents
  • 0
    We had one client with occasional database disconnections that were very puzzling. In our case they happened between noon and 1pm on Wed. I knew that we were on to something when, after daylight saving time went into effect, that our problem time was now 1pm to 2pm on Wed.

    What we finally discovered was that the virtual machines were being backed up at that time. Normally the backup would take 5-10 seconds. One of their servers was taking 20-30 minutes and this was causing the user to lose database connectivity.

    We identified the problem timeframe by running a batch file that pinged the database server every 10 seconds and logged the results to a file. We could look in the file and show that the server was disconnecting when it should not have had any problems. This issue didn't show up on my Event logs because it transcended the server itself.

    So maybe see if there is something happening to the servers vs within the server.
Reply
  • 0
    We had one client with occasional database disconnections that were very puzzling. In our case they happened between noon and 1pm on Wed. I knew that we were on to something when, after daylight saving time went into effect, that our problem time was now 1pm to 2pm on Wed.

    What we finally discovered was that the virtual machines were being backed up at that time. Normally the backup would take 5-10 seconds. One of their servers was taking 20-30 minutes and this was causing the user to lose database connectivity.

    We identified the problem timeframe by running a batch file that pinged the database server every 10 seconds and logged the results to a file. We could look in the file and show that the server was disconnecting when it should not have had any problems. This issue didn't show up on my Event logs because it transcended the server itself.

    So maybe see if there is something happening to the servers vs within the server.
Children