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
  • 0

    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.

  • 0 in reply to SpencerH

    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.

Reply
  • 0 in reply to SpencerH

    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.

Children