WD Sync on Mac not working with EX2

My Cloud OS 3 Personal & Network Attached Storage My Cloud EX2
1

The new WD Sync ot working on my Mac and with my MyCloud EX2…

I’m getting the following errors in the log:

9/28/15 7:45:24.957 PM WD Sync Service[14600]: [NASVolumeFolderChangesThread:xxxxxx:WDSync] Error requesting metaDBInfo (2.1 API) for share ‘WDSync’ from the Personal Cloud device ‘xxxxxx’. REST error = kHTTPStatusCode_BadRequest. REST error message = ‘Error in DB file location’.

My NAS is running the latest firmware, 2.10.302

Update: restarted my NAS, uninstall WD Sync on Mac, delete MyCloud folder and finally remove computer authorization from Cloud Access. Then reinstalled WD Sync without checking any of the folders (Pictures, Documents, etc). It still showed those errors in the log, but I was able to sync files by dropping them into MyCloud folder. However once I tried to add a new sync folder and sync it with one of my private shares (under the same user I’m using WD Sync), I started getting the following in my log:

9/28/15 8:09:34.680 PM WD Sync Service[14998]: [main] Successfully got firmware information for Personal Cloud device ‘EugrEX2’. Firmware version number = ‘2.10.302’.
9/28/15 8:09:34.680 PM WD Sync Service[14998]: [main] Successfully connected to the local share ‘User’ on Personal Cloud device ‘xxxxx’
9/28/15 8:09:35.248 PM WD Sync Service[14998]: [main] loginLanRequest already exists for share ‘WDSync’ on NAS ‘xxxxx’, loginLanRequest = 0x7fd22a5201d0
9/28/15 8:09:35.249 PM WD Sync Service[14998]: [main] loginLanRequest using self-signed certificate validation for share ‘WDSync’ on NAS ‘xxxxx’
9/28/15 8:09:35.249 PM WD Sync Service[14998]: [main] loginWanRequest already exists for share ‘WDSync’ on NAS ‘xxxxx’, loginWanRequest = 0x7fd22a52b780
9/28/15 8:09:35.249 PM WD Sync Service[14998]: [main] loginWanRequest using Trusted Certificate validation for share ‘WDSync’ on NAS ‘xxxxx’
9/28/15 8:09:35.249 PM WD Sync Service[14998]: [main] CERTIFICATE: Fallthrough.
9/28/15 8:09:35.259 PM WD Sync Service[14998]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
9/28/15 8:09:35.519 PM WD Sync Service[14998]: [main] Successfully got firmware information for Personal Cloud device ‘xxxxx’. Firmware version number = ‘2.10.302’.
9/28/15 8:09:35.519 PM WD Sync Service[14998]: [main] Successfully connected to the local share ‘WDSync’ on Personal Cloud device ‘xxxxx’
9/28/15 8:09:35.972 PM WD Sync Service[14998]: [main] CERTIFICATE: Fallthrough.
9/28/15 8:09:35.982 PM WD Sync Service[14998]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)

Probably has to do somethign with self-signed certificates on EX2.

So far it’s a big dissapointment. Hopefully they will fix the bugs, but for now I can’t rely on this to keep my files in sync… 

2

And you know what’s the worst? Is that WD Sync reports that my NAS is up to date in the status line… No error messages, nothing.

Jeez, programmers are too lazy handling exceptions nowadays… Facing this problem every time I hire a new programmer in my team at work. 

/rant off :frowning:

3

Welcome to the Community.

Maybe you should try contacting WD’s Technical Support about this. You can do so either by phone or email.

To Contact WD for Technical Support
http://support.wdc.com/contact.aspx

Regards,

Trancer.

4

Eugr_ wrote:

 

The new WD Sync ot working on my Mac and with my MyCloud EX2…

 

I’m getting the following errors in the log:

 

9/28/15 7:45:24.957 PM WD Sync Service[14600]: [NASVolumeFolderChangesThread:xxxxxx:WDSync] Error requesting metaDBInfo (2.1 API) for share ‘WDSync’ from the Personal Cloud device ‘xxxxxx’. REST error = kHTTPStatusCode_BadRequest. REST error message = ‘Error in DB file location’.

 

My NAS is running the latest firmware, 2.10.302

 

Update: restarted my NAS, uninstall WD Sync on Mac, delete MyCloud folder and finally remove computer authorization from Cloud Access. Then reinstalled WD Sync without checking any of the folders (Pictures, Documents, etc). It still showed those errors in the log, but I was able to sync files by dropping them into MyCloud folder. However once I tried to add a new sync folder and sync it with one of my private shares (under the same user I’m using WD Sync), I started getting the following in my log:

 

9/28/15 8:09:34.680 PM WD Sync Service[14998]: [main] Successfully got firmware information for Personal Cloud device ‘EugrEX2’. Firmware version number = ‘2.10.302’.
9/28/15 8:09:34.680 PM WD Sync Service[14998]: [main] Successfully connected to the local share ‘User’ on Personal Cloud device ‘xxxxx’
9/28/15 8:09:35.248 PM WD Sync Service[14998]: [main] loginLanRequest already exists for share ‘WDSync’ on NAS ‘xxxxx’, loginLanRequest = 0x7fd22a5201d0
9/28/15 8:09:35.249 PM WD Sync Service[14998]: [main] loginLanRequest using self-signed certificate validation for share ‘WDSync’ on NAS ‘xxxxx’
9/28/15 8:09:35.249 PM WD Sync Service[14998]: [main] loginWanRequest already exists for share ‘WDSync’ on NAS ‘xxxxx’, loginWanRequest = 0x7fd22a52b780
9/28/15 8:09:35.249 PM WD Sync Service[14998]: [main] loginWanRequest using Trusted Certificate validation for share ‘WDSync’ on NAS ‘xxxxx’
9/28/15 8:09:35.249 PM WD Sync Service[14998]: [main] CERTIFICATE: Fallthrough.
9/28/15 8:09:35.259 PM WD Sync Service[14998]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)
9/28/15 8:09:35.519 PM WD Sync Service[14998]: [main] Successfully got firmware information for Personal Cloud device ‘xxxxx’. Firmware version number = ‘2.10.302’.
9/28/15 8:09:35.519 PM WD Sync Service[14998]: [main] Successfully connected to the local share ‘WDSync’ on Personal Cloud device ‘xxxxx’
9/28/15 8:09:35.972 PM WD Sync Service[14998]: [main] CERTIFICATE: Fallthrough.
9/28/15 8:09:35.982 PM WD Sync Service[14998]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)

 

Probably has to do somethign with self-signed certificates on EX2.

 

So far it’s a big dissapointment. Hopefully they will fix the bugs, but for now I can’t rely on this to keep my files in sync… 

Eugr_,

This has been passed along to support.

1 Like
5

Hi there,

Please apologize for the inconvenience. Could you please try to rebuild the content database and let me know if you ever get the same error? You can rebuild the content data base by following the below steps:

  1. Open the WD Sync Web UI 

  2. Click on Settings

  3. Click on Cloud Access

  4. Click on Config

  5. Click on Rebuild button

Thank you.

Need Help? Please click below for further assistance or contact us at 1(855) 556-5117
https://wdsupport.wdc.com/sfdc/case.aspx

1 Like
6

Thanks Kazzzzz! That worked, and I can now synchronize my folders just fine.

It would be nice if some robust error reporting was implemented in the future though, as proper sync is very critical for data consistency across the devices.

7

We truly appreciate your feedback. I will let the engineering team know about your great input. Thank you

8

Hey Kazzzzz,

Looks like the content database is unstable on EX2.

I’m getting the same errors since this morning, will need to rebuild the database when I get back home:

10/1/15 2:44:36.762 PM WD Sync Service[6897]: [NASVolumeFolderChangesThread:xxxxx:WDSync] Error requesting metaDBInfo (2.1 API) for share ‘WDSync’ from the Personal Cloud device ‘xxxxx’. REST error = kHTTPStatusCode_BadRequest. REST error message = ‘Error in DB file location’.

Please pass along to the development team, they need to fix it.

Thanks,

Eugene.

9

Hi there,

Thank you for your response. We are currently investigating this and will let you know more when we can. Thank you for your patience.

Need Help? Please click below for further assistance or contact us at 1(855) 556-5117
https://wdsupport.wdc.com/sfdc/case.aspx

10

I have similar issues with WD Sync on Windows 8.1 and 7 Professional to my My Cloud 4TB. I have to rebuild the content database frequently and re-configure both clients.

11

@Eugr_ I believe it is a certain file type that is corrupting the content database. Do you remember the file types you transferred around the 10/1/15 2:44:36.762 PM timestamp?

I suspect files in my downloads or jobs folder have lead to the corruption. The folders are outside of the WD Sync folder, but still triggers the content database corruption shortly after the robocopy script completed.

{shareName}
|-- Downloads
|-- Jobs
|-- WD Sync

Example from November 18th.

HTTP/1.1 400 Bad Request
Date: Wed, 18 Nov 2015 13:13:38 GMT
Server: Apache
X-Orion-Version: 2.7
Content-Length: 125
Connection: close
Content-Type: text/plain; charset=utf-8
Content-Language: en

{
   "metadb_info":{
      "error_code":"400",
      "http_status_code":"400",
      "error_id":"256",
      "error_message":"Error in DB file location"
   }
}

@Kazzzzz has your team been able to track down the content database corruption root cause?