You are getting some bad advice here and some questionable advice. You might want to slow down. You've now got some keys in Qt, some keys in MultiBit, and some keys in blockchain.info. That sounds like a recipe for disaster.
It would be much better to figure out what the problem is and try to resolve it rather than randomly setting up multiple wallets that all share some private keys hoping that the problem just goes away.
Lets take this one transaction at a time. In the "Console" of the "Debug Window" under the "Help" menu of Bitcoin-Qt, type:
getrawtransaction bee92239ed763ebcd87495af1cbdd6e3d2f836e3091169eaa6880714c0565744
Then post the resulting really long string of numbers and letters here. That is the transaction that your Bitcoin-Qt created and should have broadcast onto the network. We should be able to decode it and determine if there is anything wrong with the inputs.
If the transaction looks ok, then it can be pushed manually onto the network. If you don't want it pushed onto the network, then pywallet can be used to remove it from the wallet. Either way, lets take a look at it first and see if we can figure out what's wrong with it.
