Now I see my mistake here. Thank you very much for helping me out. In Monero I didn't had to use this because I've always used the same wallet files on the same PCs offline/online. So I basically never had to recover my wallet files and thus there where no expenses my online copy didn't know about.
I really appreciate your help! There should be more guides on the Monero/MoneroV homepages regarding this, though.

But a view-only (watching-only) wallet should be able to monitor all incoming and outgoing transactions, right? otherwise it isn't possible to create/broadcast a transaction if the unspent UTXOs can't be determined.

I did the following to (try) claim(-ing) my unspent XMV which are stored at an offline workstation:
1) Recover my wallet at the offline device with my seed in "monerov-wallet-gui.exe".
2) Go to "Settings" and "Export watching-only copy".
3) Transfered my watching-only copy onto a USB stick.
4) Opend my watching-only copy of my wallet at an online workstation.
5) "monerov-wallet-gui.exe" scanned my wallet and only found all incoming tx and not a single outgoing one.

The summary is that I can't spend any of my funds because "monerov-wallet-gui.exe" just completely ignors my past outgoing tx. I can create an  unsigned tx and sign it on my offline PC, but I can't broadcast it because some of my incoming tx were already spent (that's the error message I get when doing so). So my actual balance is false to because my spendings aren't recorded. The wallet acts like if I haven't spent anything, only the coins I have received are recognized.

Although my hot-wallets work perfectly fine (all of them). I can't explain why that happens, because I did this 100 times in Monero the same way I did it in MoneroV. So it's not the first time I use offline walets.

There is an issue with the GUI/CLI wallet clients regarding view-only wallets. After the scanning process of a view-only wallet there are all previous incoming tx displayed/found, but not a single outgoing tx! This happens only with view-only wallets. Any solutions please?

I think this issue is caused by the fact that view-only wallets have no secret spend key, although they have the public one. But somehow the software doesn't check every spent output if there is no secret spend key as well. Is there any fix in sight?

I've used McAfee AV some time ago. Previously everything worked pretty well, but all in a sudden I've gotten corrupted files and crashes of ArmoryDB. I also tried to set folder exemptions, but it didn't really prevent these errors from happening. So I've tried to deinstall my AV and gotten rid of all of my AV services (except Win Defender) and then it worked like it should.
But I have to admit it was hard to drop something that's already paid in order to get Armory running. So I can't tell if that might solve your issue, but again it looks pretty similar to mine.

I've found an error regarding tx preview. I have sent some tx multiple times by using RBF and CPFP via Armory and cleared all unconfirmed tx also multiple times, which could have messed up Armory's indices.

armorylog.txt

Could this be a damaged wallet file or is it "just" a tx index that's not working. I'm currently doing a rebuild and rescan.

Kind regards :-)

Your issue reminds me on mine serveral months ago. Are you using any Anti-Virus software, NAS or encrypted HDD?

The "MAX" button functionality is broken. It can calculate the exact amount but it is not possible to spend any coins.

armorylog.txt

I've seen the same error code from another user on this topic. Actually when downgrading to 0.96.3 "MAX" button is working and I'm able to spend.

Are there any preparations needed to be done for the upcoming forks?

Because I assume that the Armory specific address type P2SH-P2PK should be avoided in case that Armory doesn't support one of the forks. Or are there any other possibilities to import the private keys of such addresses into any other wallet than Armory?

Kind regards,
Mr.Vice

Ok, thx for the info! It is really no big deal, as long as in english [us] locale everything is working well ;-)

Now I get it!! There were already indices 67-166 pre-generated P2PKH ones ;-)
I've forgotten that Armory always reserves a pool of pre-generated addresses, which are displayed in the unused addresses expander...

You can solve that issue by deleting Armory's database folder in "%APPDATA%/Armory". The reason is that after upgrading your old database can not be used anymore (not backward-compatible). So by deleting that folder after upgrade you will force a rebuild and rescan.

Thx for the info! That would be awesome :-)

Ok, I see. If there is a interface that is capable of unicode, it should cover most of the locales supported by Armory.

I have another question - I know this is off-topic but there are already so many topics opened, that would be like a data package with a header of 90%.
Since I've been using the address book many times - with german locale settings - I think that may have caused an error. Because I've been able to use/generate a P2SH-P2PK address that was 100 indices from my current address count away. Now my question is if every address I will generate in the future will dismiss 100 unused addresses in between?
I accidently transfered some BTC to that address :-/ My address count then jumped to 166 instead 66...

Yes. That's pretty strange. When I'm using german locale settings I can't select addresses via button in the address book, because Armory can't copy it in ASCII character format. As a work-around you can right-klick and copy the address and paste it into the field. When you do this Armory can identify which wallet this address belongs to. So probabbly the clipboard stores non ASCII chars and when you paste them into the text field Armory converts them back into ASCII?

But that work-around doesn't work with Lockboxes. When you create a new one and copy and paste addresses of wallets it says that a unvalid address was entered. Although it identifies the wallet that address is related to.


It was messing with Armory's DB.

The reason why there is no "mempool.dat" in your Bitcoin folder is because your Bitcoin Core version is outdated. Updating it will certainly boost the time required to fully sync. So the first things should be updating both, Bitcoin Core to 0.14.2 and Armory to version 0.96.2.
If your node has problems with connecting to others (you can check it in the debug window), then I recommend to exit core and delete "peers.dat" in your datadir and start it again.

Regarding your capacity issues. If you have an external storage I would recommend to just close Armory or Core and copy your datadir in "%APPDATA%/Bitcoin" completely to your new external HDD. Then go to "%PROGRAMFILES%/Bitcoin" and drag-and-drop "bitcoin-qt.exe" with your right mouse button to your desktop and select "create shortcut". Then right-click on your new shortcut and open properties. In the target line attend at the end of the line " -datadir="F:/YourPath/"". In your path enter the location of your copied blockchain files on your external HDD.
The next step is to open "Armory (Offline)" and go to settings. In the field bitcoin home dir you also have to specify your new datadir path.

When you have done the above start with your desktop shortcut bitcoin core and try if it works. When it does you can delete your old blockchain files on C: and let core fully sync.

In later versions of Armory the green connected label doesn't mean your node is fully synced. It just indicates if Armory is connected to your Bitcoin Core Node, which is running in the background. You can check how much percentages your node is behind by opening "%APPDATA%/Bitcoin/debug.log" and open it in your note pad. Scroll to the buttom and check the lines of "UpdateTip" for the percentage.

It depends on how many blocks your node is behind. But I recommend running Bitcoin Core only instead, until it has fully synced. Afterwards you can exit it and run Armory again.

No problem, you're welcome. ;-)

In order to use SegWit addresse or be able to sign them you have to upgrade both, the online and offline machine to Armory 0.96 or later (latest one is 0.96.2). Additionally you need at least Bitcoin Core 0.13 or later (latest one is 0.14.2) for your online machine.
Older Armory versions won't be able to sign/spent from SegWit tx.

In newer Armory versions 0.96+ you can choose in your settings which address types you would like to use for receiving and change addresses.
There are three address types available after upgrade:
1) "P2PKH": Legacy address type. Fully backwards compatible. (With this one you can still sign from your offline PC without upgrading).
2) "P2SH-P2PK": Compressed P2PKH script. Nested in P2SH output. (This address type can only be signed by Armory 0.96+. But your underlying Bitcoin Node does not have to support SegWit to spend from it. This is usefull if you want to use the Bitcoin Cash blockchain - no SegWit support - and still be able to use a compressed address (lower fees)).
3) "P2SH-P2WPKH": SegWit script. Nested in P2SH output. (This is the new segwit address type. But only wallets that support SegWit will be able to spend from it. So if there will be any fork in the future and the new chain doesn't support SegWit you won't be able to spend from that alt-chain!).

Is it possible to create a MultiSig Lockbox that supports SegWit in Armory 0.96.2?
Because P2SH addresse were originally meant to be lockbox addresses. So they should also support the new segwit script, shouldn't they?
How can I generate a segwit lockbox?

Have you tried the following?

1): Start "ArmoryQt.exe".
2): Go to "Help">"Clear All Unconfirmed".
3): Close "ArmoryQt.exe".
4): Open your file explorer and go to "%APPDATA%/Bitcoin" and delete "mempool.dat".
5): Restart "ArmoryQt.exe" and retry spending your tx.

By the way your tx id is either invalid or not in blockchain.info's mempool anymore. So it is very likely if you follow the stepts above to respend it.
Have you also upgraded your bitcoin core node? The newest version is 0.14.2 and required for the new segwit tx.

This fee is for the current state way too high. Please check https://bitcoinfees.21.co for the current fee. I recommend 60 sat./byte for a confirmation within about one hour.

Please look for further information under this topic: https://bitcointalk.org/index.php?topic=2157913.0

This issue can be tagged as soleved.

Even though I've deinstalled McAfee AV a long time ago this piece of software still hurts my neck. Because I've found out that it isn't enough to just deinstall it. In order to completely remove every "service" that is linked to it, you'll have to download a tool called "MCPR.exe" from the official McAfee website that is able to remove everything that still recides on your PC.

This tool can be found under this link: http://us.mcafee.com/apps/supporttools/mcpr/mcpr.asp

That address book issues also had been related to the german locale settings. When you're using it then you're unable to select addresses (especially when using multisig lockboxes). So after switching to English (us) everything works like it should. That would explain why you haven't encountered any of this issues.