MD cannot connect to Ameriprise after brokerage upgrade
Peter Lehrach
I have been unsuccessful at re-connecting my Ameriprise MD investment account following an Ameriprise upgrade to their brokerage system. I have checked with Ameriprise and they indicate that it is not their problem.
I receive this MD error when I use the Online Banking Signup New
Connection Wizard for Financial Institution "Ameriprise Brokerage
133":
"I'm sorry, an error occurred: java.io.IOException: HTTP Error:400
Bad"
I tried creating a new MD investment account for Ameriprise and connecting it to "Ameriprise Brokerage 133" but was unsuccessful. Any help would be appreciated.
2 Posted by kyle.c.shaw on 09 Jun, 2012 02:23 AM
Same problem, basically same timeframe. They clearly changed something with how financial software connects with them, but I don't know what exactly.
3 Posted by kyle.c.shaw on 09 Jun, 2012 02:28 AM
To clarify, I get the same basic error when trying a new connection with either "Ameriprise Brokerage 021" or "Ameriprise Brokerage 133", which both appear new to me on the Moneydance list, as I used to use simply "Ameriprise Brokerage" but that option is no longer listed. (All of which suggests someone is trying to work on this..)
Support Staff 4 Posted by Jessica Little on 10 Jun, 2012 07:24 PM
Hi,
IN order to connect to Ameriprise, you'll need to restart their new authentication process. To do so, first go to their website at: http://ameriprise.com/quicken/
This will lead you through the process on Ameriprise's side. Once that's done, you'll have 30 minutes during which you'll need to reset your connection in Moneydance. To do so, you can follow these steps:
1) Select your bank account in Moneydance
2) Select the Online->Setup Online Banking button/menu
3) Click the Disable button. If you don't see a disable button, continue to step 5.
4) Select the Online->Setup Online Banking button/menu (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
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.
Jessica Little
Moneydance Support
5 Posted by Lehrach, Peter (CCI-Atlanta) on 11 Jun, 2012 02:38 PM
Thank you for your response.
I followed your instructions and I received the same error message.
Next I tried to manually download transactions from Ameriprise and was requred to complete an online terms an conditions agreement (I was hopeful that this was why MD could not connect). Following the agreement, I successfully downloaded the transactions and reconciled them in MD. I then tried to create the MD connection to Ameriprise but, unfortunately, I received the same error message.
My Ameriprise Advisor provided me with the instructions for Quicken users (attached for your information). Perhaps you will find it useful in your trouble shooting.
Do you have any other suggestions?
Peter
6 Posted by k on 12 Jun, 2012 03:19 AM
Yeah, same -- after doing the Ameriprise activation for quicken I immediately attempted the instructions in Moneydance for a "New Connection" and upon selecting either the 'Ameriprise Brokerage 021' or 'Ameriprise Brokerage 133' options (I see no other Ameriprise options available) and clicking "OK", MD paused a second or two before giving a pop-up error of "I'm sorry, an error occurred: java.io.IOException: HTTP Error:400 Bad Request" and doesn't allow me to proceed (the "Next" box stays greyed out).
I doubt it makes a difference but I run MD 2011r2 (803) on Ubuntu, but in the absence of any other issue with MD (including continuing to successfully connect & download from another fi) it appears to be a problem interfacing with Ameriprise, not the rest of the package. Kinda anticipated a problem when I heard they were "upgrading".
Support Staff 7 Posted by Jessica Little on 13 Jun, 2012 12:09 PM
Thanks for the instructions from Amerprise, Peter. That does indeed give me some ideas as to what might be wrong.
First, you should make sure that you've updated your account number in the Moneydance settings to their new account number format, as indicated in the PDF Peter sent. Having the wrong account number can cause 400 errors.
Next, restart the verification process on the Ameriprise website. Then, make sure you are using the "Ameriprise Brokerage 133" if you full account number (not the shortened one used for connecting) ends in 133. Otherwise, use the "Ameriprise Brokerage 021" connection.
Hopefully, using the corrected account number will clear up the problem. If not, let me know and we'll keep troubleshooting.
Jessica Little
Moneydance Support
8 Posted by Jerry Rubinow on 14 Jun, 2012 03:50 AM
I tried all the suggestion in this thread, but nothing worked. I ended up fiddling with the Advanced Settings, possibly a mistake. Now when I select Ameriprise Brokerage 133 from New Connections, I get past that screen, select my account, get the user/password dialog. But when I put them in, I get this error:
There was an error communicating with your financial institution. The details of this error are below.
Bank Name: Ameriprise Brokerage 133
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
9 Posted by Peter Lehrach on 14 Jun, 2012 01:42 PM
Still no luck. I asked Ameriprise to see if everything with my account and electronic data transfer agreement(s) were OK to sync with "Quicken". They confirmed that everyting looked good from their end although the Ameriprise Website CSR left me with the impression that she wasn't very thorough in her analysis.
Support Staff 10 Posted by Jessica Little on 16 Jun, 2012 08:29 PM
Hi Peter,
It seems like Moneydance is having trouble forgetting your old connection information. To fix this, you'll need to force clear the current connection information for your bank in Moneydance. I'm sending a file called remove_one_service.py that will help do that. Before proceeding, please back up your Moneydance file, just in case something goes wrong. So far, this hasn't caused any problems, but better safe than sorry!
To use the file, first save it to your computer and then follow these steps:
1) Go to the Ameriprise website and restart the authentication process to get a new 30 minute sync window.
2) In Moneydance, click on the Extensions Menu and choose the Manage Extensions option.
3) From the list of available extensions, choose the python scripting interface extension, then click Install to download the extension and finish to complete the installation.
4) Close the Manage Extensions window.
5) Again, click the Extensions menu. This time, choose the Python Interface option.
6) In the python scripting window, click the read from file button and load the file from whereever you saved it. You will be asked to select which connection you want to clear. Choose your bank, and click OK. You'll get a confirmation message when the connection has been removed. Close the window when done.
7) Set up the connection to your bank like normal. Since all of your settings have been cleared, you should get the most recent connection information for your bank.
Hopefully, that will work. If it doesn't, let me know and we'll continue troubleshooting.
Jessica Little
Moneydance Support
11 Posted by Jerry Rubinow on 16 Jun, 2012 11:28 PM
Hi Jessica,
I cleared out both Ameriprise 021 and 133 using the script you uploaded. I then went to setup online access for one of my Ameriprise accounts:
- First I went to the Ameriprise web site and did the 30 minute enable. - Then I went to my account in MD and clicked Setup Online Banking. - I then selected New Connection and Ameriprise 133 At this point, after a pause, before I clicked Next and before the login/password dialog, I got the same 400 Bad error as has been reported.
I have the correct 8 digit account number in my Account Info. Is there any other specific info that is used from the account info?
-Jerry
Support Staff 12 Posted by Jessica Little on 17 Jun, 2012 03:25 PM
Hi Jerry,
The only other thing I can think of is to check to make sure that the routing number didn't also change with this new server. Also, can you try setting up the connection in a completely new Moneydance file? If that works, then we know the problem is with your file and not with Ameriprise.
Jessica Little
Moneydance Support
13 Posted by Jerry Rubinow on 18 Jun, 2012 02:09 AM
Hi Jessica,
I created a new MD file, minimal set of accounts. I then created an investment account and set the 8-digit account number to that of one of my Ameriprise accounts that has 133 at the end. Then I clicked Setup Set Up Online Banking, then New Connection, selected Ameriprise 133 and hit OK. A few seconds pause, and then "I'm sorry, an error occurred: java.io.IOException: HTTP Error:400 Bad".
You mention a routing number in your last email, but this is not a checking or savings account. Is Account Name or Bank Name in the account info dialog used in any way for online access?
Is there anything I can to on my end, anything I can ask my Ameriprise financial advisor, to help investigate this?
-Jerry
Support Staff 14 Posted by Jessica Little on 18 Jun, 2012 03:27 PM
Hi Jerry,
You may be able to have an Ameriprise technician look at their logs while you try to connect to see what is wrong with the connection. They might have more information from there end about exactly what the 400 error means. Any details they can give us about the error will help troubleshoot the problem. If it's on their end, hopefully they can fix it. If it's on our end, we're happy to fix it once we know what's going on.
Jessica Little
Moneydance Support
15 Posted by Jerry Rubinow on 19 Jun, 2012 02:01 AM
Hi Jessica,
I talked to my advisor and this is what they said:
Jerry I called our technology help desk and was told the following:
1- Error 400 a catch all error for a bad connection - no help
2- They only support Quicken, so they most probally can not help with issues regarding MoneyDance.
3- They will set up a case and look into it, and get back to me with any info they can (which will probally be a combination of items 1&2)
I would guess this doesn't help much, but I'll let you know if I hear anything else back.
-Jerry
Support Staff 16 Posted by Jessica Little on 19 Jun, 2012 11:30 AM
Thanks, Jerry. Hopefully they'll be able to find a little more information once they dig deeper.
Jessica Little
Moneydance Support
17 Posted by k on 19 Jul, 2012 07:16 PM
Don't know what changed, but I am now able to connect to my Ameriprise account (same one which worked prior to Ameriprise's "upgrades", then stopped working). I hadn't tried anything for a week or two, more or less. Today I simply went through the normal process; online -> setup online banking -> New Connection -> selected "Ameriprise Brokerage" (there is a separate one with "133" appended, but "021" has disappeared), and entered the relevant ID/password, etc., and it successfully downloaded transactions.
18 Posted by Peter Lehrach on 19 Jul, 2012 07:37 PM
Thanks k for letting us know; Ameriprise now works for me too. Too bad for Ameriprise that I got so frustrated with their new brokerage system that I just completed moving all of my accounts to a competitor.
19 Posted by Jerry Rubinow on 20 Jul, 2012 02:46 PM
Yes, thanks k! I'd given up hope, but I too tried again after your email and it's now working fine.
-Jerry
20 Posted by S on 16 Nov, 2012 02:24 PM
This comment was split into a new private discussion: Problem connecting to Ameriprise
I'm trying to get the brokerage part of Ameriprise working with the 133 account and everything seems to go OK, it connects and and it asks me to match the account there with the MoneyDance account, and then for downloading it asks me to match securities, which I do, and then I just see the spinning beachball and Moneydance does not respond. I waited for 30 minutes and did force quit, started with the backup, did the same steps, and had the same problem again. Any ideas about what the issue could be?
Also, is there a way to have Moneydance alphabetize security names ignoring capitialization? The order is that the all caps ones precede the regularly capitalized ones which can make it tedious to find things in a long list.