Can't delete from Inbox on my iPAQ

[Anthony Caruana]

Hi there

I've got an Activesync issue. When syncing my Inbox, I have an Unresolved Item. I have worked my way though what the item could be and have found a single item in the Outbox on my ipaq 2210. I can not delete this item and it does not sync to my desktop (AS 3.7, Win XP, OL2002 SP2).

I have deleteed and recreated the partnership and the issue persists.

The item in my Outbox can not be deleted (if I do a tap-hold | Delete nothing happens. I can not move it to another folder and I can't open it. Obviously, it is corrupt in some way.

Does anyone have any idea of how to delete this undeletable item

TIA

[TJNoff]

I saw your post while dealing with a similar problem on my Toshiba e740. I did a restore from backup, synched with my desktop (telling ActiveSync to replace the items on my e740 with the items in Outlook), and everything was fine...something I'd done in the past with no problems. But, when I synched again a second time, it showed that I had 46 unresolved items. When I clicked to resolve the items, it went through the resolve process (well, it looked like it did), counting from 1 to 46, then reported, again, 46 unresolved items! Couldn't open these items, and couldn't delete them! Arrrgggghhh! Went through this several times with the same result, even after removing the e740 from my ActiveSynch configuration.

Well, I restored my e740 from the same backup again, but checked my mail folders on the e740 before synching. Turns out that the 46 phantom items were in my INBOX on the e740 just after restoring. Somehow the synch process was moving the list of 46 messages (NOT the actual message bodies) from the INBOX to the OUTBOX. Huh??? So, before the first synch, I removed the 46 items from the INBOX, and, voila, they didn't end up in my OUTBOX after the synch. All is well now!

Don't know if this has any similarities with your problem. Besides, you've likely cured it by now, or at least burned your PPC! But, since there was a lack of information on the 'Net about this issue (including 0 responses to your post), I thought I'd share what I found....