Error: Transaction creation failed!

[Trongersoll]

Phew, i've always hated doing remote tech support. Reading this whole thread just now, I found myself holding my breath several times. Danny you have done a tremendous job and should be proud of yourself. Under your name on the left it says "Hero Member" (i know it is just a post count), after reading this, I'm convinced that you truely are. GOOD JOB!

[1714639490]

1714639490

[1714639490]

1714639490

[1714639490]

1714639490

[1714639490]

1714639490

[DannyHamilton]

bump

Sorry about my extended absence.  Life got busy, and I didn't have the time available to carefully put together raw transactions.

I tried today, but the unspent list I have from you seems to be outdated.  Several of the dust outputs I tried to sweep together were already swept by us earlier.  Apparently somewhere along the way I've lsot track of which outputs we've already cleaned up and which we haven't yet.

Can you run "listunspent" in the console again and email me the output so I have a fresh list to work from?

[Vexual]

My apologies, I must have overlooked this post

bitcoin-qt>help>debug window>debug log file (open)
look for error code associated with failed transaction

did you look at the log file yet?

I found this:
ERROR: CTransaction::CheckTransaction() : vin empty
ERROR: CTxMemPool::accept() : CheckTransaction failed
Misbehaving: 160.36.137.15:8333 (60 -> 70)

----------------------------

this:
socket recv error 10053
disconnecting node 46.158.8.177:8333

_________________________

this:
init message: Verifying wallet integrity...
dbenv.open LogDir=C:\Users\Person\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Person\AppData\Roaming\Bitcoin\db.log

I am not too proud to say that I don't understand what happened here.
A similar error is noted here: https://github.com/bitcoin/bitcoin/issues/2668

[ECore]

bump

Sorry about my extended absence.  Life got busy, and I didn't have the time available to carefully put together raw transactions.

I tried today, but the unspent list I have from you seems to be outdated.  Several of the dust outputs I tried to sweep together were already swept by us earlier.  Apparently somewhere along the way I've lsot track of which outputs we've already cleaned up and which we haven't yet.

Can you run "listunspent" in the console again and email me the output so I have a fresh list to work from?

hey i understand.

listunspent sent

[ECore]

bump.

I tried to make a purchase today...without any luck, they are locked up again.

[DannyHamilton]

bump

Sorry about my extended absence.  Life got busy, and I didn't have the time available to carefully put together raw transactions.

I tried today, but the unspent list I have from you seems to be outdated.  Several of the dust outputs I tried to sweep together were already swept by us earlier.  Apparently somewhere along the way I've lsot track of which outputs we've already cleaned up and which we haven't yet.

Can you run "listunspent" in the console again and email me the output so I have a fresh list to work from?

hey i understand.

listunspent sent

Received it.  I'll get started on putting together some additional raw transactions to sweep up what's left of the "dust".  Hopefully once we've got it all swept up, your wallet will be able to create regular transactions again.  If not, then at least we'll be able to transfer the entire balance over to a new wallet by sending it there with a raw transaction.  Either way, I'll get this problem resolved for you.

[DannyHamilton]

bump.

I tried to make a purchase today...without any luck, they are locked up again.

Do you still have that other wallet running on a computer downstairs?

If so, I can use a raw transaction to send the balance there so you can make the purchase from that computer.  Then once you're done with the purchase, we can get back to sweeping up what's left of this dust.

[ECore]

bump.

I tried to make a purchase today...without any luck, they are locked up again.

Do you still have that other wallet running on a computer downstairs?

If so, I can use a raw transaction to send the balance there so you can make the purchase from that computer.  Then once you're done with the purchase, we can get back to sweeping up what's left of this dust.

Yes, I'll go get it running.

[DannyHamilton]

bump.

I tried to make a purchase today...without any luck, they are locked up again.

Do you still have that other wallet running on a computer downstairs?

If so, I can use a raw transaction to send the balance there so you can make the purchase from that computer.  Then once you're done with the purchase, we can get back to sweeping up what's left of this dust.

Yes, I'll go get it running.

Ok, I don't want to send the bitcoin there until I know for sure that you'll be able to access it.

Can you confirm for me when it has caught up synchronizing the blockchain and can you confirm for me that the address 13s4Nxh3SKHnLfhJyvzsdncAuSt71Fzk86 is still a valid address in that downstairs wallet?

[ECore]

bump.

I tried to make a purchase today...without any luck, they are locked up again.

Do you still have that other wallet running on a computer downstairs?

If so, I can use a raw transaction to send the balance there so you can make the purchase from that computer.  Then once you're done with the purchase, we can get back to sweeping up what's left of this dust.

Yes, I'll go get it running.

Ok, I don't want to send the bitcoin there until I know for sure that you'll be able to access it.

Can you confirm for me when it has caught up synchronizing the blockchain and can you confirm for me that the address 13s4Nxh3SKHnLfhJyvzsdncAuSt71Fzk86 is still a valid address in that downstairs wallet?

Yes it is synchonized and yes that is still the address.

[DannyHamilton]

Ok, I don't want to send the bitcoin there until I know for sure that you'll be able to access it.

Can you confirm for me when it has caught up synchronizing the blockchain and can you confirm for me that the address 13s4Nxh3SKHnLfhJyvzsdncAuSt71Fzk86 is still a valid address in that downstairs wallet?

Yes it is synchonized and yes that is still the address.

Ok, then this one should transfer 22.91398781 BTC to the wallet downstairs.  Once it confirms down there, you can spend it as needed from that wallet.  Then we'll bring the balance back upstairs to continue this.

Code:

createrawtransaction [{\"txid\":\"d21898e8de64b800dc839ff454bf913278bd6f995e33099c2a4e7727583c2314\",\"vout\":517},{\"txid\":\"d3d556060425194689553b699524a71526cc42e5f38f9f84a7238bfece564cfa\",\"vout\":1},{\"txid\":\"d3f65d7ebab9dbaa331b409a30758149df5973faa5b10c4e81a89d0e0a1f6dd6\",\"vout\":5},{\"txid\":\"d4fa572f4a9783dfd9de5f93b4a5902f0883d014b2d27eee95804be524de75a3\",\"vout\":1},{\"txid\":\"d806c7239d896907891ac827ec8b1ecc6b697848aa070c8f2de8acab44e577b1\",\"vout\":5},{\"txid\":\"d9f9440c009c965c584700146a70062fa208952472f4e28190beaae31869b087\",\"vout\":0},{\"txid\":\"ddea6ff4a8f382b2c802faf5901b7d8503a5f8d7b042e8e6b1b36678ed86daa2\",\"vout\":4},{\"txid\":\"e13382821f0699ea586531b98414ed326878f1b64c7b66adfd6d616279cb9571\",\"vout\":1},{\"txid\":\"e679ad05a231e0131e6844c883aba18a1db905d2c52c72866583a1f56a36da90\",\"vout\":1},{\"txid\":\"e8347756c606bbc2dac5126e25d7978521e9bce71e07e5869f02be68bd81040f\",\"vout\":3},{\"txid\":\"e98bab4430ab93a731ac2cb86c04044326a3f4b867b436dc7a54ced5a8e17901\",\"vout\":1},{\"txid\":\"f225e2eb20982aff091a857bd6495a2181d613c4c7112841f693accbf259d453\",\"vout\":0},{\"txid\":\"f530aef1bea1de2383e10768d64b9c7cd4f7d6cf308ad0abec208b3a72fa7762\",\"vout\":0},{\"txid\":\"f7ee2ad2ece89d9e4ef655b2fd0de29210d3572afccfaa6b3eeafd6b702ac68b\",\"vout\":2},{\"txid\":\"fb1ac3e0f67c594757babc3a1bf380d40278eec8570c0f147ef905f3c54033ce\",\"vout\":0},{\"txid\":\"fc69332023c2e861cf46f3f2b3b229acafb8b87dee1952d5408c2a7b40008d47\",\"vout\":1038},{\"txid\":\"fe4144b8cc1d45c2ffe0696e0db33bdac86feefd4bb4c8f02cad7e3274f0236d\",\"vout\":2},{\"txid\":\"00742de296a1f76d468ce31c887c5f93ff4241f50aad976071e93c974db82d43\",\"vout\":5},{\"txid\":\"01fd33a9885429d1d8da6c64648e524a3363973d7498074c5af69ac4efee2b86\",\"vout\":414},{\"txid\":\"0660734386b8f2f83ab9b89dc9c9b5bcb3389c35e17912695a4f27fda68f8760\",\"vout\":2},{\"txid\":\"089fed2c4827072e9865daa9fbc5a547babcdf3b193469f40df25a33b60afb10\",\"vout\":233},{\"txid\":\"08e8bf843c479cdde5f38801ed1f203e57891772a3d3363b714e7e877974396b\",\"vout\":6},{\"txid\":\"0ae1bf137431ea89a10a83c3cfa1d3aaed4586b3d5d39e2adc54037338221468\",\"vout\":1},{\"txid\":\"0d9ab4ec4a8454708ccf2050f55e43f01b0b90faef8a7cc15e62900bcf1a094b\",\"vout\":31},{\"txid\":\"1006c647737e65d409a4b67627a71fbd4e15eb529f4bc55cca2abc1d01585fb8\",\"vout\":168},{\"txid\":\"1055f312ce45d57bbfcdec8025ed4ba388909246c6e8001de23798a421e37587\",\"vout\":1},{\"txid\":\"13b95a3376c33f3b9191fb859d50ae5fb5b3fc4b6316a6e3c6fdee1dcc0eff1d\",\"vout\":3},{\"txid\":\"191f8aab09d598da1b9a690b874a53747ebe7768bad5cd42173f1b3a65b8476a\",\"vout\":27},{\"txid\":\"19cea4c56caadfcd60a0385a48c6bffaa8733799cbced5f65068bde9a0fa2cd4\",\"vout\":2},{\"txid\":\"1a4195625a24d82ce24cd096f107ab3a352fed815ec29d1fe656540693c9cde9\",\"vout\":2},{\"txid\":\"1b4d0b05bfebdfd444622b80e6b51b99028240e5ac1cdd69476a1597f8c6e2c0\",\"vout\":1},{\"txid\":\"1ca8d7627f86c47c7aa3af8d600cc13368fe17a7867ecd80dc76a66e66fd44f9\",\"vout\":3},{\"txid\":\"1da246b189f649423a64c9acce1bfc427c6edccdb2e055009887518db506884c\",\"vout\":17},{\"txid\":\"20652bcb3b54dbc683f9641ababa7a7b33b9a01aaa0a2433e26b6c682d1e4b88\",\"vout\":2},{\"txid\":\"21b8fee8ecf43fa55afbbfb6442f0bd0734e40316e258fc184668755821c7195\",\"vout\":1},{\"txid\":\"21e3644b89370a5a26e6829345fcca6e1c902b56db21472db89c82b99d44a5b6\",\"vout\":4},{\"txid\":\"2332240f111379368c887ff14663af0b547ed9ff0ff90bad138d60bdcb5cfabd\",\"vout\":20},{\"txid\":\"2386926251ec7bfc84f0e2a0ca7ad017f13145f093737f357c19b568e18e36d0\",\"vout\":0},{\"txid\":\"260faa8387d616d589400a828fbd62a52ef5c84918db7b7a08fa678bb9f5463d\",\"vout\":8},{\"txid\":\"277f0d17fb3dc5295684051cb7619de00cf8dec2f643cc8813d58838ce7e12bb\",\"vout\":6},{\"txid\":\"299650c09ef51213ee59a5ef8093ec6d7a7d1a68e5901e9566cc57affe127dcc\",\"vout\":21},{\"txid\":\"2baffab1ee60b7a7c4b543432240aff4199372751d0446f634f7908bf57c4ea5\",\"vout\":4},{\"txid\":\"2d28deac18927117cf38e67edff1c67f09dd0127d12bcd50c585905e64c6984b\",\"vout\":3},{\"txid\":\"2e9dcd4af305fbd6433b5eeb5d8e10c37146c3b185eb2e8ceea9677934f7ab03\",\"vout\":0},{\"txid\":\"2efa15fc93c6a385d4d9a988ab2d7b0c64550d747b318a9b8e6c1550f9ee4b40\",\"vout\":16},{\"txid\":\"30a0eab460df51ce0b5dd4915eb652e8fd2077d6c5c7cdd05284e3ea877985f3\",\"vout\":2},{\"txid\":\"3163848d6cfc559ee96c831a9cb0df0b53bd785f55991fe395ead9b973bcd90f\",\"vout\":1},{\"txid\":\"31e2095e80ee1d3b698daf022ff4fb82c964b4aeaeba718a15f4e9e5d0667123\",\"vout\":8},{\"txid\":\"330e488cbbb8ae1ca3ec78f47d9ab445c31bc33bbb33db80d3b8faaffdf8af08\",\"vout\":0},{\"txid\":\"33b0bd116c2e83260210d2c5211459da24e66e81cd0596a484fc1ecaceae5e6a\",\"vout\":6},{\"txid\":\"342bb1e6b5ca9c70715d0d018cba5b767205c6a422b507d1e7eade193e14a84b\",\"vout\":1},{\"txid\":\"34d424fe0c4027ed3cc32765393381b88623368fa08359faad9ebee264e152b2\",\"vout\":264},{\"txid\":\"3568b5558a529b91c2913c520383c020b8a26ec08720970be6ed7b0a366261ee\",\"vout\":0},{\"txid\":\"37a9d18dbc87b7d923597e7b346909c67776be1cbe0c10be07c1a510d39cfd46\",\"vout\":3},{\"txid\":\"3837781df2d6fbfd8a81cafadb70bd88a26c4cf6004a42c6a5d24f88409fe5fc\",\"vout\":17}] {\"13s4Nxh3SKHnLfhJyvzsdncAuSt71Fzk86\":22.91398781}

It's been a while since we've worked on this, so as a reminerd, don't forget to issue the walletpassphrase command before the:

Code:

signrawtransaction 010000003714233c5827774e2a9c09335e996fbd783291bf54f49f83dc00b864dee89818d20502000000fffffffffa4c56cefe8b23a7849f8ff3e542cc2615a72495693b5589461925040656d5d30100000000ffffffffd66d1f0a0e9da8814e0cb1a5fa7359df498175309a401b33aadbb9ba7e5df6d30500000000ffffffffa375de24e54b8095ee7ed2b214d083082f90a5b4935fded9df83974a2f57fad40100000000ffffffffb177e544abace82d8f0c07aa4878696bcc1e8bec27c81a890769899d23c706d80500000000ffffffff87b06918e3aabe9081e2f472249508a22f06706a140047585c969c000c44f9d90000000000ffffffffa2da86ed7866b3b1e6e842b0d7f8a503857d1b90f5fa02c8b282f3a8f46feadd0400000000ffffffff7195cb7962616dfdad667b4cb6f1786832ed1484b9316558ea99061f828233e10100000000ffffffff90da366af5a1836586722cc5d205b91d8aa1ab83c844681e13e031a205ad79e60100000000ffffffff0f0481bd68be029f86e5071ee7bce9218597d7256e12c5dac2bb06c6567734e80300000000ffffffff0179e1a8d5ce547adc36b467b8f4a3264304046cb82cac31a793ab3044ab8be90100000000ffffffff53d459f2cbac93f6412811c7c413d681215a49d67b851a09ff2a9820ebe225f20000000000ffffffff6277fa723a8b20ecabd08a30cfd6f7d47c9c4bd66807e18323dea1bef1ae30f50000000000ffffffff8bc62a706bfdea3e6baacffc2a57d31092e20dfdb255f64e9e9de8ecd22aeef70200000000ffffffffce3340c5f305f97e140f0c57c8ee7802d480f31b3abcba5747597cf6e0c31afb0000000000ffffffff478d00407b2a8c40d55219ee7db8b8afac29b2b3f2f346cf61e8c223203369fc0e04000000ffffffff6d23f074327ead2cf0c8b44bfdee6fc8da3bb30d6e69e0ffc2451dccb84441fe0200000000ffffffff432db84d973ce9716097ad0af54142ff935f7c881ce38c466df7a196e22d74000500000000ffffffff862beeefc49af65a4c0798743d9763334a528e64646cdad8d1295488a933fd019e01000000ffffffff60878fa6fd274f5a691279e1359c38b3bcb5c9c99db8b93af8f2b886437360060200000000ffffffff10fb0ab6335af20df46934193bdfbcba47a5c5fba9da65982e0727482ced9f08e900000000ffffffff6b397479877e4e713b36d3a3721789573e201fed0188f3e5dd9c473c84bfe8080600000000ffffffff68142238730354dc2a9ed3d5b38645edaad3a1cfc3830aa189ea317413bfe10a0100000000ffffffff4b091acf0b90625ec17c8aeffa900b1bf0435ef55020cf8c7054844aecb49a0d1f00000000ffffffffb85f58011dbc2aca5cc54b9f52eb154ebd1fa72776b6a409d4657e7347c60610a800000000ffffffff8775e321a49837e21d00e8c646929088a34bed2580eccdbf7bd545ce12f355100100000000ffffffff1dff0ecc1deefdc6e3a616634bfcb3b55fae509d85fb91913b3fc376335ab9130300000000ffffffff6a47b8653a1b3f1742cdd5ba6877be7e74534a870b699a1bda98d509ab8a1f191b00000000ffffffffd42cfaa0e9bd6850f6d5cecb993773a8fabfc6485a38a060cddfaa6cc5a4ce190200000000ffffffffe9cdc993065456e61f9dc25e81ed2f353aab07f196d04ce22cd8245a6295411a0200000000ffffffffc0e2c6f897156a4769dd1cace5408202991bb5e6802b6244d4dfebbf050b4d1b0100000000fffffffff944fd666ea676dc80cd7e86a717fe6833c10c608dafa37a7cc4867f62d7a81c0300000000ffffffff4c8806b58d5187980055e0b2cddc6e7c42fc1bceacc9643a4249f689b146a21d1100000000ffffffff884b1e2d686c6be233240aaa1aa0b9337b7ababa1a64f983c6db543bcb2b65200200000000ffffffff95711c8255876684c18f256e31404e73d00b2f44b6bffb5aa53ff4ece8feb8210100000000ffffffffb6a5449db9829cb82d4721db562b901c6ecafc459382e6265a0a37894b64e3210400000000ffffffffbdfa5ccbbd608d13ad0bf90fffd97e540baf6346f17f888c367913110f2432231400000000ffffffffd0368ee168b5197c357f7393f04531f117d07acaa0e2f084fc7bec51629286230000000000ffffffff3d46f5b98b67fa087a7bdb1849c8f52ea562bd8f820a4089d516d68783aa0f260800000000ffffffffbb127ece3888d51388cc43f6c2def80ce09d61b71c05845629c53dfb170d7f270600000000ffffffffcc7d12feaf57cc66951e90e5681a7d7a6dec9380efa559ee1312f59ec05096291500000000ffffffffa54e7cf58b90f734f646041d75729319f4af40224343b5c4a7b760eeb1faaf2b0400000000ffffffff4b98c6645e9085c550cd2bd12701dd097fc6f1df7ee638cf17719218acde282d0300000000ffffffff03abf7347967a9ee8c2eeb85b1c34671c3108e5deb5e3b43d6fb05f34acd9d2e0000000000ffffffff404beef950156c8e9b8a317b740d55640c7b2dab88a9d9d485a3c693fc15fa2e1000000000fffffffff3857987eae38452d0cdc7c5d67720fde852b65e91d45d0bce51df60b4eaa0300200000000ffffffff0fd9bc73b9d9ea95e31f99555f78bd530bdfb09c1a836ce99e55fc6c8d8463310100000000ffffffff237166d0e5e9f4158a71baaeaeb464c982fbf42f02af8d693b1dee805e09e2310800000000ffffffff08aff8fdaffab8d380db33bb3bc31bc345b49a7df478eca31caeb8bb8c480e330000000000ffffffff6a5eaececa1efc84a49605cd816ee624da591421c5d2100226832e6c11bdb0330600000000ffffffff4ba8143e19deeae7d107b522a4c60572765bba8c010d5d71709ccab5e6b12b340100000000ffffffffb252e164e2be9eadfa5983a08f362386b88133396527c33ced27400cfe24d4340801000000ffffffffee6162360a7bede60b972087c06ea2b820c08303523c91c2919b528a55b568350000000000ffffffff46fd9cd310a5c107be100cbe1cbe7677c60969347b7e5923d9b787bc8dd1a9370300000000fffffffffce59f40884fd2a5c6424a00f64c6ca288bd70dbfaca818afdfbd6f21d7837381100000000ffffffff017df89388000000001976a9141f67deb7ac148bce94809229dc4a99ada9cb2af688ac00000000

Then remember to issue the sendrawtransaction command with the appropriate output from the signrawtransaction command (assuming it reports "complete" : true).

[ECore]

true, but I got TX rejected (code -22) went I did the sendrawtransaction

[DannyHamilton]

true, but I got TX rejected (code -22) went I did the sendrawtransaction

That most likely results from an incorrect copy of the signed transaction.

 A few possibilities exist.

• You accidentally copied more than just the hex characters to the clipboard from the signrawtransaction output (perhaps you copied the " marks along with it?)
• You accidentally missed one or more hex characters at the beginning or end of the output from signrawtransaction when copiying.
• You accidentally forgot to copy the output from signrawtransaction at all, and instead pasted/re-used the input to signrawtransaction as input to sendrawtransaction.
• You didn't forget to copy the output from signrawtransaction, but for some reason your computer failed to add it to the clipboard when you attempted to copy it

I'd suggest trying the process again if you haven't yet.  If you still have the output from the signrawtransaction in your scroll-back buffer, you only need to re-copy it and re-try the sendrawtransaction.  If you've already shut down that wallet and don't have that output available any longer, then you'll need to start over from the createrawtransaction command.

If you've already carefully re-tried and are certain that it isn't any of the possibilities that I've listed, let me know and I'll dig into the wallet source code and see exactly how/when code -22 is generated.

[ECore]

true, but I got TX rejected (code -22) went I did the sendrawtransaction

That most likely results from an incorrect copy of the signed transaction.

 A few possibilities exist.

• You accidentally copied more than just the hex characters to the clipboard from the signrawtransaction output (perhaps you copied the " marks along with it?)
• You accidentally missed one or more hex characters at the beginning or end of the output from signrawtransaction when copiying.
• You accidentally forgot to copy the output from signrawtransaction at all, and instead pasted/re-used the input to signrawtransaction as input to sendrawtransaction.
• You didn't forget to copy the output from signrawtransaction, but for some reason your computer failed to add it to the clipboard when you attempted to copy it

I'd suggest trying the process again if you haven't yet.  If you still have the output from the signrawtransaction in your scroll-back buffer, you only need to re-copy it and re-try the sendrawtransaction.  If you've already shut down that wallet and don't have that output available any longer, then you'll need to start over from the createrawtransaction command.

If you've already carefully re-tried and are certain that it isn't any of the possibilities that I've listed, let me know and I'll dig into the wallet source code and see exactly how/when code -22 is generated.

I'm fairly certain that I did it correctly.  I performed it 3 times.

[DannyHamilton]

true, but I got TX rejected (code -22) went I did the sendrawtransaction

That most likely results from an incorrect copy of the signed transaction.

 A few possibilities exist.

• You accidentally copied more than just the hex characters to the clipboard from the signrawtransaction output (perhaps you copied the " marks along with it?)
• You accidentally missed one or more hex characters at the beginning or end of the output from signrawtransaction when copiying.
• You accidentally forgot to copy the output from signrawtransaction at all, and instead pasted/re-used the input to signrawtransaction as input to sendrawtransaction.
• You didn't forget to copy the output from signrawtransaction, but for some reason your computer failed to add it to the clipboard when you attempted to copy it

I'd suggest trying the process again if you haven't yet.  If you still have the output from the signrawtransaction in your scroll-back buffer, you only need to re-copy it and re-try the sendrawtransaction.  If you've already shut down that wallet and don't have that output available any longer, then you'll need to start over from the createrawtransaction command.

If you've already carefully re-tried and are certain that it isn't any of the possibilities that I've listed, let me know and I'll dig into the wallet source code and see exactly how/when code -22 is generated.

I'm fairly certain that I did it correctly.  I performed it 3 times.

Very interesting.  So createrawtransation managed to create the transaction without any errors reported, and signrawtransaction returned {"complete : true}, but sendrawtransaction won't send it.  I'll look into it, I'm not sure how a transaction like this can be created and signed successfully and yet can't be sent.

I'll let you know what I figure out.

If anyone else reading this thread already knows what the problem is, feel free to chime in here and save us both some time.  

[ECore]

true, but I got TX rejected (code -22) went I did the sendrawtransaction

That most likely results from an incorrect copy of the signed transaction.

 A few possibilities exist.

• You accidentally copied more than just the hex characters to the clipboard from the signrawtransaction output (perhaps you copied the " marks along with it?)
• You accidentally missed one or more hex characters at the beginning or end of the output from signrawtransaction when copiying.
• You accidentally forgot to copy the output from signrawtransaction at all, and instead pasted/re-used the input to signrawtransaction as input to sendrawtransaction.
• You didn't forget to copy the output from signrawtransaction, but for some reason your computer failed to add it to the clipboard when you attempted to copy it

I'd suggest trying the process again if you haven't yet.  If you still have the output from the signrawtransaction in your scroll-back buffer, you only need to re-copy it and re-try the sendrawtransaction.  If you've already shut down that wallet and don't have that output available any longer, then you'll need to start over from the createrawtransaction command.

If you've already carefully re-tried and are certain that it isn't any of the possibilities that I've listed, let me know and I'll dig into the wallet source code and see exactly how/when code -22 is generated.

I'm fairly certain that I did it correctly.  I performed it 3 times.

Very interesting.  So createrawtransation managed to create the transaction without any errors reported, and signrawtransaction returned {"complete : true}, but sendrawtransaction won't send it.  I'll look into it, I'm not sure how a transaction like this can be created and signed successfully and yet can't be sent.

I'll let you know what I figure out.

If anyone else reading this thread already knows what the problem is, feel free to chime in here and save us both some time.  

I'm emailing you a copy of the transaction, maybe you could see if I was doing something wrong...also a copy of the debug log.

[DannyHamilton]

true, but I got TX rejected (code -22) went I did the sendrawtransaction

That most likely results from an incorrect copy of the signed transaction.

 A few possibilities exist.

• You accidentally copied more than just the hex characters to the clipboard from the signrawtransaction output (perhaps you copied the " marks along with it?)
• You accidentally missed one or more hex characters at the beginning or end of the output from signrawtransaction when copiying.
• You accidentally forgot to copy the output from signrawtransaction at all, and instead pasted/re-used the input to signrawtransaction as input to sendrawtransaction.
• You didn't forget to copy the output from signrawtransaction, but for some reason your computer failed to add it to the clipboard when you attempted to copy it

I'd suggest trying the process again if you haven't yet.  If you still have the output from the signrawtransaction in your scroll-back buffer, you only need to re-copy it and re-try the sendrawtransaction.  If you've already shut down that wallet and don't have that output available any longer, then you'll need to start over from the createrawtransaction command.

If you've already carefully re-tried and are certain that it isn't any of the possibilities that I've listed, let me know and I'll dig into the wallet source code and see exactly how/when code -22 is generated.

I'm fairly certain that I did it correctly.  I performed it 3 times.

Very interesting.  So createrawtransation managed to create the transaction without any errors reported, and signrawtransaction returned {"complete : true}, but sendrawtransaction won't send it.  I'll look into it, I'm not sure how a transaction like this can be created and signed successfully and yet can't be sent.

I'll let you know what I figure out.

If anyone else reading this thread already knows what the problem is, feel free to chime in here and save us both some time.  

I'm emailing you a copy of the transaction, maybe you could see if I was doing something wrong...also a copy of the debug log.

Thanks. Hopefully that'll help me figure out what's happening.

[Vexual]

from https://github.com/bitcoin/bitcoin/pull/1908

RPC_DESERIALIZATION_ERROR       = -22, // Error parsing or validating structure in raw format

[Vexual]

Perhaps Danny could start looking for the input(s) that cause the error by sending smaller numbers of inputs, until the error producing input(s) reveal themselves.
Is it possible the wallet file became corrupted by a disc error or something?
Is it one unique input address that is producing this error?
Is the hard drive on Ecores first machine full of physical errors?


This may be of interest:
 TheBlueMatt 7 days ago Remove broken option to skip input checking for wallet txn.
 https://github.com/bitcoin/bitcoin/blob/master/src/rpcrawtransaction.cpp

[Vexual]

If you fully automate your scripts one day Danny, you could have a very usefull tool here.
Automatic rejuvenating of dusty old corrupt wallets.
Perhaps you could switch off the parallel port too, and save people like Ecore from using too much ink and paper.