jak64950 1 Posted February 3, 2017 Share Posted February 3, 2017 I'm unable to mount my cloud drive after upgrading to .822. It starts indexing files, but errors saying "There was an error communicating with the storage provider. An entry with the same key already exists." I'm using google drive. I've tried reauthorizing and restarting my computer but it does the same thing. Quote Link to post Share on other sites
0 borez 1 Posted February 3, 2017 Share Posted February 3, 2017 Same problem also. Downgrading to .821 didn't help. There are no duplicate folders within Google Drive. Quote Link to post Share on other sites
0 Choruptian 1 Posted February 3, 2017 Share Posted February 3, 2017 I've got an inkling that it's the "*-data-ChunkIdStorage" folder that already exists that causes this. I've yet to delete try to delete it, waiting on answer in my support ticket. Could just be a bug tho. Quote Link to post Share on other sites
0 steffenmand 60 Posted February 3, 2017 Share Posted February 3, 2017 It's a bug with their new fix for missing chunk id's, i'm pretty sure that they will fix this soon Quote Link to post Share on other sites
0 Akame 0 Posted February 4, 2017 Share Posted February 4, 2017 Hello does the latest beta fix it for you guys? http://dl.covecube.com/CloudDriveWindows/beta/download/StableBit.CloudDrive_1.0.0.827_x64_BETA.exe Apparently you have to reset database in settings and reauthorize for api v3 to work. .827 * [Issue #27339] When a volume is dirty, display a more informative error message and user feedback item. .826 * [Issue #27342] Fixed "An element with the same key already exists" when multiple chunks exist with the same index. .825 * [Issue #27331] Rewrote volume name query code to not use VDS. .824 * [Issue #27344] When multiple files are found for the same chunk, note a warning in the log with the chunk number. .823 * Fixed thread aborts. * Fixed Technical Details window not updating. .822 * [Issue #27342] Updated the Google Drive provider to use the v3 API. * [Issue #27342] Enabled logging of chunk ID enumeration after database reset by default. * [Issue #27342] Added "Allow missing chunks" to the Troubleshooting menu. * Fixed uploads getting stuck. .819 * If multiple chunks exist with the same name, use the first one. .827 * [Issue #27339] When a volume is dirty, display a more informative error message and user feedback item. .826 * [Issue #27342] Fixed "An element with the same key already exists" when multiple chunks exist with the same index. .825 * [Issue #27331] Rewrote volume name query code to not use VDS. .824 * [Issue #27344] When multiple files are found for the same chunk, note a warning in the log with the chunk number. .823 * Fixed thread aborts. * Fixed Technical Details window not updating. .822 * [Issue #27342] Updated the Google Drive provider to use the v3 API. * [Issue #27342] Enabled logging of chunk ID enumeration after database reset by default. * [Issue #27342] Added "Allow missing chunks" to the Troubleshooting menu. * Fixed uploads getting stuck. .819 * If multiple chunks exist with the same name, use the first one. Quote Link to post Share on other sites
0 steffenmand 60 Posted February 4, 2017 Share Posted February 4, 2017 Newest version fixes this :-) Quote Link to post Share on other sites
0 borez 1 Posted February 4, 2017 Share Posted February 4, 2017 Newest version fixes this :-) Yep fixes the issue! Quote Link to post Share on other sites
Question
jak64950 1
I'm unable to mount my cloud drive after upgrading to .822.
It starts indexing files, but errors saying "There was an error communicating with the storage provider. An entry with the same key already exists."
I'm using google drive. I've tried reauthorizing and restarting my computer but it does the same thing.
Link to post
Share on other sites
6 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.