Quote from: imnotarobot on September 03, 2016, 09:47:00 PM

Okay...

i had an issue with the walletpassphase. no matter what i did, i kept getting an error. so i thought maybe it doesn't like the spaces in my current passphrase, so that gave me pause to think that if it didn't like it in the concole, would i even be able to change the passphrase as it needed to be entered to change it. i changed it with no worries. then went back to the console and it worked, so perhaps it was that it did not like the spaces.

No, the console will not like spaces. Each parameter is space separated, so it will think whatever you type is is multiple parameters. Rather what you should have done is put quotes (") around your password. That should have fixed the problem.

Quote from: imnotarobot on September 03, 2016, 09:53:00 PM

quick update.

this appears to have worked.

the initial transaction now has an 'x' (which when hovered over with the cursor says conflicted) in the 'transaction status' box instead of the'?' that previously existed. now there is a new transaction with a 'clock' in the 'transaction status' box with it already having 1 confirmation.

Yes. That X means that transaction is conflicted (by your second one). The thing is, it will remain there, so if you want it gone, you will need to use -zapwallettxs