Common CollectionsMax Issues With Possible Solutions :: Hosted on Windows VPS Print

  • 0

CollectionsMAX is a desktop-based debt collection software suite that runs on the Windows Operating System. It can be installed on a single computer or on a dedicated server network. CollectionsMAX is a database-driven application that uses MySQL service in the back-end to run on the server.

Since CollectionsMax is a database-driven application, SSD Windows VPS is the most recommended option to host it. You can refer to our different SSD VPS plans here. Following are some of the frequent problems that occur with CollectionsMax software with its possible solutions.

  1. More often, you can access your VPS but CollectionMax runs too slow or does not even work. In such cases, you can try the given below suggestions:

    • Firstly, make sure that MySQL is running on your server. Type services.msc in the Run box, and a window will appear with a list of all services running. Next, check the status of the MySQL service. If it is stopped, start it from the Services window. If it is already started and your issue persists, restart the MySQL service.

    • Make sure that the MySQL service is not utilizing 100% CPU. This could be the possible root cause of the slowness issue. In that case, you can try to Restart the MySQL service OR Reboot your VPS. However, if this does not fix your issue, you should consider purchasing additional vCPU or upgrading the current VPS plan to the next level.

    • Make sure that there is enough free space on your VPS. If there’s not, log in to your server and remove the unwanted data. You may need to reboot your VPS after removing unwanted data because many services might have crashed due to disk space issues. Additionally, receiving an Error code 28 clearly indicates that your server is out of disk space. In such cases, you should consider purchasing additional disk space or upgrading your VPS to the next higher plan.

    • If you face connection issues after migrating your data from the old server to the new server, you should have a look into the permission constraints. Make sure that MySQL database user has the necessary permissions over MySQL database. Such types of failures occurred when the permissions were not set in the new server.

2. If you are facing a timeout expired error in CollectionsMax like given below:


    • Mostly this error occurs when you have too many idle connections. When you have too many idle connections, the MySQL server will eventually drop them out due to extensive memory consumption, and the above error will surface. When there are too many idle connections, and they do not get reclaimed, this could take the entire MySQL server down since MySQL will stop responding to requests.

    • In several cases, you may face this error when a connection is idle, and it is considered in use. MySQL server tries to re-establish the connection, and it cannot because the maximum number of connections has been reached in the thread pool. To fix this issue, log in to the server and, invoke the MySQL Instance Configuration Wizard, re-configure for a higher number of connections (try 100 or more as the default is 20).

    • You can also try to create a callback for the day. The callback system will ping the server every minute. It will keep the connection open.

      **NOTE: While you re-configure the instance, ensure that strict mode is NOT enabled (uncheck the box) and do not modify the root password.

    • Sometimes anti-virus software installed on the VPS/computer can also close idle connections. If you find such type of software, then remove it and use anti-virus software that doesn't close idle connections. For more information about such issues, you can refer to the CollectionsMax official forum.

Please be noted the above given are only the collection of past incidents, which may or may not be applied to your issue. For further support, you can directly contact the service provider of CollectionsMax for your concerned problem(s).


Was this answer helpful?

« Back