Our IM also died w/ running IM Server. The error:

ASSER#OSX#4.2.5#IsSupportedDateTimeValue(itsUnixTime)#XDateTime_Unix.cpp#97#10.3.8#Ex...



On Mon, 4 Apr 2005, InterMapper Discussion wrote:

InterMapper-Talk Digest - Monday, April 4, 2005

 InterMapper died with DST
         by "Jason K.Werner" <[EMAIL PROTECTED]>
 Re: [IM-Talk] InterMapper died with DST
         by "Richard E. Brown" <[EMAIL PROTECTED]>
 Re: [IM-Talk] InterMapper died with DST
         by "Raza Rizvi" <[EMAIL PROTECTED]>


----------------------------------------------------------------------

Subject: InterMapper died with DST
From: "Jason K.Werner" <[EMAIL PROTECTED]>
Date: Sun, 3 Apr 2005 05:00:23 -0700

The instant we went forward an hour, InterMapper 4.2.4 (OS X Server
10.3.8) died:

Apr 3 03:00:00 presidio intermapperd[707]:
ASSERT#UNIX#4.2.4#IsSupportedDateTimeValue(itsUnixTime)#XDateTime_Unix.c
pp#97#Darwin/7.8.0#Ex61#As1#
Apr 3 03:00:05 presidio intermapperd[707]: ExitProcess with status 1.
XBugReport

Attempted restart, failed with same error.  Upgraded to 4.2.5 just for
kicks, same result.

I'm in Pacific TZ, PST/PDT.  Changed TZ to GMT, and intermapperd was
happy with that.  Experimented with various timezones (Chicago, etc.),
none worked.  Sticking with GMT for now.

Curious if anyone else is seeing this.

        -J-




____________________________________________________________________
List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]

Reply via email to