WLP 6.9.20.7 (07/10/2019) Update
Author: innertrader
Creation Date: 7/11/2019 4:42 AM
profile picture

innertrader

#1
Just updated WL software when prompted. Supposedly completed successfully, but WL won't open. Each time I try to start it prompts me with "New update available..." I've gone through it twice. The second time I got the option to Repair rather than install, so I chose that. Didn't fix the problem. I've restarted twice.

I'm on Windows 10. would like to get up and running before the market opens in US.
profile picture

Eugene

#2
If Repair doesn't fix things I'd suggest the following procedure to do a clean reinstall:

1. Uninstall WLP
2. Delete this entire folder: C:\Program Files\Fidelity Investments\Wealth-Lab Pro 6
3. Download and run the WLP installer from Fidelity's website
4. Reinstall all Wealth-Lab Extensions required for your Strategies to run

It doesn't affect your data, Strategies and settings.
profile picture

Eugene

#3
Bug Fixes and Maintenance
Minor bugs and cosmetic fixes may not be listed.

Orders Tool
Fixed "Stuck Submitted" bug that occurred for limit/stop orders with trigger prices equal to or greater than $1,000.

Data Manager
Fixed data update bug that prematurely ended updates when encountering a symbol with a split.

WealthSignals Trader
The WealthSignals Trader tool's endpoint is updated to point to the new WealthSignals host site.

Internal
· Updated processing for back-end calls to account and trade services.
· Switch endpoint for some quote service calls.


.. and this important change didn't make the Help guide...
Upgraded QWhale - now Alternet - Editor
profile picture

innertrader

#4
@Eugene Re: #2

That worked. Thanks.
profile picture

Eugene

#5
Glad to help.
profile picture

Cone

#6
Confirmed that a problem currently exists with the 64-bit "Software Upgrade".

If you've already accepted the automatic upgrade, then follow the procedure in Eugene's Post #2 above.

If you're lucky enough to read this before doing an auto-upgrade....
1. Simply Uninstall WLPro 64-bit first.
2. Download 6.9.20 from https://www.fidelity.com/wlp
3. Install it.
profile picture

thodder

#7
Thanks Eugene and Cone it helped for me as well. I have Windows 10 64-bit and am using WLP x64.

In case this helps... Before I found this forum post I noticed the following in my Windows Event Viewer which I tried to report to Fidelity (their desk wasn't open at the time of my call):

.NET Runtime Error:
Application: WealthLabPro.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidCastException
at WealthLabPro.MainModule..ctor()
at WealthLabPro.MainModule..cctor()

Exception Info: System.TypeInitializationException
at WealthLabPro.MainForm..ctor()
at t.a()

Applicaton Error:
Faulting application name: WealthLabPro.exe, version: 1.0.0.0, time stamp: 0x599c79f6
Faulting module name: KERNELBASE.dll, version: 10.0.18362.239, time stamp: 0xb6f4b059
Exception code: 0xe0434352
Fault offset: 0x000000000003a839
Faulting process id: 0xe38
Faulting application start time: 0x01d537dffc02c179
Faulting application path: C:\Program Files\Fidelity Investments\Wealth-Lab Pro 6\WealthLabPro.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 892eb9f0-3d94-4190-8d39-c589e5c9e7b3
Faulting package full name:
Faulting package-relative application ID:
profile picture

akashj303

#8
QUOTE:
1. Simply Uninstall WLPro 64-bit first.


Cone, will this still require installing all extensions again as well?

I didn't get a notification for the auto-upgrade, however I see there is a new version (6.9.20.0) available when I check through the software itself.
profile picture

Eugene

#9
No, doing so will not require reinstalling all extensions. It may not be required at all; only if WLP crashes on startup following auto-upgrade and/or
you're still unable to start it after a simple uninstall/reinstall.
profile picture

akashj303

#10
OK, thanks. Uninstalled and reinstalled successfully. Some extensions had to be updated again. For some reason, Editor settings got reset even though the settings xml file has the same timestamp as before the reinstall?
profile picture

JDardon

#11
Guys:

Had the same problem so following your advice uninstalled WLPro an reinstalled it again. However, after doing so Neural Lab is no longer functioning. My scripts were not compiling (even after uninstalling and reinstalling NeuroLab).

I did confirm that NeuroLab.dll is in my main wealth lab folder after the reinstallation, but still scripts not compiling.
I had to physically go into REferences in the editor and add a pointer to the NeuroLab.dll in the main wealth lab folder for my scripts to compile. This was not necessary before.... if the .dll was in the main wealth lab folder, it would take.

However, now that they compile, they still don't run with this runtime error:
QUOTE:
Runtime error: The type or namespace name "NeurLab" could not be found (are you missing a using directie or an assembly reference?)
at WealthLab.Strategies.PropuslionStrategy.Execute()



Edit.....
Also I can't seem to find the NeuroLab in the Tools folder

profile picture

Eugene

#12
@akashj303
QUOTE:
For some reason, Editor settings got reset even though the settings xml file has the same timestamp as before the reinstall?

The reason probably has to do with this in post #3:

Upgraded QWhale - now Alternet - Editor

@ JDardon
QUOTE:
However, after doing so Neural Lab is no longer functioning.

Not sure if it has to do with the new build yet. Could you start a new forum thread and duplicate your post there? Thanks.
profile picture

Eugene

#13
On second thought, the mandatory upgrade of the QWhale Editor (now Alternet) to get 6.9.20 working is the culprit behind the Neuro-Lab failure. :(.
profile picture

JJames

#14
Hello, I had same issue following the update. I found two installations and deleted the new one (today).
Now my Yahoo! data provider has disappeared. Any suggestions?
profile picture

kazuna

#15
The upgraded editor is giving me a lots of headache. (probably I will report them later on a new thread)
Any reason for the upgrade?
profile picture

Eugene

#16
@JJames

Try to reinstall it from our website (click) and restart WLP.

@kazuna

Yes, a grave one (that I'm not authorized to disclose).
profile picture

Eugene

#17
To WLP 6.9.20 users out there:

Sorry for any inconvenience the upgrade brings. We're paying close attention to every problem report and will act accordingly.
profile picture

LenMoz

#18
What's the status? All my strategies use Neurolab. At this point I am quite happy with my 6.9.19 install. IMHO 6.9.20 should be recalled.
profile picture

jheffez

#19
Agree with LenMoz. 6.9.20 is a disaster!

Issues I have with it:

1. Won't recognize extensions. Even if do clean install WL.
2. Won't recognize the editor colors,
3. Lots of compile errors to the point I can't run my C# code.

If I revert back to 6.19 everything works. However, after login I get the real-time agreement pop up and the pdf link/script does not show anything so I'm screwed with both 6.19 and 6.20.. Please helppppp
profile picture

Eugene

#20
QUOTE:
However, after login I get the real-time agreement pop up and the pdf link/script does not show anything so I'm screwed with both 6.19 and 6.20..

The issue is already being discussed on the forum, please use this thread for suggestions:

WLP 6.9.20 asks to sign a real time data agreement which blocks the login

QUOTE:
1. Won't recognize extensions. Even if do clean install WL.
2. Won't recognize the editor colors,
3. Lots of compile errors to the point I can't run my C# code.


#1. Some built-in extensions are reverted by 6.9.20 to their old versions (ASCII, Yahoo, TASC). Some may be deleted during uninstall of 6.9.20 and reinstall of 6.9.19. It's recommended that you reinstall all extensions required by your workflow.

#2. "The Editor colors are back to default" is not something specific to 6.9.20, I guess it's a combination of the major Editor version upgrade and having applied a custom color scheme. You'll have to simply reconfigure it I guess.

#3. Another symptom of missing extensions on which your Strategy are dependent. (If you get red squiggles in the Editor that's just a cosmetic issue.)

P.S. As for other potential issues of 6.9.20 you might be interested in checking out existing forum threads for workarounds:

https://www.wealth-lab.com/Forum/Posts/WLP-6-9-20-7-has-compiler-error-with-LINQ-methods-39743
https://www.wealth-lab.com/Forum/Posts/WLP-6-9-20-7-Missing-Extension-Manager-in-Tools-menu-39747
https://www.wealth-lab.com/Forum/Posts/WLP-6-9-20-7-New-Editor-red-squiggles-and-XML-parsing-code-39744
https://www.wealth-lab.com/Forum/Posts/WLP-6-9-20-7-New-Editor-is-too-verbose-39740
https://www.wealth-lab.com/Forum/Posts/WLP-6-9-20-7-Editor-puts-red-squiggles-for-WealthLab-Chartstyles-Trending-DLL-39742
https://www.wealth-lab.com/Forum/Posts/Neuro-Lab-failing-after-WLP-6-9-20-7-update-39737
profile picture

jheffez

#21
QUOTE:
The issue is already being discussed on the forum, please use this thread for suggestions:

WLP 6.9.20 asks to sign a real time data agreement which blocks the login


I tried that. My issue is not with 6.9.20 - It does not prompt me for the real time agreement. It's with 6.9.19. There are too many issues with X.20 and right now I need to get back to X.19.
profile picture

Eugene

#22
Except the broken Neuro-Lab and some really cosmetic issues with the Editor, the issues brought by the 6.9.20 can be resolved. It's advised to upgrade as 6.9.20 fixes the real-time agreement deadlock.
profile picture

jheffez

#23
QUOTE:
Except the broken Neuro-Lab and some really cosmetic issues with the Editor, the issues brought by the 6.9.20 can be resolved. It's advised to upgrade as 6.9.20 fixes the real-time agreement deadlock.


Attached snippet of errors. This is a DLL that is stored in the program dir and works fine with X.19.

profile picture

Eugene

#24
In my reply to you in post #20 I referred to 2 existing forum threads with a workaround for exactly this known issue. If you haven't had time to check them out yet, please do so now:

https://www.wealth-lab.com/Forum/Posts/WLP-6-9-20-7-New-Editor-red-squiggles-and-XML-parsing-code-39744
https://www.wealth-lab.com/Forum/Posts/WLP-6-9-20-7-has-compiler-error-with-LINQ-methods-39743
profile picture

haytac

#25
thanks for bringing in a new editor
as you may recall my strategy is approaching 300,000 lines of code
i have yet to test it on the other systems that i have
but so far so good
how much faster should i expect it to be for edits?
will it be slower as it checks all of the code for minor changes?
profile picture

Eugene

#26
Frankly, haven't heard of testing such gigantic code in dev or Q&A environments as it's uncommon (not a popular use case). As we're mostly focusing on 6.9.20 issues in this thread I'd appreciate if you would start a new topic for your general questions or concerns re: Alternet Editor (in the sense they differ from what the community has already found out):

https://www.wealth-lab.com/Forum/Posts/WLP-6-9-20-7-New-Editor-red-squiggles-and-XML-parsing-code-39744
https://www.wealth-lab.com/Forum/Posts/WLP-6-9-20-7-New-Editor-is-too-verbose-39740
https://www.wealth-lab.com/Forum/Posts/WLP-6-9-20-7-has-compiler-error-with-LINQ-methods-39743
https://www.wealth-lab.com/Forum/Posts/WLP-6-9-20-7-Editor-puts-red-squiggles-for-WealthLab-Chartstyles-Trending-DLL-39742
https://www.wealth-lab.com/Forum/Posts/WLP-6-9-20-7-New-Editor-and-double-byte-characters-39741

UPDATE:

FWIW, WL keeps the new Editor's preferences in a new file EditorSettings2.xml. It's likely that customizations to the old Editor's settings aren't migrated. To reiterate, users who have customized the Editor will have to reconfigure it after upgrade to 6.9.20.
profile picture

mkbryan

#27
Just downloaded 64-bit WLP from https://www.fidelity.com/wlp and checked the file properties. The detail tab show version 6.9.19. Is this a typo or is 6.9.20 not yet on the fidelity page? Hopefully we can all avoid a waste of time with the uninstall/re-install process.
profile picture

Eugene

#28
@mkbryan

The installation package's file size undoubtedly indicates this is 6.9.20. The installed size is twice as big as 6.9.19 due to inclusion of Editor's an related DLLs.

UPDATE 07/19/2019:

The team has been aware and will fix it in the next build. In fact this (incorrect version number) is a big factor to the trouble with the 64-bit installation of 6.9.20.
profile picture

gbullr

#29
Problems after upgrade.

Strategy not generating trades.

getting this error despite loading community components?

Runtime error: object references not set to an instance of an object.
@Wealthlab strategies my strategies execute
@wealthlab wealthscrypt get external symbol
@wealthlabpro chartform
@wealthlabpro mainmodule.loadexternal symbol

What else do I need to load. Thank you.
profile picture

Eugene

#30
Please check this out: Missing non-Fidelity extensions after update to 6.9.20. If that does not apply and you did restart WLP after re-installing Community Components which doesn't fix it then please start a new topic for your issue.

profile picture

mkbryan

#31
Just closing the loop. Just now uninstalled 6.9.19 and then installed 6.9.20 - no reboot after uninstall. When launching after new install, there's no Nasdaq agreement prompt . Updated non-Fidelity extensions successfully (Community Components). Logged in to Fidelity successfully. Turned on Fidelity streaming and got the first (and only) streaming bar today (Saturday) as expected. Ran a Visual Studio compiled strategy successfully. So, I'm good to go.
profile picture

Eugene

#32
To everyone affected by the WLP 6.9.20.7 upgrade which broke Neuro-Lab. NL v2019.08 with fix is out, for more details please see this post: Neuro-Lab failing after WLP 6.9.20.7 update
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).