At this point the workaround is to switch the session storage to in-memory from database storage:
Session Configuration

The in-memory storage is explained in more detail on the page linked above.

If you cannot keep crowd up long enough to access the Administration console, or crowd will simply not finish starting up, follow these steps to modify the value directly in the database:

1. Shutdown crowd - ensure the pid is stopped
2. Perform a database backup
3. Connect to the database
4. Execute this sql:

   update cwd_property 
   set property_value='false'
   where property_name='database.token.storage.enabled';

6. Restart Crowd
7. Validate the session storage is now in-memory by Navigating to Administration > Session Config

If workaround 1 does not help, you may try this. However, please note that performing this workaround will force users to login again.

1. Shutdown crowd - ensure the pid is stopped
2. Perform a database backup
3. Connect to the database
4. Execute this sql:

   delete from cwd_token;

5. Restart Crowd
6. Validate the session storage is now in-memory by Navigating to Administration > Session Config