|
| 1 | +--- |
| 2 | +title: Event ID 7 Is Intermittently Logged on a Windows Server 2025-Based DC |
| 3 | +description: Describes an issue in which event ID 7 is intermittently logged on a Windows Server 2025-based DC. |
| 4 | +ms.date: 06/25/2025 |
| 5 | +manager: dcscontentpm |
| 6 | +audience: itpro |
| 7 | +ms.topic: troubleshooting |
| 8 | +ms.reviewer: jories |
| 9 | +ms.custom: |
| 10 | +- sap:windows security technologies\kerberos authentication |
| 11 | +- pcy:WinComm Directory Services |
| 12 | +--- |
| 13 | +# Event ID 7 is intermittently logged on a Windows Server 2025-based domain controller |
| 14 | + |
| 15 | +Active Directory domain controllers (DCs) that are running Windows Server 2025 might intermittently log event ID 7. This article provides suggestions for this error. |
| 16 | + |
| 17 | +## Event sample |
| 18 | + |
| 19 | +Here's a sample of the event: |
| 20 | + |
| 21 | +> Log Name: System |
| 22 | +> Source: Microsoft-Windows-Kerberos-Key-Distribution-Center |
| 23 | +> Date: \<date time\> |
| 24 | +> Event ID: 7 |
| 25 | +> Task Category: None |
| 26 | +> Level: Error |
| 27 | +> Keywords: Classic |
| 28 | +> User: N/A |
| 29 | +> Computer: \<dc fqdn\> |
| 30 | +> Description: |
| 31 | +> The Security Account Manager failed a KDC request in an unexpected way. The error is in the data field. **The account name was** and lookup type 0x108. |
| 32 | +
|
| 33 | +Event XML: |
| 34 | + |
| 35 | +```xml |
| 36 | +<Event |
| 37 | +xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> |
| 38 | + <System> |
| 39 | + <Provider Name="Microsoft-Windows-Kerberos-Key-Distribution-Center" Guid="(guid)" EventSourceName="KDC" /> |
| 40 | + <EventID Qualifiers="49152">7</EventID> |
| 41 | + <Version>0</Version> |
| 42 | + <Level>2</Level> |
| 43 | + <Task>0</Task> |
| 44 | + <Opcode>0</Opcode> |
| 45 | + <Keywords>0x80000000000000</Keywords> |
| 46 | + <TimeCreated SystemTime="(date time)" /> |
| 47 | + <EventRecordID>29550</EventRecordID> |
| 48 | + <Correlation /> |
| 49 | + <Execution ProcessID="896" ThreadID="0" /> |
| 50 | + <Channel>System</Channel> |
| 51 | + <Computer>(dc fqdn)</Computer> |
| 52 | + <Security /> |
| 53 | + </System> |
| 54 | + <EventData> |
| 55 | + <Data Name="AccountName"> |
| 56 | + </Data> |
| 57 | + <Data Name="LookupType">0x108</Data> |
| 58 | + <Binary>0D0000C0</Binary> |
| 59 | + </EventData> |
| 60 | +</Event> |
| 61 | +``` |
| 62 | + |
| 63 | +> [!IMPORTANT] |
| 64 | +> The text of the event has a blank account name: **The account name was ...**. |
| 65 | +> |
| 66 | +> If the event ID lists a different account name or lookup type, it might be a separate issue that requires investigation. |
| 67 | +
|
| 68 | +## Resolution |
| 69 | + |
| 70 | +Microsoft has acknowledged this issue. It doesn't affect computer functionality or performance. These events can be safely ignored when the account name is blank. |
| 71 | + |
| 72 | +## More information |
| 73 | + |
| 74 | +This issue only affects Windows Server 2025 when running as an Active Directory Key Distribution Center (KDC). Other versions of Windows Server don't have this issue. |
0 commit comments