changing max_money would require a fork.
no idea if dev reads this or not ... hint hint

but if you have no luck extracting keys,
a possibility would be building a client with a larger max_money,
the transaction would not be legit on the network so should never get any confirms,
but the wallet should actually start up as the error seems to do with max_money having a tanty.

and then perhaps reindexing will fix it ..



alternatively,
the client should reject attempted transactions over max_money straight away..
this would help with future transactions.