Bitcoin Forum

Bitcoin => Bitcoin Technical Support => Topic started by: Zackgeno96 on September 06, 2015, 12:18:16 AM



Title: st13 runtime error
Post by: Zackgeno96 on September 06, 2015, 12:18:16 AM
i've been trying to resync my wallet for the past few day's on my other pc i started reindexing the blockchain, so i figured why not go download the full client again on another pc, so i downloaded my wallet and it completed before the one that is reindexing so i tried to load my wallet data into it it worked fine, but anytime i try to send coins i get this error? any idea what could be causing it? i've also tried to import keys 1 by 1 and it seems to be not working geting JSON INVALID RESCAN?

https://i.imgur.com/OXDCASt.png?1


Title: Re: st13 runtime error
Post by: alcodaapple on September 06, 2015, 12:38:39 PM
Just did a quick search on google and it has come up with githubs  bug reports there are a number of people with some answers there that might help you would link it but im on the phone sorry


Title: Re: st13 runtime error
Post by: tspacepilot on September 08, 2015, 05:42:35 PM
i've been trying to resync my wallet for the past few day's on my other pc i started reindexing the blockchain, so i figured why not go download the full client again on another pc, so i downloaded my wallet and it completed before the one that is reindexing so i tried to load my wallet data into it it worked fine, but anytime i try to send coins i get this error? any idea what could be causing it? i've also tried to import keys 1 by 1 and it seems to be not working geting JSON INVALID RESCAN?

https://i.imgur.com/OXDCASt.png?1

Since it looks like it's having a problem opening the database, I would start there.  Can you check that the bitcoin.conf file is pointing to the right datadir?

Also, it's not exactly clear the timeline of events.  Is it that you downloaded the blockchain and all seems to be working fine untill you try to import your keys?  Are you sure the blockchain is done syncing?

Invalid rescan also points to the idea that you don't have a good database.  I think if I were you I'd try to troubleshoot that database.

Maybe if you could write back with a detailed step-by-step of your error you can get better help.

Cheers!