Went searching but could not find help on he forum
I just upgraded from 6.9.20.7 to 6.9.21.0
After entering username and password I received a log in failure: Object reference not set to instance of an object.
I tried completely uninstalling WL Pro and reinstalling from Fidelity's website
Can you point to a fix or where to download the old version
Thanks for the help
Size:
Color:
Size:
Color:
Thanks
Up and running again w old version
Is my issue with the new version documented elsewhere? / resolved?
Size:
Color:
Steve, it's documented and known:
Wealth-Lab Pro® 6.9.21Simply put, you're affected by "Object reference not set to instance of an object" after login only if you use 2FA (two-factor authentication) at Fidelity for WLP (and/or VIP access, whatever it means).
Size:
Color:
Hello Eugene
I read the thread above. I have Active Trader Pro which requires two factor auth,.
I didnt see a changed login screen for WLP 6.9.21 as the thread suggested.
Something else going on?
Appreciate the help
Size:
Color:
Hi Steve,
QUOTE:
I didnt see a changed login screen for WLP 6.9.21
What do you mean? Could you take a screenshot of how the login prompt in 6.9.21 looks like for you?
Size:
Color:
My understanding is that there's two types of two-factor authentication: something called 2FA and the other is VIP Access. I've been told that you need to use VIP Access, which is a Symantec (NortonLifeLock now) mobile app. If you haven't set it up yet, you'll probably have to install the app and provide the "Credential ID" to Fidelity.
Size:
Color:
I've a Fidelity user who just installed 6.9.22.7 and now can't open Wealthab because of message
"Log In Failure: Object Reference not set to an instance of an object"
Have others encountered this error?
Thanks
Peter
Size:
Color:
Peter, I've moved your post here from a different thread. See posts #2 and #4 for the whys, wherefores and workarounds.
Size:
Color:
I also have this error message.
Why would downgrading or disabling the two step authentication solve this error given that I have utilized this program without this error, prior? With this in mind, which is the best work around?
Thank you for your time.
Size:
Color:
QUOTE:
Why would downgrading or disabling the two step authentication solve this error given that I have utilized this program without this error, prior?
Because it's a known bug. Having encountered an error message or an issue, please always check out these pages:
1.
Known Errors2.
Open IssuesIn particular, it's on the top of Open Issues:
CODE:
Please log in to see this code.
Size:
Color: