Login fails in WLP 6.9 due to comma in password
Author: mattavila
Creation Date: 4/2/2016 4:37 PM
profile picture

mattavila

#1
Ive been using WLP 6.9 in demo mode for a month. Yesterday Fidelity activated my account for this and Active Trader and interestingly I cannot get the application to login to fidelity. After a few tries my account password is also reset.

I had been running the 32 bit version on Win7 (this is a virtual machine under VirtualBox, on an Ubuntu system). Tried to also run the 64 bit version on the same machine with the same issue. Support said it relys on .NET 4.2 or higher (for authentication) so I upgraded that as I had v4.1 - still the same results. I also upgraded to .NET v 4.6 and that doesnt fix the issue either.

I spun up a "new" system on VirtualBox, Win10 this time and immediately installed WL 6.9 64 bit - nothing else... exact same issue, the application will NOT login to my account. Interestingly Active trader still had no issues and works fine (on both Win7 and the new Win10 machine).

Lastly I installed WLP 6.9 on a corporate laptop (support was 'questioning' the virtual machines) and it behave EXACTLY like the other two Virtual Machines - will not login and after a few tries my fidelity account is locked out from too many attempts.

Im thinking that there is a blocked port in firewall rules (although I dont have anything defined for blocking, I do have a few higher numbered ports hard-coded to specific machines and devices from the outside... or possibly something with my username (all alphanumeric) or password (this does contain special characters).

Any thoughts or has anyone experienced a similar issue?

Thanks
profile picture

Eugene

#2
Hi Matt,

Being a 3rd party company, we can not determine what's wrong (or not) with your WLP credentials. I'd suggest that you retry from a different network not affected by your firewall anyhow. It could be that it's getting in the way. Should that fail, please contact Fidelity regarding your login issue.
profile picture

mattavila

#3
Eugene,

Ill give it a shot albeit its not simple to do. The Laptop was on a corporate VPN (forgot to mention that) so everything was routed trough a Texas VPN concentrator. Ill give a shot to changing the account password to something "simple" as well and see what if any effect that has. As for the firewall, thats the only thing I can think that may be an issue. knowing what port requirements WLP uses would be of assistance as I could hard-code those to my workstation... assuming that may also eliminate a potential problem.

Appreciate the feedback however.

Matt
profile picture

mattavila

#4
An update as to what I think is happening....

Tried CHANGING FIDELITY LOGIN PASSWORD and actually made some progress. It appears this is twofold, first I change my password to something "simple" without any special characters - the application now says my account is not authorized for WLP (interesting as they do have Active Trader setup and assured me that WLP was active as well... another support call). The more complex password may have some issue with WLP's ability to pass this back to Fidelity. I created a test password of "Abcd,123" and authentication just hangs. Changing the password to "Abcd1234" and the dialog pops up that there is a login failure..... Im assuming that WLP has some issue passing a comma in a password for authentication!

As for the ACCOUNT not showing as WLP authorized, guess I need to work this out tomorrow morning when someone is answering the phone.... although Active trader does work fine.
profile picture

Cone

#5
QUOTE:
The more complex password may have some issue with WLP's ability to pass this back to Fidelity
Unlikely. The problem is that authentication intermittently hangs up. When it happens, you have to kill the WealthLabPro.exe process from the Task Manager and try again. It almost always works the second time (not sure why). Anyway, it's not a password-sensitive thing.

profile picture

mattavila

#6
Cone - appreciate the reply. Fidelity did finally get this active on my account. We did find however that a comma IN the password was causing issues - change the password to contain no comma and it works fine!

Appreciate the assist.
profile picture

Eugene

#7
Thank you for sharing this. Renamed the forum thread to include the culprit.
This website uses cookies to improve your experience. We'll assume you're ok with that, but you can opt-out if you wish (Read more).