locked
MSExchangeMonitoring generates account login failures RRS feed

  • Question

  • On our E2k7 server the MSExchangeMonitoring service has started generating 2 errors repeatedly. 4625 and 4673 in the security log.  I'm not quite sure how long these have been ongoing but they were noticed yesterday.  As far as we know nothing has been changed.

    Here is the 4625 error

    Log Name:      Security
    Source:        Microsoft-Windows-Security-Auditing
    Date:          6/8/2011 1:05:17 PM
    Event ID:      4625
    Task Category: Logon
    Level:         Information
    Keywords:      Audit Failure
    User:          N/A
    Computer:      computer name

    Description:
    An account failed to log on.

    Subject:
     Security ID:  SYSTEM
     Account Name:  computername$
     Account Domain:  domain

     Logon ID:  0x3e7

    Logon Type:   3

    Account For Which Logon Failed:
     Security ID:  NULL SID
     Account Name:  
     Account Domain:  

    Failure Information:
     Failure Reason:  Unknown user name or bad password.
     Status:   0xc000006d
     Sub Status:  0xc0000064

    Process Information:
     Caller Process ID: 0x2514
     Caller Process Name: C:\Program Files\Microsoft\Exchange Server\Bin\Microsoft.Exchange.Monitoring.exe

    Network Information:
     Workstation Name: computername

     Source Network Address: -
     Source Port:  -

    Detailed Authentication Information:
     Logon Process:  C
     Authentication Package: Kerberos
     Transited Services: -
     Package Name (NTLM only): -
     Key Length:  0

    This event is generated when a logon request fails. It is generated on the computer where access was attempted.

    The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

    The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

    The Process Information fields indicate which account and process on the system requested the logon.

    The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

    The authentication information fields provide detailed information about this specific logon request.
     - Transited services indicate which intermediate services have participated in this logon request.
     - Package name indicates which sub-protocol was used among the NTLM protocols.
     - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" />
        <EventID>4625</EventID>
        <Version>0</Version>
        <Level>0</Level>
        <Task>12544</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8010000000000000</Keywords>
        <TimeCreated SystemTime="2011-06-08T17:05:17.034Z" />
        <EventRecordID>69250412</EventRecordID>
        <Correlation />
        <Execution ProcessID="632" ThreadID="8220" />
        <Channel>Security</Channel>
        <Computer>computernamedomain</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="SubjectUserSid">S-1-5-18</Data>
        <Data Name="SubjectUserName">computername$</Data>
        <Data Name="SubjectDomainName">doamain</Data>
        <Data Name="SubjectLogonId">0x3e7</Data>
        <Data Name="TargetUserSid">S-1-0-0</Data>
        <Data Name="TargetUserName">
        </Data>
        <Data Name="TargetDomainName">
        </Data>
        <Data Name="Status">0xc000006d</Data>
        <Data Name="FailureReason">%%2313</Data>
        <Data Name="SubStatus">0xc0000064</Data>
        <Data Name="LogonType">3</Data>
        <Data Name="LogonProcessName">C</Data>
        <Data Name="AuthenticationPackageName">Kerberos</Data>
        <Data Name="WorkstationName">computername</Data>
        <Data Name="TransmittedServices">-</Data>
        <Data Name="LmPackageName">-</Data>
        <Data Name="KeyLength">0</Data>
        <Data Name="ProcessId">0x2514</Data>
        <Data Name="ProcessName">C:\Program Files\Microsoft\Exchange Server\Bin\Microsoft.Exchange.Monitoring.exe</Data>
        <Data Name="IpAddress">-</Data>
        <Data Name="IpPort">-</Data>
      </EventData>
    </Event>

    And here is the 4673 error. 

    Log Name:      Security
    Source:        Microsoft-Windows-Security-Auditing
    Date:          6/8/2011 1:05:17 PM
    Event ID:      4673
    Task Category: Sensitive Privilege Use
    Level:         Information
    Keywords:      Audit Failure
    User:          N/A
    Computer:      computername

    Description:
    A privileged service was called.

    Subject:
     Security ID:  SYSTEM
     Account Name:  computername$
     Account Domain:  domain
     Logon ID:  0x3e7

    Service:
     Server: NT Local Security Authority / Authentication Service
     Service Name: LsaRegisterLogonProcess()

    Process:
     Process ID: 0x278
     Process Name: C:\Windows\System32\lsass.exe

    Service Request Information:
     Privileges:  SeTcbPrivilege
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" />
        <EventID>4673</EventID>
        <Version>0</Version>
        <Level>0</Level>
        <Task>13056</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8010000000000000</Keywords>
        <TimeCreated SystemTime="2011-06-08T17:05:17.018Z" />
        <EventRecordID>69250411</EventRecordID>
        <Correlation />
        <Execution ProcessID="632" ThreadID="684" />
        <Channel>Security</Channel>
        <Computer>computername</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="SubjectUserSid">S-1-5-18</Data>
        <Data Name="SubjectUserName">computername$</Data>
        <Data Name="SubjectDomainName">domain</Data>
        <Data Name="SubjectLogonId">0x3e7</Data>
        <Data Name="ObjectServer">NT Local Security Authority / Authentication Service</Data>
        <Data Name="Service">LsaRegisterLogonProcess()</Data>
        <Data Name="PrivilegeList">SeTcbPrivilege</Data>
        <Data Name="ProcessId">0x278</Data>
        <Data Name="ProcessName">C:\Windows\System32\lsass.exe</Data>
      </EventData>
    </Event>


    Wednesday, June 8, 2011 5:13 PM

All replies

  • Hi,

     

    Here are some related documents for you, hope can give you some help:

     

    The Security event that has Event ID 4625 does not contain the user account name on a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2

    http://support.microsoft.com/kb/2157973

     

    Description of security events in Windows Vista and in Windows Server 2008

    http://support.microsoft.com/kb/947226

     

    Thanks,

     

    Evan Liu

     

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, June 13, 2011 5:55 AM
    Moderator