BMFC
asked on
Outlook 2010 "has stopped working" on New Email/Reply?
Hello all, we are experiencing a frustrating issue on all of our outlook clients (Outlook 2010 running on both Win 7 and 8).
A little bit of information to start, we recently moved from Exchange 2007 to 2013 (about a month ago) and had quite a few issues right away. We got most of these resolved and seem to have been running smoothly since then, but there are still a couple of things that we would like to get cleaned up as we can.
We have always used our clients in "cached exchange mode" and had no issues until after the migration, when we started noticing long delays in clients updating inboxes. (It will hang on "updating this folder..." in the bottom for 10-15 minutes before pulling mail into the inbox.)
As a workaround to this issue, we have tested the "online mode" (NOT cached exchange mode) which seems to completely resolve the delay issue. All messages display in the inbox instantly.
However, this "online mode" presents a new and more disabling issue: CLICKING SEND MAIL OR REPLY HANGS THE CLIENT FOR 3-4 MINUTES BEFORE OPENING THE WINDOW. If there is any input while it is hanging, the program will 'stop responding' and crash. If you are patient, after the window finally opens, then ANY SUBSEQUENT CLICKS OF NEW MAIL OR REPLY LAUNCH INSTANTLY.
The client will go on to work perfectly until it is restarted again, at which point the first attempt to compose a message will lock it up once more.
I checked the event logs and found a single very generic message from Windows Error Reporting about the hang:
This happens on any PC in our office. I have tried rebuilding the outlook profile to no avail. I tried safe mode and no dice. Returning the client to cached exchange mode will solve the issue completely, but then we would be waiting 15 minutes to see mail.
I included the note about our server upgrade because I am fairly certain the issue is with the exchange configuration and not anything on the individual clients.
A little bit of information to start, we recently moved from Exchange 2007 to 2013 (about a month ago) and had quite a few issues right away. We got most of these resolved and seem to have been running smoothly since then, but there are still a couple of things that we would like to get cleaned up as we can.
We have always used our clients in "cached exchange mode" and had no issues until after the migration, when we started noticing long delays in clients updating inboxes. (It will hang on "updating this folder..." in the bottom for 10-15 minutes before pulling mail into the inbox.)
As a workaround to this issue, we have tested the "online mode" (NOT cached exchange mode) which seems to completely resolve the delay issue. All messages display in the inbox instantly.
However, this "online mode" presents a new and more disabling issue: CLICKING SEND MAIL OR REPLY HANGS THE CLIENT FOR 3-4 MINUTES BEFORE OPENING THE WINDOW. If there is any input while it is hanging, the program will 'stop responding' and crash. If you are patient, after the window finally opens, then ANY SUBSEQUENT CLICKS OF NEW MAIL OR REPLY LAUNCH INSTANTLY.
The client will go on to work perfectly until it is restarted again, at which point the first attempt to compose a message will lock it up once more.
I checked the event logs and found a single very generic message from Windows Error Reporting about the hang:
Fault bucket , type 0
Event Name: AppHangTransient
Response: Not available
Cab Id: 0
Problem signature:
P1: OUTLOOK.EXE
P2: 14.0.7113.5000
P3: 527d6330This happens on any PC in our office. I have tried rebuilding the outlook profile to no avail. I tried safe mode and no dice. Returning the client to cached exchange mode will solve the issue completely, but then we would be waiting 15 minutes to see mail.
I included the note about our server upgrade because I am fairly certain the issue is with the exchange configuration and not anything on the individual clients.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks again Simon! I actually found the solution to my issue on another EE thread, one that you yourself answered: here
In this case, I really wasn't specific enough about the method in which we migrated/then just did an unplug of exchange-old. The Public Folders were culprit.
In this case, I really wasn't specific enough about the method in which we migrated/then just did an unplug of exchange-old. The Public Folders were culprit.
ASKER