-
Notifications
You must be signed in to change notification settings - Fork 10k
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
Helix failure EPT_S_NOT_REGISTERED
#57416
Labels
Comments
dotnet-issue-labeler
bot
added
the
needs-area-label
Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically
label
Aug 19, 2024
amcasey
added
test-failure
and removed
needs-area-label
Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically
labels
Aug 19, 2024
This was referenced Aug 19, 2024
amcasey
added a commit
to amcasey/aspnetcore
that referenced
this issue
Aug 19, 2024
Supposedly, this will tell us whether the crypto bridge into LSASS is broken. It may require multiple runs.
Possibly relevant: GSA/piv-guides#102 (comment) (via @adityamandaleeka) |
Sdk was is seeing validation errors in windows hosts dotnet/sdk#42870 |
did this start with the new helix rollout last week? |
3 tasks
Merged #57431 that hopefully avoids some of the template test problems. |
This is the same problem as dotnet/dnceng#3844 AFAICT. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've been seeing a lot of Helix runs fail with a number of messages related to
EPT_S_NOT_REGISTERED
:The failures only occur on Windows and inconsistently affect subsets of the IIS, HTTPS, Data Protection, and Certificate tests.
AFAICT,
EPT_S_NOT_REGISTERED
indicates that lsass.exe is not available.Known Issue Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=778691
Error message validated:
[(Local Security Authority cannot be contacted)|(no more endpoints available)
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 8/19/2024 8:44:57 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: