Morgan Stanley failures - 18 months and counting

jdavee

Still unable to connect to Morgan Stanley from Quicken Online Center. Quicken blames MS, MS says if I can log into MS from a browser I should from Quicken.

But I think the root problem is the web site Quicken is using for Morgan Stanley. The website Quicken shows is "morganstanley.com" but the actual login on a browser is "login.morganstanleyclientserv.com"

Where does Quicken for Windows keep the list of web addresses for financial institutions? I think that is what really needs to change.

NotACPA

Morgan Stanley has several names in Q. When you do TOOLS, Account List … which shows in the Financial Institution column across from your account in Q?

Morgan Stanley - Cash Management https://www.morganstanley.com/ 1-888-454-3965 https://login.morganstanleyclientserv.com/ux/ ACTIVE BANKING,ACCOUNTINFO&DIRECT

Morgan Stanley Wealth Management https://www.morganstanley.com/ 1-800-688-6896 https://login.morganstanleyclientserv.com/ux/ ACTIVE INVESTMENT,ACCOUNTINFO&DIRECT

Morgan Stanley at Work https://atwork.morganstanley.com/solium/servlet/userLogin#/home NA https://atwork.morganstanley.com/solium/servlet/userLogin#/home ACTIVE BANKING,CREDIT,ACCOUNTINFO&EXP-WEB-CONNECT

Also note the URL's that I've highlighted. That's what Q uses to login. IF, for some reason, that URL needs to be changed, MS will need to notify Q/Intuit to inform them of such. Neither you nor I have the authority to do so.

jdavee

Thanks for your comments but I finally found a solution. It was MS tech support that had the right answer: Change my pwd.

More concerning - when I used the MS website to make my pwd change I first just shortened it but still used a mix of upper/lower/number/special from my pwd generator.  But the MS website still rejected this pwd as invalid.  I checked the rules right on the site and the pwd was valid.  In fact, I know my old pwd was valid since I used it to log in to change it!

So I went with a different pwd logic that still makes a strong one.  The MS website liked that, and then Quicken did too.

This whole problem is just really, really silly to me. What is the point of making strong passwords that are actually allowed by the host site, only to have the Quicken connection using that same pwd fail?

I still don't know if it was MS itself (since their web site was not liking my generated random pwd) or Quicken (which may have corrupted my long/complex pwd during online connections).