Connection and activation problemsProblem:
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.
- 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?
- (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
- 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.
- If nothing helps, you will have to switch to a direct connection to the internet.
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.
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:
- 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.
- 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.
- 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.
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.
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 startGeneral troubleshooting procedure:
- Please create a support ticket.
- Reproduce the error
- 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.
- 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).
- Windows XP, Windows Server 2003:
C:\Documents and Settings\Windows User Name\Application Data\Fidelity Investments\WealthLabDev\22.214.171.124\Data\
- Windows Vista, Windows 7
C:\Users\Windows User Name\AppData\Roaming\Fidelity Investments\WealthLabDev\126.96.36.199\Data\
- In \Data\Workspaces, rename the Default.ws file if it exists. Start WLP.
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.)
- Above the \Data folder, rename the WealthLabPro parent folder (or WealthLabDev if you're a Developer 6 user); WealthLabProX 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:
- ..\WealthLabProX\188.8.131.52\Data\Strategies to \WealthLabPro\184.108.40.206\Data\Strategies
- ..\WealthLabProX\220.127.116.11\Data\FidelityStaticProvider to ..\WealthLabPro\18.104.22.168\Data\FidelityStaticProvider
- ..\WealthLabDevX\22.214.171.124\Data\YahooStaticProvider to ..\WealthLabDev\126.96.36.199\Data\YahooStaticProvider - for Developer 6 users
- ..\WealthLabProX\188.8.131.52\Data\DataSets to ..\WealthLabPro\184.108.40.206\Data\DataSets
- 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
- If none of the above worked, we'll try to help more in the ticket.
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
- Wealth-Lab Pro 6: C:\Program Files\Fidelity Investments\Wealth-Lab Pro 6\
- Wealth-Lab Developer 6: C:\Program Files\MS123\Wealth-Lab Developer 6\
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:
Failure to properly initialize any .NET application with error 0xc0000135 simply means that you don't have Microsoft .NET 4.0
Framework installed, or its version is unsuitable, or your installation was broken. Download it for free from Microsoft if you have Windows XP (.NET is built in Vista and Win7) and install to run Wealth-Lab Developer 6.
If you do have .NET 4.0 on your computer and still get the error message, make sure that the file mscoree.dll
isn't missing, or simply repair your .NET 4.0 installation.
(Applied to Wealth-Lab Developer V5.1
Wealth-Lab crashes on start after changing regional settingsProblem:
After changing regional settings in Control Panel, Wealth-Lab crashes on start with 'system.typeinitialization exception'. Solution:
in Wealth-Lab data folder:
For Wealth-Lab Developer
- Windows XP: "c:\Documents and Settings\user name\Application Data\Fidelity Investments\WealthLabDev\220.127.116.11\Data\WealthLabConfig.txt"
- Windows 7, Vista: "c:\Users\user name\AppData\Roaming\Fidelity Investments\WealthLabDev\18.104.22.168\Data\WealthLabConfig.txt"
For Wealth-Lab Pro
- Windows XP: "c:\Documents and Settings\user name\Application Data\Fidelity Investments\WealthLabPro\22.214.171.124\Data\WealthLabConfig.txt"
- Windows 7, Vista: "c:\Users\user name\AppData\Roaming\Fidelity Investments\WealthLabPro\126.96.36.199\Data\WealthLabConfig.txt"
- Either completely delete the file and start Wealth-Lab from scratch,
- 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 historyProblem: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:
- Use 64-bit Wealth-Lab
- Install as much RAM as possible (at the very least 8GB but preferably 16-32 GB)
- Disable as many performance visualizers as possible, Heat Map in the first place
in Wealth-Lab data folder:
For Wealth-Lab Developer
- "c:\Users\user name\AppData\Roaming\Fidelity Investments\WealthLabDev\188.8.131.52\Data\WealthLabConfig.txt"
For Wealth-Lab Pro
- "c:\Users\user name\AppData\Roaming\Fidelity Investments\WealthLabPro\184.108.40.206\Data\WealthLabConfig.txt"
Completely delete the file and start Wealth-Lab from scratch.
Wealth-Lab Pro 6.5 crashes on start with System.TypeInitialization in WealthLab.ChartControlProblem:
After clean install or upgrade, Wealth-Lab Pro 6.5
crashes on start with System.TypeInitialization
exception in WealthLab.ChartControl
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.
- This occurs when a non-PCM wav file (like any in C:\Windows\Media\subfolder\*.wav) is selected and Alert sounds are enabled.
- Choose only wave files that are PCM-formatted like those provided in the Wealth-Lab installation folder (C:\Windows\Media\*.wav files are probably okay). Other types and codes are unsupported.
Wealth-Lab throws a TimeZoneInformation exception
Applies to Wealth-Lab Pro 5.Problem:
After logging in to Fidelity and clicking on Streaming
, the type initializer for "Fidelity.Components.TimeZoneInformation" throws a system.typeinitialization
System.TypeInitializationException was unhandled
Message="The type initializer for 'Fidelity.Components.TimeZoneInformation' threw an exception."
: Wealth-Lab 6 is not compatible with Windows 2000.Windows XP and above
: Here's a solution to this problem found by our user wlxyz
"Apparently the upgrade fix to TimeZone updates, KB955839, is supposed to supersede KB951072. This is simply not true as KB951072 upgrades the registry with additional timezones and probably does something else besides that the most recent patch does not correct. Once I uninstalled KB955839, and installed KB951072 the timezone changed from central standard time to central daylight time. I verified the difference between 2 PCs on how the timezone is displayed and they are now synced and both work as they should. I manually updated the time on the PC with WL5.3 problem before but now that is not needed.
At least in my case the following steps appear to have fixed WL5 TimeZone issue:
- Uninstall KB955839
- Download the following patch from Microsoft
- Install KB951072
- Reinstall KB955839
- Uninstall WL5
- Re-install WL5"
System.FormatException: Input string was not in a correct formatProblem:
Charts/strategies using static
data fail with the following exception while streaming
charts work fine:
System.FormatException: Input string was not in a correct format"
Additionally, the HeatMap visualizer may
fail to load with this error message, although you are sure that your PC has .NET 3.5 SP1 installed:
"There is some problem occurred while loading Headmap. /nPlease ensure that you are having .NET runtime version 3.5+"Solution:
Windows regional settings were the culprit. All this trouble is caused by changing the symbol used to display positive numbers
. It should be and is typically empty, but if it contains a symbol or even an invisible char like space
, you can get all sorts of errors in financial and spreadsheet software. Do the following:
- Open the Regional and Language Options applet from the Control Panel.
- Note the Current Format.
- Change the Current Format to English (Australian)
- Click Apply.
- Change the Current Format to the noted format, eg, English (American).
- Click Apply and then click OK.