This communication was sent 10 January 2025. Notice 25-QI | 10 Jan 2025 Sage 200 Professional - Licence Issue We’ve recently identified, and are currently investigating an issue where Sage 200 Professional will report an error that the licence details are invalid when entering them. The issue will only occur in very specific circumstances, and to date we’ve only have one report into our teams. How does the issue occur? - An expired serial number is reactivated (i.e. expired to active). As we don’t reactivate subscription serial numbers once they have expired we don’t expect customers to experience this scenario.
- A customer/partner account has two serial numbers on the account and there is a need to swap from one to another. This can happen in the following circumstances:
- Expired Customer – this would be if a partner doesn’t notify us in time that a cancellation is delayed, and a new serial number needs to be supplied.
- Historical Licences – when the customer cancels their live licence, we set up a new historical licence and these details must be entered/swapped into the product.
- Test & Recovery Licences – as part of our work to migrate these to subscription we’ve been providing new licences and cancelling the old licences. All non-subscription test and recovery licences are set to expire 60 days after they are migrated. Please refer to our original communication for more information.
- Partner Licences – as part of our work to migrate these to subscription we’ve been providing new licences and cancelling the old licences. All non-subscription partner licences are set to expire on 31 January 2025. If you haven’t requested your licence, or swapped it in product please do so as quickly as possible. Please refer to our original communication for more information.
- Developer Licences – as part of our work to migrate these to subscription we’ve been providing new licences and cancelling the old licences.
What steps are we taking? We continue to investigate the issue, however in the meantime there is a very simple workaround, you can see the error and the workaround in our knowledgebase article. We apologise for the inconvenience caused. |