View Single Post
Old 01-15-2019, 11:01 AM   #14
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
That error is happening when the KoboTouchExtended driver is checking some data in the database on the device. It can mean a corrupt database on the device, but, I would expect if that was the case, for the error to happen earlier. But, does the device get disconnected when this happens?

If it is a corrupt database on the device, the fix is to sign-out of the Kobo account and then back in. This will recreate the database and reload the books on the device, but you will lose the reading status for any sideloaded books. A factory reset will wipe the device and you will need to reload the books.
davidfor is offline   Reply With Quote