RDP Problems in Sage 50 and How to Solve Them?
Many Sage 50 users have faced a plethora of problems on a Hosted Desktop environment. There were issues while launching, generating reports, and general navigation in Sage 50 when accessed from an RDP server. While the length and breadth of these issues are diverse, the common theme is – slowness in performance.
For instance: When Remote Desktop Service Host role is installed, generating reports would take insane amounts of time, about 4 hours, which should not take more than a few minutes even with heavy workloads. However, when RDSH role was uninstalled, the reports were generated within the desired time. Ideally, it should be a bit faster on RDS server as it has high-end configuration (typically a dual Xeon server with 64 GB RAM). If this has been the case with you, let us look at the causes of RDP problems in Sage 50.
Cause of RDP problems in Sage 50
There can be many causes for the issue, which can be easily fixed with proper checks within the internal system. Many users flock to Sage support when they are not able to solve RDP issues. Though Sage has become remote desktop compatible since v11, the Sage support is still not very adequate. If not Sage support, what can you do? First of all, you can self-identify the cause of the problem, and then solve it with respective suggestions.
The most pertinent issue which causes slowness would be huge file size or anti-virus. If you want to check if the size of your files is slowing your Sage down, you can perform compression and re-indexing operations. Additionally, you can remove redundant files, clear temp cache, delete repeat files, and perform a check again. In many cases, the number of concurrent users working simultaneously can be the cause of slowness too. If this is taken care of, the slowness issue would majorly subside.
More reasons for the slowness issue
Another reason for slowness would be the action of firewalls, which maybe blocking the operations to perform optimally. If you want to check if anti-virus or firewalls are the cause of slowness, you must install RDP role without firewall or anti-virus in an isolated environment If it is still painfully slow to load on RDS server, you must deep dive to Sage 50 error logs which includes checklist of multiple things. Check the disk IO and disk queue time, and the kind of disk used also plays a major role in speed – SSD or traditional HDD. Upgrade to a Solid-State Drive (SSD) device to check if it makes a difference.
Other checks include audiovisual scanning of Sage folders because this can be also be the cause of slowness. The way disks are raided can be the reason which may hinder speed. Also, check issues such as the compatibility of your Windows version with your domain controller. The speed of your network can also be a factor which can’t be ruled out.
There have also been cases where VPN have caused RDP problems. Evaluate the list mentioned above and take perform the action of either fixing it or removing it. If you want to perform the checks, the ideal time would be to do it when there are no users in the system. Even after above cause and effects, if Sage doesn’t work nicely, you can look for other options such as Virtual Desktop Infrastructure (VDI).
Is it a common problem with all Sage products?
Many users complain that the Sage products are designed clumsily to support Remote Desktop compatibility. Though we will stay away from generalization that Sage is always slow with RDP, we have many customers with Sage 50 which work well on our VDIs.
Apps4Rent have solved a range of RDP problems that arise in Sage 50. If you are facing any RDP issues with Sage 50, follow the checklist of things mentioned in the blog that maybe causing the issues in your RDP server. If nothing works, our experts will work out a solution that fits best for you to enable a seamless Sage experience on RDP server.
Apps4Rent has been in the cloud hosting business since 2003, serving more than 10,000 customers across the globe. Feel free to have a consulting call with our cloud experts. Call now!
