This is the old stuck message problem again, but it doesn't seem to be covered by the usual situations. Running Exchange 5.5 SP3 on W2K Server SP4; client is OE6 SP1 on W2K Pro SP4. User receives graphics files & address databases of various types and sizes, and problem happens only occasionally, so may be related to a corrupt file.
Indications: User's OE tries to get mail, fails with "Unknown error" on the POP server, Outlook Express error message 0x800C0133. This isn't an OE error (all 'CCCxx' numbers) and there is no mention of it at MS, and no reference on the web except for others trying to find out about it. Number of undelivered messages rises as new ones pile up behind stuck one.
No messages in imsdata\in.
MDBVU32 shows no messages in MTS-IN.
Doesn't appear to be a problem with STORE trying to translate, because it's not tying up the CPU (I've seen that problem before).
Cleaning the user's mailbox will remove all messages except the stuck one.
Only fix so far is to delete the user's mailbox and recreate it. Can't save any of the inbound messages for the user.
Seems like it's a 'corrupt' message or attachment that stops a component, but I don't seem to have any tools to get at it; we can't even find out who sent it to notify them not to send that type of file.
Anyone dealt with this before?
--Thanks
--WMSTech
Indications: User's OE tries to get mail, fails with "Unknown error" on the POP server, Outlook Express error message 0x800C0133. This isn't an OE error (all 'CCCxx' numbers) and there is no mention of it at MS, and no reference on the web except for others trying to find out about it. Number of undelivered messages rises as new ones pile up behind stuck one.
No messages in imsdata\in.
MDBVU32 shows no messages in MTS-IN.
Doesn't appear to be a problem with STORE trying to translate, because it's not tying up the CPU (I've seen that problem before).
Cleaning the user's mailbox will remove all messages except the stuck one.
Only fix so far is to delete the user's mailbox and recreate it. Can't save any of the inbound messages for the user.
Seems like it's a 'corrupt' message or attachment that stops a component, but I don't seem to have any tools to get at it; we can't even find out who sent it to notify them not to send that type of file.
Anyone dealt with this before?
--Thanks
--WMSTech
