I laud your dedication to this project.

I discovered and bought into Peercoin a while back, thought it had great potential. Then I watched it wither as the main developer seemed to have lost interest.

That  worked thank you.

What is it about the Armory program that causes it to stop adding blocks?

I saw somewhere that you have a v0.95 Armory version out. Is it ready for prime time?

this is my armorylog.txt, not armoryccplog.txt.

Hope that's the right one.

http://pastebin.com/Ve4B8RH6

Again, I started it from 10-25, all the pertinent  transacations began starting 10-26 and 10-28

http://pastebin.com/nTBajeh5

The whole file was too big for pastebin. I went back to just before 10-26, as that date was when I started sending the transactions in question.

I've done this before, but I don't remember where I post them.


Sorry. Help?

Hi All,

I'm using Armory 0.94.1, Bitcoin Core v 0.13.0, Win7 64 bit.

Used Armory to send two transaction in two days from the same wallet, no problem. Try to send a third, and I get the error message pop up that says:

"There was an error constructing your transaction.... more than once... two or more transactions."

I had to restore a second wallet from a paper backup, and was then able to send my third transaction.

All three transactions went through, and the recipients acknowledged that, yet those three transactions in the Armory Transaction window all show grayed out, with a zero in a gray box on the far left, instead of the check in the green box, if that  is helpful. What does that mean, anyway?

I tried a fourth transaction from both wallets a few minutes ago, and I get that error message again.

I also show the correct amount of coins in both wallets, so I got my change back.

Both updated programs installed and working fine.

Except I "still" have to run bitcoind manually to get Armory to work.

Not a big deal, but is this a bug that could be fixed?

Anyway, thanks to those who helped me. This thread is done.

So I have Bitcoin Core newly installed, updated and working fine.

Opening Armory v 93 showed my wallet, and the transaction history, and I am sure that I could have sent and received coins.

I downloaded v 0.94.1, checked the Hash, and "installed" it using default actions. It deleted a bunch, then started to unpack the new files, and threw the error:

Error opening the file for writing: ArmoryQt.exe. If I ignored it (which I know wouldn't work,) there was a cascade of other files that threw the same error.

Attempting to install v94 tanked v93, so I tired reinstalling that, only to get exactly the same errors.

So right now I have a fully functional Bitcoind, but no Armory, v93 or v94.

I'm just glad I don't need to send or receive coins right now.

No logs. I got tired of fucking with it and started over.

I'm down to 28 weeks behind. Probably finish Tuesday night.

I'll close this out when I'm back up and running.

My blockchain file was 83.9 gigs, and I had 25gigs free on top of that.

Is that not enough?

I installed bitcoin core v0.13, after checking the SHA256 hash, and installed it to the default directory.

It would open and close so fast I couldn't read the error message it threw.

I uninstalled the program  but left the roaming data then reinstalled. Nothing but error messages. Even the damned shortcut stopped working, and the newly created shortcut wouldn't work either. Did that three times.

I've now deleted everything, and am redownloading the blockchain.

Pain in the ass.

And when I go to armory.org, all I see to download is v 0.93. Where is 94? I see a reddit thread claiming that v0.94 is goatpig's, and he has no access to armory.org to post the new version.

I did PRECIOUSLY what goatpig suggested.

There WERE only the  594.dat entries, nothing following those.

I will install the updated versions and try again.

Bitcoind briskly got to 5 years and  4 weeks behind and and threw the same error.

last couple hundred lines of log:

http://pastebin.com/BSxrXcSs

If I have to delete and start from there, I might as well just start the database over. Last time, that took two weeks. Hope that isn't what I need.

On Win7 64 bit, using Armory v 0.93.3 beta with Bitcoin Core v o.12.1

Worked great for a few months ( from a new install, both programs.)

I have to NOT let Armory control Bitcoin core, in the Armory settings, for Armory to work, but it worked great. (Restore wallets, spend easily, etc.)

Couple of weeks ago, when I would manually start bitcoind, as I have to, I would get this:

Loading Blockchain index
Verifying
Activating Best Chain...
 
and the program would throw this error:

Error: a fatal internal error occurred. See debug log for details.

On pastebin, http://pastebin.com/0p1u2ydB

I appended that last couple of days that it work.

Hopefully, I went back far enough.

I'm guessing that I need to delete from some point and let it catch up again.

Any help appreciated.

I'm having the same problem, sorta. 0.94.1 has been working well past two days. Tonight I get the error:


Smaller amounts still would not send, and, as I have been doing, I have my fee set to 0.0015

Win7

EDIT:  Rescanning made no difference. Rebuild? Rebuild what, the blockchain download? I sure hope that's not what you mean. It took me a WEEK to get the whole thing.

Although it may be important that I have the blockchain downloaded into Bitcoin Core, as when I installed Armory again, (after not having it for a couple years,) it seemed to just be "offline" and doing nothing for days. The only way I could get Armory to work, after trying all the methods described here, was to start Bitcoin Core first, then start armory with the setting for "Allow Armory to manage bitcoinqt" unchecked. Worked beautifully for a few days.

Jamie,

Thanks for the reply. I am plenty well backed up, I've been using Armory for a long time.

I've done what you describe in the past, as a last resort.

It's what I consider the "nuclear option" and I'm hoping to avoid doing this.

I know this will work, the problem is that I'm "already" an old man, so to speak. 

Wasn't there a config file in the bitcoin core  that I could delete, that would be refreshed on restart, and allow the client and the core to reconnect?

I feel like such a noob, but I've been wrestling with this all day and have got nowhere.

I've been using Armory for almost a year, worked through other trouble like this, but this time I need help.

I searched unsuccessfully, although I can't believe there was nothing to find, I just didn't find it.

So here it is:

I uninstalled both the older Armory client that had been working fine for me, last use was a week ago, and the older bitcoin core x64 then installed both of the latest clients ( v0.92.1 and v0.9.2).

Since then I just cannot get Armory to go online and update. As soon as I open Armory, I get an error message jumping open saying "Bitcoind.exe has stopped working" if I ignore the message, Armory just does nothing (says it is "Initializing Bitcoin Engine" for hours on end)

or, if I tell the error prompt to close the program, Armory immediately goes into offline mode.

I'm using Win7 Ultimate, it been years since I've done any command line stuff, but if that's what I need, I'm game.

Any help?

Bank wires are easy. Just be sure you have the right info.

Once you see how your bank fills out the paperwork, you can probably do it all by email.

I can do mine by email. I print the form, fill it out, scan as .pdf and email to my bank manager.

Couldn't be easier.

Actually, now that I think about it, running to the store with a fistful of cash is much more involved. There is the paper trail, but for the most part, so what?

That doesn't make sense.

If I had to work harder to get to the MtGox trading floor, I think I'd be inclined to pay "more" for the stuff I worked so hard to get to. And there are "more" people working to get on that trading floor.  But the price is always less.

It's got to be something else doing this.

This feels like a newbie question, so I'll drop it here:

Why is the price on bitfloor consistently around $5 higher than MtGox?

Another exchange I've been watching is the same. What gives?

 Fool me once, shame on — shame on you. Fool me — you can't get fooled again