Like several others who have reported the subject issue since August, I've had the same connection issues, with my Stifel account not validating against the correct password. Very frustrating that it has taken so long to get this issue resolved.
Hi @sms2 ,
Thanks for letting us know about the issue you're experiencing with Stifel. I understand how frustrating it can be when you're unable to connect your account.
We have a Community Alert for this financial institution covering the 15500 and OL-332 errors.
If you're seeing the message, "The user entered an invalid user ID or password. Ensure that the customer ID and the password entered are correct," without an additional error code, this is related to the 15500 error, as described in our support article.
This issue has been escalated, and our team is currently working toward a resolution. At this time, there is no ETA for a fix. I suggest monitoring the Community Alert for new updates as they become available.
Thanks for your patience while this issue is being worked on.
Since this has taken so long to resolve, I'd like to have this escalated to accounting as I am paying a subscription fee for connectivity. I should not be paying for the last month that I have not been able to connect my accounts.
I'm in the same boat here, haven't been able to update Stifel for weeks now. The ONLY reason I maintain a Quicken subscription is to make up for the shortcomings of the Stifel Wealth Tracker. Without that functionality Quicken is worthless to me and this weeks long, no ETA for a fix is a getting a little old.
Hi @sms2 and @divjnky.
I understand why the lack of an ETA is frustrating, especially when Stifel connectivity is an important part of how you use Quicken.
This isn't an issue our team can fix with a setting change or workaround. The connection is still being investigated, and resolving these types of issues can require coordination between Quicken, the aggregation service provider, and the financial institution before a fix can be released. I know that doesn't provide the immediate resolution you're looking for, but I wanted to give some context as to why these connection issues can take time to resolve.
The Stifel issue involving the 15500 and OL-332 errors is still being actively worked on under Ticket #12595593 / CTP-18508. There is currently no ETA for a resolution.
I recommend bookmarking and monitoring the Community Alert for the latest updates as they become available.
We appreciate your patience while our team continues working toward a resolution.
