<p>OK, I solved this by numerous trial and error CMDs. The problem lay in the Armory implementation, specifically, the <code>--datadir</code> flag.</p>

<p>The <strong>working</strong> CLI flags:</p>

<ul>
<li><strong>ARMORY:</strong> <code>-qt.exe --testnet --datadir=d:\data\armory\testnet3 --satoshi-datadir=d:\data\bitcoincore --rpcport=8332</code></li>
<li><strong>BITCOIN-QT:</strong> <code>bitcoin-qt.exe -datadir="d:\data\bitcoincore" -testnet -rpcport=8332</code> </li>
</ul>

<p>Contradicting Armory's FAQ (in the FAQ itself) is the requirement to explicitly identify the <em>testnet<strong>3</em></strong> directory for the <code>--data-dir</code> flag (<code>--data-dir==SOME\DIR\Armory\testnet3</code>). If the testnet3 directory isn't identified, Armory confuses the mainnet blockchain data with the testnet chain data. </p>

<p>The <code>bitcoin.conf</code> contents were:</p>

<pre><code>listen=1
daemon=1
server=1
rpcconnect=127.0.0.1
rpcport=8332
</code></pre>

CC BY-SA 3.0
2015-04-05T00:44:39.593Z
2015-04-05T00:44:39.593Z
Wizard Of Ozzie
<p>Running Armory (0.93.0.82) on Win7 x64 with the following flags: </p>

<p><code>"C:\Program Files (x86)\Armory\ArmoryQt.exe" --testnet --datadir=d:\data\armory\testnet3 --satoshi-datadir="d:\data\bitcoincore" --rpcport=8332 --debug --netlog --mtdebug --logfile=d:\data\armory</code></p>

<p>You'll find <a href="https://gist.github.com/eb868e035200bb7c2d79" rel="nofollow noreferrer">the log file</a> throws a recurring error... </p>

<pre><code>    -WARN  - 1427685617: (..\Blockchain.cpp:47) Somehow tried to add header that's already in map
    -WARN  - 1427685617: (..\Blockchain.cpp:48)     Header Hash: 00000000ad4e4c886567776c89e752614f251cca28b7dfcaf16867677ba0245a
</code></pre>

<p>FYI, those times/blocks correspond to the most recent blocks, as validated by Bitcoin-CLI. </p>

<p>It's worth noting that the "current block" field in Armory shows a block ~6000 old (stuck on <code>323060</code>), and mouse hover says <em>"last block received 1.5 minutes ago"</em> (or something similar) and updates with the block discovery.</p>

<p>Bitcoincore (v0.10 btw) <a href="https://i.sstatic.net/Ycajw.jpg" rel="nofollow noreferrer">gives this screenshot</a> (the top 2 Txs - <a href="http://test.webbtc.com/tx/706b60a90510e8db0186be5980819931127110e300ce10c5a5b3f5fb04667dc2" rel="nofollow noreferrer">TxID 706b60a90510e8db0186be5980819931127110e300ce10c5a5b3f5fb04667dc2</a> - are labelled <code>?</code> however they are confirmed in Bitcoincore eventually)</p>

<p>I've tried numerous wallets instances in Armory, updating, ensuring the client is connected, using the rescanning/rebuilding database option, etc. <em>EDIT: Rescanning the database has actually erased all record of the Txs in Armory</em></p>

<p>What is wrong here?</p>

CC BY-SA 3.0
2015-03-30T04:58:23.280Z
This seems like it might be a question better suited for Armory developers, maybe you should file an issue here: https://github.com/etotheipi/BitcoinArmory/issues.
morsecoder
<testnet><armory>
Armory 0.93 on Testnet: consistent unconfirmed Txs sent from connected Bitcoin-cli (log attached)
Wizard Of Ozzie
# Armory 0.93 on Testnet: consistent unconfirmed Txs sent from connected Bitcoin-cli (log attached)

(Asked by: username_0 on 2015-03-30)

Running Armory (0.93.0.82) on Win7 x64 with the following flags: 
"C:\Program Files (x86)\Armory\ArmoryQt.exe" --testnet --datadir=d:\data\armory\testnet3 --satoshi-datadir="d:\data\bitcoincore" --rpcport=8332 --debug --netlog --mtdebug --logfile=d:\data\armory
You'll find the log file throws a recurring error... 
    -WARN  - 1427685617: (..\Blockchain.cpp:47) Somehow tried to add header that's already in map
    -WARN  - 1427685617: (..\Blockchain.cpp:48)     Header Hash: 00000000ad4e4c886567776c89e752614f251cca28b7dfcaf16867677ba0245a

FYI, those times/blocks correspond to the most recent blocks, as validated by Bitcoin-CLI. 
It's worth noting that the "current block" field in Armory shows a block ~6000 old (stuck on 323060), and mouse hover says "last block received 1.5 minutes ago" (or something similar) and updates with the block discovery.
Bitcoincore (v0.10 btw) gives this screenshot (the top 2 Txs - TxID 706b60a90510e8db0186be5980819931127110e300ce10c5a5b3f5fb04667dc2 - are labelled ? however they are confirmed in Bitcoincore eventually)
I've tried numerous wallets instances in Armory, updating, ensuring the client is connected, using the rescanning/rebuilding database option, etc. EDIT: Rescanning the database has actually erased all record of the Txs in Armory
What is wrong here?

**Tags:** testnet, armory

> **Comments:**
> **username_1**: This seems like it might be a question better suited for Armory developers, maybe you should file an issue here: https://github.com/etotheipi/BitcoinArmory/issues.  

---

## 1 answers

### Answer by username_0 on 2015-04-05. Score: 0 | Accepted answer

OK, I solved this by numerous trial and error CMDs. The problem lay in the Armory implementation, specifically, the --datadir flag.
The working CLI flags:

ARMORY: -qt.exe --testnet --datadir=d:\data\armory\testnet3 --satoshi-datadir=d:\data\bitcoincore --rpcport=8332
BITCOIN-QT: bitcoin-qt.exe -datadir="d:\data\bitcoincore" -testnet -rpcport=8332 

Contradicting Armory's FAQ (in the FAQ itself) is the requirement to explicitly identify the testnet3 directory for the --data-dir flag (--data-dir==SOME\DIR\Armory\testnet3). If the testnet3 directory isn't identified, Armory confuses the mainnet blockchain data with the testnet chain data. 
The bitcoin.conf contents were:
listen=1
daemon=1
server=1
rpcconnect=127.0.0.1
rpcport=8332


---

