it is opened now, but if we close then again we need to do the same script in cmd to open. There is no permanent solution ?

correct if you log out completely you will need to run the script, or try using the exist and log off which tales you back to login page, there are new builds available if you are on the latest version. although from what we have seen in testing the issue is resolved from the 24th

Good morning, 

It has something to do with the SSL coding in Sage.  How can this be fixed?  Without us doing an upgrade from V10.1.5 to the latest?

Looking forward to your soonest reply.

Kind regards

Emmarine

Mine does not log in - it goes to the Sage Evolution Registration screen.

I put in a new registration code last week and that code does not work now.

Good Morning Everyone

Please refer to the following article posted in Sage City:

www.sagecity.com/.../sage-200-evolution-unable-to-open---solution

in this case you will need a new rego, its a little tricky but basically the issue is in launching the app with the date as 23/02, so the workaround is to trick it by changing the date, open the app, then change your date back. So you are not really changing the date but it gets past the validation.

This is a temporary solution from us as Business partners to assist with a seemingly temporary problem. 

From what we hear coming through the problem is only on today's date, and will be working from tomorrow. 

Not the best workaround for an AD environment with users not having admin rights to change date/time settings, especially if they are not onsite at Head Office.......

Agreed, but right now we have multiple environments to cater for and any assistance to get any percentage online is a step closer. 

If the customers are working on a terminal server, change the time zone to 12 hours back, let everyone open the sage icon, and then change the time zome to correct zone for today's date.  Let them then log onto sage

I entered office today to face the horror of 23/02 bug or whatever it is with Evolution.

The above definately works, however, there is an updated .exe for version 7.20.9.14 users available at Sage ftp.

If replaced on local servers/user computers, then the app works and behaves normally without the need to do the above steps.

The location for updated exe is under your version > February 2022 fixes.

Thanks for the update Irfaan!