Failed to sync Windows wallet #523
Comments
|
@TheGift73 There's a link to the Fether FAQ in the "About" section of the Readme file for this repository. One of the questions is "Why isn't Fether syncing", which provides links and the suggestion that a potential solution is to delete the relevant chain database as it may have been corrupted. The location of the chain database varies depending on what operating system you're using, as listed here https://wiki.parity.io/Fether-FAQ#where-is-the-light-client-blockchain-database-used-by-fether-stored. We're interested in the /chains_light subdirectory as installation of Parity Ethereum "Light" client is bundled with the Fether. Since you're using Windows 7 the relevant directory is Windows 7/10: %HOMEPATH%/AppData/Roaming/Parity/Ethereum/chains_light |
|
Judging from the logs it seems that this is more a problem with the parity binary (it crashes on startup) than the syncing itself. The same issue happened to several other Fether users on Windows; it has been filed here: openethereum/parity-ethereum#10481 We're waiting for a fix |
fether.log
Parity Feather version: 0.3.1
Expected Behavior: I expected it to sync so that I could then import mt old ether JSON file and check on my tokens and/or transfer in and out.
Just wanted a wallet that I could have access to on my PC without having to download and install the complete Parity wallet. I have some airdrop tokens that I need to transfer out of my MEW wallet to a separate wallet and hoped that the Fether wallet would allow me to do this? As I am unable to even sync it though, this is an issue.
It shpws in my Roaming Profile, so the installation is fine.
Actual Behavior: Failed to sync just after installing and creating account and passwords etc. Got the error, as attached when it was syncing. It failed at 2%. I ran the .exe as admin to see if this were a permissions error, but to no avail.
I am running Windows 7 x64 Ultimate. Anti-virus and anti-malware are both disabled, so those are not an issue.
First time filling out an issue on github, so if I am missing something, please let me know.
The text was updated successfully, but these errors were encountered: