I'll do my best to clarify here:

I have not been able to see the address once the wallet is loaded. Only place I've seen the address is in the line error stated before. The restored wallet that produced the error with the address in questions shows zero transaction history or balance. 

The logs for the currently operational restored wallet and core are pasted here: (let me know if I'm missing any)

ArmoryLog = https://pastebin.com/Pjiqj68G


Armorycpplog = https[Suspicious link removed] txt file = https://pastebin.com/j0ffFe1L


ArmorySettings = https://pastebin.com/YJj0rMGm


dbLog = https://pastebin.com/DwPz0t1T


bitcoin_debug = https://pastebin.com/sRh6hDEg


I can take screenshots of the ArmoryQT and BitcoinQT to show that they are running / online / fully sync - just need instructions on how to provide those if that is needed.


Apologies for any miscommunications / understanding just trying to retrieve the history for the address that showed up in the reported line error (that error doesn't appear anymore now with the sync wallet). 

 

Yes.  I was actually reconciling my crypto against the exchanges I use and this one address reconciled out to having a balance.  All the other addresses and amounts have been accounted for either through the explorer and the exchange or the explorer and the mining pool.

I was able to pre-determine it was my Armory wallet address due to the dates.  Upon installing newest versions of Armory and Bitcoin Core I had some difficulties with my drive resources so I changed locations of the databases to my F then G drives.  It was during that trial and error process that I came across the address, I had been looking for, in my log file with the error AsciiSerialize.pyc:74 - Expected str....  Once I was able to spin up both databases and sync I was optimistic all of the transactions for that address would be present and the balance would match what I derived from the explorer and exchange transactions.

That's when I discovered that the restored wallet had no transactions displayed.  I tried redoing my setup process with Bitcoin Core and Armory a few times then decided to seek help here.

 I'm obviously connecting dots in my head that I still have the correct wallet restore and seeing that one off error with the address I was searching for displayed.  Is it possible that the scanning process missed some blocks?  Although it probably doesn't matter if I'm unable to see the address within the wallet itself or does any part of the scanning or recreation have the probability to not load all the correct address from the past?.

Thank for the insight.

The logs from that day do indeed show the issues I was having with moving the Armory and Bitcoin data to a non C drive location.  I was able to correct all those issues and get the Bitcoin Core and Armory DB to load and sync (I did use the shell prompt from the ArmoryDB file location) and when starting ArmoryQT everything loads up and shows Online and the current block sync at the bottom right corner.  I'm able to look at the transactions tab and addresses in the wallet. 

I guess my true dilemma is that in doing the initial troubleshooting to have Bitcoin Core and Armory sync I came across that error that stated "the bitcoin address that I used in transferring funds to Coinbase" in 2014.  Which gave me comfort in that knowing I only used Armory during that period and the wallet should still have a balance to which when I get everything loaded doesn't show anything.  I believe its 6 transactions that should be present in the wallet - I'd have to double check if that info would help.

Any further guidance would be greatly appreciated.

Hi goatpig :

1) This error isn't related, this would happen when trying to sign for a lockbox (multisig) - ok. I didn't remember a lockbox feature in the original wallet version I was running, so I'm sure I clicked this during the troubleshooting.

2) How are you restoring this wallet? What's the source? How many addresses are in it?

I used my paper backup - was able to get everything fully sync and operational (after a few tries)  but wasn't able to see any transactional history.  I know this backup was the account used as I can find my complete history on the blockchain for the address.  It has a ton of unused addressed listed and I check each one of those over a week period and none of them are on the blockchain - which I would agreed as I only used the one address. 

3) Need to see the full logs. I posted the log here -> https://pastebin.com/XJyeQUWk [I took out a few hundred lines of scanning at the start.]


Additional notes:  Noting that the lockbox multisig you mentioned provided the error that contained the address I was previously using - is it then possible that my file / backup is corrupt?  Seeing the address just in my mind validated that I'm using the correct Armory file.

I've used the workaround to get my Armory Online and Fully sync.  I had a vey old version of Armory which would not load.  Downloaded v. 96.5 and Bitcoin Core v. 20.1

1) Installed both programs.
2) Started Bitcoin Core and let sync
3) Used shell command to run ArmoryDB and it fully sync with no major errors
4) Started ArmoryQT - it did the normal start up prompts and asked to create or import wallet
5) Entered my paper backup info
6) ArmoryQT loaded and sync, shows last and accurate Block found in bottom right, however no transactions are found in history
7) upon looking at "armorylog" file under roaming location I see my wallet address in an  Error Line:
(INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode
(ERROR) -- ArmoryUtils.pyc:1442 - Attempting to unserialize something not an ASCII block
(ERROR) -- AsciiSerialize.pyc:74 - Expected str "TXSIGCOLLECT", got "1F...(aka my address)...F9"
(ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 13320, in SRD
TypeError: unsupported operand type(s) for %: 'QString' and 'int'

Rebuilt Bitcoin Core twice and ArmoryDB three times to no avail.  Any idea why my restored wallet isn't fully loading my address and transaction history? Does this have anything to do with original wallet was deployed in an online and offline pc config?