1. Home
  2. Quicken Personal Finance
  3. to add to the chase fun

to add to the chase fun

I had been trying for a week to get the reauthorization to work and it kept failing [so I'd cancel out , tell it "skip this time" and it happily continued with direct connect]. Today I called chase [it is now the third or fourth time over ten days that it has failed] and they worked with me and we kept checking and eventually the last-ditch attempt was to deactivate the account and try to reactivate it. It *still* failed but now I can't revert back to direct connect since I deactivated.

I wondered if it was a browser problem. I use firefox [on win 10/pro] and so I gave "Edge" [which I hate using for anything] a try and it immediately failed -- what I had tried doing was doing the reauth and it'd open the Chase reauth link in firefox and I'd copy the link to Edge and try it there and I'd give Edge my credentials and I'd get an *immediate* fail in quicken. I have no idea why -- it certainly hadn't timed out since it took less than a minute for me to copy , paste into Edge and authorized there.

So: maybe the third time is the charm: I did the unthinkable.. I made Edge my default browser [so the Quicken link would open directly into Edge]. And... it all worked!! I got to the page asking for my accounts, checked the box, hit continue and quicken woke up and asked me which quicken account to connect Chase to. So everything is working now [and, of course, I immediately changed my browser default back to Firefox :o)]

I have no idea why the quicken->chase link wouldn't work in firefox, but it didn't... but at least all's well now.

/Bernie\

Reply to
Bernie Cosell
Loading thread data ...

I don't think the reauthorization has anything to do with conversion. I got the reauthorized message, reauthorized, left quicken, entered back in and everything was ok. The connection type was still DirectConnect. I suspect that the reauthorization just has to be done periodically.

-- John

I had been trying for a week to get the reauthorization to work and it kept failing [so I'd cancel out , tell it "skip this time" and it happily continued with direct connect]. Today I called chase [it is now the third or fourth time over ten days that it has failed] and they worked with me and we kept checking and eventually the last-ditch attempt was to deactivate the account and try to reactivate it. It *still* failed but now I can't revert back to direct connect since I deactivated.

I wondered if it was a browser problem. I use firefox [on win 10/pro] and so I gave "Edge" [which I hate using for anything] a try and it immediately failed -- what I had tried doing was doing the reauth and it'd open the Chase reauth link in firefox and I'd copy the link to Edge and try it there and I'd give Edge my credentials and I'd get an *immediate* fail in quicken. I have no idea why -- it certainly hadn't timed out since it took less than a minute for me to copy , paste into Edge and authorized there.

So: maybe the third time is the charm: I did the unthinkable.. I made Edge my default browser [so the Quicken link would open directly into Edge]. And... it all worked!! I got to the page asking for my accounts, checked the box, hit continue and quicken woke up and asked me which quicken account to connect Chase to. So everything is working now [and, of course, I immediately changed my browser default back to Firefox :o)]

I have no idea why the quicken->chase link wouldn't work in firefox, but it didn't... but at least all's well now.

/Bernie\

Reply to
JohnA

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.