-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
still can't read my .ldb file #3
Comments
Sorry for delay. I download it, place to desktop, unzip 1 - make dir for show folder you are sure what you have correct rights in system for desktop folder ? |
I still got the same error. I tried your solution both in cmd and PowerShell with administrator mode.I also tried rename my data folder into "leveldb". There were both failed. |
you are sure what you use correct leveldb folder ? this is for example my folder also if you have all old folder, you may copy it to new chrome location chrome need close before any operations with chrome data folders |
install latest Microsoft Visual C++ Redistributable https://support.microsoft.com/en-ph/help/2977003/the-latest-supported-visual-c-downloads |
I had the same problem and this worked for me: I copied all of the dll files from the location below into the BIN folder of my compiled LevelDBOneTab app. It then worked as expected. In your case, I think you would use the path of the version of Visual Studio that you used to build the app. In my case, I built using VS 20189, so took the redist files from that path. NOTE: I think these redist files are for when you build in Debug mode. C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Redist\MSVC\14.21.27702\debug_nonredist\x86\Microsoft.VC142.DebugCRT |
Yes
thanks
i want use virtual box for run clear windows, and test it
12 черв. 2019 18:14, "Andrew M" <[email protected]> напис.
… I had the same problem and this worked for me:
I copied all of the dll files from the location below into the BIN folder
of my compiled LevelDBOneTab app. It then worked as expected. In your case,
I think you would use the path of the version of Visual Studio that you
used to build the app. In my case, I built using VS 20189, so took the
redist files from that path. NOTE: I think these redist files are for when
you build in Debug mode.
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\
Redist\MSVC\14.21.27702\debug_nonredist\x86\Microsoft.VC142.DebugCRT
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3?email_source=notifications&email_token=AGHZVJIAWP4437EJSLKE64DP2EHFZA5CNFSM4GILEWFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXQYR5I#issuecomment-501319925>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGHZVJLIPNYXUZRALR3O2GTP2EHFZANCNFSM4GILEWFA>
.
|
Hi I have the same problem too, Can you help me, I have visual studio installed 2019 and put a copy of the 2 DLL from the folder exepath to the directory of C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Redist\MSVC\14.21.27702\debug_nonredist\x86\Microsoft.VC142.DebugCRT Thanks
|
Hello
i have big problems with health, so not work with computer last time
if you you have studio, you may re- build project, this may help with dlls
about out of index error, i not test it
you data in one tab is very big?
Andrey
|
okay man get well soon and i hope everything would be better. not really just a couple of less than a hundred mb. 10k links? I don't know I to rebuild stuff will just go back the later month. thank you very much man I just manually did that visual studio folder |
I'd like thank you for this solution first.It's like a burning candle to me in the darkness after I lost my oneTab data.But there is still some problem while I trying to practice.I managed to get old .ldb file in my backup and stuck after I ran you command.
But this module is right in the same folder.BTW, the "11_29" folder is where I put files from leveldb folder.
So I am quite confusing about this.
Was I did something wrong? Please help me with this issues. Any info could be helpful!
The text was updated successfully, but these errors were encountered: