I have tried to add several different accounts with a couple of banks to KMyMoney. With aqbanking I have successfully connected, but I am unable to get anything besides the following errors in KMyMoney. These errors happen every time, first the #2000 error, then the #15500 error. ERROR #2000 General error: "Error other than those specified by the remaining error codes. (Note: Servers should provide a more specific error whenever possible. Error code 2000 should be reserved for cases in which a more specific code is not available.)" Server message: Not Authorized ERROR #15500 Signon invalid: "The user cannot signon because he or she entered an invalid user ID or password." Reproducible: Always Steps to Reproduce: 1. Enter the "Map to Online Account" wizard for KMyMoney OFX 2. Select a bank (In my case America First Credit Union) 3. Enter username/password 4. Identify as "Quicken Windows 2008" and Header version "102". 5. Select next and see the errors occur. Actual Results: Got two error messages, a #2000 and a #15500 Expected Results: It allows me to select one of the accounts the OFX supplier returns.
My guess is that this is not an error with etiher KMM or libOFX, but a configuration issue with the bank(s). I have had problems with the initial configuration of almost all of my OFX connections, and all were eventually resolved by correcting little issues with various configuration details. The best way to start would be to check all the configuration details that aqbanking uses, and then see the OFX connection is using exactly the same information.
Could you try Jack's suggestions and report back?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!