user78: When someone gets a status of "0/unconfirmed" on a transaction for a long time - what could he be doing wrong? What should he check to solve this?

user2526: If a transaction has been unconfirmed for three days, clients will delete it. This generally happens when you force a zero transaction fee. 

user85: One common cause of this condition is manually forcing a zero transaction fee. If you force a zero transaction fee on a 'large' transaction (one that gathers Bitcoins from many other transactions or sends Bitcoins to many different sources) other nodes in the Bitcoin network will refuse to relay your transaction.
While there are some nodes that will relay all valid transactions, your client will only send the transaction out about once every half an hour or so. As a result, it can be a long time before, by sheer luck, your client happens to send the transaction to a node that's willing to relay it (that happens to be able to relay it to other nodes that are similarly willing).

user153: When users are quick to close the client, the transaction being sent will not get re-broadcast if for some reason it didn't propagate sufficiently when the first attempt was made.
So before even trying anything -- leave the client up and running on a reliable connection for maybe an hour.  If it still stays at 0/unconfirmed, then other troubleshooting is warranted.

user-1: You can search for your transaction hash on http://blockchain.info/rejected. It will say if your transaction hash did not meet the minimum fees or my client could not connect it's inputs.

user22: Try running bitcoind from the command line with the -rescan option. It may be that your transaction was erroneous or a double-spend attempt and it only exists in your client. You could double-check the receiving address in blockexplorer to see if the transaction ever came through from the rest of the network's perspective. If this is a zero transaction fee transaction (or is just otherwise unlucky) it might still be in-queue to be included in a block. Bitcoin Charts has a list of in-queue transactions you can check as well.
Assuming blockexplorer sees the transaction, your client probably isn't downloading blocks and may not even be connected at all. Check that the block number in your client matches the block number at blockexplorer (or any of a number of other sites), check if your client has 0 connections. If you have no connections, try the troubleshooting steps from this question. Worst case scenario delete everything from the Bitcoin data folder except for wallet.dat and re-launch the client. Several hours later when you've finished downloading a fresh copy of the block chain, your 0/unconfirmed transaction will probably be resolved.

78: <p>When <a href="http://www.reddit.com/r/Bitcoin/comments/klce4/0unconfirmed_status_for_almost_a_week_help/">someone gets a status of "0/unconfirmed" on a transaction for a long time</a> - what could he be doing wrong? What should he check to solve this?</p>
 2526: <p>If a transaction has been unconfirmed for three days, clients will delete it. This generally happens when you force a zero transaction fee. </p>
 85: <p>One common cause of this condition is manually forcing a zero transaction fee. If you force a zero transaction fee on a 'large' transaction (one that gathers Bitcoins from many other transactions or sends Bitcoins to many different sources) other nodes in the Bitcoin network will refuse to relay your transaction.</p>

<p>While there are some nodes that will relay all valid transactions, your client will only send the transaction out about once every half an hour or so. As a result, it can be a long time before, by sheer luck, your client happens to send the transaction to a node that's willing to relay it (that happens to be able to relay it to other nodes that are similarly willing).</p>
 153: <p>When users are quick to close the client, the transaction being sent will not get re-broadcast if for some reason it didn't propagate sufficiently when the first attempt was made.</p>

<p>So before even trying anything -- leave the client up and running on a reliable connection for maybe an hour.  If it still stays at 0/unconfirmed, then other troubleshooting is warranted.</p>
 -1: <p>You can search for your transaction hash on <a href="http://blockchain.info/rejected" rel="nofollow">http://blockchain.info/rejected</a>. It will say if your transaction hash did not meet the minimum fees or my client could not connect it's inputs.</p>
 22: <p>Try running <code>bitcoind</code> from the command line with the <code>-rescan</code> option. It may be that your transaction was erroneous or a double-spend attempt and it only exists in your client. You could double-check the receiving address in <a href="http://www.blockexplorer.com" rel="nofollow noreferrer">blockexplorer</a> to see if the transaction ever came through from the rest of the network's perspective. If this is a zero transaction fee transaction (or is just otherwise unlucky) it might still be in-queue to be included in a block. Bitcoin Charts has a <a href="http://bitcoincharts.com/bitcoin/" rel="nofollow noreferrer">list of in-queue transactions</a> you can check as well.</p>

<p>Assuming blockexplorer sees the transaction, your client probably isn't downloading blocks and may not even be connected at all. Check that the block number in your client matches the block number at blockexplorer (or any of a number of other sites), check if your client has 0 connections. If you have no connections, try the troubleshooting steps from <a href="https://bitcoin.stackexchange.com/questions/464/why-cant-i-get-over-8-connections-on-my-client">this question</a>. Worst case scenario delete everything from the Bitcoin data folder <strong>except for wallet.dat</strong> and re-launch the client. Several hours later when you've finished downloading a fresh copy of the block chain, your 0/unconfirmed transaction will probably be resolved.</p>
