It should be possible to broadcast the transaction to the network from within armory. How is this done?

I'm still syncing headers. It's been quite a process. The indications are that there were issues with the path after the upgrades to bitcoin core 0.20.1 and armory 0.96.5. that shouldn't matter, though.

I don't know how to identify a RAW transaction. Is it in HEX, or can it include other characters?

The characters in the file are not all HEX numbers. I can't say that I have a sent transaction in RAW HEX format. Can somebody tell me what it is? the characters include upper and lower case letters from throughout the alphabet.


https://bitcointalk.org/index.php?topic=245910.msg2607452#msg2607452
There are posts from 2013 and 2014. Is there a more current update?

I have a file that I intended to send to the network. My bitcoin core was not synced at the time when I attempted it. The file format is not in a standard HEX format. How can I broadcast it to the network using the Armory SENT file?

Does anyone have an idea as to where to go from here? It looks like everyone else has dropped off this thread.

Install bitcoin core 0.21.0 and then reinstall the .exe version of armory 0_96_5? Install the armory to the C:\...\appdata\roaming\armory directory? Last time, I probably installed to the d:\ drive.

Bitcoin core is not running anymore. I can launch the splash page that checks wallet consistency. Then it says done loading
Bitcoin core never opens up and syncs. I tried running Bitcoin Core and Armory as administrator. I don't know what could have happened.

The owner is 'enduser' - it's the only login that is being used on this system. I will see if I can run armory as administrator when the time comes. Maybe my armory 0_96_5 installation is still misconfigured? There are no current files in the \appdata\roaming\armory directory. There are only files from 0.96.3. It looks as if the 0_96_5 are all in the d:\armory 0_96_5 directory.

How much simpler and easier would it be to reinstall everything on a new system and restore the wallet for watching only?

I am currently syncing up bitcoin core. Would it be typical to start bitcoin core using the bitcoin-qt executable?

I found an armory settings file with no appropriate data directory setting. It's in d:\btc

https://pastebin.com/yJPGf3e4

Maybe this will help to show where the path is being misdirected. Since the upgrades to bitcoin core 0.20.1 and Armory 0.96.5 this watching wallet installation has been offline and does not scan databases.

https://pastebin.com/5C5zQ3fh

Please let me know if anyone can see a configuration tweak that will get armory running again. Will it be necessary to upgrade bitcoin core from 0.20.1 to 0.21.0?

I have at least two versions of bitcoin-qt installed. The one that I have been launching is on the d: drive. I'll shut down and then try the one in the path you indicated on the c: drive.

bitcoin-qt on the c: drive launches 0.14.2
the version on the d: drive - d:\bitcoin\bitcoin-qt launches 0.20.1

I  am trying to import a .jpg of the d:\ listing

How does that work on this blog?

There are a number of related directories on the d:\ drive.

https://pastebin.com/WkZWvTbw
https://pastebin.com/pg7m0tZP

current logs

OK, I am waiting for further direction.

My configuration is exactly like the one you posted. i have repeatedly closed down armory and bitcoin core and restarted the PC. I checked for the armory.conf file in the appdata\roaming\Armlory subdirectory on the C: drive. There is no file by that name, but there is an ArmorySettings with the value for SatoshiDatadir set appropriately.

Confirmed. Both bitcoin core and armory are set for d:\btc datadir 96-2
Neither has the backslash after the name of the directory, btc datadir 96-2

Could that be a factor? It looks as if the system using the default path.

Yes, I did that in Armory. I used the GUI. will have to verify the setting for bitcoin core later on.

I have completed all the steps listed. It looks like armory should be back online and scanning databases, but it's not.

https://pastebin.com/35QvGKmt

https://pastebin.com/qsp4Jbrz

I have noticed the armory process still running in Windows. I have started to kill that using task manager prior to launching armory. This message has come up a few times after stopping and then restarting bitcoin core.
Cannot obtain a lock on d:\BTC datadir 96-2 - bitcoin core directory. Bitcoin core is probably already running.

Could that be related to the armory process that has been running after exiting armory?

I used the first line command to launch armory when the posted log files were produced. I have tried the second one, too. I can't shake the thought that the executable might be tryiing to access the wrong datadir. The bitcoin core database files are definitely active in d:\btc datadir 96-2\blocks

D:/armory 0_96_5/armory_0.96.5_win64/ArmoryStandalone/armoryqt -- datadir=d:\armory 0.96.3.992\Armory
D:/armory 0_96_5/armory_0.96.5_win64/ArmoryStandalone/armoryqt -- datadir=d:\btc datadir 96-2\Armory

Tried running the 'scan armory databases' from the help menu in armory. Armory is still offline, and is not coming up beyond the scanning transaction history utility in the lower right on startup.

https://pastebin.com/NxzspU0s

https://pastebin.com/exmFXEyR

I downloaded this version of the .zip file and extracted it at the root level of an external drive.
armory_0.96.5_win64
When  the extract had completed, there was an Armorystandalone directory in the path. Is that the way is should be?
Maybe I should be using the win64 installer instead of downloading the .zip file?
Armory is offline, according to a message in the lower right of the dashboard.
Added server=1 to bitcoin.conf

The armorylog.txt starts with entries from 2017, so I cleared it out. Syncing bitcoin core so that I can restart armory. I will post the armorylog.txt later on.
This might be an old version of dblog:

https://pastebin.com/xLRHewqk

It was bitcoin core 0.20.1

I downloaded and extracted the indicated version of armory. The executable runs and lists the right version - 0.96.5
Transactions do not appear, and I still have a 0 balance. Shouldn't my BTC have been restored to the wallet? I can't see any difference after the upgrade. The armory log file is also identical to the one before the upgrade.
In terms of where I would like to go from here: ideally, I would see the BTC in the wallet again, and then I would generate another transaction. This time, the transaction would be broadcast to the network.

The signed transaction file is a .SENT.tx and begins with a delimiter and this, like a header TXSIGCOLLECT

It has a mixture of upper and lower case letters; alphanumeric chars. HEX has a mixture of counting numbers and upper case letters, 0 through F -- right?

I am running armory 0.96.3.992-beta-8a 7f18a499
qt version 5.9.8
armory offline 0.92.3

I was not running these versions when issues first came up. I attempted to send my BTC. I have a signed transaction that was never broadcast to the network. At that point, bitcoin-qt was out of sync, preventing the transaction from being broadcast, the way it looks. My previous posts have indicated the issues that were encountered getting past that. I have rebuilt the bitcoin database. I have an empty qt wallet and listed, but apparently inactive (grayed-out) wallets for primary and watching wallet on my online system. The balances are (...) on each wallet.
I still have the signed transaction on a usb drive. Where do I go from here? It's probably really easy... I hope.

In armory, 'preparing databases' and 'scanning transaction history' are not active at all - they are grayed out. The wallet consistency check runs successfully in the lower left on armory startup.

I have my armory log file. Is it possible that my Satoshi data dir is pointing to the wrong folder? I must have installed the upgrade into a new folder on the external drive.