Alright, I have read elsewhere that Bitcointools can help, so I tried that as well.
./dbdump.py --wallet
(stack trace)
'DB_RUNRECOVERY: Fatal error, run database recovery -- PANIC: Invalid argument'
Also not helpful.
Topic: Wallet.dat (Read 2513 times)
Both installs were 64.
Did you reinstall from 64 bit to 32 bit or 32 to 64 bit?
It dies. I have tried the new version as well as the older version (0.3.20.2) that the file was created with. No dice.
Does Bitcoin actually die, or does it just hang?
Did you change Bitcoin versions?
Did you change Bitcoin versions?
Nope.
Bound to port 8333
Loading addresses...
dbenv.open strLogDir=C:\Users\Couchinator\AppData\Roaming\Bitcoin/database strErrorFile=C:\Users\Couchinator\AppData\Roaming\Bitcoin/db.log
Loaded 19166 addresses
addresses 200ms
Loading block index...
LoadBlockIndex(): hashBestChain=00000000000003b98eb5 height=124512
block index 2120ms
Loading wallet...
That's where it ends. It's very annoying to have BTC in the file somewhere but I just can't get to it
Bound to port 8333
Loading addresses...
dbenv.open strLogDir=C:\Users\Couchinator\AppData\Roaming\Bitcoin/database strErrorFile=C:\Users\Couchinator\AppData\Roaming\Bitcoin/db.log
Loaded 19166 addresses
addresses 200ms
Loading block index...
LoadBlockIndex(): hashBestChain=00000000000003b98eb5 height=124512
block index 2120ms
Loading wallet...
That's where it ends. It's very annoying to have BTC in the file somewhere but I just can't get to it
Does debug.log say anything about it?
Tried that, still crashes
Try running with the -rescan flag. From the command prompt, in the directory containing Bitcoin, run "bitcoin.exe -rescan"
So I reinstalled Windows the other day and transferred my wallet.dat file from my old install to my new one. I placed it into the AppData\Roaming\Bitcoin directory and now Bitcoin crashes when I try to start it up. There are no other files in the folder, although new copies of the rest of the files are generated when I start Bitcoin. I don't see how anything could have happened to the file. There seem to be many other people with a similar problem but I haven't found any answers. I can't figure out how to use the Berkeley DB tools to get the file fixed. Does anyone have any insight as to why the file might just stop working?
Thanks
Thanks
Jump to: