EXCEPTION: St13runtime_error CWallet::GetCredit() : value out of range

[agibby5]

I'm getting this error and I cannot open Bitcoin with my wallet.  I got a message at the bottom of the Bitcoin Client in Ubuntu that I needed to upgrade. However, I was already on the newest version.  I decided to download the latest blockchain from the nightly from here: http://eu1.bitcoincharts.com/blockchain/ since I hadn't run the Client for a week or so.

I deleted my old blockchain files and replaced them with this one. I opened bitcoin-qt with the -rescan option and it appears that now I cannot open Bitcoin at all with my wallet.
EXCEPTION: St13runtime_error
CWallet::GetCredit() : value out of range

I tried opening my wallet on Linux and Windows. Under Windows, I tried 0.5.4 and 0.4.1 per the suggestion of another post which was unrelated. I cannot find another instance of this error happening.  However, I did stumble across this code: http://gitorious.org/intersango/bitcoind/blobs/e9f61c8787af99c49678ba4bc182b24b8fdba0c4/src/wallet.h

There, it looks like it fails the check of:
if (!MoneyRange(txout.nValue))
            throw std::runtime_error("CWallet::GetCredit() : value out of range");

I do not know what this means.

Any ideas on this and/or how to remedy it?

I know this is in the wrong place, but I don't have permission to post anywhere else and I'm sorta desperate!  I have about ~30 bitcoins in that wallet.

Thanks in advance.

[Stephen Gornick]

I'm getting this error and I cannot open Bitcoin with my wallet.

Sorry to ask the obvious, but just in case ... no backup?

Do you use an encrypted wallet?

What does debug.log show?

Have you tried to access the keys with a tool, like pywallet?

[agibby5]

I'm getting this error and I cannot open Bitcoin with my wallet.

Sorry to ask the obvious, but just in case ... no backup?

Do you use an encrypted wallet?

What does debug.log show?

Have you tried to access the keys with a tool, like pywallet?

I did not have backups, sadly. That is something I will immediately start doing after this situation is remedied.

No.

Not sure. As a first step to try to fix this, I deleted everything except the blockchain I downloaded from the nightly tar and my wallet file.

I have found and tried the fixwallet.py with --notxes (https://bitcointalk.org/index.php?topic=11331.0).  It opened this time!  It is currently rescanning now. Hopefully it doesn't crash again as it picks up my later transactions.

[agibby5]

Phew. This thing is taking a long time to process the blocks.  I downloaded the nightly blockchain tar from 8/16, yet it's still synchronizing with the network with 18k+ blocks left.  It's been running almost 12 hours now. I thought the purpose of downloading a full blockchain was that it would go quicker. It still looks like it's pulling alot from the P2P network.

[casascius]

If you can extract the private keys then you have the upper hand: you can always import them into a new wallet.

[Stephen Gornick]

Phew. This thing is taking a long time to process the blocks.  I downloaded the nightly blockchain tar from 8/16, yet it's still synchronizing with the network with 18k+ blocks left.  It's been running almost 12 hours now. I thought the purpose of downloading a full blockchain was that it would go quicker. It still looks like it's pulling alot from the P2P network.

It is creating the index, which is just about as slow as downloading the blockchain itself.

I think the ones from Sourceforge include the index, so you only need to download the new blocks since.

 - http://sourceforge.net/projects/bitcoin/files/Bitcoin/blockchain/bitcoin_blockchain_170000.zip