Traveler Error: Assertion failing

Hello

that’s a repost thats why the old date’s, maybe someone got some info on this:


Since i tested a “Hard Reset Device” on my own iPhone, im getting this error and can’t Sync anymore. It Connects to the Server and on the Console i get the Error Below:

Notes Traveler: SEVERE CN=Tibor Cetl/O=namics Assertion failing [Wed Oct 21 08:03:18 CEST 2009] thread=1674994646 PS-039 [CN=Tibor Cetl/O=namics] [null] [null] [0 runnables] [Busy? true] [Last Runnable: Wed Oct 21 08:03:18 CEST 2009] [Running: 16ms] [Idle: 0ms] com.lotus.sync.TSS.Util.AssertionException: Internal error

at com.lotus.sync.TSS.Util.AssertionException.(AssertionException.java:38)

at com.lotus.sync.TSS.Util.Assertion.fail(Assertion.java:49)

at com.lotu

21.10.2009 08:03:18 Notes Traveler: WARNING CN=Tibor Cetl/O=namics Internal error

com.lotus.sync.TSS.Util.AssertionException: Internal error

at com.lotus.sync.TSS.Util.AssertionException.(AssertionException.java:38)

at com.lotus.sync.TSS.Util.Assertion.fail(Assertion.java:49)

at com.lotus.sync.TSS.Util.Assertion.t(Assertion.java:87)

at com.lotus.sync.TSS.DBInt.CafDB.dinkySync(CafDB.java:2555)

at com.lotus.sync.TSS.DBInt.CafDB.startSession(CafDB.java:3421)

at com.lotus.sync.TSS

21.10.2009 08:03:18 Notes Traveler: SEVERE CN=Tibor Cetl/O=namics Unexpected SendActionExceptionException for user=CN=Tibor Cetl/O=namics#primesync

com.lotus.sync.TSS.DBInt.SendActionExceptionException: Backend failure.

at com.lotus.sync.TSS.DBInt.SendActionExceptionException.(SendActionExceptionException.java:35)

at com.lotus.sync.TSS.CoreEngine.CoreEngine.checkForBackendIntegrity(CoreEngine.java:904)

at com.lotus.sync.TSS.CoreEngine.CoreEngine.processAction(CoreEngine.java:208)

I did a Clear wipe/Allow access also tried to delete my device and user in the Traveler-Database and set up the profile again.

It shows me connected and such.

Is there another place i could clean up my user on the server?

Thanks!

kind regards

Tibor


Subject: RE: Traveler Error: Assertion failing

Basically means the Traveler server is unable to reach the mail server for the user. Generally this would be a network error or the server is down. If this is a persistent issue would recommend opening a request for support so we could review the setup and logs.