The armory finished everything but would never connect to the node. So, I exited Armory, waited for a few minutes for Bitcoin Core to shut down, then started up Armory without checking the Task Manager (very wrong move!) - and nothing really worked.
I had to quit Armory, kill everything that was left in the Task Manager (so from now on I have to keep a close eye on the Task Manager), and after starting Armory again, I was able to import my Watch-Only wallets, which in turn scanned addresses.
Just transferred some BTC into my wallet, everything looks great so far.
Topic: Watch-Only wallets (Read 86 times)
It looks that I got it to finally work. At some point I noticed ArmoryDB sitting in Task Manager, but I looked there before and it wasn't there, weird.
That happens to me most of the time.After closing Armory-qt, there's always a lingering process of ArmoryDB.exe left in the Task Manager.
It looks that I got it to finally work. At some point I noticed ArmoryDB sitting in Task Manager, but I looked there before and it wasn't there, weird.
It is building Databases currently. Bitcoin Core was connected, but then it got disconnected (I received a notification).
My understanding is that it will Initialize Bitcoin Engine after it's done with building DB.
After that It will scan Transaction History, after which Bitcoin Core will be reconnected, and I will be able to import my Watch-Only wallets.
It is building Databases currently. Bitcoin Core was connected, but then it got disconnected (I received a notification).
My understanding is that it will Initialize Bitcoin Engine after it's done with building DB.
After that It will scan Transaction History, after which Bitcoin Core will be reconnected, and I will be able to import my Watch-Only wallets.
After I upgraded, the log file was filling up like crazy, something was way off.
I went ahead and uninstalled Armory and removed everything.
Reinstalled it into c:\Program Files\Armory folder. Added all the paths in the settings, but it still tries to look for the node in a default folder.
And my ArmorySettings file has this content:
I went ahead and uninstalled Armory and removed everything.
Reinstalled it into c:\Program Files\Armory folder. Added all the paths in the settings, but it still tries to look for the node in a default folder.
Code:
2021-12-04 15:50:34 (INFO) -- ArmoryUtils.pyc:1720 - C++ block utilities loaded successfully
2021-12-04 15:50:34 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\Val\AppData\Roaming\Armory\ArmorySettings.txt
2021-12-04 15:50:34 (ERROR) -- ArmoryUtils.pyc:3735 - Unsupported language specified. Defaulting to English (en)
2021-12-04 15:50:34 (INFO) -- ArmoryUtils.pyc:3738 - Using Language: en
2021-12-04 15:50:34 (INFO) -- BDM.pyc:353 - Using the asynchronous/multi-threaded BlockDataManager.
2021-12-04 15:50:34 (INFO) -- BDM.pyc:354 - Blockchain operations will happen in the background.
2021-12-04 15:50:34 (INFO) -- BDM.pyc:355 - Devs: check TheBDM.getState() before asking for data.
2021-12-04 15:50:34 (INFO) -- BDM.pyc:356 - Registering addresses during rescans will queue them for
2021-12-04 15:50:34 (INFO) -- BDM.pyc:357 - inclusion after the current scan is completed.
2021-12-04 15:50:36 (INFO) -- ArmoryUtils.pyc:3578 - Using settings file: C:\Users\Val\AppData\Roaming\Armory\ArmorySettings.txt
2021-12-04 15:50:36 (INFO) -- ArmoryQt.py:2060 - loadWalletsAndSettings
2021-12-04 15:50:36 (INFO) -- ArmoryQt.py:2120 - Loading wallets...
2021-12-04 15:50:36 (INFO) -- ArmoryQt.py:2185 - Number of wallets read in: 0
2021-12-04 15:50:36 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2021-12-04 15:50:38 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2021-12-04 15:50:38 (INFO) -- ArmoryQt.py:1463 - Armory already registered for current user. Done!
2021-12-04 15:50:38 (INFO) -- ArmoryQt.py:566 - Usermode: Advanced
2021-12-04 15:50:38 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2021-12-04 15:50:38 (INFO) -- ArmoryQt.py:1699 - From: Advanced
2021-12-04 15:50:38 (INFO) -- ArmoryQt.py:1707 - To: Advanced
2021-12-04 15:50:38 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2021-12-04 15:50:38 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2021-12-04 15:50:38 (INFO) -- ArmoryQt.py:1891 - Setting satoshi datadir = G:\Bitcoin
2021-12-04 15:50:38 (INFO) -- SDM.pyc:171 - Found bitcoind in the following places:
2021-12-04 15:50:38 (INFO) -- SDM.pyc:173 - E:\Program Files\Bitcoin\daemon\bitcoind.exe
2021-12-04 15:50:38 (INFO) -- SDM.pyc:175 - Using: E:\Program Files\Bitcoin\daemon\bitcoind.exe
2021-12-04 15:50:38 (INFO) -- SDM.pyc:340 - Called startBitcoind
2021-12-04 15:50:38 (WARNING) -- SDM.pyc:445 - Spawning bitcoind with command: E:\Program Files\Bitcoin\daemon\bitcoind.exe -datadir=G:\Bitcoin
2021-12-04 15:50:38 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: [u'E:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', '-datadir=G:\\Bitcoin']
2021-12-04 15:50:38 (INFO) -- SDM.pyc:451 - PID of bitcoind: 12168
2021-12-04 15:50:38 (INFO) -- SDM.pyc:452 - PID of armory: 23556
2021-12-04 15:50:38 (INFO) -- ArmoryUtils.pyc:689 - Executing popen: ['C:\\Program Files\\Armory\\guardian.exe', '23556', '12168']
2021-12-04 15:50:38 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2021-12-04 15:50:38 (ERROR) -- BDM.pyc:197 - DB error: C:\Users\Val\AppData\Roaming/Bitcoin/blocks is not a valid path
2021-12-04 15:50:38 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 0
2021-12-04 15:50:38 (INFO) -- ArmoryQt.py:1905 - loadBlockchainIfNecessary
2021-12-04 15:50:38 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
2021-12-04 15:50:38 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
And my ArmorySettings file has this content:
Code:
Default_FeeByte | 200
ManageSatoshi | True
AdjustFee | True
MainWalletCols | xxxxxxxx removed xxxxxxxxxx
MainGeometry | xxxxxxxx removed xxxxxxxxxx
LastDirectory | C:\Users\Val\AppData\Roaming\Armory\
Agreed_to_EULA | True
NotifyBtcIn | True
FeeOption | Auto
DNAA_UnlockTimeout | False
AlwaysArmoryURI | False
NotifyDiscon | True
NotifyIgnore |
DNAA_IntroDialog | False
SatoshiDatadir | G:\Bitcoin
DateFormat | 25592d25622d25642025493a254d2570
Default_FeeByte_BlocksToConfirm | 3
Default_ReceiveType | P2PKH
AdvFeature_UseCt | 0
UnlockTimeout | 10
Default_Fee | 20000
LastFilterState | 0
MinimizeOrClose | Minimize
User_Mode | Advanced
Load_Count | 2
First_Load_Date | 1638654323
NotifyBtcOut | True
MinimizeOnOpen | False
First_Load | False
Default_ChangeType | P2PKH
IgnoreAlerts |
DNAA_DeleteLevelDB | False
NotifyReconn | True
SatoshiExe | E:\Program Files\Bitcoin
DNAA_DefaultApp | False
LastVersionLoad | v0.96.5
Wow, thank you, hosseinimr93! I was wondering why do I see v0.96-beta-a3d01aa722 on my installations. I was completely sure that I downloaded v0.96.5 installation from the website. It looks that I downloaded it off of https://www.bitcoinarmory.com/download/ and it was v0.96 instead.
Do I just close Armory and run the setup file in-place? Do I need to remove/rebuild database files, or are they all completely compatible between v0.96 and v0.96.5?
Thanks again for pointing me to right version!
Do I just close Armory and run the setup file in-place? Do I need to remove/rebuild database files, or are they all completely compatible between v0.96 and v0.96.5?
Thanks again for pointing me to right version!
You should empty the "databases" folder before running 0.96.5. You can install 0.96.5 over 0.96, it will replace the older binary. Wallet and databases data will be left untouched.
Wow, thank you, hosseinimr93! I was wondering why do I see v0.96-beta-a3d01aa722 on my installations. I was completely sure that I downloaded v0.96.5 installation from the website. It looks that I downloaded it off of https://www.bitcoinarmory.com/download/ and it was v0.96 instead.
Do I just close Armory and run the setup file in-place? Do I need to remove/rebuild database files, or are they all completely compatible between v0.96 and v0.96.5?
Thanks again for pointing me to right version!
Do I just close Armory and run the setup file in-place? Do I need to remove/rebuild database files, or are they all completely compatible between v0.96 and v0.96.5?
Thanks again for pointing me to right version!
What is the version of Armory you are using for your watch-only wallet?
I think everything should be fine if you use the latest version of Armory which is 0.96.5.
In the case you are not using the latest version of Armory, download it from the official website.
I think everything should be fine if you use the latest version of Armory which is 0.96.5.
In the case you are not using the latest version of Armory, download it from the official website.
I am unable to use watch-only wallets to generate receiving addresses. Every time I click on the "Receive Bitcoins" button, select a watch-only wallet, and click the "OK" button (Error #1), I get the "Loading..." window with progress bar showing 0% (it sits there forever until I click on "X" to close it).
If I go into the "Wallet Properties" window and click on the "Receive Bitcoins" link/button (Error #2), it does not respond at all.
The following error messages get logged in the armorylog.txt file.
Error #1:
Error #2:
I created a full test wallet, it loads the "New Receiving Address" window with no issues.
It's a two-system setup on Windows 10 OS.
Thank you.
If I go into the "Wallet Properties" window and click on the "Receive Bitcoins" link/button (Error #2), it does not respond at all.
The following error messages get logged in the armorylog.txt file.
Error #1:
Code:
2021-12-04 13:42 (ERROR) -- Traceback (most recent call last):
File "ArmoryQt.py", line 3490, in clickReceiveCoins
File "qtdialogs.pyc", line 2062, in showRecvCoinsWarningIfNecessary
AttributeError: 'ArmoryMainWindow' object has no attribute 'Warning'
Error #2:
Code:
2021-12-04 13:43 (ERROR) -- Traceback (most recent call last):
File "qtdialogs.pyc", line 1541, in getNewAddress
File "qtdialogs.pyc", line 2062, in showRecvCoinsWarningIfNecessary
AttributeError: 'DlgWalletDetails' object has no attribute 'Warning'
I created a full test wallet, it loads the "New Receiving Address" window with no issues.
It's a two-system setup on Windows 10 OS.
Thank you.
Jump to: