nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Northwest Plan Services FDP-103 error (edited)

ssparrish

Northwest Plan Services 401k / yourplanaccess.net has been failing to sync for a couple days with FDP-103. I know this is usually a credentials error but the credentials are unchanged and reconnecting or re-adding as a new account results in the same error. Meanwhile the same credentials work fine on their website and app.

Any idea what the problem could be?

Find more posts tagged with

Online Banking

Comments

ssparrish

Interesting note - when I try to add the account again as a new account i enter credentials and hir link. It says its connecting for a sec and drops back to the user/pass screen with no error but I can't proceed

ssparrish

Ooh just now I tried re-authorizing again and now I get a FDP-1400 error. What's that mean?

Coach Jon

Hello @ssparrish,

Thanks for reaching out. I can see from our side that you are receiving an FDP-103 error when trying to connect. Typically, you will receive error code: 103 when an invalid username and password for the bank you are trying to connect with have been entered. I am not seeing the FDP-1400 error on our side, however. Can you provide a screenshot of that error within Quicken Simplifi? In the meantime I would have you try these steps as well:

Verify the bank selected is the correct instance.
- You may see several different instances of your bank that you can add in the Add Account screen. Check to see if you’re using the correct one.
Verify that your login information is correct.
- Type your password/PIN into a text application to ensure you don’t have any typographical errors. Then, copy and paste your login information into Quicken Simplifi to ensure accuracy.
Verify your login at the bank’s website – Try to sign in to your bank’s website using the same login credentials to ensure you've not locked yourself out of the account and that the credentials are still valid.
Check for an app-specific password – Some banks require users to use a specific app password when connecting to a third party. Check with your bank to see if you need to use an app-specific password.
Update your credentials – Try temporarily updating your password at your bank's website and then try again to connect to Quicken Simplifi. We recommend NOT using the following special characters: & < > / \.

Thanks,

Coach Jon

ssparrish

I figured out how to chat with support today, they said this is due to an ongoing issue affecting multiple FIs and to wait 48hrs to attempt reconnecting.

ssparrish

Support has not been very helpful so far. I sent a 'send feedback' dump, spent time on the phone with someone and then went around and around with them wanting a screenshot of the 'view account' page which on this site is just a menu. Then they demanded something showing my account number when for this service there is no such thing, they use your SSN which I'm certainly not sharing to debug a connection issue.

Now support emails every day or so asking me to try again or try NWPS Retirement / nwps401k.com which is a completely different service.

Meanwhile I created an account on [removed], tried syncing my Northwest Plan Services account and it worked right away. [removed] prompted for 2fac while Simplifi is immediately failing with FDP-103 on the same credentials, so I wonder if 2fac is not being handled properly for Simplifi's sync?

I may be shouting into the wind at this point but on the off chance anyone can fix this great. Otherwise I'm probably migrating to [removed].

Coach Kristina

Hello @ssparrish,

I can see that when you contacted Support earlier today, the issue was sent to an escalated team for further investigation and resolution. No ETA or further information is available at this time.

Thank you!

icebear

@ssparrish I'm having the same exact issue (FDP-103 error, then FDP-1400) and went through the same steps with support (sent a 'send feedback' dump, kept getting requests for screenshots of the account information/nickname or number page, etc.). They ended up escalating it with no ETA for resolution. Just adding another data point.

ssparrish

After some time I tried again this week and got a 2fac prompt which then errored with FDP-105 - different error at least. Tried again 24hrs later and it works now. It seems like NWPS added 2fac for syncing like this and it needed to be implemented? Because now it prompts for a 2fac code at every sync and didnt before. I'm glad it works though!