[Tickets #12259] Re: Error with Ping command with Activesync 2.4.0beta4

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/12259
------------------------------------------------------------------------------
  Ticket           | 12259
  Aktualisiert Von | Twilek at gmx.de
  Zusammenfassung  | Error with Ping command with Activesync 2.4.0beta4
  Warteschlange    | Synchronization
  Version          | Git master
  Typ              | Bug
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       | Michael Rubinsky
------------------------------------------------------------------------------


Twilek at gmx.de (2013-05-16 18:40) hat geschrieben:

I have set error reporting to E_ALL so WARNs should show up. But it´s  
just this error showing up repeatedly every 10 minutes or so with no  
WARN in front of it. I just didn´t think HTTP 500 Errors where  
supposed to happen during normal operations of any system. If it is  
supposed to be like that everything is fine, as I said the sync works  
without noticeable problems otherwise.

> There should have been an entry with level WARN above that.
>
> If so, this is just the result of PING not finding any pingable  
> collections. For EAS versions < 14 this must return a HTTP 500,  
> hence the error message about the 500. It should eventually be  
> followed by a either a SYNC or a full PING request.