|
Ullo
|
 |
August 13, 2014, 12:47:51 PM |
|
When I start simplewallet got this
014-Aug-13 14:01:42.396965 bytecoin wallet v1.0.0.312()
2014-Aug-13 14:01:54.918681 Loaded wallet keys file, with public address: 2AspARvBH...................................................................... ...................
2014-Aug-13 14:01:54.973684 ERROR C:\projects\sorrybigbro\src\common/boost_serialization_helper.h:104 Exception at [unserialize_obj_from_file], what=unsupported version
2014-Aug-13 14:01:54.973684 ERROR ..\..\src\wallet\wallet2.cpp:683 !r. THROW EXCEPTION: error::file_read_error
2014-Aug-13 14:01:54.974684 ..\..\src\wallet\wallet2.cpp:683:struct tools::error::file_error_base<2>: failed to read file "b.bin"
2014-Aug-13 14:01:54.974684 Error: failed to load wallet: failed to read file "b.bin"
2014-Aug-13 14:01:54.975684 ERROR ..\..\src\simplewallet\simplewallet.cpp:431 could not open account
2014-Aug-13 14:01:54.975684 ERROR ..\..\src\simplewallet\simplewallet.cpp:1121 Failed to initialize wallet
All files are there, old simplewallet read it without problem
Investigating. |
|
|
|
|
|
|
|
|
|
|
|
|
The Bitcoin network protocol was designed to be extremely flexible. It can be used to create timed transactions, escrow transactions, multi-signature transactions, etc. The current features of the client only hint at what will be possible in the future.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
pepi
|
|
August 13, 2014, 12:58:18 PM |
|
When I first time start new daemon: he rebuild blockchain. Maybe I need to download blackchain again? Or it is error from wallet only.
|
|
|
|
|
|
Rias
|
|
August 13, 2014, 01:20:24 PM |
|
When I start simplewallet got this
014-Aug-13 14:01:42.396965 bytecoin wallet v1.0.0.312()
2014-Aug-13 14:01:54.918681 Loaded wallet keys file, with public address: 2AspARvBH...................................................................... ...................
2014-Aug-13 14:01:54.973684 ERROR C:\projects\sorrybigbro\src\common/boost_serialization_helper.h:104 Exception at [unserialize_obj_from_file], what=unsupported version
2014-Aug-13 14:01:54.973684 ERROR ..\..\src\wallet\wallet2.cpp:683 !r. THROW EXCEPTION: error::file_read_error
2014-Aug-13 14:01:54.974684 ..\..\src\wallet\wallet2.cpp:683:struct tools::error::file_error_base<2>: failed to read file "b.bin"
2014-Aug-13 14:01:54.974684 Error: failed to load wallet: failed to read file "b.bin"
2014-Aug-13 14:01:54.975684 ERROR ..\..\src\simplewallet\simplewallet.cpp:431 could not open account
2014-Aug-13 14:01:54.975684 ERROR ..\..\src\simplewallet\simplewallet.cpp:1121 Failed to initialize wallet
All files are there, old simplewallet read it without problem
I've had the same error while updating. It was quite easy to solve though: 1. Open daemon, let it rebuild block chain data structure. 2. Close daemon 3. Delete "wallet.bin" file ("wallet" should be replaced with whatever the name of your wallet file is). Do not delete the .keys file!4. Reopen and re-synchronize daemon and simplewallet. |
|
|
|
|
|
Rias
|
|
August 13, 2014, 01:24:21 PM |
|
When I first time start new daemon: he rebuild blockchain. Maybe I need to download blackchain again? Or it is error from wallet only.
Nope, it's just rebuilding the internal structure of the block chain that you already had. I think this is related to the decreased RAM consumption; the devs had to adjust the stored files. So you shouldn't re-download the block chain. |
|
|
|
|
|
pepi
|
|
August 13, 2014, 01:31:43 PM |
|
When I start simplewallet got this
014-Aug-13 14:01:42.396965 bytecoin wallet v1.0.0.312()
2014-Aug-13 14:01:54.918681 Loaded wallet keys file, with public address: 2AspARvBH...................................................................... ...................
2014-Aug-13 14:01:54.973684 ERROR C:\projects\sorrybigbro\src\common/boost_serialization_helper.h:104 Exception at [unserialize_obj_from_file], what=unsupported version
2014-Aug-13 14:01:54.973684 ERROR ..\..\src\wallet\wallet2.cpp:683 !r. THROW EXCEPTION: error::file_read_error
2014-Aug-13 14:01:54.974684 ..\..\src\wallet\wallet2.cpp:683:struct tools::error::file_error_base<2>: failed to read file "b.bin"
2014-Aug-13 14:01:54.974684 Error: failed to load wallet: failed to read file "b.bin"
2014-Aug-13 14:01:54.975684 ERROR ..\..\src\simplewallet\simplewallet.cpp:431 could not open account
2014-Aug-13 14:01:54.975684 ERROR ..\..\src\simplewallet\simplewallet.cpp:1121 Failed to initialize wallet
All files are there, old simplewallet read it without problem
I've had the same error while updating. It was quite easy to solve though: 1. Open daemon, let it rebuild block chain data structure. 2. Close daemon 3. Delete "wallet.bin" file ("wallet" should be replaced with whatever the name of your wallet file is). Do not delete the .keys file!4. Reopen and re-synchronize daemon and simplewallet. Yes it does do the trick! Thanks But when I delete bin file and open in the wallet got error. Then I cloes it and reopen again in simplewallet and then sync started! Happy back to solo mining  |
|
|
|
|
|
Ullo
|
|
August 13, 2014, 02:31:18 PM |
|
When I start simplewallet got this
014-Aug-13 14:01:42.396965 bytecoin wallet v1.0.0.312()
2014-Aug-13 14:01:54.918681 Loaded wallet keys file, with public address: 2AspARvBH...................................................................... ...................
2014-Aug-13 14:01:54.973684 ERROR C:\projects\sorrybigbro\src\common/boost_serialization_helper.h:104 Exception at [unserialize_obj_from_file], what=unsupported version
2014-Aug-13 14:01:54.973684 ERROR ..\..\src\wallet\wallet2.cpp:683 !r. THROW EXCEPTION: error::file_read_error
2014-Aug-13 14:01:54.974684 ..\..\src\wallet\wallet2.cpp:683:struct tools::error::file_error_base<2>: failed to read file "b.bin"
2014-Aug-13 14:01:54.974684 Error: failed to load wallet: failed to read file "b.bin"
2014-Aug-13 14:01:54.975684 ERROR ..\..\src\simplewallet\simplewallet.cpp:431 could not open account
2014-Aug-13 14:01:54.975684 ERROR ..\..\src\simplewallet\simplewallet.cpp:1121 Failed to initialize wallet
All files are there, old simplewallet read it without problem
Investigating. We've updated the source code and the binaries. The problem has been fixed. Thank you for submitting this issue. |
|
|
|
|
pepi
|
|
August 13, 2014, 02:53:26 PM |
|
One more issue: cannot send BCN: before update address was fine, after it say invalid address
[wallet 2AspAR]: transfer 0 27gKck9................... 7900 cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92
Error: wrong address: cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92
|
|
|
|
|
|
ndrog
|
|
August 13, 2014, 02:57:31 PM |
|
Everything is working normally (once deleted bin files). I sent test amount to hitbtc...everything is fine.
|
|
|
|
|
pepi
|
|
August 13, 2014, 03:00:58 PM |
|
Everything is working normally (once deleted bin files). I sent test amount to hitbtc...everything is fine.
On hitbtc I got that error |
|
|
|
|
|
Rias
|
|
August 13, 2014, 03:09:21 PM |
|
One more issue: cannot send BCN: before update address was fine, after it say invalid address
[wallet 2AspAR]: transfer 0 27gKck9................... 7900 cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92
Error: wrong address: cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92
It seems that there is a new format for transfer: transfer <mixin_count> <addres> <amount> [-p payment_id] [-f fee] So in your case: transfer 0 27gKck9................... 7900 -p cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92 |
|
|
|
|
|
ndrog
|
|
August 13, 2014, 03:09:28 PM
Last edit: August 13, 2014, 03:43:53 PM by ndrog |
|
I just sent some test coins to poloniex. Transfer left wallet....if there is an issue the transaction should bounce back.
Oh yeah don't forget to add -f 0.10000000 at the end of the command line. So far have managed to transfer bcn this way
|
|
|
|
|
pepi
|
|
August 13, 2014, 03:44:02 PM |
|
One more issue: cannot send BCN: before update address was fine, after it say invalid address
[wallet 2AspAR]: transfer 0 27gKck9................... 7900 cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92
Error: wrong address: cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92
It seems that there is a new format for transfer: transfer <mixin_count> <addres> <amount> [-p payment_id] [-f fee] So in your case: transfer 0 27gKck9................... 7900 -p cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92 [wallet 2AspAR]: transfer 0 27gKck9SmH3dr......................... 7900 -p cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92 Error: transaction <4c16294f3482414f8d58a46b71e048154e3b533cf27d8caf0b291f82def320a0> was rejected by daemon with status "Failed" |
|
|
|
|
|
ndrog
|
|
August 13, 2014, 03:48:41 PM |
|
One more issue: cannot send BCN: before update address was fine, after it say invalid address
[wallet 2AspAR]: transfer 0 27gKck9................... 7900 cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92
Error: wrong address: cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92
It seems that there is a new format for transfer: transfer <mixin_count> <addres> <amount> [-p payment_id] [-f fee] So in your case: transfer 0 27gKck9................... 7900 -p cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92 [wallet 2AspAR]: transfer 0 27gKck9SmH3dr......................... 7900 -p cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92 Error: transaction <4c16294f3482414f8d58a46b71e048154e3b533cf27d8caf0b291f82def320a0> was rejected by daemon with status "Failed" Your command should be like this: transfer 0 27gKck9................... 7900 -p cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92 -f 0.10000000 |
|
|
|
|
pepi
|
|
August 13, 2014, 03:52:47 PM |
|
[wallet 2AspAR]: transfer 0 27gKck9SmH3drYvGx8aw3QdtpPnaTr1... 7900 -p cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92 -f 0.10000000
Error: transaction <e5503c422833739e88e5277f238b9ef7a86bf5f6b15d697b83f2e717f57937b8> was rejected by daemon with status "Failed"
[wallet 2AspAR]: refresh
Starting refresh...
Refresh done, blocks received: 5
balance: 8000.00000000, unlocked balance: 8000.00000000
|
|
|
|
|
|
ndrog
|
|
August 13, 2014, 03:54:21 PM |
|
Beats the hell out of me. It should work  |
|
|
|
|
33zer0w0lf
|
|
August 13, 2014, 04:32:30 PM |
|
Upgraded Wallet and Daemon @ Extremepool went without issue.
|
|
|
|
|
pepi
|
|
August 13, 2014, 04:32:59 PM |
|
Beats the hell out of me. It should work but it doesnot work. And now I cannot transfer and sold my bytecoins What a great UPDATE!!! |
|
|
|
|
|
33zer0w0lf
|
|
August 13, 2014, 04:35:13 PM |
|
One more issue: cannot send BCN: before update address was fine, after it say invalid address
[wallet 2AspAR]: transfer 0 27gKck9................... 7900 cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92
Error: wrong address: cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92
its not working because you are trying to send to an address that is not a bcn address. |
|
|
|
|
pepi
|
|
August 13, 2014, 04:38:36 PM |
|
One more issue: cannot send BCN: before update address was fine, after it say invalid address
[wallet 2AspAR]: transfer 0 27gKck9................... 7900 cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92
Error: wrong address: cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92
its not working because you are trying to send to an address that is not a bcn address. Really?? Interesting just before upgrade do 1.0V it was , and last month it was, but now it is not any more?  |
|
|
|
|
|
Rias
|
|
August 13, 2014, 04:43:01 PM |
|
[wallet 2AspAR]: transfer 0 27gKck9SmH3drYvGx8aw3QdtpPnaTr1... 7900 -p cd0200624cd1350538518ad6ffdcc068d7be710ceee23e767c70757744415a92 -f 0.10000000
Error: transaction <e5503c422833739e88e5277f238b9ef7a86bf5f6b15d697b83f2e717f57937b8> was rejected by daemon with status "Failed"
[wallet 2AspAR]: refresh
Starting refresh...
Refresh done, blocks received: 5
balance: 8000.00000000, unlocked balance: 8000.00000000
What does the daemon say when it rejects the transfer? Could you paste the output here? |
|
|
|
|
|
