Hi Mike,

AUSE 001 is normally an error that indicates a problem contacting the update service. However, v20 is no longer a supported version so we're limited in the amount of advice or support we can give. Sage Technical Support would be able to advise in terms of upgrade options if you wanted to consider that?

Andy,
Sage UKI

The problem is indeed that the software cannot contact the update service. The error message is the smoking gun here. The reason why the software cannot contact the update service is because it is trying to use an older version of TLS that is no longer secure and has been deprecated so the update service no longer supports it.

At the time that version of Accounts was written (around 13 years ago) the technologies it was based on were considered secure. But as time and technology moves on, and hackers discover new exploits, what was once considered secure no longer is. Newer versions of Accounts have long since been updated to use newer and more secure versions of TLS so do not encounter this kind of issue currently. Note that I say 'currently' there as it is almost inevitable that given enough time even what are the latest version of the software today (v33) will start to encounter issues due to changes in underlying technology that interferes with them working as originally designed. Of course we will have been producing newer versions that stay ahead of technology changes so in another 13 years time we could be on v46 or even later.

This is unfortunately a common sort of thing to encounter when trying to run older software of any kind. Sooner or later something breaks. Upgrading is certainly the best option if at all possible

The problem is indeed that the software cannot contact the update service. The error message is the smoking gun here. The reason why the software cannot contact the update service is because it is trying to use an older version of TLS that is no longer secure and has been deprecated so the update service no longer supports it.

At the time that version of Accounts was written (around 13 years ago) the technologies it was based on were considered secure. But as time and technology moves on, and hackers discover new exploits, what was once considered secure no longer is. Newer versions of Accounts have long since been updated to use newer and more secure versions of TLS so do not encounter this kind of issue currently. Note that I say 'currently' there as it is almost inevitable that given enough time even what are the latest version of the software today (v33) will start to encounter issues due to changes in underlying technology that interferes with them working as originally designed. Of course we will have been producing newer versions that stay ahead of technology changes so in another 13 years time we could be on v46 or even later.

This is unfortunately a common sort of thing to encounter when trying to run older software of any kind. Sooner or later something breaks. Upgrading is certainly the best option if at all possible