The 6.9.21 release is expected tomorrow afternoon (9 Oct 2019). Here's what to expect:

Authentication Update
Wealth-Lab Pro® 6.9.21 uses upgraded Fidelity authentication that requires customers to Log in to Fidelity each time after launching Wealth-Lab Pro.

Orders Tool
Wealth-Lab Pro will now handle the intermittent server error that can result in the stale "Submitted" order status condition. If the error is detected, the order should fail with an "Error" status.

Strategy Monitor
Possible fix for intermittent crashes reported in the previous build.

Data Manager
· Fixed batch updates for ESS fundamental data. Previously, only the first symbol in a 10-symbol group was updated.
· Fixed the option to "Import the Symbols from a Fidelity.com Watchlist " when creating a new Fidelity DataSet.

Accounts
Fixed the problem for not displaying positions for All Live Accounts.

WealthSignals Trader
The WealthSignals Trader tool will honor the "Set Account" configuration when Staging/Placing Strategy orders.

Editor
· Red 'squiggles' fixed
· A reference to System.Runtime is now included automatically (e.g., required for programmers using LINQ methods)


WealthScript
· DataSeriesOp.SplitReverseFactor() was corrected for splits that fall beyond the analysis date range.
Hint: You should use this method when backtesting strategies that test if price is above or below some level. See WealthScript Programming Guide > WealthLab.Rules Classes > DataSeriesOp
· Synthetic Options: Put High/Low values were reversed. The underlier's Low/High is passed to the Black-Scholes method to calculate a put's High/Low, respectively.

Performance Visualizers
Using SplitPosition() intermittently crashed the Profit Distribution visualizer in some cases due to high memory use - fixed!


When you upgrade and evaluate, please add your feedback below!

Well, this is why we don't like to make announcements. Something always comes along to foil the plan. Look for this build sometime next week. Sorry about that!

Thank you for the announcements. I really appreciate it.

QUOTE:
Wealth-Lab Pro® 6.9.21 uses upgraded Fidelity authentication that requires customers to Log in to Fidelity each time after launching Wealth-Lab Pro.

I have a concern about it if it's going to break my semi-automation system. Does it actually change the way how to login? Or is it just to require to login regardless of the streaming state (e.g. Chart Window with streaming enabled and Strategy Monitor with strategy activated)?

QUOTE:
Wealth-Lab Pro will now handle the intermittent server error that can result in the stale "Submitted" order status condition. If the error is detected, the order should fail with an "Error" status.

Is it going to be an error message indicating the server error so you can distinguish the error from the regular order issue (e.g. insufficient funds to buy or no position to sell)?

QUOTE:
Wealth-Lab Pro® 6.9.21 uses upgraded Fidelity authentication that requires customers to Log in to Fidelity each time after launching Wealth-Lab Pro.

QUOTE:
I have a concern about it if it's going to break my semi-automation system.

Well, perhaps in a future release, a salted password could be placed on the command line of the Wealth-Lab Pro shortcut.

My concern is having to reenter the password each time I perform a new DLL library build with Visual Studio. But the salted password on the WL command line could fix that too. Or there could be a waiver to the login process for development purposes. You could just perform the login process after WLP starts up, and if the user doesn't login after an hour, close the WLP session. Would that work for everyone?

I do think employing the same authentication code snip-it for both ATP and WLP is a good move, however. That way you have less code to manage and maintain.

Thanks for fixing the Log-in issue, All Live Accounts issue, and Data Manager issue with Summary Score static updates! And I too appreciate the announcements, although we understand the exact release date can only be estimated.

Yes, the login dialog change and the fact that it's required at startup may be disruptive for some of you. The new login box, looks like ATP's login dialog (I think) and you can choose to save the username.

I'd recommend installing the x86 version and copying all your extensions from your current x64 install into the x86 install folder. WLP won't let you run both x86 an x64 versions simultaneously, but at least if something doesn't work out for your out of the box, you can easily switch to build 20 and we can try to accommodate you in build 22.

Will WLP automatically log out and require re-login or shut down after about 10 hours like ATP? Or will it, as currently, stay open and able to do backtests and data updates after automatic logout?

QUOTE:
Will WLP automatically log out and require re-login or shut down after about 10 hours like ATP?

If it works as designed, a "forced login" modal dialog will appear when the 10-hour login cookie expires. So it doesn't shut down but requires you to log in to continue interaction; operations may continue in the background.

My experience in the QA environment is that the forced dialog may appear early, late or not at all. As in this case, sometimes it's difficult to determine if the problem is caused by a real bug or one in the environment. I'll be anxious to hear your feedback.

An AutoIT macro could be used to automate the forced login dialog e.g. How to launch Wealth-Lab from Perl. If I were in your position and wanted to avoid storing your WLP credentials in the script (and knowing that the "salted password" from post #4 above probably ain't going to happen), I'd prompt for them in the AutoIT script when it starts up and store in memory for subsequent logins until the macro gets eventually terminated.

Yes, AutoIt is one of the biggest advantage for WLP over ATP.
Because ATP seems drawing its own window contents by themself, AutoIt doesn't work with ATP.

Sneak peek at the new login dialog...

Does it work with AutoIt?

It looks very similar to ATP which AutoIt (AutoIt Window Info) cannot identify the boxes and buttons.

QUOTE:
wanted to avoid storing your WLP credentials in the script

I think the solution is to copy the password handling design of your email client (or web browser) and have the WL application simply store the salted password itself. That's how I have it set up on my email client.

Aside: I do not have my Fidelity login stored in Firefox. That's because Firefox can let any user walk up to your Firefox session and show all your passwords for all your websites (if you don't have a master password set, which I don't). An application should never allow encrypted passwords to be shown.

This also brings us to supporting 2-factor authentication (2FA). Yes there should be some type a salted password challenge between client and server for each login following modern 2FA protocol at some point. I think Fidelity is beginning to support that, and it's only a matter of time before Fidelity will require both ATP and WLP to support that as well (if it hasn't already). It's a question of "when," not if.

Having read post #12, I take my words back. Instead of using AutoIT there's easier and more straightforward way: Keepass. When my password management plugin for Firefox named Kee stumbles or I need to log in to IB TWS etc., I simply use the Keepass Auto-Type feature (Ctrl-Alt-A). So I need not worry about the password security (protected by Keepass) and it supports a lot of custom fields, special keys, placeholders, and variables (if required).

KeePass Auto-Type guide

QUOTE:
Yes, the login dialog change and the fact that it's required at startup may be disruptive for some of you.

Please don't roll out these kinds of disabling changes without warning. I have AutoHotKey scripts to start Wealth-Lab Pro every trading day, update the data, run my trading strategies and email me a list of trades for the day. Therefore, I can simply check my email, regardless of where I am, and do my trading. All of that can happen with Windows locked. I am planning to be out of town next week, which means that whenever version 6.9.21 gets rolled out, I'm not going to be able to trade for the rest of the week!

QUOTE:
I simply use the Keepass Auto-Type feature (Ctrl-Alt-A).

That only works if you have KeePass open and, obviously, this can't be done with the computer locked. As a result, it's hardly a secure option if you're away from your computer. Not only are you exposing your Fidelity log-on information, but also every other user name and password stored in KeePass.

It would be very much appreciated if you could make a beta version available ahead of time, so people can figure out how to deal with the changes. At the very least, please allow users to install updates, rather than forcing them to be installed the next time Wealth-Lab starts. I can't possibly program anything to deal with unknown potential future updates being forced on me when I'm away from my computer.

QUOTE:
It looks very similar to ATP which AutoIt (AutoIt Window Info) cannot identify the boxes and buttons.

Neither can AutoHotKey.

I also use AutoHotKey with AutoIt3 Windows Spy which identifies the ATP login window as:
ahk_class HwndWrapper[DefaultDomain;;f20636b5-453b-487d-b62e-4c5a6c9d876a]

The number portion is unique on each login. Have you tried these suggestions? I have not worked them.
https://autohotkey.com/board/topic/100317-whats-hwndwrapper-and-defaultdomain/
https://www.autoitscript.com/forum/topic/106832-class-hwndwrapper-not-working/

QUOTE:
Windows Spy which identifies the ATP login window

The problem is that for AutoHotKey to work when Windows is locked, you can't just use Send, you need to use ControlSend, which also requires a ClassNN identifier.

CODE:
Please log in to see this code.

Maybe there is a ClassNN identifier for the ATP login window, but it isn't showing up in Windows Spy.

QUOTE:
Does it work with AutoIt?

Yes.

This will autostart Wealth-Lab Pro using AutoHotKey and runs even if Windows locked:

CODE:
Please log in to see this code.

Obviously, this doesn't get around the issue of how you secure your user name and password. My solution is to keep my computer locked when I'm not around, to store this script in a directory that is not shared with any other computers on the network and have my drive protected with Bitlocker. I also keep the *.exe file in a non-shared directory so it is not accessible to de-compile. Please feel free to chime in, but I think that is a pretty secure solution.

Eugene/Cone hope you are well.

I don't understand where to go to get the program started. I can login and it asks me to enroll in full view but how do I get the program started.

Keep getting this message when I try to install WealthLab. I removed the old version after having issues when doing the update this morning. Please see attachment for image.

@01439

If you upgraded all the way to 6.9.21 (as suggested by the screenshot showing version 6.6) without having installed previous builds 6.9.x then I'm afraid you cannot roll back to a trusty 6.9.x using the "Downloaded installations" workaround. In any case, please do an uninstall, download the installer from Fidelity's website and install from scratch.

UPDATE 10/18/2019:

For solution, see Cannot install Wealth-Lab Pro 6.9.21: Warning 1909

@gbullr

Sorry, we don't have a solution at the moment. Please try to go back to the previous build using the "Downloaded installations" workaround.

Eugene I uninstalled prior version; downloaded the latest version from fidelity and I get this window after logging in.

What am I/we suppossed to do?

@gbullr

You've done something different from what I suggested. But let's help the development team track down the error. Please create a support ticket for instructions.

P.S. I've corrected the usage of external image hosters in your post. It's not a good idea since content is used to die away.

When signing in to WL, I found it impossible to get out of Fidelity ATP after being forced to do the double authentication (which, if it worked, would probably be a good thing, as added it to ATP sign in quite some time ago).

So, I downgraded to WL 6.9.20.7, which seems to enable WL to function as it should (as it did previously).

QUOTE:
Fidelity ATP after being forced to do the double authentication

Does ATP support 2FA if you have 2FA enabled on your Fidelity accout? This is the first time I have ever heard of 2FA on ATP.

What does it do with new WLP?

Yes, ATP does support 2FA, and the new WLP login looks just like the ATP login.

And, at least for me, when trying to login to the latest WLP, it in fact took me to ATP instead.

QUOTE:
And, at least for me, when trying to login to the latest WLP, it in fact took me to ATP instead.

So if you have ATP installed, WLP starts ATP for 2FA login? What if you uninstall ATP? Does WLP opens its own login prompt?

Cone,

QUOTE:
Does it work with AutoIt?

QUOTE:
Yes.

Unfortunately, I cannot make AutoIt to work for this new login window.
AutoIt Window Info cannot identify the control texts and boxes.
Any idea to control this new login window from AutoIt?
Never mind. Panache's comment #20 works great. Thank you, Panache!

QUOTE:
QUOTE:
So if you have ATP installed, WLP starts ATP for 2FA login? What if you uninstall ATP? Does WLP opens its own login prompt?

I did not try to uninstall ATP, so I don't know.

I also never save user or password information, so can't speak to that issue either.

What I did do was to go to the WL 6.9.20.7, which was still in my download folder. I ran the ".exe" application executable file from WL 6.9.20.7.

After restarting computer and opening WL 6.9.20.7, everything seemed to work, including TASC Indicators 2019-10, even though WLP says the operating version is 6.9.20.7.

@ell7123

If you ever need build 21 to fix bugs then you might want to create a support ticket. There are some ideas on how to fix it but the developer would like to reproduce it on affected PC with some debug code.

QUOTE:
Panache's comment #20 works great.

You're welcome. Please note, I updated my post. I had to change the ControlClick statement to add a ClassNN identifier so it would run when Windows is locked.

QUOTE:
I had to change the ControlClick statement to add a ClassNN identifier so it would run when Windows is locked.

Yes, I tested it and confirmed it to work while Windows is locked.

However, it sometime fails and I'm figuring it out now. What makes it difficult to figure out the problem is Fidelity authentication server that appears to lock the account (or deny the computer) immediately when the authentication failed (incorrect user name or bad password for more than once). Once it happens WLP refuses to login and it takes an hour or so to get back to work. I don't want my account totally locked out while trading, I have to wait until the market to close to investigate it further.

Streaming Quotes drops to 15 mins delayed quotes.
WL started with fidelity credentials and show "Streaming Data" as connected but sometime later quotes update changes to 15 mins delay. Once this has happened, main screen continue to show streaming Data as Connected. To get the the RT, I need to go to accounts and login again. I had to do this multiple times today.
I need to manually update certain lists multiple times during the day. This is how I noticed the shift to 15 min delayed. Didn't have any issue with versions prior to the current.

Log in to Fidelity requires VIP Access code as well, is there a way to include that code with the password?

I get this error after trying to login with my fidelity account. WLP does not start ATP, and the 2FA window is not opened either.

QUOTE:
authentication failed (incorrect user name or bad password for more than once

It is possible that the script is beginning to type before the window is open, so the first part of your username isn't getting entered every time. Try

CODE:
Please log in to see this code.

instead of

CODE:
Please log in to see this code.

If that doesn't work, comment out the last line, so you can confirm your user name is being entered correctly.

If that doesn't work, try adding a Sleep statement before each ControlSend.

Obviously, I haven't spent too much time testing it yet.

QUOTE:
I get this error after trying to login with my fidelity account.

@hmg2020

Please create a support ticket.

UPDATE 10/19/2019: Users with two factor authentication enabled get this error message on WLP login: "Log In Failure: Object reference not set to an instance of an object" :(

While I was testing the script, after login and close WLP for 5 times or so, all of the sudden Fidelity started refusing the login.
The script didn't fail at all and all login went fine but WLP stopped accepting the login.
Apparenly they are monitoring the account access so strictly.
This is bad because if you have multiple WLP logging at once, your account would be locked!

Attached is the error message you get after several login and close.
This error window is also very unfriendly to the scripts because the scripts cannot identify the difference from the login window.
Could you consider changing the window title at least?

@Panache

QUOTE:
If that doesn't work, try adding a Sleep statement before each ControlSend.

Thank you for your suggestion.

Unfortunately neither changing the sleep time nor adding sleep in-between fixed the problem. But I think I found something causing the intermittent problem.

The problem happens when there is a window other than WLP login window has focus. In which case, sending the first "Enter" key doesn't activate the input.

Also sending ControlClick seems moving the focus location somewhere else other than the Username box. That's probably why the first "Enter" key isn't reaching to the Username box.


EDITED by Eugene 10/20/2019:
Update to my post.

QUOTE:
While I was testing the script, after login and close WLP for 5 times or so, all of the sudden Fidelity started refusing the login.
The script didn't fail at all and all login went fine but WLP stopped accepting the login.
Apparenly they are monitoring the account access so strictly.

This issue appears to be due to hiccup on server side and the login itself works fine now.

QUOTE:
This is bad because if you have multiple WLP logging at once, your account would be locked!

So far I tested 3 WLPs logging simultaneously, my account didn't get locked.

Harapa, I too am experiencing a 15 min delay while streaming. This had happen the first day after upgrading. Then I tried rebooting my computer and Wealth Lab seemed to be working fine. But during the last two days at one point or another Wealth Lab would not display the last two 5 minute bars while streaming. This behavior would seem to start when I switched to another symbol and then it would not correct itself no matter what symbol I went to until I shut down Wealth Lab and restart it.

@Harapa, @Starburst

QUOTE:
I too am experiencing a 15 min delay while streaming

Please create a support ticket.

1. Is 6.9.21 released and stable?
2. What are known issues?
3. Please separate the automation stuff, AutoIt etc., into a new "remote control" thread (or I probably wouldn't have asked question #1.)

You can read about issues of build 21 in this thread and related topics (#1, #2) and decide for yourself how stable it is. Make sure to read Cone's post #5, though.

UPDATE 10/20/2019
Slightly edited the "automation stuff", merging / updating some posts above.

+1 on giving more advanced warning of potentially disruptive changes, which a login change to daily definitely is at least for me. Hoping to see a command line option coming soon.

QUOTE:
Hoping to see a command line option coming soon.

If you're referring to suggestion in post #4 then this is not considered, sorry.

QUOTE:
if something doesn't work out for your out of the box, you can easily switch to build 20

Please guide how to revert to previous version if I elected to auto upgrade.

Please see post #21 above.

Note to LenMoz: The new release is a mess. It crashes every day. And it often won't submit and execute orders.

If by crash you mean an abnormal program termination then we haven't had any crashes reported with 6.9.21.

Call it what you wish. It logs me off, freezes, then requires a restart.

WLP has logged me off 5 times today during regular market hours. Once, it froze and required a restart. The other times I could re-log in. I am not detecting an internet connection disconnect with my other trading programs. (I am in a major city with Cox high speed cable and a wired connection, not wifi.) It logged me off several times during the day yesterday, also.

Hope this helps.

This issue is known (forced login problem) and hopefully gets fixed in next build. Don't want to give false promises but a fix is in the works.

Just installed Wealth Lab Pro v6.9.21.
Called Fidelity to verify that I am enabled for their 30 day trail.
When I try to start WLP I get a small login window and I enter my Fidelity User ID and PW as instructed.
My Fidelity account appears in the 3 by 4 inch login Window.
An indication that something is loading appears and then goes away.

No WLP window appears.
Under task manager I see WealthLabPro.exe running using about 258,400K

I realize there are numerous other entries related to this problem for earlier version of WLP.
What do I have to do to be able to actually use WLP.

@QuantumAI

Kill the WealthLabPro.exe process and restart WLP. Can you start it normally? If not please create a support ticket.

This issue is known and the developer is working on providing a fix in 6.9.22 but it may require testing/troubleshooting.

I've been running the new version for about a week with no issues.

QUOTE:
the developer is working on providing a fix in 6.9.22 but it may require testing/troubleshooting.

I would be happy to be a beta tester for you, but I would really like the opportunity to see how the next version performs on one of my non-essential computers before having to install it on my primary computer.

Hopefully, notification that the next version is available will be made via a pop-up that does not steal focus from the main program, so that those of use starting Wealth-Lab via AutoHotKey or AutoIT can continue to run Wealth-Lab unattended until we choose to manually update it.

PROBLEM

If after you log in to WLP, it just shows a Fidelity web page inside the small browser-like window e.g.



WORKAROUND

1. Upgrade to 6.9.22.
2. Log in and then strike Ctrl-K key to close the window and start WLP.

Ctrl-K did nothing for me. Is there an ETA on 6.9.23?

If Ctrl-K did nothing, you're not on 6.9.22. Do a complete uninstall and reinstall.

ETA for fix to WLP 6.9.22 login issue

Do you have a direct link? I downloaded the setup from Fidelity's web page on a clean machine and must have gotten the old version.

Thanks

https://www.fidelity.com/wlp

Hi Eugene and Cone.

Back to this same problem. Ctrl-K no longer works as a work around.

I am now getting this message.

Thank you for any help that can be provided.

Fidelity WLP stopped working today