I recently posted the issue of not being able to open SecureAccess 2 with my original .dat files.
Today, I finally resolved the .dat files issues with an 0x80070052 exception and/or procedure to reinstall the “sandisksecureaccessv2-win” installation file to fix the issues. I took the time to create another long descriptive post since there are many users with the same problem with little to no help.
Please note that I had 13,114 files and 1 folder with 998 MB. There are no warnings on file size exceeded during the copy process a week ago. I have 28.3 GB free out of 29.4 GB. I am not sure if it is a limitation of SecureAccess program or just the procedure of saving files to an opened “My Vault” file.
Lesson learned: Do not cut/paste all files from the SanDisk USB drive to Windows PC. First. run the backup function from the Tools menu within “My Vault” before you do anything else. Second, you only need to save SanDiskSecureAccess Vault (File folder) to your PC/MAC. Otherwise, here is what I endured until I finally got access to my encrypted .dat files again.
For new users, here are the information and steps that I did. I succeeded on one drive, as a test, but not the other because of the file size in nature.
(1) Original files on SanDisk Ultra 32 GB USB drive copied to Windows 7 Desktop in a folder — named SanDiskSecureAccess—ORIG.
(2) Format the drive, as exFAT.
(3) Copied and ran the “sandisksecureaccessv2-win” installation file on USB drive as administrator.
(4) Created the same password used for the original Vault file.
(5) Copied one working document file to “My Vault” and opened to see if the document will open, and it did.
(6) Closed “My Vault” — File | Exit.
(7) The files listed on the USB drive are:
- sandisksecureaccessv2-win (application), and
- SanDiskSecureAccess Vault (File folder).
(8) Accessed “SanDiskSecureAccess Vault” folder, and the files listed are:
- System Files (File folder),
- {730bcdbd-224c-4111-9c07-6513879e4f0f}.dat 13 KB (Note: this is the exact file size reported inside “My Vault”)
- desktop (Configuration settings), and
- vault (icon) 232 KB.
(9) Accessed System Files folder, and the files with file size are:
- A5000644B2750C91.enk 1 KB
- encryptstickconfig.enc 2 KB (Note: Time stamp changes each time “My Vault” file is closed.)
- filesys.enc 1 KB (Note: Time stamp changes each time “My Vault” file is closed.)
- stickauth.enc 1 KB (Note: Time stamp changes each time “My Vault” file is closed.)
- USB Flash Drive-A5000644B2750C91.idx 1 KB (Note: Time stamp changes each time “My Vault” file is closed.)
- USB Flash Drive-A5000644B2750C91.idx.bak 1 KB
(10) Accessed “My Vault” file again, added another file, and closed “My Vault” file.
(11) Accessed “SanDiskSecureAccess Vault” folder, and the change listed are:
- System Files (File folder),
- {730bcdbd-224c-4111-9c07-6513879e4f0f}.dat 13 KB
- {540cac0d-5ff4-4fc0-b81e-9921ab59d7c8}.dat 16 KB (NEW)
- desktop (Configuration settings), and
- vault (icon) 232 KB.
(12) Copied “SanDiskSecureAccess Vault” folder to Windows 7 PC Desktop as a test.
- Verified file size — 10 files, 1 folder with 262 KB.
(13) Deleted all .dat files and System Files of “SanDiskSecureAccess Vault” folder on USB drive.
(14) Right-clicked for Properties on my original “SanDiskSecureAccess Vault” folder in “My Document” folder on PC and unchecked “Read Only” attributes.
- Copied and pasted the .dat files and System Files folder into “SanDiskSecureAccess Vault” folder on USB drive.
(15) Ran the “sandisksecureaccessv2-win” (application).
Only this time, it prompts for a new password meaning that I will not be able to access the “My Vault” file of the encrypted .dat files. By typing in the new password, it created a new “My Vault” file, which there are no files to see. It is an infinite loop to no resolution. I have spent hours after six days when I copied the files to the Windows 7 PC without running the backup function when I was not able to add any more files into “My Vault” file. Again, one of the suggestion was to format the drive to exFAT 32, which did not work anyway at the time.
The theory is that this process should allow me to access the original “My Vault” file, which is about 1 GB. Please note that I was able to do the same process, outlined in the former, with a different drive (Cruzer Glide 32 GB) with different “My Vault” files that are much smaller in size. I am working with the new 32 GB Ultra drive. The process for the larger “My Vault” file will not work on Cruzer since I noticed the name reference for both USB drives is different in the System Files folder. You will notice the difference when sandisksecureaccessv2-win application prompts for a new password and creates a new “My Vault” file.
Last, each time, even with a formatted USB drive, when I ran the sandisksecureaccessv2-win application from the Windows 7 PC desktop, it looks for the USB drive and installs the program and creates a new “My Vault” file.
UPDATE:
VOILA! I resolved the problem by moving small sets of .dat files until I reached the offending 0x80070052 on two .dat files. For some reason, I suspect that the “My Vault” folder either has reached its limitation to add more files, or the .dat files were corrupted, or the program looked for specific numbers of files before opening the “My Vault” file. Instead, I put both files on the root directory and finally I reached the password prompt, which I was able to gain access to my files again! Please note that there is an upgrade to version 3 — “SanDiskSecureAccessV3_win” — and be sure to follow the procedure, as outlined, in http://kb.sandisk.com/app/answers/detail/a_id/17502 titled, “Migrating from SecureAccess 2.0 to SecureAccess 3.0 on a PC”.
I was able to do that with success. I know how frustrating the whole process becomes until you do the right steps. Remember to make an extra copy of your .dat files to another folder so that you can retain your original files to avoid from corruption. As long as you have the listed files similar to mine and many .dat files with reported file size above zero, you should be able to succeed. Otherwise, your data is corrupted and/or lost.
Best of luck.