[adamli9]

We upgraded to BES 4.1.5 for Exchange about a week ago. Last night I began getting BES Alert messages for these log entries:

[40000] (04/30 10:40:54.088):{0x1168} {usergoeshere@domaingoeshere}-GetTZIndexByTZName-Unrecognized time zone string Eastern Time (US & Canada)
[30000] (04/30 10:40:54.088):{0x1168} {usergoeshere@domaingoeshere}-GetRIMApptParent- GetTZIndexByTZName() failed Entry tag =2625967
[50000] (04/30 10:40:54.134):{0x1168} Invalid log entry - Level:15, EventId:0(0x00000000), Format:{%s}-%s- Compare Exclusion Date:%s Ox%x No %d with appt start date:%s, User:<null>, ArgCount:3, Args:arg[1](char*)=usergoeshere@domaingoeshere arg[2](char*)=AdjustExclusionList arg[3](char*)=<null>
[50000] (04/30 10:40:54.134):{0x1168} Invalid log entry - Level:15, EventId:0(0x00000000), Format:{%s}-%s- Compare Exception Date:%s Ox%x No %d with appt start date:%s, User:<null>, ArgCount:3, Args:arg[1](char*)=usergoeshere@domaingoeshere arg[2](char*)=AdjustExclusionList arg[3](char*)=<null>
[50000] (04/30 10:40:54.134):{0x1168} Invalid log entry - Level:15, EventId:0(0x00000000), Format:{%s}-%s- Comparing date %s, User:<null>, ArgCount:3, Args:arg[1](char*)=usergoeshere@domaingoeshere arg[2](char*)=SimilarExclDates arg[3](char*)=<null>
[50000] (04/30 10:40:54.134):{0x1168} Invalid log entry - Level:15, EventId:0(0x00000000), Format:{%s}-%s- compared to date %s, User:<null>, ArgCount:3, Args:arg[1](char*)=usergoeshere@domaingoeshere arg[2](char*)=SimilarExclDates arg[3](char*)=<null>
[50000] (04/30 10:40:54.134):{0x1168} Invalid log entry - Level:15, EventId:0(0x00000000), Format:{%s}-%s- compared to date %s, User:<null>, ArgCount:3, Args:arg[1](char*)=usergoeshere@domaingoeshere arg[2](char*)=SimilarExclDates arg[3](char*)=<null>
[50000] (04/30 10:40:54.134):{0x1168} Invalid log entry - Level:15, EventId:0(0x00000000), Format:{%s}-%s- compared to date %s, User:<null>, ArgCount:3, Args:arg[1](char*)=usergoeshere@domaingoeshere arg[2](char*)=SimilarExclDates arg[3](char*)=<null>
[50000] (04/30 10:40:54.134):{0x1168} Invalid log entry - Level:15, EventId:0(0x00000000), Format:{%s}-%s- compared to date %s, User:<null>, ArgCount:3, Args:arg[1](char*)=usergoeshere@domaingoeshere arg[2](char*)=SimilarExclDates arg[3](char*)=<null>
[50000] (04/30 10:40:54.134):{0x1168} Invalid log entry - Level:15, EventId:0(0x00000000), Format:{%s}-%s- compared to date %s, User:<null>, ArgCount:3, Args:arg[1](char*)=usergoeshere@domaingoeshere arg[2](char*)=SimilarExclDates arg[3](char*)=<null>
[30000] (04/30 10:40:54.166):{0x1168} {usergoeshere@domaingoeshere}-GetRIMApptParent- Returned Parent RefID=-1837450384 Status=Parent not been changed
[50000] (04/30 10:40:54.166):{0x1168} Invalid log entry - Level:15, EventId:0(0x00000000), Format:{%s}-%s- QueryByGOIDAndInstance %s, deleted child instance date = %s, User:<null>, ArgCount:4, Args:arg[1](char*)=usergoeshere@domaingoeshere arg[2](char*)=ChildBeenDeleted arg[3](char*)=not found arg[4](char*)=<null>
[50000] (04/30 10:40:54.166):{0x1168} Invalid log entry - Level:15, EventId:0(0x00000000), Format:{%s}-%s- QueryBySourceKeyAndInstance not found deleted child instance date = %s, User:<null>, ArgCount:3, Args:arg[1](char*)=usergoeshere@domaingoeshere arg[2](char*)=ChildBeenDeleted arg[3](char*)=<null>

I've seen two users affected so far, but they haven't noticed any problems with their BBs. Any ideas on what could cause this? The BTSC didn't have anything.

[Ugg]

Odd. I think that there was a bit of a "time zone" issue associated with the writing of information to log files on the "original" release of 4.1.5, which was corrected. Just checking, but what bundle number does your BES think it is (from the "support info" in "add/remove programs").

Does your BES have the "automatically adjust the clock for daylight saving" box ticked? In Windows date and time properties, is there a GMT-5 entry called "Eastern Time (US & Canada)"?

[adamli9]

It says it's 4.1.5 Bundle 79. The server is set to GMT -5 Eastern Time (US & Canada) with automatically adjust for DST checked.