Thanks for explaining more details! I'll definitely update my client sooner or later.

Indeed. This fixed it. Silly me. I thought this was to rebuild the blockchain, which could take days.

I'm familiar with debugging in general and also with MSVC.

Yeah, I found (after my last post) that it was a library, but as I don't know Python I still didn't figure out the connection.
Maybe I'll try to build the Windows client myself as a tiny first step. Are the build instructions still valid or did you update them somewhere?
On the other hand, I'm pretty busy as usual (it's now 2.30am and I have to go to work tomorrow), so maybe I never get anything done.
Looks like you don't want to talk about donations. If you want, put an address into your profile.
Thanks again, great work!

Yes. I know. I just came back without doing much with Bitcoin for at least one year and find my environment somehow broken although there was no blockchain fork as far as I know. First I'd like to find out what is wrong before considering any changes. Today I found out about the Armory company issue and that you took over the client maintenance. Thanks a lot for that! Let me know where to donate; I'll send something as soon as sending works again for me.  
I won't tell here what amount I have in my wallet (maybe just a few Satoshis, maybe millions), but you have to always assume that people fear of losing money (and there could be millions in the wallet). Therefore any change can potentially break things or make it unsafe. I didn't know that Armory was taken over and how trustworthy the new "organization" is and all that. Anyway, I'll probably upgrade soon. Forget this side topic.

You can't ever be sure that it wouldn't happen in 0.95 before finding the reason. I don't think it's fee-related, because adjusting the fees is working. The amount just doesn't get sent out. Anyway, I tried today again and also with setting a higher fee. it's a relatively small transaction (only one input address, two output addresses) with an amount 0.024579 and fee 0.0007 (more than enough from what I read) and it still failed without error message.

You're right here of course. And I was also wrong saying that there is nothing; I looked at the wrong log (the cpp log). In the normal log you can see Armory crashing.
And when I was looking at the cpp log, there was not date/time info, so it was difficult to find out what was new, but I searched for "error" and couldn't find anything interesting.
Here's the log:
http://pastebin.com/raw/rH2mbmyZ
It contains both log and cpplog, but only the entries after Armory has started up.
I clicked a link somewhere else (Bitcoin payment link), therefore you see the entries "already open" and that stuff.
I censored the wallet name, my Windows user name in the directory names and the exact bitcoin: link that I clicked, as the same error also happens when I copy/paste the destination address manually into the send dialog.
So what sticks out is the crash:
Any ideas what is causing this? Is there a way I can debug this code? I'm not familiar with Python, but I know C++ very well.
Where did it crash exactly? In CppBlockUtils.pyc/2014ff? Where can I find this old file? I can't find it in the etotheipi guthub repo.

Hi, I'm using Armory 0.93.3 with Core 0.11.1 and everything seems fine. Armory client is in status Connected and wallet shows correct amount.
Now I wanted to make a purchase, but when I click the actual "Send!" button, nothing happens. No error, dialog remains open. No asking for unlocking the wallet.
When I leave the default fee of 0.0001 and click the send button, I get a dialog that the fee is too small and should be increased. If I click OK, the fee gets increased in the dialog, but also nothing else happens, not even when I click "Send!" again.
I've seen that Armory 0.95.1 with Segwit is out (no idea what that is), but shouldn't be sending work as expected with the 0.93.3 client? Is there a known bug?
In the log there is no error or anything I could see. Is this a known issue? I couldn't find anything. I'm using Win10 (anniversary update) in 64 bit and the wallet was created with an older Armory version.
I thought of changing the wallet password to see if unlocking works, but I'm afraid now to change anything if there is something wrong anyway.

That's a good start. But if you want to be safe against 0-days viruses, at least encrypt the wallet.

Yes, I'm using 0.3.23 Win exe, downloaded from the start page bitcoin.org.

Ok, thanks.

Congratulations to your idea and the domain name!

But before you get rich, there are a few things you need to do:
- improve the design (someone offered help already)
- add an initial amount to the jackpot, maybe 1 BTC, better more. If nobody enters and you still have to payout the sponsored 1 BTC, then you'll lose it. But nobody will pay 0.10 BTC for a chance to win 0.02 BTC.
- give more infos, like traffic, number of participants, current jackpot subtracted the fees, security measures, previous winners, etc etc This is needed to build up confidence.

I've read quite a few times in this thread to make backups of your bitcoin wallet. But if I'm not completely wrong, then even stealing just the backup data results in losing all your bitcoins. So from a security perspective, better don't make backup copies!

Instead of buying a notebook, I would store a wallet with a fixed amount on a new memory stick. Plug it in only when you intend to pay with it. Don't store more than you could afford to lose on each stick. Delete all backups on computer after using the wallet. And plug it only into computers you know that are clean.

Open questions are: 1, 2, 7. For 2: yes, I have an old dual CPU (each single core) motherboard as my client PC (running Vista 32). But I didn't give any thread limitations and I was talking about the official client, not about any miner. So the question remains why it's using CPU at all.

And if I understood you correctly, it's not worth running *any* mining software on the server (although the server is running anyway), because the miner would increase CPU usage causing more electricity costs not worth the results. Correct?

Thanks Fjordbit. Although it doesn't answer all my questions, it's a real good start for me and really helps. Thank you!

Hi, I'm running a Windows 2008 32 bit server as my domain controller and file server and web server and thought I could run a bitcoin miner on it as it is running anyway 24 hours a day. The only problem is that it is running on very old hardware (around 5-10 years old), so no GPU support and even the CPU is slow (Pentium 4, 2.8GHz). But as it doesn't cost my anything to let some software run permanently on it, should I do it or is it not worth it? I would also have an unused latest generation (around 6 month old) Mac Mini, but I would have to turn it on which costs energy (0.1787 CHF/kWh at day, 0.1167 CHF/kWh at night). Also I have several PCs available that could get the software installed, so they mine in the background, but none has strong graphical power.

Questions:
1. When I run the official Windows client, is it mining? Or is this client only for transactions?
2. Why is the official client using exactly 50% CPU? If it's mining, then I would expect 100% CPU, if not I'd expect ~0%.
3. What software should I install on my old server to do CPU mining?
4. What are the security risks running a miner on a server having the ports open? Or can mining be done "offline", transferring the results only manually once a day or so?
5. Is it worth powering up the Mac Mini running any miner? If yes, which one?
6. Is it worth letting *any* mining software run on the server or is this way to slow anyway?
7. The official client didn't ask me any setup questions. Where are my bitcoins if I get any through mining or transactions?
8. How would I join a mining group? Do I need special software for that? The official client has no options.

Please no guessing. But if you have a clear answer to any single question, I'd greatly appreciate the answer. Or ask if you need to know more details. Thanks for helping.