Share via

Cannot locate lsp.log in Windows Server 2016 to check an error reported by trust scanner operations

IT_MAN_ 1 Reputation point
2022-12-19T12:30:08.073+00:00

Hello everyone, this is my first question in Microsoft Learn.

I'm trying to find lsp.log because I've been receiving since two weeks ago each 8 hours, events 6149 and 6153, this events are reporting that there is at least one error in the trust scan operation.

I tryied to follow this instructions that are refered to this events (Investigating failed PDC trust scanner operations): https://learn.microsoft.com/en-us/troubleshoot/windows-server/windows-security/windows-updates-add-new-ntlm-pass-through-authentication-protections

But when I'm in the step 4, I can't find the lsp.log, I tried also to find it using explorer and also in "C:\Windows\Logs" folder, but it isn't there.

Does anyone else have this problem?

Thanks in advance.

Windows for business | Windows Client for IT Pros | Directory services | Active Directory
Windows for business | Windows Server | User experience | Other
Windows for business | Windows Server | Devices and deployment | Configure application groups
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-12-19T16:30:18.523+00:00

    Looks like you'll need to enable it, then a reboot may be required.
    https://learn.microsoft.com/en-us/troubleshoot/windows-server/windows-security/windows-updates-add-new-ntlm-pass-through-authentication-protections#enable-and-disable-lsa-logging-lsplog-by-using-powershell 

    Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Lsa" -Name LspDbgInfoLevel -Value 0x1820000 -Type dword -Force   
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Lsa" -Name LspDbgTraceOptions -Value 0x1 -Type dword -Force

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    1 person found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.