If the coins did not make it into the block chain then try: repair wallet, then, if that does not work, salvage wallet and finally delete all roaming except wallet.dat and restart wallet which will re-build the chain. Your roaming has a chain where you tried sending. A new chain should only show what really happened in the chain. Good Luck. There is another command zapwallettxes=1 which rebuilds your wallet showing your address txes that took place in the chain but I don't think it is available in CAP
Hopefully others may be able to help more.
Thanks Woody for the ideas unfortunately nothing worked. Repair the wallet saw nothing wrong and rebuilding the the block chain and block index did not work. I guess the coins are lost unless there is a way to tell the wallet to unsend the coins or mark them as not sent, those coins are lost. Fortunately it is not my main wallet.
If the issue is :
when you view the transaction , it stays unconfirmed .
(Make sure it is connected to Peers , otherwise you have a firewall issue)Click on Help, Debug, Console,
Type in repairwallet , after the wallet is repaired , the amount in overview should include the unconfirmed amount, Close the wallet , then reopen the wallet , after being open a few minutes , it should resend the transaction automatically.
The trick is closing & reopening the wallet after the repair and just letting it sit for an hour or so.
(Wallet has to be in sync and No staking until the transactions are sent) 
FYI:
Only other option is to get your last wallet backup instead and open it with a -rescan to make sure the coin amounts are correct.
The failed sends won't be in it, but the 1st method has worked for me. (it is the waiting that was hardest)
FYI2:
If you don't have a recent backup and are running windows , you can use shadow explorer to get a copy that is only a few days old.
http://www.shadowexplorer.com/
Poll
