CPU infinite loop on REPLY (2002)

Topic

New Reply

I have been experiencing this 100% CPU issue with Outlook for quite a while with v2000 and was hoping that v2002 would fix this. It happens right after I hit the SEND button after composing a reply to a message

This is very consistent: any message that has cause the problem will cause it again on further attempts to REPLY.

I did all that I know to “fix” any issue with my .PST: outlook /clean reminders (several times) and also as part of moving my .PST to v2002, I followed Woody’s recommendation for rejuvinating Outlook: I used the new Outlook 2002 .PST file, opened the “old” .PST and copied all relevant into the new one; to no avail.

Does anybody know what may fix this problem.

Thanks in advance,

Arthur

Reply | Quote

Replies

Because Outlook tries to send a message immediately when you press Send (unless you turn this off), it’s difficult to be certain that it is a problem just with replies. Dies it ever happen when sending a new message to the same addressee? In the same format? Have you found any pattern to it?

Reply | Quote

Here are the few things that I know:
1) it does not happen in the send process: Outllok locks up when the “send Immediately…” is turned off;
2) it happens so often and randomly that I now save the text of my replies to the clipboard before cklicking the Send button;
3) the format of the original message is not relevant: happens with both HTML and plain text;
4) in all lockup cases, Task Manager will flag Outlook and all its open windows as “not responding”.
5) in the lastest occurences on a brand new .PST under v2002, only e-mail messages and contacts were copied over from the old v2000 .PST, nothing else.

I am going to try one more thing: re-create a new .PST (again) and copy messages to newly created sub-folders (rather than drag the message sub-folders across.

Thanks for helping.

Reply | Quote

I don’t know what all Outlook is doing when you click Send. Address resolution, spell-checking, creating a message in the Outbox folder, deleting from the Drafts folder (if you saved)…

One thing that is unique to replies and forwards is that, at some point, Outlook annotates the original message with an indication that you replied/forwarded at a certain date/time. Not sure when this happens (sometimes the annotation is there even if you merely drafted and saved a message, and never sent it).

One thing that I believe is unique to replies is that Outlook tracks the account into which a message was received so it can send back out on that same account.

None of the above sounds easy to debug, unfortunately…

Reply | Quote

A couple more things I can identify:
1) the lockup occurs before:
a) the message in the Outbox is created, and
the original message is marked as “replied to”.
2) the same message will lockup on two different machines
running different OS and diferrent versions of Outlook
(I pull my messages to two diffferent machines, leaving
a copy on the server for 10 days).
3) I have 7 different accounts at 2 different IPS’s.

I anything like this happened in a “real” database, I would export/import the whole file

Thanks for helping.

Reply | Quote

Two machines, this is very strange. Can you isolate the problem to a particular account(s) or sender(s)? (I assume you do not use Word as your editor…)

Reply | Quote

Arthur and J-

We’ve started having this problem since we recently upgraded to 2002. On one machine, it would even just hang while composing a message. I did find that by turning off word as editor, you could continue composing (but the usage stayed at 100%) and even send the message. For now I’ve turned off Word, but it may be that going back to 2000 will be our final answer.

The only other issue I’m investigating is the use of Spam filters. We were using I Hate Spam and I could see some funny “screen resolution” issues, so we uninstalled it and switched to Junk Out (advertised on Woody’s home page). This seemed to solve all the issues I was afraid were coming from the other addon, but tonight Outlook locked up and disabled Junk Out with an error message saying JunkOut caused an error in Outlook. We’ll see.

If I still have these problems without using Word or other addons, I think I’ll need a complete reinstall of windows and office or go back to 2000.

I’ll be following your progress.

cheers,

tom

Reply | Quote

Arthur and J-

We’ve started having this problem since we recently upgraded to 2002. On one machine, it would even just hang while composing a message. I did find that by turning off word as editor, you could continue composing (but the usage stayed at 100%) and even send the message. For now I’ve turned off Word, but it may be that going back to 2000 will be our final answer.

The only other issue I’m investigating is the use of Spam filters. We were using I Hate Spam and I could see some funny “screen resolution” issues, so we uninstalled it and switched to Junk Out (advertised on Woody’s home page). This seemed to solve all the issues I was afraid were coming from the other addon, but tonight Outlook locked up and disabled Junk Out with an error message saying JunkOut caused an error in Outlook. We’ll see.

If I still have these problems without using Word or other addons, I think I’ll need a complete reinstall of windows and office or go back to 2000.

I’ll be following your progress.

cheers,

tom

Reply | Quote

Two machines, this is very strange. Can you isolate the problem to a particular account(s) or sender(s)? (I assume you do not use Word as your editor…)

Reply | Quote

A couple more things I can identify:
1) the lockup occurs before:
a) the message in the Outbox is created, and
the original message is marked as “replied to”.
2) the same message will lockup on two different machines
running different OS and diferrent versions of Outlook
(I pull my messages to two diffferent machines, leaving
a copy on the server for 10 days).
3) I have 7 different accounts at 2 different IPS’s.

I anything like this happened in a “real” database, I would export/import the whole file

Thanks for helping.

Reply | Quote

I don’t know what all Outlook is doing when you click Send. Address resolution, spell-checking, creating a message in the Outbox folder, deleting from the Drafts folder (if you saved)…

One thing that is unique to replies and forwards is that, at some point, Outlook annotates the original message with an indication that you replied/forwarded at a certain date/time. Not sure when this happens (sometimes the annotation is there even if you merely drafted and saved a message, and never sent it).

One thing that I believe is unique to replies is that Outlook tracks the account into which a message was received so it can send back out on that same account.

None of the above sounds easy to debug, unfortunately…

Reply | Quote

Here are the few things that I know:
1) it does not happen in the send process: Outllok locks up when the “send Immediately…” is turned off;
2) it happens so often and randomly that I now save the text of my replies to the clipboard before cklicking the Send button;
3) the format of the original message is not relevant: happens with both HTML and plain text;
4) in all lockup cases, Task Manager will flag Outlook and all its open windows as “not responding”.
5) in the lastest occurences on a brand new .PST under v2002, only e-mail messages and contacts were copied over from the old v2000 .PST, nothing else.

I am going to try one more thing: re-create a new .PST (again) and copy messages to newly created sub-folders (rather than drag the message sub-folders across.

Thanks for helping.

Reply | Quote

Because Outlook tries to send a message immediately when you press Send (unless you turn this off), it’s difficult to be certain that it is a problem just with replies. Dies it ever happen when sending a new message to the same addressee? In the same format? Have you found any pattern to it?

Reply | Quote