Ok, new tip for you. When you're the person that gets the Server Status Reports from the Small Business Server, and you notice a critical error that your boss (or person who pays your salary/bills) can't sync his mobile phone to the server, you may want to jump on it a little faster than I did.
Sure, I didn't get in trouble because I was actually doing the rest of my job, but it would have made his life easier.
What am I talking about? Daily I have seen the following exerpt from the Server Status Report on our Catfood server here at the office:
Now finally getting the chance to take a peak, I looked at the IIS logs located in %windir%\logfiles\w3svc I was able to determine that the phone was indeed logging into the server, but failing to synch. So the password wasn't an issue.
The goal was to get it fixed as quickly as possible. So we took the approach to remove the inbox from the server sync schedule, sync the phone, and then add the inbox back in, essentially resetting the inbox sync with the server. Problem solved, the phone now sync's perfectly, and there aren't any ugly red X's on my server status report.
... Now if I can just get people on the team to stop typing their password incorrectly, I might get a clean server status report!
Whoops, I just realized that the error above is a picture, so MSN and Google won't be able to find this post if you search for it. The error is "Unexpected Exchange mailbox Server error: Server:  User:  HTTP status code: . Verify that the Exchange mailbox Server is working correctly."