Sage Evolution 200 Login Problems


Hi everyone

Need some advice please, we picked up that every now and then some of our clients experience this issue with SAGE Evolution 200 , that whenever they try and login to Sage Evolution, it will simply hang on the start screen after they typed in their credentials, and display "Not responding" and then the application will crash.

This happens with any user agent name and usually on all the listed companies, sometimes this comes right by itself in an hour or so, and other cases we have to completly uninstall and re-install SAGE for it to work correctly again.

We had this happen at three of our clients already this week.
We restarted the SQL services as well as reboot the server, nothing worked.

Anyone else that perhaps experienced this type of issue before that can assist ?

Parents Reply Children
  • 0 in reply to Akash21

    Sent a mail to Sage Technical for assistance and they provided feedback that this has been an ongoing issue.

    They are not sure on the cause of this, but found that the only real solution at this stage is to uninstall / re-install Sage Evolution on the affected Workstations or if its a RD server case then on the server.

    In extreme cases you need to use Revo Uninstaller to completely remove any left over settings and registry entries, but personally did not have to go to such extremes yes.


    Hope this helps someone.

  • 0 in reply to AFI Support

    I have what I assume is a temporary fix, to "bypass" the issue.

    The program shortcut must be on /MULTIINSTANCE (if not already). When the "not responding" login comes up, open the program shortcut a second time and try to login again. Now it will login and the shortcut can be changed back (if the user was not a multiinstance user). The bypass seems to fix whatever was blocking the login.

    And I say blocking deliberately - when the problem occurs the front page login screen is not accessing the SQL database - trying incorrect password does not give you the immediate incorrect password error, but checking the settings for the company still finds the company databases fine.