AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Input string was not in a correct format.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.formatException: Input string was not in a correct format. at System.Text.StringBuilder.formatError() at System.Text.StringBuilder.Appendformat(IformatProvider provider, String format, Object[] args) at System.String.format(IformatProvider provider, String format, Object[] args) at DotNetNuke.Modules.Events.EventNotification.SendEventNotifications() at DotNetNuke.Modules.Events.EventNotification.DoWork()
Source:
Server Name: SERVER19

Hi Scott,

This is almost certainly to do with the inaccuracies time-handling within the DNN framework. There are many points at which dates can be calculated wrong mainly because DNN does not support DST (since .Net V2 does not). The team have made their best attempt at accuracy, but unfortunately this isn't entirely possible.

I think 1 hour of your inaccuracy could be because of DST, the other hour could be because you are in a different timezone to your server. So could try changing your timezone for the module instance to negate this.

We hope to improve on this funtionality when DNN provides proper timezone support on .Net 3.5. Howevert this is no timeline for this support within DNN at this time.

Cheers
Roger