Errors | General

Modified on 2021/03/13 11:54 by Eugene — Categorized as: Knowledge Base

Installation issues



Problem:

Installation of WLD 6.9.23 fails at installing .NET 4.6.2+ stage with error message"

"Installation Did Not Succeed.
.NET Framework 4.6.2 has not been installed because:
 A certificate chain processed but terminated in a root certificate which is not trusted by the trust provider."

Solution:

You're running outdated, unsupported and insecure Windows 7. Upgrade it to a modern operating system i.e. Windows 10, or at the very least to Windows 7 Service Pack 1. It's required for .NET 4.6.2+ to install and run.



Connection and activation problems



Problem:

You can't activate the 30-day trial or an activation key because Wealth-Lab throws an exception:

System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required.

Solution:

  1. At first, please make sure that your computer is configured to let Wealth-Lab connect to the authentication server: Which ports need to be opened to activate Wealth-Lab Developer 6?
  2. (Does not apply to recent WL versions from 6.4 and higher.) If that didn't help, then the problem is caused by a documented bug with proxy authentication in Microsoft .NET 2.0. It has been patched but the patch is actually in the .NET 3.5 installation. Please install the following .NET 3.5 patch from Microsoft to fix the problem Microsoft .NET Framework 3.5 Service Pack 1
  3. One more workaround to try:
    • Download this Zip file containing patched version of the WealthLabDev.exe.config file.
    • Close WLD6.
    • Unpack this file to \Program Files\MS123\Wealth-Lab Developer 6\, replacing existing WealthLabDev.exe.config.
    • Start WLD6 and try again.
  4. If nothing helps, you will have to switch to a direct connection to the internet.

Problem:

When you try to run the application, the Activation Wizard is opened, you register for a free trial (or activate your key), then the application doesn't start.

Solution:

If you have trouble starting WL6 for the first time, right-click the shortcut and select "Run as administrator" even if you're logged in as admin.

Problem:

The Activation Wizard refuses to activate/authenticate a trial/a key with the following exception message: "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel."

Solution:

  1. First and foremost, ensure your PC clock is correct. This message could indicate that your clock is ahead too much, making the secure certificate appear expired. Otherwise look in this Microsoft knowledge base article for possible workarounds.
  2. If using an unsupported operating system like Windows XP or Server 2003, the problem may arise from its outdated Internet Explorer component which has trouble making secure "handshaking" with our server that no longer supports SSL 3.0 due to POODLE exploit: Fix for critical 'POODLE' attack against SSL 3.0 could break Web for Internet Explorer 6. If the problem persists after making sure your PC clock is correct, consider switching to a modern operating system. Also note that it won't be possible to install latest Wealth-Lab version because it's incompatible with unsupported Windows XP/2003.
  3. Other ideas to try:
    • Add any live proxy that supports HTTPS connections to Windows Control Panel > Internet Options (search within the many lists of free proxies on the web).
    • If already using a VPN, change country.
    • In Windows Internet Options, clear browser cache and clear SSL state, then restart
    • Add WealthLabDev.exe to the antivirus/firewall greenlist. As an alternative, disable your firewall and/or antivirus or their HTTPS scanning feature in particular.

Problem:

The Activation Wizard refuses to activate/authenticate a trial/a key with the following exception message: "Exception: The underlying connection was closed: An unexpected error occurred on a send."

Solution:

Disable your antivirus or add Wealth-Lab to its whitelist.

Problem:

You're using a corporate PC. The Activation Wizard refuses to activate/authenticate a trial/a key with the following exception message: ""ERROR: Unable to determine PC Fingerprint. This implementation is not part of the Windows Platform FIPS validated cryptographic algorithm""

Workaround:

  1. Open regedit.exe, go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa.
  2. Under a subkey you should see FipsAlgorithmPolicy
  3. Change the "Enabled" DWORD from 1 to 0
  4. Reboot Windows if required.

If the FIPS policy is enforced on startup by your employer, prior to starting Wealth-Lab you can run a script that loads the key into the system registry using reg.exe. You can save the FipsAlgorithmPolicy key using regedit.exe to a .reg file and load that with reg.exe (admin privileges required).

Problem:

The Activation Wizard dialog pops up each time you start Wealth-Lab Developer.

Solution:

Make sure that the system AppData\Local folder is not cleared after exiting the program, like in some (paranoiac) security configurations.



Wealth-Lab crashes on start



General troubleshooting procedure:

  1. Please create a support ticket.
  2. Reproduce the error
  3. If there's a link like "What data does this error report contain?", copy the "Error signature" data and paste it into the ticket text.
  4. Find your User \Data folder. Enable hidden file visibility if required: How to show hidden files in Windows. The folder name may read different if you're a user of localized Windows (e.g. C:\Benutzer in German Windows).

    C:\Users\Windows User Name\AppData\Roaming\Fidelity Investments\WealthLabDev\1.0.0.0\Data\
  5. In \Data\Workspaces, rename the Default.ws file if it exists. Start WLD.
    Did it help? -> Zip and attached the Default.ws file to the ticket. (If you used both 32 and 64-bit versions and have installed extensions for one version and not the other, the default workspace may be trying to initialize a component that does not exist, for example, a Chart Style.)
  6. Above the \Data folder, rename the WealthLabDev parent folder; WealthLabDevX for example. Start WL6.
    You can now close WL6 (the WealthLabPro/Dev directory structure will be recreated). Did it help? -> There's something in the user data that the Wealth-Lab support team need to find, or you can do this yourself:
  7. Copy:
    • ..\WealthLabDevX\1.0.0.0\Data\Strategies to \WealthLabDev\1.0.0.0\Data\Strategies
    • ..\WealthLabDevX\1.0.0.0\Data\YahooStaticProvider to ..\WealthLabDev\1.0.0.0\Data\YahooStaticProvider
    • ..\WealthLabDevX\1.0.0.0\Data\DataSets to ..\WealthLabDev\1.0.0.0\Data\DataSets
  8. Sometimes, crash can be caused by rare reasons such as:
    • conflicting libraries (DLLs) that you placed in WLD/WLP's main folder. In this case, uninstall the software, rename the Wealth-Lab's main folder under Program Files, and then reinstall it (but do not download any Extensions and do not copy your own DLLs yet).
    • antivirus removing WealthLab.Extensions.Agent.exe on installing or updating an extension. (For example, Avast's CyberCapture is known to delete said file, causing crash on restart of WLP/D. In this case, turn off CyberCapture and repair your WLP/D installation from Windows Control Panel).
    • HDD (SSD) failure
  9. If none of the above worked, we'll try to help more in the ticket.



Problem:

The application can't be opened, the error report dialog pop up.

Solution:

Most likely, you're running Wealth-Lab .NET from a normal user account which doesn't have admin rights. Give the Users group Modify and Write rights to:


Problem:

The application crashes with the following error message:

"The initialization of the application is not correct (0xc0000135). To close the application please click OK button."

Solution:

Install Microsoft .NET 4.5 Framework and higher (if it isn't installed). If v4.5 or 4.6 is already installed and you still get the error message, make sure that the file mscoree.dll isn't missing, or simply repair your .NET 4.5 installation.

Problem:

The application doesn't start (cannot be found in the Task Manager), reinstallation and general troubleshooting procedure do not help.

Solution:

If you're unable to launch an app in Windows 10, supposedly your Windows user account is misconfigured. A workaround is to create a new user account and copy over your Strategy and config files to that account as per Step 7 of the Procedure above.



Wealth-Lab crashes on start after changing regional settings



Problem:

After changing regional settings in Control Panel, Wealth-Lab crashes on start with 'system.typeinitialization exception'.

Solution:

Find WealthLabConfig.txt in Wealth-Lab data folder:


  1. Either completely delete the file and start Wealth-Lab from scratch,
  2. or find all lines that contain dates and look like this:

DataRange=FixedBars;1000;10;01.05.1998 0:00:00;30.04.2008 0:00:00
...
StrategyRankings.DataRange=FixedBars;500;10;01.09.1999 0:00:00;31.08.2009 0:00:00

Delete either the whole line or the values leaving the key ( e.g. DataRange= ) in place.



Wealth-Lab suddenly crashes when backtesting a symbol with large intraday history



Problem:

Scenario:

You successfully backtest a symbol with large intraday history (say 1 million bars). After changing some settings, Wealth-Lab suddenly crashes in runtime with StackOverflow exception.

You're not expected to ever experience this issue unless you have tried almost every tool from the toolbox: used a hundred Indicators, PosSizers etc. Their settings get stored in Wealth-Lab's config file. When your system happens to create a lot of trades (e.g. a dozen thousand), the multitude of saved preferences makes Wealth-Lab exhaust the stack memory space and crash.

Solution:

Before anything else, to work with large intraday history you should do the following:

  1. Use 64-bit Wealth-Lab
  2. Install as much RAM as possible (at the very least 8GB but preferably 16-32 GB)
  3. Disable as many performance visualizers as possible, Heat Map in the first place

Find WealthLabConfig.txt in Wealth-Lab data folder:


Completely delete the file and start Wealth-Lab from scratch.



Wealth-Lab Pro 6.5 crashes on start with System.TypeInitialization in WealthLab.ChartControl



Problem:

After clean install or upgrade, Wealth-Lab Pro 6.5 crashes on start with System.TypeInitialization exception in WealthLab.ChartControl.

Solution:

Download and reinstall latest Microsoft .NET 4.0 or 4.5 from Microsoft's website.



Wealth-Lab crashes when executing a Strategy that generates an Alert (Sound)



Problem:

Scenario:

Wealth-Lab crashes unrecoverably when a Strategy generates an Alert.
Solution: