Ok yes, it looks like the first one is not connected to peers. You see it says "has not been successfully broadcast yet".
Do you definitely have peers connected?
I am not solomining (not enough hashrate) in the wallet, so cannot test. Nothing changed between the two wallet releases though other than.
1. DNS seeds were updated to help get wallet synced without adding nodes
2. UPNP was built in to increase number of nodes available to connect to a sync the blockchain
Other than that, nothing else changed in the code, so I am at a loss to know why the new wallet would be behaving differently when solomining. If you want to keep solomining, perhaps you could move back to the old wallet version which is still at http://sdrv.ms/1esmm4H but I actually think there is no reason the new wallet would be doing anything different regarding solomining.
I also just checked some of my own solomined blocks (from day 1) in both the old and new wallets and they look exactly the same. Of course, I haven't tried generating any new solomined blocks in the new wallet, but it does sync OK for me and finds peers.
Please check your peers (either just look at the connected peers in the gui, or do getpeerinfo in the debug console). Sometimes, I've had wallets fail to sync and just closing and reopening them has fixed it?
All right. Thank you. I received the following information:
22:53:49 getpeerinfo
22:53:49 [
{
"addr" : "5.135.140.184:5889",
"services" : "00000000",
"lastsend" : 1390163948,
"lastrecv" : 1390168423,
"bytessent" : 126,
"bytesrecv" : 5303,
"blocksrequested" : 0,
"conntime" : 1390163948,
"version" : 0,
"subver" : "",
"inbound" : false,
"startingheight" : -1,
"banscore" : 0
},
{
"addr" : "192.241.125.216:5889",
"services" : "00000000",
"lastsend" : 1390164765,
"lastrecv" : 1390168423,
"bytessent" : 126,
"bytesrecv" : 4537,
"blocksrequested" : 0,
"conntime" : 1390164765,
"version" : 0,
"subver" : "",
"inbound" : false,
"startingheight" : -1,
"banscore" : 0
},
{
"addr" : "54.197.230.111:5889",
"services" : "00000000",
"lastsend" : 1390167640,
"lastrecv" : 1390168429,
"bytessent" : 126,
"bytesrecv" : 455,
"blocksrequested" : 0,
"conntime" : 1390167640,
"version" : 0,
"subver" : "",
"inbound" : false,
"startingheight" : -1,
"banscore" : 0
},
{
"addr" : "23.83.200.162:5889",
"services" : "00000000",
"lastsend" : 1390168159,
"lastrecv" : 1390168424,
"bytessent" : 126,
"bytesrecv" : 327,
"blocksrequested" : 0,
"conntime" : 1390168159,
"version" : 0,
"subver" : "",
"inbound" : false,
"startingheight" : -1,
"banscore" : 0
},
{
"addr" : "84.106.121.125:5889",
"services" : "00000000",
"lastsend" : 1390168308,
"lastrecv" : 1390168424,
"bytessent" : 126,
"bytesrecv" : 211,
"blocksrequested" : 0,
"conntime" : 1390168308,
"version" : 0,
"subver" : "",
"inbound" : false,
"startingheight" : -1,
"banscore" : 0
}
]
I am rebooted the computer and wallet. After that, I re-started Vertcoin CGMinerAleksNR3. I'm going tonight to see what happens. If still be problems I'll come back an older version of a wallet. I'll let you know when solve (if I solve) the problem.