I have two symptoms to what I'm hoping is just one problem - or I have two problems that have both recently appeared in WLP 5.6.

The first one that I ran into is that I have not been able to download Fidelity data since March 2nd. I have downloaded many many times from Fido in the past, and I have no idea of anything that has changed in the setup. Here are a couple of things I've verified in my process of elimination:
- I can download from MSN, Google, Yahoo, etc...
- I can download to my desktop computer also running a nearly identical setup of Win7, Macafee, etc...
- I have tried downgrading to 5.5, I've tried upgrading to 5.6. I've tried "hiding" all of my data files (so WLP creates a fresh set of stock datasets, WealthLab100 etc..., I've even uninstalled and reinstalled the program entirely.

The actual failure is that when I try to update a dataset (or update data for all datasets) involving fidelity, the program begins the download, and then closes it less than a second later. Looks like this:

QUOTE:
Updating DataSet Broadline ...
Update completed (0.4 sec)
----------------

The OTHER problem, is that when I try to run a strategy on Fidelity data, it fails to run saying

QUOTE:
Runtime Error: CurrentTimeZone not found
at WealthLabPro.ChartForm.p()
at WealthLab.BarsLoader.GetData(DataSource ds, String symbol)
at WealthLab.DataProviders.FidelityStaticProvider.RequestData(.......

There are 3 or 4 more at WealthLab lines and then it ends with

QUOTE:
at Fidelity.Components.TimeZoneInformation.get_CurrentTimeZone()

This doesn't happen when I run the strategy on a Yahoo dataset.

I spent two very frustrating calls with Fidelity tech support both ending up in "not sure what to tell you, that's weird". I probably should have come here first and saved myself a couple of hours.

Please help! This is a major bummer for an otherwise rock solid product

Usually, when on very rare occasions it happened, restarting the program was a cure for the "instant update" quirk. But since you've already reinstalled WLP, that must be a different issue.

1. Can you take a look at what does "...\WealthLabPro\1.0.0.0\Logs\wlp.txt" in %AppData% show? (I doubt that LastUpdateLog.txt will contain any new information, hence the interest in the main log file.)

2. When you say:

QUOTE:
"hiding" all of my data files (so WLP creates a fresh set of stock datasets, WealthLab100 etc...,

Do you mean actually hiding the data files (i.e. Fidelity's BarDataStore - the directories starting with Fidelity* and containing *.WL files), or just the DataSets (i.e. XML descriptions), making Wealth-Lab create them from scratch (i.e. taking them from Program Files\Fidelity Investments...) but leaving the actual data as is?

QUOTE:
Runtime Error: CurrentTimeZone not found

It happens when WLP can't identify your time zone e.g. when returned description of the time zone of the computer is incorrect.

First and foremost - What exactly is your current time zone? What is the output of this code snippet (if you run it on non-Fidelity data):

CODE:
Please log in to see this code.

Anything specific about the computer clock, region, regional settings?

1)

Lots and lots of these errors, but I just went to update a bunch of datasets from Fidelity, then closed and restarted, and that didn't cause any of these types

QUOTE:
2010-03-25 22:45:45,910 [1] ERROR WealthLabPro.ChartForm [(null)] - Index was outside the bounds of the array.
2010-03-25 22:45:45,921 [1] ERROR WealthLabPro.ChartForm [(null)] - Index was outside the bounds of the array.
2010-03-25 22:45:45,923 [1] ERROR WealthLabPro.ChartForm [(null)] - Index was outside the bounds of the array.

It did, however, throw these errors

QUOTE:
2010-03-26 12:48:21,626 [1] ERROR WealthLabPro.MainModule [(null)] - Inside ManiModule, trying to create the instance of Visualizers
2010-03-26 12:48:21,811 [1] ERROR WealthLabPro.MainModule [(null)] - The exception message is Exception has been thrown by the target of an invocation.
2010-03-26 12:48:21,811 [1] ERROR WealthLabPro.MainModule [(null)] - The inner Exception is Could not load file or assembly 'ZedGraph, Version=5.1.4.31904, Culture=neutral, PublicKeyToken=02a83cbd123fcd60' or one of its dependencies. The system cannot find the file specified.

2)
What I meant was that I took the entire contents of

QUOTE:
C:\Users\Win7Home\AppData\Roaming\Fidelity Investments\WealthLabPro

made a copy elsewhere on my HD, and deleted the folder. Next time I opened WLP it created a fresh folder, complete with the default strategies & datasets, but nothing else. This was a troubleshooting suggestion from the friendly folks at Fidelity. BTW, I asked whether WLP maintained any kind of more detailed log for troubleshooting, and they said "nope". Clearly the txt file you pointed me to is something they're unaware of



3)
Here's the output of your code

QUOTE:

Standard time name:
Daylight saving time name: Pacific Daylight Time
Daylight saving time? True
UTC offset: -07:00:00

Nothing abnormal I can think of with my time zone or clock settings. I've tried changing it to another time zone and then back again. No dice. I'm in 2010, current time, current day, daylight savings - yes, etc...

Thanks

Thank you. Clearly, the output is abnormal - i.e., the complete absense of standard time name:

QUOTE:
Standard time name:

Like said above, this is what perplexes WLP - it can't identify your time zone. The returned description of the time zone of your computer is incorrect: localZone.StandardName is blank, while "Pacific Standard Time" is expected to be returned.

I wouldn't be surprised if it explains the Fidelity update failures as well. Please create a support ticket, including a link to this thread would be enough. tia.

Fidelity downloads are sensitive to the time in your computer clock. Make sure that your computer time is correctly synchronized for your timezone and daylight saving setting. In other words, you should have selected "Automatically adjust for daylight saving time", and if it is, your computer clock should be correct or the Pacific time zone.

Resolution of this issue for the community:

I went into my Windows 7 clock/calendar function in the tray, unchecked the "synchronize with internet clock" (or something like that) and all was good. Weird since my calendar/clock/timezone didn't change at all, but that was giving Fidelity problems.

Cheers

That is strange. Is anybody else having a data download problem in Win 7 with the above symptoms?

Hi

when I want to open the strategy monitor in my WLD 5.6, I got the error message:
Current TimeZone not found.

Tee output of Eugene's code above would be:
Standard time name: W. Europe Standard Time
Daylight saving time name: W. Europe Daylight Time
Daylight saving time? True
UTC offset: 02:00:00

Could you help me, please

Thx

Hi Patrick,

Please enter a new support ticket. Copying and pasting the complete error message would be appreciated. tia.

Hi

I got a similar issue like Patrick has (or has had) with the system time setting not changed from one week to the other. But somehow the Strategy Manager doesn't work anymore. Instead I get an error message that reads like:

unexpected error
Current TimeZone not found

I have the choice between continuing without S Manager or closing WL.

To solve the issue I already tried out the following:
- I tried to uncheck the "synchronize with internet clock" like Chad explained.
- I ran the "code test" to read out the system time like above with the same results Patrick has.

I rebooted the system but nothing changed.

As I'm currently evaluating a 30 day trial to check whether WL meets my expectations and/or requirements I'm not sure if I would be allowed to open a new ticket.

Any idea/support how to solve this issue is highly appreciated.


Thank you in advance,
Florian

Hi,

Since then, the culprit has been determined -- it's the change of display language:

When Strategy Monitor is opened, you get an error message saying that Current TimeZone not found that looks like below:

The authentication server logs confirm that your Windows edition is one of those that allow that change. Unfortunately, the only workaround is to roll back the display language change.

Hi,

Thanks for your undelayed response. I didn't expect it that fast!

Alright.
Indeed, rolling back the display language solves the issue.
I apologize, but I still don't understand why it changed from one day to the other with no system changes in between. The only thing that sort of changed is the network I use to connect to the internet.
I mean I haven't changed the display language since installing WL. Original language of my Win7 Ultimate was English. I changed it to German about 1 year before installing WL. And WL worked fine until Friday last week. Then, like instantly it kind of changed its mind. I guess it might 'go together' with the authentification eventually on a different WL-server caused by a different network I'm currently using?

So I guess to return to my preferred language would only be possbile if the authentification server would be reset for my account data, right? Or alternatively reinstall WL after purchasing...?


Thanks again,
Florian

WL might have worked fine, it's the Strategy Monitor that is affected by this issue (only). Neither authentication nor network have anything to do with it.

Is there a little chance the minor update release 6.4.62 might fix this issue?

Thanks,
Florian

No, sorry.

Noticed interest in this thread from a visitor who found it after starting a free trial of WLD. So I decided to post an update. So far, four reasons which cause this error have been found. One of them was discovered recently and is a pretty obscure one:

Errors | Strategy > Current TimeZone not found

Hi

I got a similar issue like other users with the time setting.
When I try to run the backtest I get an error message that reads like:

Current TimeZone not found

To solve the issue I already tried out the steps:
1. In Windows, Internet time synchronization is enabled. Disable it.
2. (Applies to: Windows Ultimate or Enterprise). You're using a localized (e.g. German) Windows Ultimate. This version lets you change the system language and you changed Display Language or all language options to English. As a workaround, change your Display Language back to native (e.g. German). On Windows 10, restarting PC after applying the change seems to do the trick. This can also be caused by installing an additional language pack on Windows Pro.
3. If you've changed the time zone in Windows recently, try reverting the change.
4. New: Microsoft input keyboard is known to cause this error with multiple languages added. If the default language is set to English, it changes to another user-specified language on WL startup. Solution: remove all other languages.


As I'm currently evaluating a 30 day trial to check whether WL meets my expectations and/or requirements

Any idea/support how to solve this issue is highly appreciated.


Thank you in advance,
Thiago

Hi Thiago,

Does this apply to all backtests or some strategies? How about charts, are they also affected?

1. Less likely.
2. Hardly applies to your English Windows Home unless you installed a language pack from Microsoft. Did you?
3. Did you change the time zone?
4. What languages are installed in Microsoft input keyboard now?

For your information, I got again the same error just after updated my Windows to the last buid "2004".

Windows 10 build 2004 is problematic and not even recommended to update to immediately by Microsoft:

Windows 10 May 2020 update: you might want to hold off for a bit

Hi Eugene!

Besides not being able to do the tests, I can't open any graph.
I have a language pack installed on my Windows 10 Home but I tried to uninstall to see if it worked but it didn't work.
The only language pack I have installed here is Portuguese (Brazil)

Thiago,

Your Windows 10 Home has English locale ID (i.e. not Portuguese). This PT-BR language pack is the problem. Installing a language pack modifies the list of installed time zones which cannot be handled properly. Somehow it must be uninstalled in a complete way for WL to work correctly.

I don't really have much to suggest here. Try to uninstall that language pack and restart your PC until it works. Not sure but maybe System Restore could help. You could reinstall (factory reset) Windows as the last resort but that's difficult to do. If you have a 2nd PC without a language pack, that'd be the easiest option.

Eugene,

I can not restore my computer because of a program that doesn't work properly.

I work with IT and I have never seen such an orientation from a company.

That's why I offered you several workarounds for this known issue which for some reason remains open. Reverting the Display Language change makes the error go away. As you work in IT you should have no trouble how to accomplish it?

As i said, i already tried it and it didn't work.

Before asking here I made sure to read all the guidelines and do all the tests

If your Windows 7 Enterprise PC hasn't had a language pack installed then you should have success with restarting the trial on it. Please let me know and I'll reset your trial record on our end to enable you to take the trial on this PC.

I just went through the same problem and fixed by: go to Control Panel, then Clock and Region, then Region, then Administrative, Change System Locale to English, and You may also want to click on Copy Settings to ensure all in English.

My system in Windows 10, but it should be applied to Windows 7 as well. The key is: System Locale, or anything related to Locale.
If you write one line C# code just to inspect System.TimeZoneInfo.GetSystemTimeZones(), if it returns zones all in English, then it will be good.

QUOTE:
If you write one line C# code just to inspect System.TimeZoneInfo.GetSystemTimeZones(), if it returns zones all in English, then it will be good.

The zone names (standard/display) here doesn't have to be in English but perhaps their Ids must.