Logging in through a database group or portal still pointed to the prior year produces the error This account has expired, even though the account's expiration date does not appear when checked through Security > Users under the main database group.
Environment
- New Year Rollover completed — the main database group's default database is now the new year database
- A secondary database group or portal — for example, the Summer/Summer School database group, or Teacher Portal — still defaults to the prior year database, since it was not updated to point to the new year
Cause
The account's expiration date is set on the record in the prior year database, which is now reachable only through the secondary group or portal still pointed there. Logging in through that connection correctly reports the account as expired. Checking the account through the main database group's Security > Users page shows no expiration, because that group now defaults to the new year database, which holds no record of it.
Resolution
1. Identify which database group or portal is still pointed to the prior year
- Common examples: the Summer/Summer School database group, Teacher Portal
2. Access the prior year database through that group or portal
- Log out of the main database group first, then log in using the affected group — the prior year remains the default database there