Sorry to hear of the issue you have encountered when connecting with your bank in Moneydance. I've checked our connection information for Fidelity Netbenefits and it appears to be up to date, from testing the connection also looks to be working. Can you let me know what version of Moneydance you are using? You can check this within Moneydance by navigating to Help --> About Moneydance (Moneydance --> About Moneydance on a Mac).
Can you both try re-creating your connection with your financial institution and see if that fixes the issue that you're seeing? You will need to disable your current connection to your bank and then recreate it using the New Connection button on the Online Banking Setup screen. To do so, you can follow these steps:
Select your bank account in Moneydance
Select the Online->Setup Online Banking button/menu
Click the "Disable" button. If you don't see a disable button, just close the setup window.
Repeat the previous steps for any additional accounts at the same institution.
Select the Online->Setup Online Banking button/menu (again)
Click the "New Connection" button and select your bank and hit OK
Continue with the setup process, entering your username/password
Make sure you pick new connection, even though your bank is still one of the connection choices after you disable it. Choosing your bank from the list of available banks will force Moneydance to download the updated information, which should then allow you to connect.
Please let me know if you continue to have connection problems after recreating your connection.
Thanks for checking back. I believe you are good at IK. Looks like these connection are broken to Quicken/Moneydance/StockmarketEye software. I use all. Fidelity Netbenefits continues to deny there is an issue, after 4 hours on the phone yesterday I finally got someone to admit there is a known issue. I about lost my mind with the poor fellow.
This has become a very frequent problem over there and I believe we are living in a world of technical incompetence. More than likely exacerbated by the bureaucracy in which we operate.
I am also on 1671 and about 3 days ago, Fidelity NetBenefits stopped working throwing off the error messages identified in earlier posts. I have another software program for my investment portfolios and it stopped downloading information about a month ago, and then about 3 days ago, threw off a different error message indicating invalid user signon. I talked to Fidelity NetBenefits on this topic and they basically said if it ain't Quicken we can't help you. Recently as I've researched this problem, it is becoming more evident that even Quicken is having problems. Perhaps Fidelity NetBenefits will offer some help now.
Of course, I'll always accept the kind help from the MD team if a solution shows up. I had hopes that 1670 or 1671 would solve the problem (referenced in many other posts within the last 30 days), but I am on 1671, so looks like Fidelity has indeed changed their security protocols.
I have tried PocketSense, set up the accounts, and tested the account and the direct OFX download threw off the error "Error signing on". I will try to remove the downloading information in MD and then re-enable downloads, but I do not believe this will result in success, as PocketSense says error, my portfolio program says error, and MD says error. No downloading happiness :(
"The given customer ID or PIN is not valid. For more information, contact your financial institution.
Additional information from the server:
Error occurred logging in."
As others have mentioned, accessing normal (non-NetBenefits) Fidelity brokerage accounts still works, and I can log in via the NetBenefits web interface with the same credentials I use for Moneydance without issues.
All evidence seems to point to a problem with Fidelity's NetBenefits direct connect system for OFX.
We have had a number of customers report this issue with the Fidelity Netbenefits connection. I've checked our connection information in Moneydance and it does appear up to date.
As Robert has highlighted, from looking online it would seem Moneydance is not the only personal finance software encountering this issue with Fidelity Netbenefits. Customers have reported this to Fidelity and have been informed that they are aware of this situation and currently working on a fix. I'll continue to monitor the situation and will update Moneydance's connection information for Fidelity Netbenefits if required.
Please accept my apologies for the inconvenience, I'll update you as soon as there is further information.
I'm still getting errors when attempting to download Fidelity NetBenefits transactions (my 401K account). Attached are the error message and Console Window files for your reference. Please advise as to resolution steps.
Sorry to hear some are still unable to connect successfully with their Fidelity Netbenefits
accounts. For those still encountering difficulties connecting, can you please confirm the version of Moneydance you are using? I'll then split these into Private threads as troubleshooting may require the passage of potentially sensitive information.
You can check the version in use within Moneydance by navigating to Help --> About Moneydance on a Windows system, and Moneydance --> About Moneydance on a Mac.
For information purposes, I am still able to download from NetBenefits at Fidelity. I am using Windows 10, and MD ver 1671. From my discussions with Fidelity this did appear to be a change in their security login procedures. NetBenefits, from my experience, ALWAYS gets the tail end of these things rolling out. As well, the communications within Fidelity itself is poor to non-existent within the two groups and ESPECIALLY between the two groups. The NetBenefits side, even when you get to anybody with technical knowledge of the system and is not close minded about you asking questions about anything other than Quicken, generally still is clueless as to what Fidelity side is or has done, or when or if something is coming to NetBenefits side.
I am always grateful for the great response from the MD support staff!
Ian any update on this? This has existed for months and none of the recent checkins mention improvements. Is the problem understood and being worked or is the hope that Fidelity does something to fix it?
Downloaded build 1684, followed instructions per post #3 verbatim, still getting "A communication or parsing error occurred. This could be the result of a network problem, a proxy error, or misconfigured server.
Error Description: java.io.IOException: HTTP Error:400 Bad Request" error.