You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Event ID 7 is intermittently logged on a Windows Server 2025-based DC
13
+
# Event ID 7 is intermittently logged on a Windows Server 2025-based domain controller
14
14
15
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
16
@@ -28,9 +28,9 @@ Here's a sample of the event:
28
28
> User: N/A
29
29
> Computer: \<dc fqdn\>
30
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.
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.
> The text of the event has a blank account name: **The account name was ...**.
64
+
> The event text contains a blank account name.
65
65
>
66
66
> If the event ID lists a different account name or lookup type, it might be a separate issue that requires investigation.
67
67
68
68
## Resolution
69
69
70
-
This issue doesn't affect computer functionality or performance. These events can be safely ignored when the account name is blank.
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
71
72
72
## More information
73
73
74
-
This issue only impacts Windows Server 2025 when running as an Active Directory Key Distribution Center (KDC). No other versions of Windows Server have this issue.
75
-
76
-
Microsoft has acknowledged this issue. These events can be safely ignored.
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