Skip to content
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

Unable to open the skype 8 leveldb #63

Open
pkt30 opened this issue Jul 22, 2018 · 15 comments
Open

Unable to open the skype 8 leveldb #63

pkt30 opened this issue Jul 22, 2018 · 15 comments
Assignees

Comments

@pkt30
Copy link

@pkt30 pkt30 commented Jul 22, 2018

I tried to open the skype 8 level db using the FastoNoSql v1.17.6 but each time I got the following error on the console

11:44:53.133: SCAN function error: Corruption: corrupted compressed block contents

I selected indexed_db as comparator and snappy as compression.

The skype 8 level db file is located at
C:\Users\machine-username\AppData\Roaming\Microsoft\Skype for Desktop\IndexedDB\file__0.indexeddb.leveldb

@topilski topilski self-assigned this Jul 22, 2018
@topilski
Copy link
Member

@topilski topilski commented Jul 22, 2018

Hi @pkt30, please try without compression

Loading

@simplyQQ
Copy link

@simplyQQ simplyQQ commented Aug 7, 2018

I have the same error using latest version with and without compression.

1.17.4 seems to open and load contents, but produces following:

capture

what else are we missing and why does latest version not work?

Loading

@topilski
Copy link
Member

@topilski topilski commented Aug 7, 2018

Hi @simplyQQ , it is hexed or unicode strings (binary data). We updated LevelDB from master but LevelDB sources have bug in current master branch, need to wait fixes, or use old versions,.

Loading

@simplyQQ
Copy link

@simplyQQ simplyQQ commented Aug 7, 2018

I've tried different preview methods but neither seems to decode it. These do seem binary, but when viewing raw LDB file I can clearly see text data in it?

Loading

@topilski
Copy link
Member

@topilski topilski commented Aug 7, 2018

No, not readable for human.

Loading

@pkt30
Copy link
Author

@pkt30 pkt30 commented Aug 7, 2018

Earlier I was just able to open the db once, there I also got the similar encoded value. From the UI, there is some menu "get value" from which we could the value which is readable.
I do not know if this menu is available in all version.

It's value looks something

� ���
o"�_serverMessagesA�o"�isactiveT" threadtopic"�GE1" messagetype"�RichText"�conversationLink"}https://ea2hk2-client-s.gateway.messenger.live.com/v1/users/ME/conversations/19:eeb791f1941f4805adf02744a557ed50@thread.skype"�origincontextid"�0" contenttype"�text"�originalarrivaltime"�2018-07-19T10:36:48.075Z"�from"Zhttps://ea2hk2-client-s.gateway.messenger.live.com/v1/users/ME/contacts/8:ab.vat"�content"�test"
imdisplayname"�abVat"�counterpartymessageid"
1531996608501"�id"
1531996608501" ackrequired"khttps://ea2hk2-client-s.gateway.messenger.live.com/v1/users/ME/conversations/ALL/messages/1531996608501/ack"�version"
1531996608501"�type"�Message"�clientmessageid"�2598134417786739980" composetime"�2018-07-19T10:36:48.075Z{�$

Loading

@topilski
Copy link
Member

@topilski topilski commented Aug 7, 2018

Hi @pkt30 , you can simple enter "get key" command in console. "get value" availible in all versions.

Loading

@topilski
Copy link
Member

@topilski topilski commented Aug 7, 2018

Loading

@topilski
Copy link
Member

@topilski topilski commented Aug 7, 2018

I think symbol: � is snappy compression lenght.

Loading

@topilski
Copy link
Member

@topilski topilski commented Aug 9, 2018

Hello guys, i updated FastoNoSQL version, and fixed LevelDB issue, please check.

Loading

@simplyQQ
Copy link

@simplyQQ simplyQQ commented Sep 10, 2018

I would test it, but my trial has expired :(

Loading

@topilski
Copy link
Member

@topilski topilski commented Sep 10, 2018

@simplyQQ please send an email to support@fastogt.com i will extend your trial

Loading

@jmvermeulen
Copy link

@jmvermeulen jmvermeulen commented Feb 11, 2019

I can get some values readable by converting them to xHex.
But the data still isn't fully correct, seems a kind of reversed.

Edit: If the value is decoded as Sting as BigEndianUnicode the text is quite readable and not reversed any more!

Loading

@ffrappo
Copy link

@ffrappo ffrappo commented Feb 15, 2019

Still doesn’t work. @jmvermeulen could you explain your process with more detail?

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants