Check debug.log for errors.
If you are not making progress, just try resyncing. Delete %APPDATA%/Zcash (backup your wallet.dat first if you have funds) and then restart zec-qt-wallet.
1 Like
Ok, here we go… ! Watched block 1 begin downloading with 1 connection. What a beautiful sight. Now, do I simply replace wallet.dat file with my backup to retrieve my balance?
1 Like
Replacing the wallet.dat file with a backup file most times work but i have encountered problems (in general and not ZEC related!). Problems can happen on various occasions, some general code change, fork, whatever.
In case you hold the private keys i always would go with importing private keys as it’s just the best way in my opinion. Nowadays i keep the wallet.dat file backups just as last solution for the worst case if everything else fails for some reason.
In case you have the private keys what you should:
Under File ==> Import Private Key
you can add them all at once in case you have more adresses with funds, no matter if Z or T adresses.
THANK YOU, ZCASH COMMUNITY. I’m back up and running. I’m so grateful for your support.
So, you are saying, instead of replacing wallet.dat with the backup version, i could import my private keys. The private keys are associated with my balance accounts, thereby giving me access to my balances (just like replacing wallet.dat with the backup version would do). Am I understanding this correctly? Thank you in advance.
Yes, and in my opinion it’s more secure, faster and in most cases easier, enough you don’t have 200 adresses with 200 private keys. Have in mind that each adress has it’s own privatekey!!!
But as well always keep a wallet.dat file backup somewhere. At least that’s what i’am doing.
1 Like
Hello, again!
So, I upgraded to zec-qt-wallet v0.5.11 and my zcash node flopped…
i see this error: 
I also ran zcashd on its own and received a similar error.
I found this in debug.log:
2019-02-23 00:16:40 Zcash version v2.0.3-fd31be7-dirty (2019-02-19 16:47:43 -0800)
2019-02-23 00:16:40 Using OpenSSL version OpenSSL 1.1.1a 20 Nov 2018
2019-02-23 00:16:40 Using BerkeleyDB version Berkeley DB 6.2.23: (March 28, 2016)
2019-02-23 00:16:40 Default data directory \Zcash
2019-02-23 00:16:40 Using data directory \Zcash
2019-02-23 00:16:40 Using config file \Zcash\zcash.conf
2019-02-23 00:16:40 Using at most 125 connections (2048 file descriptors available)
2019-02-23 00:16:40 Using 2 threads for script verification
2019-02-23 00:16:40 scheduler thread start
2019-02-23 00:16:40 Loading verifying key from \ZcashParams\sprout-verifying.key
2019-02-23 00:16:40 Loaded verifying key in 0.004000s seconds.
2019-02-23 00:16:40 Loading Sapling (Spend) parameters from \ZcashParams\sapling-spend.params
2019-02-23 00:16:40 Loading Sapling (Output) parameters from \ZcashParams\sapling-output.params
2019-02-23 00:16:40 Loading Sapling (Sprout Groth16) parameters from \ZcashParams\sprout-groth16.params
2019-02-23 00:16:41 Loaded Sapling parameters in 1.560000s seconds.
2019-02-23 00:16:41 HTTP: creating work queue of depth 16
2019-02-23 00:16:41 HTTP: starting 4 worker threads
2019-02-23 00:16:41 Using wallet wallet.dat
2019-02-23 00:16:41 init message: Verifying wallet…
2019-02-23 00:16:41 CDBEnv::Open: LogDir=\Zcash\database ErrorFile=\Zcash\db.log
2019-02-23 00:16:41 Bound to [::]:8233
2019-02-23 00:16:41 Bound to 0.0.0.0:8233
2019-02-23 00:16:41 Cache configuration:
2019-02-23 00:16:41 * Using 2.0MiB for block index database
2019-02-23 00:16:41 * Using 120.0MiB for chain state database
2019-02-23 00:16:41 * Using 328.0MiB for in-memory UTXO set
2019-02-23 00:16:41 init message: Loading block index…
2019-02-23 00:16:41 Opening LevelDB in Zcash\blocks\index
2019-02-23 00:16:41 Opened LevelDB successfully
2019-02-23 00:16:41 Opening LevelDB in \Zcash\chainstate
2019-02-23 00:16:42 Opened LevelDB successfully
2019-02-23 00:16:57 LoadBlockIndexDB: last block file = 137
2019-02-23 00:16:57 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1950, size=25335044, heights=484254…486205, time=2019-02-19…2019-02-22)
2019-02-23 00:16:57 Checking all blk files are present…
2019-02-23 00:16:57 LoadBlockIndexDB: transaction index disabled
What should I try next?
Maybe your db has become corrupted? Try restarting zcashd with ./zcashd -reindex