Good Evening

Interesting query! 

Is Evolution running from a Terminal Service on a RDP connection or is it locally installed?

Also, please confirm the Evolution version 

Finally, have you already deleted the agent key in the local PC Registry Editor?

Kind Regards

Bennie 

Same issue here - started a few days ago and this morning all users cannot log into Evolution including trying directly on RDP server.

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.

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.

Hi All,

Is there a long-term solution for this issue ? We have a client who is experiencing the same issue.

Sage 200 Evolution 9.10.2.000 is running on a Windows Server and clients are connection via an RDP session.

Previously deleting the agent registry keys temporarily resolved the issue. This time around it has not.

It seems to fix itself however this is highly disruptive as the client is constantly working.

I have not found a permanent solution on my side - and the problem comes and goes. The MULTIINSTANCE trick is somewhat tedious as well for every user to do. 

A new workaround (without having to reinstall) that works for me, is get a successful login going on the server for any one company (run Evolution as admin). Use the MULTIINSTANCE trick if the server is also playing up with the login. Leave the server logged into Evolution - all RDP user will be able to log in now without issue (at least that's best workaround I've tested so far). 

Good luck.

WOW!!!  Thanks Akash for sharing such valuable insights!

Many blessings 

Bennie 

Thank you Akash!