eM Client is continuously crashing

Crashing eM Client
1

eM Client is continuously crashing, whereas the db checker indicates that the db is ok. 

The crash log says: System.ArgumentException: Kind property of dateTime is Utc but the sourceTimeZone does not equal TimeZoneInfo.Utc
I have the full crash log, but it is rather long, Shall I paste it in here? 
Below is part of the crash log: 

Thanks, Bart 

eM Client (6.0.24316.0)

Windows: Microsoft Windows NT 6.2.9200.0, Framework: 4.0.30319.42000

The following error has occurred:

System.Reflection.TargetInvocationException: Het doel van een aanroep heeft een uitzondering veroorzaakt. —> System.Reflection.TargetInvocationException: Het doel van een aanroep heeft een uitzondering veroorzaakt. —> System.ArgumentException: Kind property of dateTime is Utc but the sourceTimeZone does not equal TimeZoneInfo.Utc

bij System.TimeZoneInfo.ConvertTime(DateTime dateTime, TimeZoneInfo sourceTimeZone, TimeZoneInfo destinationTimeZone)

bij MailClient.TimeZone.TimeZoneConvert.ConvertTime(DateTime dateTime, TimeZoneInfo sourceTimeZone, TimeZoneInfo destinationTimeZone)

bij MailClient.TimeZone.TimeZoneConvert.ConvertTimeToLocalTimeZone(TimeZoneInfo sourceTimeZone, DateTime dateTime)

bij MailClient.iCalendar.ScheduleComponent.GetPropertyTimeAsLocal(Calendar calendarObject, ScheduleComponent component, String propertyName)

bij MailClient.UI.Schedule.Imip.ImipUserInterface.CreateScheduleItemDetail(ItipMessage result, ItipMessageItem item, StringBuilder html)

bij MailClient.UI.Schedule.Imip.ImipUserInterface.CreateHTMLUserInterface(ItipMessage result)

bij MailClient.UI.Controls.controlMessageDetail.<>c__DisplayClassf.b__e()

2

So is mine. Was wondering if it is to do with the leap year?

3

Found that if I re-set my system date to 28th Feb, eM Client will open normally.  Have changed date back to 29th Feb and eM Client remains open.  

4

hmm, mine keeps crashing if I change the system date. I have changed the system date back and forth now a couple of times… 
What did you exactly do? Did you change the timezone too? What timezone are you in, as that may also cause the crash…? 

5

It’s a bit shoddy that an app like this can’t handle the concept of leap years isn’t it? Happening to me too, I can open the app, but I can only open the calendar if I have the system date set to something other than 29th Feb.

6

hmm I have a slightly different problem: 
System.ArgumentException: Kind property of dateTime is Utc but the sourceTimeZone does not equal TimeZoneInfo.Utc
it looks like a difference in timezones is the culprit… ?? 
Does anyone have any idea? 

7

Hi,
there is a bug in the month view of the program that manifested with the leap year.
This update should fix the issue: http://www.emclient.com/dist/v6.0.249…

Regards,
Olivia

8

Hi Olivia, 
Thank you for your reply! 
Unfortunately, it doesnt solve the issue… 
Below you see the first few lines of the bug report, that I just saved after installing the new version you linked. 
I hope you can help me…
btw: I really like eM Client, its a great tool. 
Thanks, Bart 

eM Client (6.0.24918.0)

Windows: Microsoft Windows NT 6.2.9200.0, Framework: 4.0.30319.42000

The following error has occurred:

System.Reflection.TargetInvocationException: Het doel van een aanroep heeft een uitzondering veroorzaakt. —> System.Reflection.TargetInvocationException: Het doel van een aanroep heeft een uitzondering veroorzaakt. —> System.ArgumentException: Kind property of dateTime is Utc but the sourceTimeZone does not equal TimeZoneInfo.Utc

9

Perform the following steps.
Exit eM.
Set your system date to February 28.
Start eM.
GO to Calendar and select ANY view except Month view. I prefer Week view.
GO back to mail.
Exit eM.
Reset system date to February 29.
Start eM.
Everything should work but do NOT go to Month view. It will immediately experience an application error.
Hope this helps.

10

Hi Eric, 

Thanks for your reply, but I tried that solution like 10 times already. My eM Client keeps crashing so your third bullet, ‘Start eM’, doesnt work with me. 

I dont have a February 29th problem. I have a slightly different problem, something with the Timezones being not equal, see the text in the log file: “System.ArgumentException: Kind property of dateTime is Utc but the sourceTimeZone does not equal TimeZoneInfo.Utc”. 
People with the February 29th problem have a different error message in the log file.

Thanks, Bart 

11

My apologies. Have you tried a timezone other than UTC?

12

Works fine - thank You!

13

Hi Olivia, 
I hope you are still working on this issue, as I am still unable to start up eM Client. 
Please, also refer to the following thread, i think it has more information regarding the crash log etc. 
https://forum.emclient.com/emclient/topics/error_message_regarding_timezone
Thanks, Bart 

14

Hello.

Mine started crashing too, on Feb 29th exactly, when opening the window (it keeps iconized in the session). The error was a bit different, saying that “some date could not be represented”.
Same thing the day after, nothing even rebooting repaired…

Using other applications (Sunbird and Android) confirmed that the calendars were not in cause. And I hadn’t done any change in the calendars since the day before when it was working.
Also, all my calendars share the same timezone and are hosted on my own local caldav server.

So I think there was a bug in the soft that woke up on Feb. 29 2016 due to… some internal way of counting the time.

Then I downloaded the last version 6-0-24928 and this one could restart, with no data loss.
This may help you, and also to locate the bug.

Best regards.