![]() ![]() Test the new “WD Drive Utilities v2.1.1.100” application. Move the “WD Drive Utilities v2.1.1.100” application to wherever your previous “WD Drive Utilities” application was located.ġ0. Paste the “WD Drive Utilities” application on your desktop and rename it “WD Drive Utilities v2.1.1.100”ĩ. ![]() Open the “WD Drive Utilities” folder and copy the “WD Drive Utilities” application.Ĩ. Scroll down in the “Resources” folder and double-click the “WD Drive Utilities.zip” file.ħ. Instead, right-click the file “WD Drive Utilities Installer” application and select the “Show Package Contents” option.Ħ. Open the “WD Drive Utilities” disk image. Double-click the “WD_Utilities_Installer_for_Mac_2_1_1_100.dmg” to create the “WD Drive Utilities” disk image on your desktop.ģ. WD SYNC FOR MAC ZIP FILEDouble-click the downloaded zip file to create the “WD_Utilities_Installer_for_Mac_2_1_1_100.dmg” on your desktop.ģ. ![]() WD SYNC FOR MAC DOWNLOADDownload WD_Utilities_Standalone_Installer_Mac_2_1_1_100.zip file from MacUpdate.Ģ. So far it’s a big dissapointment.Assuming you have an older version of the “WD Drive Utilities” application installed, here is how I installed the newer WD Drive Utilities (v2.1.1.100) application:ġ. Hopefully they will fix the bugs, but for now I can’t rely on this to keep my files in sync… Probably has to do somethign with self-signed certificates on EX2. Firmware version number = ‘2.10.302’.ĩ/28/15 8:09:35.519 PM WD Sync Service: Successfully connected to the local share ‘WDSync’ on Personal Cloud device ‘xxxxx’ĩ/28/15 8:09:35.972 PM WD Sync Service: CERTIFICATE: Fallthrough.ĩ/28/15 8:09:35.982 PM WD Sync Service: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843) Firmware version number = ‘2.10.302’.ĩ/28/15 8:09:34.680 PM WD Sync Service: Successfully connected to the local share ‘User’ on Personal Cloud device ‘xxxxx’ĩ/28/15 8:09:35.248 PM WD Sync Service: loginLanRequest already exists for share ‘WDSync’ on NAS ‘xxxxx’, loginLanRequest = 0x7fd22a5201d0ĩ/28/15 8:09:35.249 PM WD Sync Service: loginLanRequest using self-signed certificate validation for share ‘WDSync’ on NAS ‘xxxxx’ĩ/28/15 8:09:35.249 PM WD Sync Service: loginWanRequest already exists for share ‘WDSync’ on NAS ‘xxxxx’, loginWanRequest = 0x7fd22a52b780ĩ/28/15 8:09:35.249 PM WD Sync Service: loginWanRequest using Trusted Certificate validation for share ‘WDSync’ on NAS ‘xxxxx’ĩ/28/15 8:09:35.249 PM WD Sync Service: CERTIFICATE: Fallthrough.ĩ/28/15 8:09:35.259 PM WD Sync Service: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9843)ĩ/28/15 8:09:35.519 PM WD Sync Service: Successfully got firmware information for Personal Cloud device ‘xxxxx’. 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:ĩ/28/15 8:09:34.680 PM WD Sync Service: Successfully got firmware information for Personal Cloud device ‘EugrEX2’. It still showed those errors in the log, but I was able to sync files by dropping them into M圜loud folder. Then reinstalled WD Sync without checking any of the folders (Pictures, Documents, etc). Update: restarted my NAS, uninstall WD Sync on Mac, delete M圜loud folder and finally remove computer authorization from Cloud Access. ![]() My NAS is running the latest firmware, 2.10.302 REST error message = ‘Error in DB file location’. I’m getting the following errors in the log:ĩ/28/15 7:45:24.957 PM WD Sync Service: Error requesting metaDBInfo (2.1 API) for share ‘WDSync’ from the Personal Cloud device ‘xxxxxx’. WD SYNC FOR MAC MACThe new WD Sync ot working on my Mac and with my M圜loud EX2… ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |