Yes, it is the simple paper back-up.
I have been searching extensively for any possible record of addresses, but have not had any luck so far. Many of the exchanges/accounts that I had used in 2013/2014 no longer exist, so it is much harder to cross reference.

Soooooo...

I finally got it working after all of the above steps and troubleshooting, another armory reinstall, and then an armory database rebuild/rescan.
All told this represented several weeks of troubleshooting...

...The wallet appears empty. The transaction list is empty.

Since 2014 I have meticulously been maintaining an empty paper wallet. Confusing. Perplexing. Stressful.

There really should only be one transaction (receiving) but I don't see anything. I have rescanned the transactions and nothing.

I'm really at a total loss.

Thanks @HCP and @goatpig for all of your help.

I have posted my most recent logs for review:

dbLog: https://pastebin.com/H1b3iDtp
The top section is me opening ArmoryDB manually and it seems to show that it is reading blocks but not seeing any addresses.
The bottom section is be restarting Armory application itself and it gets to registering addresses and gets stuck.

Armorylog: https://pastebin.com/7WpHcCq0
There seems to be a new WARNING re: Spawning the DB that I am seeing recently but no specific new errors I can see.

The UI itself just shows that it is stuck on "Build Databases" with "Scanning Transaction History" blank with no progress.

Thanks HCP. I actually am already halfway done that process! Over this past week I went ahead and created a virtual Windows 10 machine as I kept running into roadbloacks on MacOS. I found that the Windows 10 VM was running into similar issues and it made me think that perhaps the block data was the problem. I have reindexed/downloaded everything and I'm now back on the Building Databases in Armory step and it seemed to at least initially go much faster. I'm currently on "Starting address registration process" as the last line in by dbLog and it has been staying there for some time now - this is a new line that I did not previously see in any of my past logs. Currently in Activity Monitor I only see the Armory Bitcoin Client (taking minimal resources) and ArmoryDB is notably absent. I have tried to shut things down, restart, and manually start ArmoryDB, etc. and the same thing happens - Builds the database MUCH faster than in the past, but then sits at "Starting address registration process."

Some updates:
I ended up reinstalling Armory and did NOT restore my wallet out of the gate. I was able to get Armory up and runny to the point it said it was online and up to date with blocks. I then attempted to restore my wallet from there and it immediately hung while 'mirroring' the wallet. There was nothing in the dblog or armorylog - it just hung with "Armory is not responding" in the activity monitor. When I restarted it, it seemed to be able to access multiple cores (~300% processor use) and was initially building the database much quicker than previous, but then it dropped down suddenly after about 5 minutes to the same 99% of one core and took several hours to build from there. Nothing showing up in the error logs outside of the type of lines I have posted above. When it finally finished building the database it then stuck on Scanning Transactions and made no progress and no entries in the logs for the last ~12 hours. Any additional thoughts?

It says "Parsing Tx Hashes", and in the bottom right corner says "Connected (0 blocks)"

Thank you for your ongoing help with this, I appreciate it.

As a follow-up I shutdown Armory and ArmoryDB, and manually opened ArmoryDB and Armory again from there.
I am now back to "running 100 zc parser threads" but it only took about 6 hours this time instead of multiple days.

No, nothing is being added at this point.
It has stalled at "running 100 zc parser threads".

Yes, it seems to be running incredibly slow. I have let it run for the last couple of days and it does seem to be progressing, but at a glacial pace. The last entry on the log is now "running 100 zc parser threads" but nothing after that for the last 24 hours. The computer is a 3.8Ghz Quad Core i5 with 32GB of ram, so I would imagine it should be more than fine to run Armory.

I have imported all of the "unused" addresses listed in the back-up into Electrum and there are no visible transactions. This would have been the only wallet I used on Armory, as I sent BTC to it specifically for its paper wallet function.

Thank you for your response bob123.

I purposefully waited a bit longer to reply, as I had seen some other user reports that the step I was stuck on just took extra time.
As such I gave it a couple of extra days, and the ArmoryDB continues to be at 99% of one of my cores, and has progressed to "Parsing Tx Hashes" but has been stuck there for days now.

The log is pasted here:
https://pastebin.com/jDqwppm4

At this point, I have decided to transition to a different wallet. I have previously attempted to export my private keys, but the process included 100 'unused' addresses after restoring my wallet. I checked many of the initial addresses and they were empty.

Thanks for your help.

Hello everyone,

I have been attempting to troubleshoot my current setup for the last few days/weeks. I was previously on an earlier Armory build as I couldn't get 0.96.5 to work, but ultimately was able to followed droark's suggestions in other posts and am now running 0.96.5.


Where things are at currently:

I restored a back-up paper wallet, and when I start up Armory, it will take a few hours to build and "Organize Blockchain". The bar will be full blue, the spinning green/grey wheel will freeze, and then nothing will happen. The lower right of the Armory window is green, says Connected (0 blocks).
BitcoinCore is running and is fully synced.

Looking at the logs, I don't see any specific errors at present.
There are hundreds of Scanning mode lines and hundreds of parsed block lines.

The last few lines of the log are:
-INFO  - 14:43:06: (DatabaseBuilder.cpp:281) parsed block file #2445
-INFO  - 14:43:51: (Blockchain.cpp:248) Organizing chain
-INFO  - 18:20:45: (Blockchain.cpp:370) Organized chain in 13013s
-INFO  - 18:20:48: (DatabaseBuilder.cpp:76) updated HEADERS db in 19858s
-INFO  - 18:20:48: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 18:20:48: (DatabaseBuilder.cpp:1231) verifying txfilters integrity
-INFO  - 18:20:49: (DatabaseBuilder.cpp:1314) done checking txfilters
-INFO  - 18:20:49: (BDM_supportClasses.cpp:1891) Enabling zero-conf tracking

Then it just sits there. Each time I restart Armory, it takes hours to get to the same point with no change beyond this.
Looking at Activity Monitor, ArmoryDB is running ~99% on one of my computer's cores.

Since the transactions don't scan/complete, I am unable to send anything from the wallet.

Any assistance would be greatly appreciated. Thank you.