Discover Card problem
Bryan Martin
As of today, Moneydance will not connect with Discover if there is an @ symbol in the password. I went through troubleshooting with the Discover web team technical support and by process of elimination, we discovered this was the culprit. MD was throwing a bad password error. It worked fine until today. Disabling and resetting up online access in MD had no effect. I assume Discover has changed something in their server. I am running version 1242. Thanks!
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by avp2 on Jul 07, 2015 @ 10:00 PM
Same problem for me. Discover's tech help person indicated about 10min ago that there were no reported problems. Removed a period (.) from my password and now it works again.
Periods do still work for website logon. Called back tech support and told them about the situation - so it should be in there support db.
2 Posted by -Kevin N. on Jul 08, 2015 @ 02:03 AM
Hi Bryan, avp2,
As it turns out an equal sign (=) in the password will also throw an error @ Discovercard.
HTH -Kevin N.
Support Staff 3 Posted by Ethan on Jul 08, 2015 @ 12:20 PM
Thanks everyone for pointing this out. This is quite strange for Discover to decide to limit their passwords in this way. I guess we should make sure that people who are having connection problems with Discover are only using letters and numbers in their passwords.
Bryan, I want to confirm that you are completely disabling and re-enabling all affected accounts through the following steps:
1) Open your bank account register by clicking on it in the left sidebar in Moneydance
2) Select Online->Setup Online Banking from the menu bar
3) Click the Disable button. If you don't see a disable button, continue to step 5.
4) Select Online->Setup Online Banking from the menu bar (again)
5) Click the New Connection button and select your bank from the list of available institutions that pops up. Hit OK
6) Continue with the setup process, entering your username/password
7) Repeat steps 1-6 for any additional accounts from this bank
Ethan
Moneydance Support
4 Posted by -Kevin N. on Jul 08, 2015 @ 01:29 PM
Hi Ethan,
Just as an FYI...
The error thrown is very generic and unlike one's I've seen before involving OFX connections in Moneydance. There is no mention of the financial institution involved and no error number given.
"The given customer ID or PIN is not valid. For more information, contact your financial institution.
Additional information from the server:
Signon (for example, user ID or password) invalid."
-Kevin N.
Support Staff 5 Posted by Ethan on Jul 08, 2015 @ 01:40 PM
Hi Kevin,
Thanks for that information. That unfortunately seems very typical with our experience helping people connect with Discover; they usually give out the vaguest error messages out of any bank. I've let our support team know that this may be the issue if many Discover customers start reporting in with errors in the next few days.
Ethan
Moneydance Support
6 Posted by avp2 on Jul 08, 2015 @ 02:02 PM
I forgot to mention that the MD error message did not return an error code for invalid credentials - only the error message. Lack of a code number seemed to draw a red flag "question mark" from the Discover tech person until I gave him the OFX code obtained from the console - 15500.
I think I remember MD showing an error code for bad credentials in previous versions and it did show one (15502 I think) when I later got a lock out from Discover's server from trying to connect too many times. Probably be good if MD showed all error codes to make it easy to report to support people.
7 Posted by oberman on Jul 09, 2015 @ 01:04 PM
I had the same error, for me it's either * or & (I use 1password to randomly generate passwords).
8 Posted by mark.howell on Jul 10, 2015 @ 12:49 PM
I am also getting the error 2000 with Discover as I use special characters in my password which still allows me to connect via a web browser. I changed the password to alpha-numeric and disabled the account in MoneyDance 2014 using the recommended options including using a python script. I setup the online account again and after putting in the password I immediately get the error again.
9 Posted by Ian L on Jul 10, 2015 @ 12:52 PM
Could you try clearing your passwords using the Online->"Forget Online Passwords" menu option? This will remove all passwords from your file, so we prepared to enter them in again for each account.
Also, if you have special characters in your username, you'll need to change that as well. We've gotten a couple reports of special characters in usernames also causing this error.
Ian
Infinite Kind Support
10 Posted by mark.howell on Jul 10, 2015 @ 01:16 PM
Well as it turns out I had to change my User Name also and remove any special characters to use only alpha-numeric and this allowed me to set up the account again. What I don't understand is the fact that I am allowed to use special characters to log into the web site via a browser. How would logging in to the server via a browser be different from logging in with MoneyDance. I know it may be hitting a different server but to not allow special character via a different method does not make sense to me. If this was a change on the Discover side then I will contact them. If it is an issue with MoneyDance getting kicked out because we are using special characters then maybe this requires a little more investigation. My passwords I make very complex and change on a regular basis so not being able to use special characters makes me feel more vulnerable given the current state of affairs with identity theft.
Update: I was able to setup the account again but I still get the server 2000 error when attempting to actual download the transactions
Support Staff 11 Posted by Ethan on Jul 10, 2015 @ 01:37 PM
Hello,
It is unlikely that this is a Moneydance issue. My reasoning for this statement is that we've received reports of this happening only with Discover in the last few days, and from many Discover customers (maybe around 15 so far, although I just answered another a moment ago). No other customers have reported similar issues with their banks, and I find it hard to imagine that only Discover customers are using special characters in their passwords. All of that together seems to me to suggest that this is something that Discover changed on their end with their direct OFX connection server, since we haven't changed anything in Moneydance that would prevent these characters from being used.
Ethan
Moneydance Support
12 Posted by mark.howell on Jul 10, 2015 @ 02:04 PM
I agree that it is more than likely a Discover issue however even after removing special characters from my user name and password and being able to setup the account again after disabling it when I attempt to download the transactions I still get an error.
13 Posted by avp2 on Jul 10, 2015 @ 03:29 PM
I just got a good Discover transaction download. It has been working since I eliminated the special characters from the password. I do have at least one capital letter and number - which may be required.
Discover tech support may know what the requirement (and change in their system) is by now.
14 Posted by mark.howell on Jul 11, 2015 @ 12:37 PM
I was able to download transactions finally after resetting up the account and making sure the User Name and Password were alpha-numeric but in order to do so I had to "Forget online passwords" and then re-enter them as they tried to connect even though I setup Discover again from scratch.
15 Posted by avp2 on Jul 11, 2015 @ 04:40 PM
Sounds right. If I remember correctly, MD only remembers/saves the user password after the first successful transaction download - for which you have to reenter the password.
If a download fails, you have to reenter. If there are multiple accounts with an institution that has failed a download failure for any one of the accounts will cause all of the accounts for that institution to request password entry. To save some frustration when it happens, disable all such accounts the first time one fails and reenable each, one at a time, starting with the left-side, top-most one and after getting each previous one to work. That way, a later fail does not mess up a previously good reset.
Kind of a pain that the individual account credentials are not managed/saved completely independently. That is the way it works now but I think many users would appreciate account credential being independent.
The “forget all passwords” function is drastic if you have many accounts. Thankfully, you do not need it real often. It also is not foolproof. Sometimes, removing credentials requires the “remove an account” python script available from support.
System closed this discussion on Mar 19, 2016 @ 05:01 AM.