Cannot Connect To Ameriprise Account??

[ccclapp]

Today I tried to add my Ameriprise Account (Ameriprise Financial Services) and get the errors and messages about going to a quicken page at Ameriprise. When I go to the url specified there is no option to approve a connection etc.

The attached file shows screenshots of the messages and steps taken.

Receive errors connecting to Ameriprise Financial Services.docx

Error Screenshots

(68.55 KiB) Downloaded 212 times

How do I proceed?

Thanks

[Mark]

Hi ccclapp,

Interesting. If you go to that URL:

https://www.ameriprise.com/quicken

It looks like you can "verify your identity", and then go back to Fund Manager within 30 minutes to continue retrieving your data. Fund Manager and Quicken both use the same OFX interface, so whatever steps you take for Quicken would apply to Fund Manager as well.

[ccclapp]

Hi Mark

small progress but no resolution, yet...

1) Interestingly the url shown in the error message in FM is http..., but the link you gave is https.
2) using the secure link (https) I do get the expected verification screen and instruction to log in followed by instruction to close the browser window., but...
3) When I then try to connect in FM, I get a different error shown on the attached...

Note, in addition to using the https url, I also closed open windows and connected via incognito browser. Not sure which made the difference, however next error still remains...

Errors part 2.docx

(113.87 KiB) Downloaded 193 times

[Mark]

Hi ccclapp,

Unfortunately, that is some error coming from their OFX server, not FM directly, and I'm not sure what it means. This will probably require some help from someone at Ameriprise to explain why this error is happening. If you have Quicken, you could also try retrieving from Quicken to see if you get the same error. If so, I'd suggest contacting Ameriprise and asking them for help or an explanation.

[ccclapp]

Mark

I saw a prior thread on this forum about user who were previously connected and then had issues. I believe the user gave you a number and you spoke to Ameriprise and shortly thereafter the issue was resolved. That thread indicated the user was not able to resolve, because it related to them and software connections. I expect if I call, they will have no idea how to help and I will not be able to give any meaning info since I dont know how FM connects.

Would it make more sense for you to be back in contact with them? Here is the link to the other thread...

https://www.fundmanagersoftware.com/forum/viewtopic.php?f=6&t=5840&p=23571&hilit=ameriprise#p23571

I will also try quicken and report back...

Thanks

[Mark]

Hi ccclapp,

Thanks for the reminder. Yes, that other thread you mentioned was for "Ameriprise Brokerage 133 Direct". It is technically a different connection than "Ameriprise Financial Services". I'm not sure why there are 2, but they go to different services. The issue with "Ameriprise Brokerage 133 Direct" was resolved by them, without any changes on our end. At that time, we did receive a contact from Ameriprise, so I have just now tried calling them. I had to leave a message. Hopefully they will return my call next week. Unless they hear complaints from their customers, they may not put emphasis on resolving it, so it still might be worthwhile for you to call.

[ccclapp]

Sounds like we are moving in the same direction...

When I was setting up Quicken to connect, it gave me the "Brokerage 133 Direct" and "Brokerage 133 Web" options, both of which have the Brokerage 133 designation and not the Ameritrade Financial Services option (even though when I connect to the Ameritrade website, it is listed as the latter).

When I edit the connection in FM and connect to the https link, and login there, and then close the window as instructed and then re-initiate the FM connection but this time using Brokerage 133 Direct, It seems to connect!!

I am still working through it, but so far big progress.

Users should note to only use the "Brokerage 133 Direct" option and apparently to use an https url vs the http url given in the initial connection error message.

Ill report back...