Failed to get children from device: IDispatch error #7689

[kovidgoyal]

Yes, that is the same error as originally. I reverted the change in 5.19 as it caused crashes, which is unacceptable.

[jackb]

Hello,

A quick update, I just installed version 5.21 and am no longer having any problems at all.

I've tested it twice and both times Calibre came up and communicated with the phone just fine. I did notice that the the initial job that goes out to interrogate the phone lasted very long, approximately 90 seconds, but it all worked just fine.

Many many thanks for a wonderful product and such phenomenal support.

[kovidgoyal]

Weird there werent any changes in 5.21 related to this at all.

[rasteps]

Originally Posted by jackb

Hello,

A quick update, I just installed version 5.21 and am no longer having any problems at all.

I've tested it twice and both times Calibre came up and communicated with the phone just fine. I did notice that the the initial job that goes out to interrogate the phone lasted very long, approximately 90 seconds, but it all worked just fine.

Many many thanks for a wonderful product and such phenomenal support.

Strange. I still have the error.


calibre, version 5.21.0
ERROR: Error: Error communicating with device

C:\r\src\src\calibre\devices\mtp\windows\content_e numeration.cpp:336:Failed to EnumObjects() of folder from device:[hr=0x80042009 wCode=7689] IDispatch error #7689: o117

Traceback (most recent call last):
File "calibre\gui2\device.py", line 89, in run
File "calibre\gui2\device.py", line 515, in _books
File "calibre\devices\mtp\driver.py", line 220, in books
File "calibre\devices\mtp\driver.py", line 192, in get_driveinfo
File "calibre\devices\mtp\windows\driver.py", line 272, in filesystem_cache
wpd.WPDError: C:\r\src\src\calibre\devices\mtp\windows\content_e numeration.cpp:336:Failed to EnumObjects() of folder from device:[hr=0x80042009 wCode=7689] IDispatch error #7689: o117

[rasteps]

UPDATE:

Somehow the new update 5.221 reset something and now my phone connects to Calibre. Like Jackb's situation, it took about 2-1/2 minutes to scan at first, but then scanned faster the next time round.

@Kovid: Thank you for the support. And even if you didn't do anything, thank you spending time looking into the solution.

@Jackb: Your workaround solved another prob I was having with processing filenames before sending them to my phone, so I'm actually going to keep using that.

[philipblee]

Originally Posted by kovidgoyal

That's an error on the device,scanning its filesystem is failing. Dont know of any way to fix that short fo resetting the device.

calibre, version 7.9.0
ERROR: Unhandled exception: <b>WPDError</b>:C:\r\src\src\calibre\devices\mtp\windows\conten t_enumeration.cpp:337:Failed to EnumObjects() of folder from device:[hr=0x80042009 wCode=7689] IDispatch error #7689: o13

calibre 7.9 embedded-python: True
Windows-10-10.0.22631-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.22631')
Python 3.11.5
Windows: ('10', '10.0.22631', 'SP0', 'Multiprocessor Free')
Interface language: None
EXE path: C:\Program Files\Calibre2\calibre.exe
wpd.WPDError: C:\r\src\src\calibre\devices\mtp\windows\content_e numeration.cpp:337:Failed to EnumObjects() of folder from device:[hr=0x80042009 wCode=7689] IDispatch error #7689: o13



So above is the error message from Calibre when I connect my brand new Kindle Fire 11 (13th Generation).

To make sure I did not do anything wrong, I reset the Kindle back to factory settings. I'm not sure why Calibre is having trouble reading the device. I wonder if it's a defective device.

I am able to "Send to Kindle" so books are getting loaded on to the device, but this error occurs on startup when a job is launched to read the contents of the kindle.

If anyone has any ideas of what to try, let me know.

Much appreciated.

[JSWolf]

The problem could be that another task is accessing the Kindle Fire when you plug it in. Only one task at a time is allowed to access MTP devices.

[theducks]

Too much built in help ?

Somethings may be syncing (Like photos) to-from your PC over the USB.

Everytime I turn around, One of my devices turns on (or removes) a feature that behaves in a way I did not want (breaks something I had been getting away with doing my way )

[philipblee]

I just purchased the brand new Kindle Fire 11 Max (referred to as KF11 Max in the rest of this message).

I am using Calibre v7.10 on Windows 11. KF11 is running Fire OS 8.3.2.3

When I connect KF11 Max to Calibre and a job is launched to "get list of books from the device". I immediately get WPD #7689 Error message which means that the Kindle Fire returns an error when Calibre does an MTP Request for scanning the device.

This error makes transferring files from Calibre to the KF11 Max very problematic.

I discovered a work-around to this problem that isn't perfect, but it works and I can get my eBooks onto the KF11 Max. Here are the exact steps:

1. Do not connect the KF11 Max to Calibre (avoid #7689 Error)

2. Click Connect/Share-->Connect to Folder-->Select Folder (selected folder)

3. Select the eBooks you want sent to your KF11 Max

3. Click Send to Device-->Send Specific Format-->Main Memory-->AZW3

4. This takes a little time depending on the number of eBooks, but this launches a job to upload those eBooks to the 'selected folder' from step 2

5. Change the USB setting on your KF11 Max device to "File Transfer" and make sure that Windows Explorer can display "Fire" in "My PC".

6. Finally, use File Explorer to copy all eBook files from the 'selected solder' to KF11 Max Drive/Documents folder.

7. The KF11 Max should start ingesting the eBooks and displaying the covers in your KF11 Max Kindle Library

I hope you find this message helpful.

[philipblee]

Originally Posted by JSWolf

The problem could be that another task is accessing the Kindle Fire when you plug it in. Only one task at a time is allowed to access an MTP devices.

That's a really good point. The Kindle Fire is constantly doing things like syncing with the server, etc. I do turn off wi-fi but there may be other processes running that try to access MTP simultaneously.