This has been caused by the failure of the RDB program to contact our licence server.
We will need access to your SQL server to implement a workaround while our engineers resolve this issue - please contact us via the MyAccess portal and reference the title of this article.