Share via


MSExchangeTransport 1035

 

Ultima modifica dell'argomento: 2011-03-19

In questo articolo vengono fornite una spiegazione e delle possibili soluzioni per uno specifico evento Exchange. Per ulteriori informazioni, vedere la Guida di Exchange 2010.

Details

Product Name

Exchange

Product Version

14.0

Event ID

1035

Event Source

MSExchangeTransport

Category

SmtpReceive

Symbolic Name

SmtpReceiveAuthenticationFailed

Message Text

Inbound authentication failed with error %1 for Receive connector %2. The authentication mechanism is %3. The source IP address of the client who tried to authenticate to Microsoft Exchange is [%4].

Explanation

This event indicates that a remote Exchange\ server cannot authenticate in association with the SMTP Receive component of the Microsoft Exchange Transport service on the local Microsoft Exchange server.

The Microsoft Exchange Transport service controls the sending and receiving of messages in Microsoft Exchange Server 2010. The Exchange 2010 transport pipeline uses the SMTP Receive component to validate the message content before the message can be submitted to the Submission queue. The SMTP Receive component applies a series of receive events and, if configured, antivirus and anti-spam events to validate the message. Additionally, the SMTP Receive component authenticates connections to route internal users' messages among servers.

For more information, see the following topics:

User Action

To troubleshoot this issue, do one or more of the following:

  • Verificare se nel registro applicazioni e nel registro eventi di sistema sui server Exchange 2010 sono presenti eventi correlati. Ad esempio, eventi che si sono verificati immediatamente prima e dopo questo evento possono offrire ulteriori informazioni sulla causa principale dell'errore.
  • Review the Operations Console in Operations Manager for detailed information about the cause of this problem. For more information, see the "Introduction" section in this article.
  • Increase diagnostics logging to log the components in the transport pipeline. To increase diagnostics logging for the Transport components, follow these steps:
    1. In the Exchange Management Console, expand Server Configuration, and then click Hub Transport.
      Note   For and Edge Transport server, click Edge Transport.
    2. In the Actions pane, click Manage Diagnostic Logging Properties for the appropriate server.
    3. Expand MSExchangeTransport.
    4. Click the following components, click Expert, and then click Configure for each component:
    • Smtpreceive
    • Smtpsend
    • DSN
    • Components
    • Remote Delivery
    • Categorizer
  • Verify that the time on the Exchange server is synchronized with the domain controller. Also, verify that the SPN for the SMTP service is registered correctly. For more information, see Microsoft Knowledge Base article 979174, Event ID: 1035 is logged when some e-mail messages are stuck in a remote delivery queue in a Microsoft Exchange Server 2007 environment or in a Microsoft Exchange Server 2010 environment.
  • Increase diagnostics logging for Kerberos on the Exchange server. To do this, follow these steps:
    1. Start Registry Editor (Regedit.exe).
    2. Create the following registry entry if it does not already exist:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Lsa\Kerberos\Parameters
      Value name: loglevel
      Value type: REG_DWORD
      Value data: 1
    3. Examine the Application log for any Kerberos-related events. After you finish troubleshooting the issue, set the loglevel value to 0 (zero) or remove the value.
  • Enable diagnostics logging on the affected receive connector. To do this, follow these steps:
    1. Run the following commands from the Exchange Management shell:
      Set-ReceiveConnector "name of connector " -ProtocolLoggingLevel Verbose
      Set-TransportServer Exchange01 -ConnectivityLogEnabled $true
      Set-TransportServer "Exchange01" -IntraOrgProtocolLoggingLevel Verbose
    2. After Event ID 1035 is logged, , examine the SmtpReceive log file. By default, this file is located in the following directory:
      %ProgramFiles%\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpReceive
  • If the server is part of an Exchange hosting environment, consider disabling Windows authentication on the client receive connector. In this scenario, you may be unable to control the authentication mechanism used by clients. Clients may be trying to connect by using Basic authentication. To remove Windows authentication, follow these steps:
    1. Start the Exchange Management Console.
    2. Expand Server Configuration, and then click the Hub Transport server.
    3. Click the Receive Connectors tab, click the Client receive connector, and then click Properties in the Actions pane.
    4. Click the Authentication tab, and then click to clear the Integrated Windows authentication check box.
    5. Click OK.
  • Risolvere il problema utilizzando le opzioni di supporto in autonomia e/o assistito e altre risorse. È possibile accedere a queste risorse dal centro soluzioni di Exchange Server (la pagina potrebbe essere in inglese). In questa pagina fare clic su Self-Support Options nel riquadro di spostamento per utilizzare le opzioni di supporto in autonomia. Il supporto in autonomia prevede, tra le altre, soluzioni quali la ricerca nella Microsoft Knowledge Base e l'invio di domande ai forum di Exchange Server. In alternativa, nel riquadro di spostamento fare clic su Assisted Support Options per contattare un addetto al supporto tecnico Microsoft. Dal momento che l'organizzazione potrebbe avere una procedura specifica per contattare direttamente il Servizio Supporto Tecnico Clienti Microsoft, esaminare innanzitutto le linee guida dell'organizzazione.

For more information about the transport pipeline in Exchange 2010, see Informazioni sulla pipeline di trasporto.

To obtain transport architecture diagrams, see the Exchange Server Team blog article, Exchange 2010 Transport Architecture Diagrams Available for Download.

Il contenuto di ogni blog e il relativo URL sono soggetti a modifica senza preavviso. Il contenuto di ogni blog viene fornito "COSÌ COM'È" senza garanzie, e non conferisce alcun diritto. L'utilizzo del codice o degli script di esempio forniti è soggetto ai termini specificati nella pagina Web Condizioni di utilizzo di Microsoft.