MobileRead Forums - View Single Post - Aura H2O Kobo won't connect to a PC anymore

davidfor · 08-03-2017, 09:15 PM

I don't know how to solve the problems reported. One of the reasons is because there are not enough details. Reporting that calibre displays the message, "error communicating with device" is almost completely useless. This will be displayed for a lot of different reasons. You need to look at the detailed message to get a better idea of what is happening.

For example, JosieB's first report sounds like the database was corrupt. My guess is that the database got corrupted and she added books afterwards. These were processed into the memory list of books, but could not be written to the database. Now, at disconnect, the database is reloaded and books are missing and have to be reprocessed. That's an educated guess. Seeing the details of the message would tell me if that was the likely reason.

Issybird's report also suggests a corrupt database, but probably in a different part of the database and a less severe problem.

08-03-2017, 09:15 PM	#13
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	I don't know how to solve the problems reported. One of the reasons is because there are not enough details. Reporting that calibre displays the message, "error communicating with device" is almost completely useless. This will be displayed for a lot of different reasons. You need to look at the detailed message to get a better idea of what is happening. For example, JosieB's first report sounds like the database was corrupt. My guess is that the database got corrupted and she added books afterwards. These were processed into the memory list of books, but could not be written to the database. Now, at disconnect, the database is reloaded and books are missing and have to be reprocessed. That's an educated guess. Seeing the details of the message would tell me if that was the likely reason. Issybird's report also suggests a corrupt database, but probably in a different part of the database and a less severe problem.