Business Critical | Exchange 2007 | Emails sent from OWA go to drafts

Emails users send via Outlook Web Access go into the drafts folder and are never sent.  If the same email is subsequently sent using the Outlook client, it sends as expected.  Rebooting the CAS servers temporarily alleviates the problem.  Dynamics CRM is not installed in the environment.
LVL 6
page1985Asked:
Who is Participating?
 
page1985Author Commented:
This issue has been resolved.

McAfee Enterprise 8.8 was installed on one of the transport servers.  After rebooting, the problem began.  We disabled McAfee 8.8 by setting the McAfee services in the services MMC to disabled and rebooting the server.
0
 
motaz_mohamedCommented:
Check this thread:

http://forums.msexchange.org/OWA_Sent_Email_Stuck_in_Drafts_Folder/m_1800436521/tm.htm

To save you some time reading the whole thread and in summary here is the proposed solution:

"I had a similar issue to this problem, and I found out that I had to adjust my Windows Firewall settings to fix this.  I essentially used:

netstat -n -o -a | find /i "list"

to get a list of listening ports, and their process ID numbers.
Then went to task manager to get the executable name, and mapped that to actual files.  Then I excluded each Exchange-related file from the firewall.  After that, messages were sending fine.  I had a front-end/back-end configuration, and it seems like the back-end server couldn't notify the front-end that an outbound message was pending"
0
 
motaz_mohamedCommented:
If the above doesn't work, please follow the suggestions in this thread:

http://www.petri.co.il/email-stuck-in-drafts-folder.htm
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
page1985Author Commented:
Windows firewall is not enabled on the system.

The server is Exchange 2007 and Dynamics CRM is not loaded.

We are seeing the following events:

Event Type:      Error
Event Source:      MSExchangeTransport
Event Category:      Categorizer
Event ID:      9213
Date:            8/15/2012
Time:            10:43:34 PM
User:            N/A
Computer:      [REDACTED]
Description:
A non-expirable message with the internal message ID 2607713 could not be categorized. This message may be a journal report or other system message. The message will remain in the queue until administrative action is taken to resolve the error. Other messages may also have encountered this error. To further diagnose the error, use the Queue Viewer or the Mail Flow Troubleshooter.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Event Type:      Error
Event Source:      MSExchange ActiveSync
Event Category:      Server
Event ID:      1016
Date:            8/15/2012
Time:            8:34:31 PM
User:            N/A
Computer:      [Redacted]
Description:
Exchange ActiveSync has encountered repeated failures when it tries to access data on Mailbox server [REDACTED]. Exchange ActiveSync will temporarily stop making Exchange ActiveSync requests to the Mailbox server. The process will be postponed for [60] seconds. This may be caused if the Mailbox server is overloaded. If this event is frequently logged, review the Application log for other events that could indicate the root cause of performance problems on the Mailbox server specified in the event description.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
 
Sushil SonawaneCommented:
Make sure your mail submissioin services is started state.
0
 
Sushil SonawaneCommented:
Make sure your mail submissioin services is started state and Exclude the exchange database and installation folder from antivirus scan.
0
 
page1985Author Commented:
Exclusions are already present.  There is a known issue with McAfee 8.8's filter driver that causes various issues from application instability to complete server crashes.  With McAfee 8.8 Patch 1 Hotfix 1, McAfee did a complete rewrite of the filter drivers.  You can check the version of the drivers by going to %systemroot%\system32\drivers and viewing the properties of any .sys file starting with "mf".  If the version is older than 14.4.0.474, you are open to the bugs.  The problem arises from the change in the filter driver framework in Windows Server 2008.  McAfee wrote the new drivers in 8.8 to work with this new framework, so only older systems (running Windows Server 2003) are affected by the bug.
0
 
Sushil SonawaneCommented:
If your exchange services pack not update then update sp-3.
0
 
page1985Author Commented:
Located solution myself.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.