Quantcast
Channel: SQL Server Database Engine forum
Viewing all articles
Browse latest Browse all 12963

Event ID 4625 is logged on Windows Security logs for every 30 minute but nothing in SQL Server logs

$
0
0

I'm using SQL Server 2008 R2.  Event ID 4625 is logged on Windows Security logs for every 30 minute but nothing is logged on SQL Server logs.

This is from the General tab of Windows Security logs:

An account failed to log on.

Subject:
 Security ID:  SYSTEM
 Account Name:  TEST$
 Account Domain:  XXX
 Logon ID:  0x3e7

Logon Type:   3

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

Failure Information:
 Failure Reason:  The specified user account has expired.
 Status:   0xc0000193
 Sub Status:  0xc0000193

Process Information:
 Caller Process ID: 0xab4
 Caller Process Name: C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe

Network Information:
 Workstation Name: TEST
 Source Network Address: -
 Source Port:  -

Detailed Authentication Information:
 Logon Process:  Authz  
 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.

This is from the Details tab of Windows Security logs:

-<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
-<System>
 <ProviderName="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>
 <TimeCreatedSystemTime="2013-12-23T17:21:00.916876600Z" />
 <EventRecordID>2131255</EventRecordID>
 <Correlation/>
 <ExecutionProcessID="576" ThreadID="644" />
 <Channel>Security</Channel>
 <Computer>TEST.xxx.xxx</Computer>
 <Security/>
 </System>
-<EventData>
 <Data Name="SubjectUserSid">S-1-5-18</Data>
 <Data Name="SubjectUserName">TEST$</Data>
 <Data Name="SubjectDomainName">XXX</Data>
 <Data Name="SubjectLogonId">0x3e7</Data>
 <Data Name="TargetUserSid">S-1-0-0</Data>
 <DataName="TargetUserName"
/>
 <DataName="TargetDomainName"
/>
 <Data Name="Status">0xc0000193</Data>
 <Data Name="FailureReason">%%2305</Data>
 <Data Name="SubStatus">0xc0000193</Data>
 <Data Name="LogonType">3</Data>
 <Data Name="LogonProcessName">Authz</Data>
 <Data Name="AuthenticationPackageName">Kerberos</Data>
 <Data Name="WorkstationName">TEST</Data>
 <Data Name="TransmittedServices">-</Data>
 <Data Name="LmPackageName">-</Data>
 <Data Name="KeyLength">0</Data>
 <Data Name="ProcessId">0xab4</Data>
 <Data Name="ProcessName">C:\Program Files\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
</Data>
 <Data Name="IpAddress">-</Data>
 <Data Name="IpPort">-</Data>
 </EventData>
 </Event>

Can this be related to the owner of some databases in that instance that has expired password?  However, I really doubt that since there is another sql instance which also has some databases owned by the same owner and there is nothing logged in Windows Security logs for that instance.


Viewing all articles
Browse latest Browse all 12963

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>