WL5.3 Exception Thrown
Author: WLXYZ
Creation Date: 3/20/2009 9:54 AM
profile picture

WLXYZ

#1
The type initialize for "Fidelity.Components.TimeZoneInformation' threw an exception.

Then I got a message to send this stuff to Microsoft and declined.
profile picture

Cone

#2
Are you running Windows 2000?
profile picture

WLXYZ

#3
Using Windows XP SP3 and attempted to display a chart AA on 5 minute interval.
profile picture

WLXYZ

#4
Further info: Error occurs after login to Fidelity and click on Streaming button.

EventType : clr20r3 P1 : wealthlabpro.exe P2 : 5.3.44.0
P3 : 49933624 P4 : wealthlab P5 : 1.0.0.0 P6 : 49933618 P7 : 71c
P8 : 12 P9 : system.typeinitialization
profile picture

Cone

#5
Another user had the same problem with a non-Win 2K computer, but they somehow solved it and we didn't get any clues.

Does it only occur for 1 symbol?
For that symbol and scale?

If so, drawing objects are always a prime suspect. Please try different things and create a ticket if you get stuck. A ticket wouldn't be a bad idea anyway, but if we can solve it here, it would be good to have a public reference for it.
profile picture

WLXYZ

#6
I got further info:

System.TypeInitializationException was unhandled
Message="The type initializer for 'Fidelity.Components.TimeZoneInformation' threw an exception."
Source="Fidelity.Components"
TypeName="Fidelity.Components.TimeZoneInformation"
StackTrace:
at Fidelity.Components.TimeZoneInformation.ToLocalTime(DateTime utc, String targetTimeZoneName)
at WealthLab.MarketHours.ConvertLocalTimeToNative(DateTime localTime)
at WealthLab.DataProviders.FidelityStreamingProvider.a(String A_0)
at WealthLab.DataProviders.FidelityStreamingProvider.b()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
InnerException: System.NullReferenceException
Message="Object reference not set to an instance of an object."
Source="Fidelity.Components"
StackTrace:
at Fidelity.Components.TimeZoneInformation.a(Byte[] A_0)
at Fidelity.Components.TimeZoneInformation..cctor()
InnerException:
profile picture

Cone

#7
What time zone is your computer set to? Arizona perhaps (no DST)?
profile picture

WLXYZ

#8
The timezone is set to CST with the adjust for daylight savings time box checked.

I also tried uninstalling WL5 and re-installed from scratch. Same problem.

I also tried uninstalling .Net 2.0 runtime but Windows refused to do this.
profile picture

Cone

#9
Please answer:

Does it only occur for 1 symbol?
For that symbol and scale?

If so, drawing objects are always a prime suspect. Please try different things and create a ticket if you get stuck. A ticket wouldn't be a bad idea anyway, but if we can solve it here, it would be good to have a public reference for it.
profile picture

WLXYZ

#10
Sorry, no it does not happen with just one symbol. I have tried AA GOOG QID, all with the same result.

The problem appears on both daily and 5 minute charts. The charts I used were created with File..New Chart option so it has default drawing object.

AA 5 min
QID 5 min
GOOG daily

All with 500 bars.

I have also deleted the default.ws in the data directory as suggested with a different
problem resolution.

I am open to more suggestions.

Also, the problem appears to be related with streaming data as locally edited data appears to work with drawing objects

Thanks.


P.S. I will be out of pocket for awhile but will continue to get WL5.3 to work on this PC so you will not be wasting your time if you can give me some more ideas to try.
profile picture

Cone

#11
Please create a Ticket so we can hand this over to the responsible programmer.
profile picture

WLXYZ

#12
Ticket 17959 created
profile picture

WLXYZ

#13
Cone:

Here is a solution to the problem with TimeZone:

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:

1) Uninstall KB955839
2a) download the following patch:
http://www.microsoft.com/downloads/thankyou.aspx?familyId=81d03da3-846c-4f7f-8791-cd9943ce0893&displayLang=en&hash=m2NGbeQ4T1OBvWEnvz%2f9TyPeNIgbftt7K%2f6Fvhm7PjKFGATO0ngeNRGE7qdAkmb%2fYKuATqoQZelcigq8WFcXrA%3d%3d
2) Install KB951072
3) Reinstall KB955839
4) Uninstall WL5.3
5) Re-install WL5.3

profile picture

Cone

#14
Thanks for posting this information.

Steps 4 and 5 are probably not required since a simple restart would basically accomplish the same thing (unless some component of WL was truly damaged or missing).