Debuggin a 301-A

Is there any way to figure out what's happening with a persistent 301-A
error? [q 2018/r 11.19] I haven't been able to get my Wells Fargo
information for three days now. It does 'updating financial information'
and then I get an ol-301-a. None of my three accounts get updated. I
can't figure out the OFX logs at all, but I seen it send an
"SIGNONMSGSRVQ1" I see the request all filled with account #s and my auth
credentials and such. And the next thing is
2000ERRORWe
are unable to process your request at this time. Please try again later or
contact us at 1-800-956-4442....
I'm guessing I'm out of luck and just have to wait until Wells Fargo
figures something out, yes?
/B\
Reply to
Bernie Cosell
One thing I often try is to create a new Quicken file and add the troublesome accounts. If that fails I assume bank issues. If it works, it may be time (after saving a copy) to deactivate and reactivate the accounts.
Reply to
Marc Auslander
"Bernie Cosell" wrote
Is there any way to figure out what's happening with a persistent 301-A error? [q 2018/r 11.19] I haven't been able to get my Wells Fargo information for three days now. It does 'updating financial information' and then I get an ol-301-a. None of my three accounts get updated. I can't figure out the OFX logs at all, but I seen it send an "SIGNONMSGSRVQ1" I see the request all filled with account #s and my auth credentials and such. And the next thing is
2000ERRORWe are unable to process your request at this time. Please try again later or contact us at 1-800-956-4442....
I'm guessing I'm out of luck and just have to wait until Wells Fargo figures something out, yes? -----------------------------------------------------------------------------
Wait?
What part of "contact us" in "Please try again later or contact us at 1-800-956-4442" is not clear?
Reply to
John Pollard
} } > Is there any way to figure out what's happening with a persistent 301-A } > error? [q 2018/r 11.19]
} I suggest you follow: }
formatting link
}
Thanks! For the uninterested, as of Wednesday Quicken posted an update explaining:
Express Web Connect/Quicken Connect and Direct Connect connections with Wells Fargo Bank have been temporarily deactivated while we are working with Wells Fargo to resolve the 501/581/580, 101/181/180, OL-301 and incorrect transaction data errors. Attempts to add or update accounts using these methods may result in various errors or messages not limited to the already listed codes.
At this time there is not an ETA on when connections will be restored however this is a high priority issue that we are working to resolve as quickly as possible.
Apparently the folks in customer service at W-F haven't been informed about the situation..:o) Since I doubt I'll get a notice from W-F I guess I'll sign up for getsatisfaction so I can 'follow' the thread.
/B\
Reply to
Bernie Cosell
} Is there any way to figure out what's happening with a persistent 301-A } error? [q 2018/r 11.19]
Related question [Calling Wells-Fargo has proven useless]: since the bug that is causing the 301-A's hasn't been fixed yet and today's Quicken update [11.20] I got to wondering about my 'repeating' payments. I wonder if they'll go through.. guess I'll have to watch my WF account by hand...
/B\
Reply to
Bernie Cosell
} For what it's worth I'm getting WF downloads and checks sent with no } problem - so it's not a global issue.
Amazing. I just checked getsatisfaction [they were supposed to email updates when the status changed and didn't. GRRRR]:
Hello All, This issue with Wells Fargo is now resolved; you should be able to add and update accounts without issue.
Thank you for your patience while we worked with Wells Fargo to correct this issue--
and I just tried again and got the OL-301-A again. I tried to 'reset' and got an immediate error. So I deactivated my account and now cannot reactivate it: -------------------------------- Quicken is having trouble connecting to Wells Fargo Bank An Additional message from Wells Fargo Bank
We are unable to process your request at this time. Please try again later. ------------------------------
Sigh ...I suppose I could also try "web connect" in the interim. Guess I'll try again in the morning and then get to spend another happy hour on the phone with WF online support...
/Bernie\
Reply to
Bernie Cosell

} > This issue with Wells Fargo is now resolved; you should be able to add } > and update accounts without issue.
} > and I just tried again and got the OL-301-A again. I tried to 'reset' and } > got an immediate error. So I deactivated my account and now cannot } > reactivate it: } } I suggest you now follow: }
formatting link
Thanks!
Wells Fargo had recent issues they confirmed were resolved (see this announcement for more:
formatting link
, however it appears they are still running maintenance based on the latest error being reported. We are currently working with them to determine an ETA for resolution, and apologize for any inconvenience in the interim.
OY! I've set up to get the RSS feed of new topics about quicken..:o)
/B\
Reply to
Bernie Cosell

Site Timeline Threads

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.