"Not installed": Can't find Community Extensions after installation in WLP 6.9.18
Author: kcbars
Creation Date: 7/13/2017 5:18 PM
profile picture

kcbars

#1
Hello. I installed v 6.9.18 yesterday, and the community components and community indicators extensions don't seem to install correctly. I get the pop up screen saying they were added, but when I run wealth lab they aren't there. This is a brand new installation on a computer that has never had wealth lab installed. Is there a way to insert them manually? Thanks.
profile picture

Eugene

#2
1. Having confirmed UAC prompt, did the popup show a "Success" for both the extensions?
2. Do you have WLP 32-bit and 64-bit installed side by side?
3. Does the WLP main folder under Program Files contain these 3 files: HtmlAgilityPack.dll, WealthLab.Components.Community.dll and WealthLab.Indicators.Community.dll? What are their date and size?

More troubleshooting suggestions:

Extension installed in Wealth-Lab Developer doesn't show up after restarting application.
profile picture

kcbars

#3
Yes, prompt showed success for all extensions.
No, have only installed 64 bit.
Yes, has all three files dated today, 132, 158, and 284 kb respectively.

I checked the link above, and none of these files have a "file downloaded from internet" designation in properties.

Thanks.
profile picture

Eugene

#4
Looks OK to me. How have you determined exactly that they aren't there?
profile picture

kcbars

#5
The first clue was that strategies wouldn't run correctly. I looked in extension manager, changed it to other extensions, and the community items weren't there. I could then drag and drop the downloaded files to extension manager again, and they re-installed (normally I get the "this is already installed/up to date, are you sure?). I also tried installing all the others that show as not installed (ASCII static, Yahoo finance, etc.), and the same thing happens. It says they are successful, but when I start the program it says they are not installed. On my older computer with the previous version, I uninstalled wealth-lab, downloaded the new version, installed it, and everything is fine.
profile picture

Eugene

#6
Thanks for the thorough problem description. It's non standard program behavior and I hardly have a clue. This looks like a misconfiguration of your Windows environment, or to be precise something is deleting the files on your PC. For example, some paranoiac security configurations in corporations clear the entire AppData\Local folder on program exit (this isn't exactly your case as we're talking about Program Files here). Some antivirus, sandbox utility or system protection software - it's up to you to figure that out.
profile picture

kcbars

#7
The really strange thing is it worked fine yesterday - I was able to optimize strategies, etc. I've turned off everything I can think of, antivirus, firewall, etc., and it seems the only extension that it will keep installed is the tasc indicators. But oh well.
profile picture

Eugene

#8
1. Make a backup copy of those 3 DLLs with "file downloaded from internet" cleared to avoid reinstallation and make sure that it's not a WL issue.
2. Close WLP, copy the files into the WLP main folder, start WLP, close WLP.
3. Are the files still around?
profile picture

kcbars

#9
Yes, they are still there.
profile picture

Eugene

#10
Supposedly this is the first occasion of Wealth-Lab removing extensions at its own will. I still think there's something else behind this, security-related.

At least you have the workaround.
profile picture

kcbars

#11
Hi. I've discovered that the extensions are there and working, but they just don't show up inside extension manager. And for the ones that come uninstalled with the program, you can install them, but they still show as not installed inside extension manager. This is the first time I've installed the software in windows 10, so maybe that has something to do with it? It's strange because some of them show up (TASC indicators, genetic optimizer), and some do not (community components/indicators). Thanks.
profile picture

Eugene

#12
Hi,

You probably haven't switched to "Other Extensions". Mentioned extensions aren't "Fidelity supported" and for this reason have always been listed under "Other Extensions". Almost for a decade now.
profile picture

kcbars

#13
No, I switched - nothing appears under "Other Extensions" for some reason.
profile picture

Eugene

#14
There's clearly something odd with your computer's software configuration. Nobody seems having similar issues as you in this thread. If they wouldn't work I'd suggest to uncheck that "downloaded from the internet" flag but since you say they work I'm not sure what's happening.

@Cone

Robert, can you see the "Community" libraries listed under "Other Extensions"?
profile picture

akashj303

#15
QUOTE:
Nobody seems having similar issues as you in this thread.


I have just encountered the same issue. To summarize - New computer, copied Data folder contents and .dlls into their respective folders. All strategies working as intended so everything ported over just great except Extension Manager is unable to recognize any of the "Other Extensions" (all tabs empty) and 5 of the Fidelity supported extensions. Interestingly, 2 of the Fidelity Supported Extensions do get installed successfully - "Neuro-Lab" and "TASC Magazine Indicators". For all others, it's an endless loop - Install, Restart to finish, Successfully installed message, but Extension manager does not recognize.

All other checks mentioned here and in the Wiki either do not apply or are successfully passed. Uninstalled/deleted everything and tried again without porting over any of the folders/files from old install. Same result as above, so it would seem the porting process is not at fault.

OS: Windows 10 Pro ver 1809 (same as old computer).
profile picture

Cone

#16
I've personally never seen this from copying files between computers, but dlls won't be recognized if the zone identifier changes, otherwise known as the "downloaded from the internet" security warning.

If this is the problem, you should be able to clear this in a batch fashion by copying the dlls to a pen drive and then to/back to the destination. Otherwise, you'll need to copy the files to the desktop (or another neutral location) and one-by-one right click > Properties > General > Unblock.

Let us know that does the trick!
profile picture

akashj303

#17
I haven't seen it either Cone, and none of the files have that property set after copying.

Moreover, in my second test mentioned above there was no copying of files involved. The .dlls are getting created (using the normal install process), but still not recognized by Extension Manager.
profile picture

Eugene

#18
0. Double check the "bitness" of WLP (32-bit, 64-bit) that you're actually running and the one whose DLL files you're examining. Do they correspond?

1. Before anything else, what is the complete list of extensions which are not recognized?

2. Extension Manager aside, are the "missing" extensions functioning? Like data provider is present in the New DataSet Wizard and/or is data can be updated, methods from C.Components are callable from Strategies etc.
profile picture

akashj303

#19
UPDATE: A bit embarrassing, but after a reboot overnight, the issue seems to have resolved itself. Not sure what changed other than the reboot. I think I had tried rebooting yesterday itself though, so not sure if that is the actual solution to this issue.

Cone/Eugene - Thanks for taking the time to respond and trying to help! Will update if anything appears erratic again on this.
profile picture

Eugene

#20
Glad that you got it resolved automagically ;)

To some extent this behavior might resemble the one of an antivirus quarantine.
profile picture

akashj303

#21
QUOTE:
Glad that you got it resolved automagically ;)

Sometimes the elves come in handy ;)

QUOTE:
To some extent this behavior might resemble the one of an antivirus quarantine.

Possibly. I've never liked McAfee which came preinstalled on the new rig. So let's go with that. :)
profile picture

kazuna

#22
I just found one of my computers having this issue.

Apprently Extension Manager.isn't correctly recognizing the installation status.
The extension itself seems working fine but it's just Extension Manager not recognizing them.

I can install/uninstall Neuro-Lab and TSAC but nothing else.
Even if I install [Other Extensions] or copy those DLL from other working computer, Extension Manager show "No items to display".
But these extensions (e.g. Community.Components) are working fine in the strategy code even if Extension Manager doesn't show it.

kcbars,
How did you fix the problem? Apprently you were having the exactly the same issue.
profile picture

Eugene

#23
For akashj303 it helped to simply have the PC rebooted. Give this a try.

It's hard to tell considering that I don't know which extensions are installed. But I'd start with adding them one by one to a clean WLP installation and restarting WLP afterwards. Then check all the EM's four tabs with "Other Extensions" mode activated. Perhaps it's some particular one that breaks the EM?

P.S. Does the WLP folder have such files as ...

HtmlAgilityPack.dll
WealthLab.DataProviders.MarketManager.dll
WealthLab.Extensions.Attribute.dll

?
profile picture

kazuna

#24
Reboot doesn't fix the problem.

Yes, WLP folder has all those three files.

In fact, Neuro-Lab and TSAC extentions show up correctly in Extension Manager.
I can uninstall and install them on Extension Manager.
That means it works in some cases but doesn't work in most cases.

All other extemsions, Fidelity Supported Extensions and Other Extensions don't show up correctly in Extension Manager.
Extension Manager shows them as "Not Installed" even if they are installed and working fine in the code.
profile picture

Eugene

#25
I think that the "Not Installed" status may mean some failure to connect and query the wealth-lab.com server for extension status. Potential culrpits on your PC include the firewall, antivirus etc.
profile picture

kazuna

#26
I have firewall turned off and I never install 3rd party anti-virus and anti-malware softwares on those trading computers.
All those trading computers are configured to the same setting and one of them is having this problem.

Where are the extension informations stored other than the DLLs in WLP program folder?
profile picture

Eugene

#27
Disregard my previous comment in post #25. The culprit here is some extension, including but not limited to:

1. your very own, custom built DLL
2. some MS123 extension compiled by you from the source code (read: from the WL Wiki)
3. a duplicate extension DLL copied inadvertently e.g. in Windows Explorer
4. a 3rd party DLL obtained not from wealth-lab.com

It's something about the incorrect ExtensionInfo attribute in this DLL that makes the EM stumble. To fix it, move out all DLLs not included with the WLP installation and then start adding them one by one, restarting WLP and checking the EM until it "breaks". Focus on your DLLs, I'm pretty sure that no Extension published on our website is to blame.
profile picture

kazuna

#28
I don't have any DLLs other than Fidelity Supported Extensions and MS123 extensions.
As I stated earlier, I copied WLP folder from working system but the results are the same.
I will try installing fresh WLP and adding extensions one by one.
profile picture

Eugene

#29
OK please let us know if you discover something.
profile picture

superticker

#30
If you're running WL 6.9.20.X, it "might" require component libraries built for the newest .NET framework before the Windows loader will load them. The old WL 6.9.19 app used .NET framework 4.6.2. I'm guessing WL 6.9.20 needs more recent libraries built for .NET framework 4.7.X (or later) to load these libraries. Can someone confirm this? What .NET version is WL 6.9.20.X using now so I can recompile my own libraries for loading compatibility?

Anyway, my suggestion is to download the newest build of all your WL libraries from the WL website and install those with Extension Manager if you're running WL 6.9.20. Just my 2-cents.
profile picture

kazuna

#31
No, this one is still running on WLP 6.9.19.

By the way, WLP 6.9.20 seems using the same .NETFramework 4.6.2 according to WealthLabPro.exe.config.
CODE:
Please log in to see this code.
profile picture

kazuna

#32
QUOTE:
OK please let us know if you discover something.

I installed fresh WLP 6.9.19 and 6.9.20 but neither fixes the problem.
Adding extension one by one also doesn't fix it.

Apparently something other than WLP's setting seems causing the issue.
Is it some sort of .NET Framework cache or something?

How does Extension Manager look up those extensions in the Program directory?
Is it via .NET Framework query interface or something?
profile picture

Eugene

#33
What timestamps and file+product versions do these files have according to Windows Explorer?

WealthLab.Extensions.Agent.exe
WealthLab.Extensions.dll
WealthLab.Extensions.Attribute.dll

P.S.
QUOTE:
Is it some sort of .NET Framework cache or something?

They aren't cached if you mean "put into GAC" (global assembly cache).

QUOTE:
Apparently something other than WLP's setting seems causing the issue.

I rather think it's Extension Manager stumbling onto a "bad" extension and stopping listing it and other extensions that might follow. Let's not discard the idea in my post #25 above, though.
profile picture

kazuna

#34
These files are fine. I confirmed them by binary comparing with working systems.

2019/05/24 10:54 25,584 WealthLab.Extensions.Agent.exe
2019/05/24 10:54 14,848 WealthLab.Extensions.Attribute.dll
2019/05/24 10:54 189,936 WealthLab.Extensions.dll

In fact, I tried both fresh install and copying program files from working system but the issue persists.
That means this issue is not due WLP installation but something else.
profile picture

Eugene

#35
The file sizes do not match mine. Could you also share on the file and product versions? Thanks.

At the moment I have nothing to add to my suggestions in previous posts. It must be something specific to this PC and/or a "bad" DLL file (per post #27) that you haven't gotten removed. BTW, starting over implies deleting the entire "Wealth-Lab Pro 6" folder following uninstallation.
profile picture

kazuna

#36
WealthLab.Extensions.Agent.exe
File version 1.0.2.0
Product version 1.0.2.0

WealthLab.Extensions.Attribute.dll
File version 1.1.1.0
Product version 1.1.1.0

WealthLab.Extensions.dll
No version information

Yes, I deleted the entire "Wealth-Lab Pro 6" folder before installation.
profile picture

Eugene

#37
Thanks, the version numbers are in line. Sorry but I'm out of ideas right now. Just to confirm: all the extensions work fine (Strategies run, Neuro-Lab opens, data providers are present where they belong etc.) so the EM issue is cosmetic?
profile picture

kazuna

#38
Yes, it is cosmetic, sort of... but the real problem is the inability to update the extensions.
profile picture

Eugene

#39
Can't you update Extensions from the Extensions section of our website? Despite they being listed as "not installed" and no updates being found by the EM, there are 3 ways to install them from our website as instructed by this illustrated tutorial and/or the Wealth-Lab User Guide > Extension Manager.
profile picture

kazuna

#40
Yes, Drag & Drop works.

So once I notice an update on other system, I download it manually and drag and drop it into EM on the affected system.
It requires manual operation but perhaps it is the only workaround.
profile picture

Eugene

#41
Glad to help.

I'd like to discard the AV/FW connectivity issue as per post #25. While it's not a 100% indicator could you give this a try on the affected system:

1. Open Strategy > Download... (check "Download Public strategies" and uncheck "Published since...")
2. Open up 2 instances of a recent strategy, ideally S&C 2019-05, click on "Strategy Summary" tab, and there click on two links, one link per Strategy instance:

a. "Requires installed Community Indicators library version 2019.04 or higher." (www.wealth-lab.com)
b. "For more details, please visit this Wiki link." (www2.wealth-lab.com)

This should navigate the built-in browser component to the 2 domains of the WL website. Can you open them from within WL correctly? Assuming that WLP and WealthLab.Extensions.Agent.exe are greenlisted in your AV/FW software, of course.
profile picture

kazuna

#42
QUOTE:
While it's not a 100% indicator could you give this a try on the affected system:

Yes, I can open them from within WLP correctly.
profile picture

Eugene

#43
Hmm. Having read your response I thought it must be the built-in IE host that renders those pages. But traffic sniffer says it's WealthLab's own executable process indeed. So we can finally discard post #25 and my working hypothesis is still in post #27.

Please run this and attach the TXT file here:

dir "c:\program files\fidelity investments\wealth-lab pro 6" > c:\users\Windows username\documents\files.txt
profile picture

kazuna

#44
QUOTE:
Please run this and attach the TXT file here:

Here you are.
profile picture

Eugene

#45
Thanks.

1. Before anything else please update ASCII, it must be years old in 6.9.20:

2019/05/24 10:54 110,592 WealthLab.DataProviders.AsciiFilesStatic.dll

2. It's better if you get rid of these files completely:

2019/05/24 10:54 65,536 WealthLab.DataProviders.WL4Files.dll
2019/05/24 10:54 1,124,352 WealthLab.DataProviders.WL4Files.Win32DBClient.dll

Now if after WLP restart you don't see difference, close WLP and move out all these DLLs...

(Y! and MM)
2019/05/24 10:54 135,664 WealthLab.DataProviders.MarketManager.dll
2019/05/24 10:54 211,456 WealthLab.DataProviders.Yahoo.dll

(MS)
2019/05/30 11:45 35,840 WealthLab.DataProviders.MetaStockStatic.dll

(the ones you've manually installed yesterday)
2019/07/15 23:54 128,000 WealthLab.Optimizers.Genetic.dll
2019/07/15 23:54 33,280 WealthLab.Optimizers.Genetic.Test.exe
2019/07/15 23:54 432,640 WealthLab.Visualizers.MS123.dll
2019/07/15 23:54 72,704 WealthLab.Visualizers.MS123.Helper.dll
2019/07/15 23:54 52,224 WealthLab.Addins.DataTool.dll
2019/07/15 23:54 164,864 WealthLab.Components.Community.dll

...then start copying them back batch by batch and starting/closing WLP. Does it make difference in the EM?
profile picture

kazuna

#46
Unfortunately, no. It doesn't make any difference in the EM.

In fact, this is essentially the same I already tried by copying the program folder from the working system.
profile picture

Eugene

#47
Do the files from posts #34-#36 completely match the ones on the other PC which works? If so, it's a shame but I'm out of practical suggestions. Some other factors may be at play here which we hardly can determine without remote access.
profile picture

kazuna

#48
Yes, the files completely match with the ones on the other PC which works fine.
profile picture

kazuna

#49
Not sure if it is related but one thing I found which is specific to the affected system is the following folders are missing from "Program Files" and "Program Files (x86)" folders.

2018/12/07 19:29 <DIR> MSBuild
2018/12/07 19:29 <DIR> Reference Assemblies
profile picture

kazuna

#50
All right. I fixed it!

On Windows 10, open "Control Panel", then go Programs and "Turn Windows features on or off".
Enable ".NET Framework 3.5 (includes .NET 2.0 and 3.0)" and apply it.

It will install files in "MSBuild" and "Reference Assemblies" folders under "Program Files" and "Program Files (x86)" folders.

Now all extensions will show up in Extension Manager.

Apparently Extension Manager requires .NET 2.0, 3.0 or 3.5 to access the assemblies.

I have never uninstalled .NET Framework 3.5 and I have no idea why it is not installed.
profile picture

Eugene

#51
Thank you for posting the solution, I've just added it to the Wealth-Lab Wiki's Errors section. It's some new information to me.

Indeed you haven't uninstalled 3.5, it requires being enabled in "Windows Features" like you told.

Glad to finally hear the sigh of relief! :-)
profile picture

superticker

#52
QUOTE:
Apparently Extension Manager requires .NET 2.0, 3.0 or 3.5 to access the assemblies.
So things work "by default" under Windows 7, but fail to work by default under Windows 10. Interesting--good it know. Sounds like the WL InstallShield installer wasn't configured right to install .NET 3.5 under Windows 10, if necessary.

I would "attempt" to construct the WL build so it automatically works by default under Windows 10 without having to worry about OS (or framework) backward compatibility issues. That's InstallShield's job.
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).