Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to translate Schannel errors recently #397

Open
jdickson289 opened this issue Dec 11, 2024 · 3 comments
Open

Unable to translate Schannel errors recently #397

jdickson289 opened this issue Dec 11, 2024 · 3 comments

Comments

@jdickson289
Copy link

Windows Server 2019 Datacenter

Schannel errors appear like this now where before they were transcribed.

Log Name: System
Source: Schannel
Date: 12/11/2024 6:37:43 PM
Event ID: 36871
Task Category: None
Level: Error
Keywords:
User: S-1-5-18
Computer:
Description:
Unable to resolve description, see XML for more details.
Event Xml:



36871
0
2
0
0
0x8000000000000000

1568233


System




client
10013

@jschick04
Copy link
Contributor

Is this resolving locally or with the databases?

@jdickson289
Copy link
Author

jdickson289 commented Dec 12, 2024 via email

@jschick04
Copy link
Contributor

Let me clarify, which scenario are you performing...

  1. Are you using databases under settings and viewing a saved log from 2019 on a non 2019 system.
  2. Using databases under settings and viewing a saved log from 2019 on a 2019 system.
  3. Using databases under settings and using "File > Open > Live Event Log > System".
  4. No databases enabled under settings and using "File > Open > Live Event Log > System".
  5. No databases enabled under settings and viewing a saved 2019 log from a non 2019 system.
  6. No databases enabled under settings and viewing a saved 2019 log on a 2019 system.

I have only able to repro this when using multiple databases if the event is from an older system.
Example, loading a 2019 log and having databases for 2019 and 2022 enabled. This causes an issue because the event descriptions are different between versions and only the newer template is used. Because the event descriptions are different, the template parameters count does not match the events parameters count which is 1 reason we display "Unable to resolve description". If I disable the 2022 database and only use the 2019 database, then it resolves just fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants