NA

[BitHappy24]

English: https://gulden.com
Dutch: https://gulden.com/nl
German: https://gulden.com/de
Spanish: https://gulden.com/es
Frensh: https://gulden.com/fr
Greek: https://gulden.com/gr
Turkish: https://gulden.com/tr
Russian: https://gulden.com/ru
China: https://gulden.com/cn
Indonesia: https://gulden.com/id
Portugal: https://gulden.com/pt

All updates here
https://www.reddit.com/r/gulden/comments/3qg5lu/guldencom_website_translations
https://bitcointalk.org/index.php?topic=1221290

nice, thanks for the continued updates

[MaNI]

@Shopem, i googled a bit and saw that possibly you can retrieve the private key with a hex-program. I have no experience with that. Once you have the private key you can import that in a new wallet. I think it is wise to wait for the experts to assist on this.

Did you have only 1 backup file?

I recovered multiple wallet.dat and other files

Are the files maybe marked as read only? Right click them, go into properties and ensure they are writeable.
Note: this alone might be enough to make the 'corruption' disappear so try this first without the salvage wallet option even.  (That bitcoin-qt reports read only wallet files as corrupted is horrific and something that we must fix - I am going to open a bug on our github for this immediately)

[MaNI]

@Shopem, i googled a bit and saw that possibly you can retrieve the private key with a hex-program. I have no experience with that. Once you have the private key you can import that in a new wallet. I think it is wise to wait for the experts to assist on this.

Did you have only 1 backup file?

I recovered multiple wallet.dat and other files

Are the files maybe marked as read only? Right click them and ensure they are writeable.
Note: this alone might be enough to make the 'corruption' disappear so try this first without the salvage wallet option even.  (That bitcoin-qt reports read only wallet files as corrupted is horrific and something that we must fix - I am going to open a bug on our github for this immediately)

https://github.com/Gulden/gulden-dev/issues/55

Let this also be a reminder to everyone, please make regular backups of your wallet.dat
Also please report wallet bugs on our github if you find them, the more bug reports the more fixes the better the wallet

[veertje]

Are the files maybe marked as read only? Right click them, go into properties and ensure they are writeable.
Note: this alone might be enough to make the 'corruption' disappear so try this first without the salvage wallet option even.  (That bitcoin-qt reports read only wallet files as corrupted is horrific and something that we must fix - I am going to open a bug on our github for this immediately)

I hope for Shopem this is it, to be solved.

[ShopemNL]

@Shopem, i googled a bit and saw that possibly you can retrieve the private key with a hex-program. I have no experience with that. Once you have the private key you can import that in a new wallet. I think it is wise to wait for the experts to assist on this.

Did you have only 1 backup file?

I recovered multiple wallet.dat and other files

Are the files maybe marked as read only? Right click them, go into properties and ensure they are writeable.
Note: this alone might be enough to make the 'corruption' disappear so try this first without the salvage wallet option even.  (That bitcoin-qt reports read only wallet files as corrupted is horrific and something that we must fix - I am going to open a bug on our github for this immediately)

I wish this was the problem... Unfortunly not!

[veertje]

MaNI, maybe this can help? http://forum.bitcoin.org/index.php?topic=8274.0

[MaNI]

MaNI, maybe this can help? http://forum.bitcoin.org/index.php?topic=8274.0

It is possible as a last resort.
I think it is better to first try and use salvagewallet, from what I can see currently the salvage is not failing but rather it is failing to rename the file (which it does before the salvage even begins) so as a first step it would be best to figure out why this is.

[veertje]

MaNI, maybe this can help? http://forum.bitcoin.org/index.php?topic=8274.0

It is possible as a last resort.
I think it is better to first try and use salvagewallet, from what I can see currently the salvage is not failing but rather it is failing to rename the file (which it does before the salvage even begins) so as a first step it would be best to figure out why this is.

Ok, that sounds plausible.

[MaNI]

@Shopem, i googled a bit and saw that possibly you can retrieve the private key with a hex-program. I have no experience with that. Once you have the private key you can import that in a new wallet. I think it is wise to wait for the experts to assist on this.

Did you have only 1 backup file?

I recovered multiple wallet.dat and other files

Are the files maybe marked as read only? Right click them, go into properties and ensure they are writeable.
Note: this alone might be enough to make the 'corruption' disappear so try this first without the salvage wallet option even.  (That bitcoin-qt reports read only wallet files as corrupted is horrific and something that we must fix - I am going to open a bug on our github for this immediately)

I wish this was the problem... Unfortunly not!

Please try the following:
1) Create a new folder C:\Recover
2) Place just a single wallet.dat in the folder
3) Ensure both the folder and wallet.dat are readable and writeable
4) Run Gulden.exe -datadir=C:\Recover -salvagewallet -debug from the prompt
5) If it fails send me the debug.log

[ShopemNL]

Please try the following:
1) Create a new folder C:\Recover
2) Place just a single wallet.dat in the folder
3) Ensure both the folder and wallet.dat are readable and writeable
4) Run Gulden.exe -datadir=C:\Recover -salvagewallet -debug from the prompt
5) If it fails send me the debug.log

PyWallet gives me the following error
Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again

Same problem;

2015-10-29 10:05:46 Gulden version v1.5.2.0-f0e8ba6 (2015-10-10 12:42:24 -0400)
2015-10-29 10:05:46 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2015-10-29 10:05:46 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2015-10-29 10:05:46 Default data directory C:\Users\AKKIE\AppData\Roaming\Gulden
2015-10-29 10:05:46 Using data directory N:\Gulden
2015-10-29 10:05:46 Using config file N:\Gulden\Gulden.conf
2015-10-29 10:05:46 Using at most 125 connections (2048 file descriptors available)
2015-10-29 10:05:46 Using 8 threads for script verification
2015-10-29 10:05:46 Using wallet wallet.dat
2015-10-29 10:05:46 init message: Verifying wallet...
2015-10-29 10:05:46 CDBEnv::Open: LogDir=N:\Gulden\database ErrorFile=N:\Gulden\db.log
2015-10-29 10:05:46 Failed to rename wallet.dat to wallet.1446113146.bak
2015-10-29 10:05:46 GUI: initializeResult : Initialization result:  0
2015-10-29 10:05:46 GUI: requestShutdown : Requesting shutdown
2015-10-29 10:05:46 GUI: shutdown : Running Shutdown in thread
2015-10-29 10:05:46 Shutdown: In progress...
2015-10-29 10:05:46 StopNode()
2015-10-29 10:05:46 Shutdown: done
2015-10-29 10:05:46 GUI: shutdown : Shutdown finished
2015-10-29 10:05:46 GUI: shutdownResult : Shutdown result:  1
2015-10-29 10:05:46 GUI: ~BitcoinApplication : Stopping thread
2015-10-29 10:05:46 GUI: ~BitcoinApplication : Stopped thread


Note : The wallet.dat files i recovered are much different then the one from the new wallet. I can recover all data from the new wallet.dat i created. It seems like the wallet.dat files are not right. The recovered files are build somewhere in 2014. Can it have something to do with the fact there are build in old outdated guldencoin wallets?

Edit :
Older wallets giving the same problem

2015-10-29 10:16:07 Guldencoin version v1.3.1.0-unk-beta (Jan  7 2015, 23:42:14)
2015-10-29 10:16:07 Using OpenSSL version OpenSSL 1.0.1h 5 Jun 2014
2015-10-29 10:16:07 Default data directory C:\Users\AKKIE\AppData\Roaming\Guldencoin
2015-10-29 10:16:07 Using data directory N:\Gulden
2015-10-29 10:16:07 Using at most 125 connections (2048 file descriptors available)
2015-10-29 10:16:07 Using 8 threads for script verification
2015-10-29 10:16:07 init message: Portomonnee aan het controleren...
2015-10-29 10:16:07 dbenv.open LogDir=N:\Gulden\database ErrorFile=N:\Gulden\db.log
2015-10-29 10:16:07 Failed to rename wallet.dat to wallet.1446113767.bak
2015-10-29 10:16:07 Shutdown : In progress...
2015-10-29 10:16:07 StopNode()
2015-10-29 10:16:07 Flushed 0 addresses to peers.dat  0ms
2015-10-29 10:16:07 Shutdown : done

[MaNI]

Please try the following:
1) Create a new folder C:\Recover
2) Place just a single wallet.dat in the folder
3) Ensure both the folder and wallet.dat are readable and writeable
4) Run Gulden.exe -datadir=C:\Recover -salvagewallet -debug from the prompt
5) If it fails send me the debug.log

PyWallet gives me the following error
Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again

Same problem;

2015-10-29 10:05:46 Gulden version v1.5.2.0-f0e8ba6 (2015-10-10 12:42:24 -0400)
2015-10-29 10:05:46 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2015-10-29 10:05:46 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2015-10-29 10:05:46 Default data directory C:\Users\AKKIE\AppData\Roaming\Gulden
2015-10-29 10:05:46 Using data directory N:\Gulden
2015-10-29 10:05:46 Using config file N:\Gulden\Gulden.conf
2015-10-29 10:05:46 Using at most 125 connections (2048 file descriptors available)
2015-10-29 10:05:46 Using 8 threads for script verification
2015-10-29 10:05:46 Using wallet wallet.dat
2015-10-29 10:05:46 init message: Verifying wallet...
2015-10-29 10:05:46 CDBEnv::Open: LogDir=N:\Gulden\database ErrorFile=N:\Gulden\db.log
2015-10-29 10:05:46 Failed to rename wallet.dat to wallet.1446113146.bak
2015-10-29 10:05:46 GUI: initializeResult : Initialization result:  0
2015-10-29 10:05:46 GUI: requestShutdown : Requesting shutdown
2015-10-29 10:05:46 GUI: shutdown : Running Shutdown in thread
2015-10-29 10:05:46 Shutdown: In progress...
2015-10-29 10:05:46 StopNode()
2015-10-29 10:05:46 Shutdown: done
2015-10-29 10:05:46 GUI: shutdown : Shutdown finished
2015-10-29 10:05:46 GUI: shutdownResult : Shutdown result:  1
2015-10-29 10:05:46 GUI: ~BitcoinApplication : Stopping thread
2015-10-29 10:05:46 GUI: ~BitcoinApplication : Stopped thread


Note : The wallet.dat files i recovered are much different then the one from the new wallet. I can recover all data from the new wallet.dat i created. It seems like the wallet.dat files are not right. The recovered files are build somewhere in 2014. Can it have something to do with the fact there are build in old outdated guldencoin wallets?

Does the file wallet.1446113146.bak exist afterwards? There is something very strange going on that a basic file rename is failing...

[ShopemNL]

Does the file wallet.1446113146.bak exist afterwards? There is something very strange going on that a basic file rename is failing...

No

[MaNI]

Does the file wallet.1446113146.bak exist afterwards? There is something very strange going on that a basic file rename is failing...

No

Possibly try to run your command prompt as administrator and turn off your virus scanner. Ensure you have the 64 bit version of the program installed if it is a 64 bit windows.
I'm not sure what else to suggest, but the program is at this point not even reaching the part where it tries to recover the wallet.dat (it is failing just to make a copy of the wallet.dat with a different name) and this indicates something external is wrong e.g. unable to even access the file for some reason. (The read only attribute being the most obvious thing here - you are 100% sure the read only attribute is not set?)
If you send me the full debug.log in private perhaps I can pick up some other clues from it.

[ShopemNL]

Possibly try to run your command prompt as administrator and turn off your virus scanner. Ensure you have the 64 bit version of the program installed if it is a 64 bit windows.
I'm not sure what else to suggest, but the program is at this point not even reaching the part where it tries to recover the wallet.dat (it is failing just to make a copy of the wallet.dat with a different name) and this indicates something external is wrong e.g. unable to even access the file for some reason. (The read only attribute being the most obvious thing here - you are 100% sure the read only attribute is not set?)
If you send me the full debug.log in private perhaps I can pick up some other clues from it.

Yes i am pretty sure it aint that. Running cmd in admin modes. I just recovered more then just wallet.dat (It contains 2.12 GB) and going to try it again. I will let you know.

[MaNI]

Possibly try to run your command prompt as administrator and turn off your virus scanner. Ensure you have the 64 bit version of the program installed if it is a 64 bit windows.
I'm not sure what else to suggest, but the program is at this point not even reaching the part where it tries to recover the wallet.dat (it is failing just to make a copy of the wallet.dat with a different name) and this indicates something external is wrong e.g. unable to even access the file for some reason. (The read only attribute being the most obvious thing here - you are 100% sure the read only attribute is not set?)
If you send me the full debug.log in private perhaps I can pick up some other clues from it.

Yes i am pretty sure it aint that. Running cmd in admin modes. I just recovered more then just wallet.dat (It contains 2.12 GB) and going to try it again. I will let you know.

Okay, the next step then is probably to try and get the private keys directly with a hex editor - there are a few scripts around for this.

[ShopemNL]

Possibly try to run your command prompt as administrator and turn off your virus scanner. Ensure you have the 64 bit version of the program installed if it is a 64 bit windows.
I'm not sure what else to suggest, but the program is at this point not even reaching the part where it tries to recover the wallet.dat (it is failing just to make a copy of the wallet.dat with a different name) and this indicates something external is wrong e.g. unable to even access the file for some reason. (The read only attribute being the most obvious thing here - you are 100% sure the read only attribute is not set?)
If you send me the full debug.log in private perhaps I can pick up some other clues from it.

Yes i am pretty sure it aint that. Running cmd in admin modes. I just recovered more then just wallet.dat (It contains 2.12 GB) and going to try it again. I will let you know.

Okay, the next step then is probably to try and get the private keys directly with a hex editor - there are a few scripts around for this.

Can you pm me or add me on skype? aron@shopem.nl

[ShopemNL]

@Shopem: Are all maps readable? Maybe N:user/Appdata/Roaming/Gulden/ map can't be reached?

Go to Configure Map options in windows for that.

I am using N: disk to solve it so it doesnt use appdate folder. If i remove the wallet.dat file and start gulden.exe  it works without a problem.

[MaNI]

Possibly try to run your command prompt as administrator and turn off your virus scanner. Ensure you have the 64 bit version of the program installed if it is a 64 bit windows.
I'm not sure what else to suggest, but the program is at this point not even reaching the part where it tries to recover the wallet.dat (it is failing just to make a copy of the wallet.dat with a different name) and this indicates something external is wrong e.g. unable to even access the file for some reason. (The read only attribute being the most obvious thing here - you are 100% sure the read only attribute is not set?)
If you send me the full debug.log in private perhaps I can pick up some other clues from it.

Yes i am pretty sure it aint that. Running cmd in admin modes. I just recovered more then just wallet.dat (It contains 2.12 GB) and going to try it again. I will let you know.

Okay, the next step then is probably to try and get the private keys directly with a hex editor - there are a few scripts around for this.

Can you pm me or add me on skype? aron@shopem.nl

Best would be if you can come on slack, if not PM, I won't be able to skype until later.

[ShopemNL]

Best would be if you can come on slack, if not PM, I won't be able to skype until later.

gulden.slack.com? I cant get in

[ShopemNL]

Best would be if you can come on slack, if not PM, I won't be able to skype until later.

gulden.slack.com? I cant get in

https://gulden.com/nl/join

Done that