Got an interesting problem here, first the Exchange Side... Exch 2k7, SP1, Rollup 6... Publishing Activesync (and OWA) through an ISA server (2006 SP1, etc)... We've been using Activesync with Windows Mobile (5 & 6) phones for years without issue. I've also got about 4-5 iPhone 3G users who don't appear to have issues...
However, I'm adding the first 3GS phones (OS v3.01) to the bunch.... The phones will connect to Activesync OK, download the full mail folder list, contents of the Inbox (past x days, doesn't seem to matter), Calendar and Contact items without error... However, when opening some mail item, I will get an error on the phone that states: "This message has not been downloaded from the server" ... At the bottom of the message is a button "Download remaining 0 bytes"... The remaining byte count is always zero... Tapping the button yields a screen refresh, but no change in the error message. At this point, the occurrence of the issue is random. Message size and type do not seem to matter. I've had success with both plain text and HTML messages, and failure with both HTML and plain text messages. Some messages with attachments came through fine, and I can read the attachments without issue while others just come up with the "This message has not..." error... Even a simple one line, plain text message (sent from the Iphone itself, back to my own mail account) elicited the error; even though I could see the whole text of the message within the message list preview! The only other instances I've been able to find of this error with Google are either with IMAP as the protocol (where the issues was fixed in Exch Rollup 3), or there was no resolution when Activesync was mentioned. I've looked through the IIS logs, and don't see anything out of the ordinary.... I've connected the iPhone to our internal WLAN and bypassed the ISA firewall.. Still the same results. I've also tried with two different iPhone 3GS's and two different Exchange accounts.. Same issues on both phones and with both accounts. I've contacted Apple, and they claim it's a Microsoft issue... And although I haven't contacted Microsoft yet, they'll probably claim it's an Apple issue... Before I do contact Microsoft, does anyone have any suggestions of settings on the Exchange side I may want / need to look at? Anyone else run into this problem? Joe Pochedley Network & Telecommunications Manager Fives North American Combustion, Inc. email: [email protected] v: +1 216-206-5505 f: +1 216-641-7852
