0.96.3991 - Non Sync with BC Core 0.15.1 - Win 10 x 64

[Armory non geek]

This is copied from an assistance inquiry incorrectly entered to the development thread re 0.96.4 RC2

actions report re the update to the friend's computer:

I found the link for Armory 0.96.3.991 and installed to the friend's Win 10 x 64 computer.

The load in of 0.96.3991 successfully interfaced and upgraded the 0.96.3 already installed, retaining the watcing only "offline" security status of the wallets already installed (with non correct zero balance indicated for each of the watching only copies of those on line wallets).  

Bitcoin core 0.15.1 had already been installed and synced to itself.

Once Armory 0.96.3991 was loaded various experiments were attempted:

1) close BC core 0.15.1, and then start 0.96.3991 - result 0.96.3991 continued to not sync to BCcore 0.15.1

2) open core 0.15.1 first and then start 0.96.3991 - same result of 0.96.3991 not syncing to Core 0.15.1

3) open 0.96.3991 first and then attempt to open CoredB 0.15.1 - result 0.15.1 opened and self synced but absent any correlation to 0.96.3991 - also missing any conflict error messages about 0.96.3991 already accessing the CoreDb (ie to the effect that only one copy of CoredB can be open at one time).

----

Throughout all the above experiments with 0.96.3 and now with 0.96.3991 the watching only wallets are not synced to the CoreDb 0.15.1 and all indicate a zero balance.  

Thank you for your assistance. Is there a different version of Armory which should be installed beyond 0.96.3991 in order to sync Bitcoin core 0.15.1
(after the Bitcoin core 0.15.1 has self synced to itself)?

Or is there a necessary different procedure of install (as in the older versions 0.93.3 and earlier - where Armory was first installed and then Armory needed to complete the full self sync of the BCcore database) so the wallets will sync and indicate their balances?

----

There are requests by the admins here to post the log files, and droark suggested using PasteBin, 0Bin, CryptBin, etc, for the transmission of those log files.  

----

Non geek here, with left brain training in fields outside of IT.  


Do I look for the log files from the "Open Program" commands used by Win 10? Or do you need the copy of the code entry which input into Win 10 when I downloaded the "exe" file?  

As a non geek, what commands does one enter/activate from Win 10 to observe and copy these log files.  

TY for your help - where I'm happy to send you the Log files which you need (once I learn how to find them).

[1715392869]

1715392869

[1715392869]

1715392869

[1715392869]

1715392869

[1715392869]

1715392869

[1715392869]

1715392869

[1715392869]

1715392869

[goatpig]

Post your logs now. They're in your datadir (where you wallets are). I need armorylog.txt and dbLog.txt. Use pastebin to post them.

Thank you for your assistance. Is there a different version of Armory which should be installed beyond 0.96.3991 in order to sync Bitcoin core 0.15.1

Use the most up to date stuff, always.

[Armory non geek]

Post your logs now. They're in your datadir (where you wallets are). I need armorylog.txt and dbLog.txt. Use pastebin to post them.

Thank you for your assistance. Is there a different version of Armory which should be installed beyond 0.96.3991 in order to sync Bitcoin core 0.15.1

Use the most up to date stuff, always.

TY for the specifics of the log files needed. 

At present I don't have admin access to any folders deeper than C:\users\owner\  and the customary windows folders

Cheating (using a paused defrag from Glary Utilities) I can see that the files are stored within
  C:\users\owner\AppData\Roaming\Bitcoin\chainstate\  then the unique respective files

We have a plan to visit the computer shop Friday morning (show them this thread) ask for the keys to admin access,
and also have them assist us to get both the most recent (complete) armorylog.txt and dbLog.txt files & get them into
pastebin - where we can enter them here. 

TY for both your assistance and your patience, while my friend and I get the txt logs you need (entered here via pastebin). 

[goatpig]

At present I don't have admin access to any folders deeper than C:\users\owner\  and the customary windows folders

You don't need admin privileges to access your user account. That's the whole point of user accounts. Otherwise, the software you run would need elevation to write to that path.

Cheating (using a paused defrag from Glary Utilities) I can see that the files are stored within
  C:\users\owner\AppData\Roaming\Bitcoin\chainstate\  then the unique respective files

I don't know where you read this stuff from but don't use backwards tricks like that, that don't do what you think it does to begin with. You cannot start a defragmentation process without admin privileges. The reason you can't see the AppData folder is because it is hidden. Just go in the folder settings and make hidden files visible. You can see folders belonging to other accounts, you just can't read their content.

We have a plan to visit the computer shop Friday morning (show them this thread) ask for the keys to admin access,
and also have them assist us to get both the most recent (complete) armorylog.txt and dbLog.txt files & get them into
pastebin - where we can enter them here.  

Don't, the shop will steal your wallets!

Stop everything you are doing, do not take your computer to a goddamn shop, and just ask for help on how to export your private keys to another wallet. Armory is for expert Bitcoin users, you don't even know your way around Windows. Also consider stepping out of crypto currencies, you are basically asking to get robbed.

[Armory non geek]

TY for the warning.  I have a personal Armory Wallet going back to late 2013 with the On Line/Off Line configuration - updated through 0.93.3 - late 2017 updated to a higher speed net connection, appropriate speed for an upgrade with the latest Armory & BC core. 

Early 2017 I introduced the local area friend to Bitcoins and we have a mutual project through his fast cable modem and Win 10. 

A decade back I knew how to find the hidden files but hadn't the need to do so over the subsequent duration.  I did re-find the info about opening the View options for the hidden files and got the txt files you desire this morning from the friend's computer. 

https://pastebin.com/7UEH61N2 and https://pastebin.com/UkHnaMsE

- yes, yours is a valid criticism re one who continues to prefer analog, yet with some coin positions going back to early 2014.  Thus the "non geek" ID

TY for the assistance.

[goatpig]

If you understand the need for keeping your private keys offline and how to operate that kind of setup with Armory, you are fine. Otherwise you're just asking for trouble. As long as you keep your coins offline, we can proceed. I assumed the worst since it didn't appear you would be taking security seriously. I stand corrected.

Let's get to it then.

1)

Code:

2018-01-12 09:24:39 (INFO) -- SDM.pyc:459 - Called stopBitcoind
2018-01-12 09:24:39 (WARNING) -- SDM.pyc:509 - bitcoind exited, bitcoind STDOUT:
2018-01-12 09:24:39 (WARNING) -- SDM.pyc:511 -
2018-01-12 09:24:39 (WARNING) -- SDM.pyc:512 - bitcoind exited, bitcoind STDERR:
2018-01-12 09:24:39 (WARNING) -- SDM.pyc:514 -
2018-01-12 09:24:39 (INFO) -- SDM.pyc:465 - ...but bitcoind is not running, to be able to stop
2018-01-12 09:24:39 (INFO) -- ArmoryQt.py:5490 - Attempting to close the main window!

bitcoind is choking when Armory tries to spawn it for you. Start BitcoinQt manually, is it borked? Does it want to resync? Also, are you trying to use a custom folder for your blockchain data?

2) From the looks of your dbLog, it seems ok. To be on the safe side, once the Bitcoin node issue is fixed, delete your databases folder for the good measure before running Armory again (C:\Users\Owner\AppData\Roaming\Armory\databases)

[Armory non geek]

TY for examining the conditions of the log files.  

Bitcoind 0.15.1 is loaded to the default location, as is Armory 0.96.3991
Bitcoind 0.15.1 always self-syncs when opened, again confirmed as I was typing this reply.  

Let me know if there is any other information you need.  

TY again for your kind and quick response.  

------

FYI, This evening (and Saturday, Sunday) schedules will keep me fully away from the friend's computer until sometime on Monday.

----  

added info re my experiences over the years, is the observation of how the database fragments the files on the hard drive, and for
which I regularly run the Glary Utilities program routine to defrag and re-optimize the file locations (typically with a defrag once or
twice per week; plus the defrag and optimize routine circa every week to 10 days).  

We have an additional computer set operating Armory 0.96.0.4 along with bitcoin core 0.14.2 (from mid July 2017, pre fork).
This is the initial step toward upgrading all of our Armory wallets and databases to the most current versions.

[goatpig]

TY for examining the conditions of the log files. 

Bitcoind 0.15.1 is loaded to the default location, as is Armory 0.96.3991
Bitcoind 0.15.1 always self-syncs when opened, again confirmed as I was typing this reply. 

Let me know if there is any other information you need. 

TY again for your kind and quick response.   

1) Delete the databases folder as instructed

2) Turn off auto bitcoind in Armory, under File -> Settings.

3) Start BitcoinQt manually, then Armory.

added info re my experiences over the years, is the observation of how the database fragments the files on the hard drive, and for
which I regularly run the Glary Utilities program routine to defrag and re-optimize the file locations (typically with a defrag once or
twice per week; plus the defrag and optimize routine circa every week to 10 days). 

Both Core's DB and ArmoryDB point to block data by offset on disk. Defragmentation displaces on disk data. Defragmentation is 100% useless on SSDs and pretty useless on HDDs. The only thing it achieves is giving you a chance to damage your Bitcoin/Armory setup twice a week. Stop doing that.

[jojo69]

...do not take your computer to a goddamn shop...

I hesitate to bulk up the thread, but feel compelled to chime in.

Non geek, goatpig may come off a bit brusk here, but when I read your plans the hair on the back of my neck stood up.  They are very correct that you should trust NO third party to have access to these systems.  You have been communicating well.  Remain calm, provided you have appropriate backups and continue on your course here I am confident it will all get figured out.

As always, goatpig, your patience with end user minutia is very much appreciated.

[Armory non geek]

TY for the assistance (& encouragement) replies.

These have been your suggestions

primary reply to my inquiry after receiving my ArmoryLog and dbLog files:

<From the looks of your dbLog, it seems ok. To be on the safe side, once the Bitcoin node issue is fixed, delete your databases folder for the good measure before running Armory again (C:\Users\Owner\AppData\Roaming\Armory\databases)>

reply to my action confirmation inquiry:


<1) Delete the databases folder as instructed

2) Turn off auto bitcoind in Armory, under File -> Settings.

3) Start BitcoinQt manually, then Armory.>

------

My actions:

databases folder deleted from the ...AppData\Roaming\Armory folder
within Armory 0.96.3991 File -> Settings "auto bitcoind" has been turned "off" (unchecked from that option choice)

Bitcoin core 0.15.1 has been started and sync'd (and presently remains active).
Armory 0.96.3991 was started

The initial "Armory Loading" (rounded corner rectangle) green progress bar indicates 100% loaded
It then hangs there with zero further action into the opening page of actual Armory

The opening page of Armory remains absent.
(preparing databases progress bar, Loading Database Headers, Scanning Transaction History, nor wallet consistency check progress bars). 

All is stuck on the opening rounded rectangle with the Armory logo. 

------

If further experiments are necessary, is there a best means to close the Armory rounded rectangle (absent a close button)? 

At present it will be necessary to use Glary Utilities Process Manager, or Windows Task Manager to close Armory QT. 

------

Once Bitcoin core 0.15.1 has been sync'd, should it be closed first before engaging Armory 0.96.3991 ? 
as stated, it remains active when I activated Armory 0.96.3991 and now stuck in this "hanging" mode
(opening logo page stuck with 100% loaded displayed for the initial progress bar at the top of the rounded corner rectangle).

TY for your continued assistance.

(and TY for the warning re the computer shop - and from your push I did find the correct info to view the "Hidden Files")
2 computer implementation and full paper (encrypted print) backups have been the modus operandi for myself going back to my initial load of Armory in late 2013 - same implementations with my local area friend. 

[droark]

0.96.4 RC3. RC2 (the one you're using) has a known Windows issue that causes hangs.

[Armory non geek]

TY droark

Is there a remedy regarding the "hangs" for Win 10.  My friend's ISP mandates a windows computer,
as does my personal ISP for my own net connection (my ISP different from that of the friend). 

Do we need to do a forced shut down of Armory 0.96.3991 when it is in the "Hangs" mode? 

<Holding off on other computer upgrades until the Win 10 x 64 friend's Armory is operating> 

Code:

-ERROR - 16:56:12.125: (..\\BlockDataMap.cpp:80) merkle root mismatch!
-ERROR - 16:56:12.125: (..\\BlockDataMap.cpp:81)    header has: 17930e89ab2efd9f06a3644df2bbdf442ce5814deafaf49afacc7a6dbd0b675e
-ERROR - 16:56:12.125: (..\\BlockDataMap.cpp:82)    block yields: 1a26c2397f16376c83eac57c7e346cdb4c1e283a981f7862fa1bc4eb65379655
-ERROR - 16:56:12.125: (..\\DatabaseBuilder.cpp:366) block deser except: invalid merkle root
-ERROR - 16:56:12.125: (..\\DatabaseBuilder.cpp:367) block fileID: 938

Looks like your blockchain files have been corrupted somehow.

Does the above error require a complete reload of the Bitcoin core 0.15.1 database? 
If so, does one need to delete the C:....AppData\Roaming\Bitcoin.... folder? and reload from scratch?
Or is there a shorter duration remedy?

Thank you for your continued assistance. 

[droark]

1)Please install 0.96.4 RC3 (0.96.3.992). I've already asked you to do this once.

2)What I pasted was meant for another thread. Sorry about that. Don't know how that landed here!

[Armory non geek]

TY for confirming that bitcoin core 0.15.1 should be OK

Following a non successful attempt to install Armory 0.96.3992 these are the two most current Log files

https://pastebin.com/eA1zP2gr  and   https://pastebin.com/D77ejppq 

Copy of the install pop up messages are as follows:

 

"Error opening file for writing"

C:\Program Files (x86)\Armory\PyQt4.QtCore.pyd

Click Abort to stop the installation
Retry to try again, or
Ignore to skip this file

<Clicked the Retry button on the Win Pop up >

Hangs at Extract: MSVCP.90dll... 100%

<Following is indicated on the installation progress pop up: >

Output folder:C:\ProgramFiles(x86)\Armory
Delete file:C:\ProgramFiles(x86)\Armory\ArmoryDB.exe
Delete file:C:\ProgramFiles(x86)\Armory\MSVCP90.dll
Extract:ArmoryDB.exe... 100%
Extract:MSVCP90.dll... 100%       

<Clicked Abort - Pop up now indicates >

Installation Aborted
Setup was not completed successfully.

Can't write C:\ProgramFiles(x86)\Armory\PyQt4.QtCore.pyd

<With the install progress indication as >

Output folder:C:\ProgramFiles(x86)\Armory
Delete file:C:\ProgramFiles(x86)\Armory\ArmoryDB.exe
Delete file:C:\ProgramFiles(x86)\Armory\MSVCP90.dll
Extract:ArmoryDB.exe... 100%
Extract:MSVCP90.dll... 100%
Can't write C:\ProgramFiles(x86)\Armory\PyQt4.QtCore.pyd

TY for the continued assistance.

[Armory non geek]

TY to all for the assistance. 

Now have Successful install and sync re 0.96.3992 with BC core 0.15.1


Wednesday afternoon I made a further experiment on the friend's computer. 

Uninstalled BC core 0.15.1 db management program.
Uninstalled my earlier attempt to install Armory 0.96.3992

Reinstalled Bitcoin core 0.15.1 and let it fully sync. 
Closed the 0.15.1 program after completion of the db sync. 

Reinstalled Armory 0.96.3992. 
0.96.3992 correctly completed the install and commenced the Armory sync to BC core 0.15.1
let it continue through the night. 

---

Returned to the friend location on Thurs
Armory 0.96.3992 is fully sync'd.
Each respective watching wallet indicates the correct balance. 

Confirmed that 0.96.3992 will generate a receiving code for one of the wallets.
Confirmed that 0.96.3992 can initiate an off-line spend transaction (requiring off line confirmation).

---------

For the subsequent part of this mutual project with the friend's computer:
To separate out BCH from each of the respective legacy BTC positions
(last transaction mid July 2017 successfully tested consolidation of two wallets with Armory 0.96.0.4), 
should one follow the sequences within the prior thread re Armory 0.96.3?:

Install Bitcoin ABC database on a different machine, etc? 
Will one also use Armory 0.96.3992 to sync the Bitcoin ABC database on the separate computer?
Follow the remaining sequences on the earlier thread for the separation of BCH from the legacy BTC? 

----

Independent question:
Should Bitcoin Core 0.15.1 and Armory 0.96.3992 install with equal facility on a
Win 7 x 64 computer  (2TB HDD & 8GB Ram) as on this Win 10 x 64 computer (same size HDD and Ram)? 
I presume it will be necessary to first uninstall all the prior Armory 0.93.3 and respective bitcoin core files.

TY all for your assistance and continued suggestions.   

[droark]

Uninstall Armory and Core to be safe (although it should be fine to upgrade on top of them), install the newest versions, delete the Armory database folder, and sync Core before running Armory again.

[Armory non geek]

Uninstall Armory and Core to be safe (although it should be fine to upgrade on top of them), install the newest versions, delete the Armory database folder, and sync Core before running Armory again.

Thank you for the excellent information and sequences re updating the Win 7 x 64 computer.

BC Core 0.15.1 updated the prior Core 0.13.xx database to the most recent format.
(I appreciated the time savings of Not reloading it).  0.15.1 sync'd perfectly. 

Per your suggestion I did delete the prior Armory database folder before installing Armory 0.96.3992.
Next closed the core 0.15.1 database program.  Then installed 0.96.3992 

Armory 0.96.3992 fully sync'd to 0.15.1 on the Win 7 x 64 computer. 

Thank you for the excellent suggestions. 

---

Now doing the same processes as above with the computer on which Armory 0.96.0.4 and Core Database 0.14.2 had been installed in July 2017.   

Armory 0.96.3992 is presently sync'ing to the updated 0.15.1 Core database on the 3rd computer.