Exchange Error Log
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company exchange 2010 logs location Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags exchange 2010 smtp log file location Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only exchange 2010 transaction logs location takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Exchange server email logs location up vote 2 down exchange 2010 receive connector log location vote favorite Recently we not get some emailes, from a specific provider. It seems the mails reach our server (there is no error on the sender side), so I want to check the logs why our Exchange server not process those emailes. exchange exchange-2010 share|improve this question asked Jan 27 '14 at 10:10 NoNameProvided 1182211 add a comment| 2 Answers 2 active oldest votes up vote 3 down vote accepted I'd try something like this
Exchange 2010 Log Files Growing Rapidly
from the Exchange Management shell (or another machine with the Exchange cmdlets): Get-MessageTrackingLog -start '[date it started]' -resultsize unlimited | where-object {$_.Sender -like '*theirdomain.com'} If that turns up a bunch of FAIL, try: Get-AgentLog -startdate '[date it started]' | where {$_.P1FromAddress -like '*theirdomain.com'} | select-object Reason | group-object Reason for an explanation of why Exchange doesn't love them. Silent drops are frequently antispam. If there's no record of them ever touching Exchange, I'd assume that something is wrong on their end. share|improve this answer answered Jan 27 '14 at 12:57 Katherine Villyard 15.4k42549 1 I just don't see anything, maybe the error is elsewhere. I marked this as answer. –NoNameProvided Jan 27 '14 at 15:34 add a comment| up vote 3 down vote From the Exchange Management Console, in the toolbox menu, you can use the Message Tacking feature (this will open the GUI in the web interface). Edit : To open the GUI whithin the Exchange Management Console, select Mail Flow Troubleshooter From here you can define many filters to search for specific emails, and see how your transport servers have processed them. http://exchangeserverpro.com/exchange-2010-message-tracking/ Also, if you have an Anti-spam software/hardware appliance in front of your Exchange servers, it could be useful to check them to see if they have not considered these emails as Spam and dropped/quarantine them. share|improve this answ
Availability Migration You are here: Home / Tutorials / Troubleshooting Email Delivery with Exchange Server Protocol LoggingTroubleshooting Email Delivery with Exchange Server Protocol Logging August 10, 2012 by Paul Cunningham 56 Comments This week I
Exchange 2010 Log File Location Best Practice
tweeted a tip that can help you troubleshoot email delivery for your Exchange servers. exchange server 2010 transaction log files location #MSExchange Tip: Turn on protocol logging on your send/receive connectors now, so you have the logs when you need them. exchange 2010 transaction logs default location — Exchange Server Pro (@ExchServPro) August 9, 2012 In this article I'm going to expand on that topic and explain why protocol logging is useful, and how you can enable it in your http://serverfault.com/questions/570084/exchange-server-email-logs-location own environment. What is Exchange Server Protocol Logging? Protocol logs capture the SMTP communications that occur between servers. The information that is written to the protocol log files looks very similar to what you see when you are using Telnet to make an SMTP connection. Example of a protocol logging log file This information is invaluable in troubleshooting scenarios, because it captures events that occur during http://exchangeserverpro.com/exchange-server-protocol-logging/ message delivery that may not appear in other logs on the server. For example, many administrators are used to looking in message tracking logs when they troubleshoot email delivery. But message tracking logs only record events for messages once they are in the transport pipeline. If a message is never sent/received because the SMTP connection itself is rejected, the message tracking log will show no useful troubleshooting information. There are two parts to the configuration of protocol logging in Exchange Server, and they are basically the same across Exchange 2007, Exchange 2010, and Exchange 2013. Configuring Protocol Logging on Transport Servers The first is the per-server settings, configured on Hub Transport and Edge Transport servers for Exchange 2007/2010, or either Client Access or Mailbox servers in Exchange 2013. Protocol log paths can be set in the Exchange Management Console in the properties of the server. However, most of the other useful settings can only be configured in the Exchange Management Shell. You can use Get-TransportServer to view existing settings. [PS] C:\>Get-TransportServer ho-ex2010-mb1 | select *protocollog* IntraOrgConnectorProtocolLoggingLevel : None ReceiveProtocolLogMaxAge : 30.00:00:00 ReceiveProtocolLogMaxDirectorySize : 250 MB (262,144,000 bytes) ReceiveProtocolLogMaxFileSize : 10 MB (10,485,760 bytes) ReceiveProtocolLogPath : C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Log
View All Mail Protocols Internet Information Services (IIS) Administration Tools Active Directory Licensing Mailbox Management Performance Scripts and Programming User Settings Calendar http://searchexchange.techtarget.com/tip/Troubleshooting-Exchange-Server-error-messages and Contact Management Email, Messaging and Collaboration Clients View All IM and Unified Messaging Microsoft Outlook Mobile Devices MS Office 365 Outlook Web Access Email, Messaging and Collaboration Servers View All Legacy Exchange Servers Microsoft Exchange Server 2003 Microsoft Exchange Server 2007 Microsoft Exchange Server exchange 2010 2010 Microsoft Exchange Server 2013 Exchange 2016 SharePoint Small Business Server Exchange Security View All Compliance Management Compliance tools Email Compliance Email Encryption Email Policy Management ISA Server and Firewalls Password Management Microsoft Exchange Server Permissions Phishing and Email Fraud Protection Spam and virus protection User exchange 2010 log Authentication for Outlook and OWA Virtual Private Networks (VPNs) Exchange Administration View All Mail Protocols Internet Information Services (IIS) Administration Tools Active Directory Licensing Mailbox Management Monitoring and Logging Performance Scripts and Programming User Settings Calendar and Contact Management Exchange Deployment and Migration View All Deployment and Migration Advice Deployment and Migration Tools Exchange Storage and Data Management View All .OST Files .PST Files Backup Microsoft Exchange Server Clustering Database Management Defragmentation Email Archiving Hardware Management Information Store Public Folders Storage Management Replication and Synchronization Transaction Logs Topics Archive View All Please select a category Email, Messaging and Collaboration Clients Email, Messaging and Collaboration Servers Exchange Security Exchange Administration Exchange Deployment and Migration Exchange Storage and Data Management Section Problem Solve News Get Started Evaluate Manage Problem Solve Sponsored Communities Troubleshooting Exchange Server err