Windows Mobile not syncing with HTTP 500 internal server error and nextags showing problems with syncstate table

Odd one this, it seems a couple of the reasons this can be seen are down to a corrupt syncstate table, for whatever reason..

Also if we hit problems with limits on named properties we may fail with an internal server error 500 if something like iphone is adding further named props and Exchange has hit a limit on these. But to be honest if youre at the stage where youre dealving into nextags logging you might be in a good place to give us at support a call!