admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2021-10-18 18:55:32 +00:00
parent 705861a618
commit 8d44174369
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/8.0/ayanova/docs/adm-license.md
View File

@@ -15,12 +15,12 @@ User starts AyaNova, no key found this is one of the options in UI License form
3) was this being used before and want to use existing data? Link to restore page in docs
# User count exceeded
If you receive an error message stating that the User count has exceeded this means that AyaNova has found there to be more Active Scheduleable Users than the license permits.
If you receive an error message stating that the Server is locked due to exceeding licensed active scheduleable User limit this means that AyaNova has found there to be more Active Scheduleable Users than the license permits.
This is typically a sign that the database has been directly edited outside of AyaNova and needs to be fixed by restoring from backup made *before* the editing took place or, if it is absolutely *certain* this was the only change made, setting Scheduleable User's to Active=false to match the *Licensed* Active Schedulable user count.
Directly editing the database circumvents the many checks and balances for ensuring data integrity can lead to breaking AyaNova completely or worse: problems that are not noticed for some time resulting in data damaged beyone repair.
Directly editing the database circumvents the many checks and balances for ensuring data integrity and can lead to breaking AyaNova completely or worse: problems that are not noticed for some time resulting in data damaged beyond reasonable repair.
Modifying the data outside of AyaNova itself should never be attempted unless specifically directed to by AyaNova technical support department.
Modifying the data outside of AyaNova itself should never be attempted unless directed by AyaNova technical support personnel.
Your support agreement does *not* cover damage caused by directly editing the database and if this is found to be the case it may lead to costly down time and hourly charges at our discretion to bring the database into compliance.