Topic: Wallet.dat preventing Bitcoin qt from opening (0.7.0) (Read 874 times)
Thanks for the responses. Again, it isn't that big a deal as I have copies, but it is curious that there are no errors in db or elsewhere, just this endless initialization lag. I'll try the pywallet script, thanks again.
Quote
I may have renamed wallet.dat in the appdata folder while bitcoin was in the process of closing
That definitely can corrupt a walletYou still can salvage with deepceleron's answer or try pywallet if that doesn't work
The db.log or debug.log may have information about what errors are happening when the wallet is being accessed.
A preliminary recovery option is to run Bitcoin with the command-line option -salvagewallet.
A preliminary recovery option is to run Bitcoin with the command-line option -salvagewallet.
So I spent today going through various extraneous wallets I had lying about, consolidating, securing, etc. All was going well, until *ta-da*, bitcoin qt suddenly gets hung up on its initial startup, when using one particular wallet, but is fine on all others.
The wallet doesn't have that much in it, and I have copies of it that *are* working, so no worries. But I am concerned that this happened at all --- I wouldn't want it to happen on a more significant wallet.
It's a 0.7.0 client, and I think I may have renamed wallet.dat in the appdata folder while bitcoin was in the process of closing, in order to switch to a different wallet.dat. Trying to connect via daemon yields a "cannot connect to server" error, while debug lists nothing but load attempts with really long (failed) load times (in ms). Any explanation or indication of the problem is greatly appreciated, any potential solutions too.
Thank you.
The wallet doesn't have that much in it, and I have copies of it that *are* working, so no worries. But I am concerned that this happened at all --- I wouldn't want it to happen on a more significant wallet.
It's a 0.7.0 client, and I think I may have renamed wallet.dat in the appdata folder while bitcoin was in the process of closing, in order to switch to a different wallet.dat. Trying to connect via daemon yields a "cannot connect to server" error, while debug lists nothing but load attempts with really long (failed) load times (in ms). Any explanation or indication of the problem is greatly appreciated, any potential solutions too.
Thank you.
Jump to: