Failed to get children from device: IDispatch error #7689 - Page 3

kovidgoyal · 06-06-2021, 10:02 PM

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

jackb · 06-13-2021, 10:50 AM

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 · 06-13-2021, 10:52 AM

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

rasteps · 06-14-2021, 08:16 AM

Quote:

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 · 06-26-2021, 02:50 AM

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.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Glo HD Unknown USB Device (Device Descriptor Request Failed)	Thargor	Kobo Reader	7	09-11-2020 10:00 AM
ERROR: Failed: Failed to export data	Funkybassman	Library Management	3	05-09-2020 07:22 AM
Error:Failed to create library: Failed	wolfkin	Library Management	1	06-18-2019 04:42 PM
Failed feed: Tips_<urlopen error [Errno 11004] getaddrinfo failed>	Danesh	Recipes	4	03-19-2015 03:45 AM
calibre, version 0.8.8 ERROR: Error: Error communicating with device no such column:	e-bookuser	Devices	1	07-03-2011 04:09 PM

06-06-2021, 10:02 PM	#31
kovidgoyal creator of calibre Posts: 43,856 Karma: 22666666 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Yes, that is the same error as originally. I reverted the change in 5.19 as it caused crashes, which is unacceptable.

06-13-2021, 10:50 AM	#32
jackb Member Posts: 11 Karma: 10 Join Date: May 2021 Device: none	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.

06-13-2021, 10:52 AM	#33
kovidgoyal creator of calibre Posts: 43,856 Karma: 22666666 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Weird there werent any changes in 5.21 related to this at all.

06-26-2021, 02:50 AM	#35
rasteps Zealot Posts: 118 Karma: 10 Join Date: Sep 2010 Device: Kindle, Android phone	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.