Gary,
Has the bank changed any of their security settings recently? Maybe
Thomas will see something in the log that I missed, but there doesn't
seem to be much to go on.
I might be tempted to unmap the account and try remapping it. That
might leave you unable to remap - but I suppose that's no worse than
not being able to download. It might possible give you a different
error which might help track down the underlying problem.
Jack
On 2016.07.30 12:52, Gary Harmon wrote:
Hi Thomas.
I reproduced the problem following your instructions. The ofxlog.txt
file
is attached. The only values I modified were:
USERID -> userid
USERPASS -> userpass
ACCTID -> acctid
Please let me know if there is anything else I can do to help.
Thanks.
Gary
-----Original Message-----
From: Thomas Baumgart [mailto:t...@net-bembel.de]
Sent: Saturday, July 30, 2016 1:22 AM
To: Gary Harmon <harmo...@sbcglobal.net>
Cc: kmymoney-devel@kde.org
Subject: Re: General Error (Code 2000)
Hi Gary,
On Friday 29 July 2016 14:06:32 Gary Harmon wrote:
> Hi Thomas.
>
> I tried with 4.8.0 and the problem remains (attached snapshot). As
> with
> 4.7.2 the other accounts will update as expected.
>
> Can you provide diagnostic instructions for me? I'll be happy to
give
> that a try.
Create an empty file named "ofxlog.txt" under "C:/Documents and
Settings/Username" where you replace 'Username' with your login name.
As soon as it exists, KMyMoney logs the OFX activity (requests and
responses) to it. Beware that it contains your user credentials and
other
account information in clear text, so don't send that file over a
network
(at least not without replacing any sensible information).
To stop recording simply remove this file (it's a good idea to
actually wipe
it with 0 data or something like that also).
Hope that helps.
> -----Original Message-----
> From: Gary Harmon [mailto:harmo...@sbcglobal.net]
> Sent: Monday, July 25, 2016 7:53 PM
> To: Thomas Baumgart <t...@net-bembel.de>
> Cc: kmymoney-devel@kde.org
> Subject: Re: General Error (Code 2000)
>
> My apologies, Thomas, that was an oversight on my part: 4.7.2 on
> Windows is right.
>
> I'm currently out of town but will try 4.8.0 when I can and let you
> know the results.
>
> Thank you for your help.
>
> Gary
>
> Sent from my iPhone
>
> > On Jul 23, 2016, at 11:59 PM, Thomas Baumgart <t...@net-bembel.de>
wrote:
> >
> > Gary,
> >
> > unfortunately, you did not mention the version of KMyMoney you're
using.
> > Assuming from the screen layout and the fact that you are using it
> > over a year, I end up with 4.7.2 on MS-Windows.
> >
> > Can you try to upgrade to 4.8.0 and see if the problem goes away
or
>
> remains?
>
> > Check https://kmymoney.org for the latest version. Make sure you
can
> > fallback to your previous version just in case something goes
wrong
> > (which I don't expect, but I am not a windows expert and have not
> > built
>
> the package).
>
> > If that does not help, we need to dive into diagnosing the problem
> > on the protocol level. Please get back to us here on the list and
I
> > will try to give you instructions on how to do that.
> >
> > Regards
> >
> > Thomas
> >
> >> On Saturday 23 July 2016 08:42:26 Gary Harmon wrote:
> >>
> >> I've been using KMyMoney for over a year now and have had a good
> >> experience with it. Just a few days ago I started getting a
> >> failure when updating a specific account (see attached). All was
> >> well with updating this account until recently.
> >>
> >>
> >>
> >> Any thoughts? Suggestions on how to diagnose? The financial
> >> institution passed it off as a KMyMoney issue (which they "don't
> support").
