Skip to content

Commit bc05c28

Browse files
authored
Merge pull request #8266 from MicrosoftDocs/main
Sync to live
2 parents 2df291b + 7368e6e commit bc05c28

File tree

4 files changed

+106
-0
lines changed

4 files changed

+106
-0
lines changed
Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
3+
title: Error AADSTS500011 - Resource Principal Not Found
4+
description: Describes a problem in which a user experiences an AADSTS500011 error when trying to sign in to Microsoft Entra ID.
5+
author: custorod
6+
ms.author: custorod
7+
ms.service: entra-id
8+
ms.topic: troubleshooting-problem-resolution
9+
ms.date: 01/16/2025
10+
ms.subservice: authentication
11+
ms.custom: sap:Issues Signing In to Applications
12+
---
13+
14+
# AADSTS500011 - Resource Principal Not Found
15+
16+
This article describes a problem in which users experiences an "AADSTS500011" error when they try to sign in to Microsoft Entra ID.
17+
18+
## Symptoms
19+
20+
When users try to sign in to an application that uses Microsoft Entra ID authentication, they receive the following error message:
21+
22+
> `AADSTS500011 - The resource principal named [resource URL] was not found in the tenant named [tenant ID]`
23+
24+
## Cause
25+
26+
This issue occurs if the resource principal (the application or service) is not found in the tenant. This issue occurs if:
27+
28+
- The resource application isn't provisioned by the administrator in the tenant.
29+
- The resource application isn't consented to by any user in the tenant.
30+
- The resource URL is not configured correctly.
31+
- The tenant ID is not correct.
32+
33+
## Resolution
34+
35+
To resolve this issue, follow these steps:
36+
37+
1. **Verify resource application provisioning**:
38+
39+
- Make sure that the application (resource principal) is registered correctly in your Microsoft Entra ID tenant.
40+
- Go to the [Azure portal](https://portal.azure.com), and navigate to Microsoft Entra ID > Enterprise applications.
41+
- Check whether the application is listed and correctly configured.
42+
43+
1. **Consent to application**:
44+
- Make sure that the resource application has been consented to by an administrator or a user in the tenant.
45+
- Go to the [Azure portal](https://portal.azure.com), and navigate to Microsoft Entra > Enterprise applications.
46+
- Find the application, and make sure that it has the necessary permissions and consent.
47+
48+
1. **Check resource URL**:
49+
- Verify that the resource URL that appears in the error message matches the resource application that you provisioned in your tenant ID.
50+
- Make sure that the authentication request is sent by using the correct resource URL.
51+
52+
1. **Check tenant ID**:
53+
- Verify that the tenant ID that appears in the error message is the same as your tenant ID.
54+
- Make sure that the authentication request is sent to the correct Microsoft Entra ID tenant.
55+
56+
## More information
57+
58+
For a full list of authentication and authorization error codes, see [Microsoft Entra authentication and authorization error codes](/azure/active-directory/develop/reference-error-codes).
59+
60+
To investigate individual errors, go to [https://login.microsoftonline.com/error](https://login.microsoftonline.com/error).
61+
62+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/entra/entra-id/toc.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,9 @@
8181
href: app-integration/error-code-aadsts530004-acceptcompliantdevice-setting-not-configured.md
8282
- name: Error AADSTS50057 - user account is disabled
8383
href: app-integration/error-code-aadsts50057-user-account-is-disabled.md
84+
- name: AADSTS500011 - Resource Principal Not Found
85+
href: ./app-integration/error-code-aadsts500011-resource-principal-not-found.md
86+
displayName: AADSTS500011
8487
- name: Error AADSTS500571 - guest user account is disabled
8588
href: app-integration/error-code-aadsts500571-guest-user-account-is-disabled.md
8689
- name: Error AADSTS50105 - user not assigned a role
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
title: Unable to Find an Entry Point Error When Updating SQL Server 2022
3+
description: This article describes an issue where the command line generates an error message when applying a SQL Server 2022 Cumulative Update (CU).
4+
ms.date: 02/21/2025
5+
ms.custom: sap:Installation, Patching, Upgrade, Uninstall
6+
ms.author: brcarrig
7+
ms.reviewer: jopilov, v-sidong
8+
---
9+
# Unable to find an entry point error when updating SQL Server 2022
10+
11+
This article describes an issue where the command line generates an error message when applying a SQL Server 2022 Cumulative Update (CU).
12+
13+
_Applies to:_   SQL Server 2022 on Windows
14+
15+
## Symptoms
16+
17+
Consider the following scenario:
18+
19+
- You have a computer that's running an operating system (OS) that has an earlier build of the Windows OS than Windows 10 Build 20348, such as Windows Server 2016 or Windows Server 2019.
20+
21+
- You apply a cumulative update (CU) to SQL Server 2022 using **setup.exe** from the command line. For information on how to run the setup from command line, see [Install and configure SQL Server on Windows from the command prompt](/sql/database-engine/install-windows/install-sql-server-from-the-command-prompt).
22+
23+
In this scenario, an exception occurs in the setup console during the update process, displaying the following error message:
24+
25+
> System.EntryPointNotFoundException: Unable to find an entry point named 'GetNumaNodeProcessorMask2' in DLL 'kernel32.dll'
26+
27+
## Cause
28+
29+
When **setup.exe** runs on an OS version where the [GetNumaNodeProcessorMask2 API](/windows/win32/api/systemtopologyapi/nf-systemtopologyapi-getnumanodeprocessormask2) is unavailable, an exception appears in the setup console.
30+
31+
## Resolution
32+
33+
No resolution steps are necessary as the exception doesn't affect the setup behavior or success of the update. The error message can be safely ignored.
34+
35+
## More information
36+
37+
This exception is only visible in the setup console when running **setup.exe** from the command line and only applies to CU15 and later.
38+
39+
For information on all cumulative updates released after the release of SQL Server 2022, see [SQL Server 2022 build versions](../../../releases/sqlserver-2022/build-versions.md).

support/sql/database-engine/install/windows/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
items:
22
- name: .Net Framework requirements for SQL Server
33
href: understanding-dotnet-framework-requirements.md
4+
- name: Unable to find an entry point error when updating SQL Server 2022
5+
href: error-command-line-cu-sql-server-2022.md
46
- name: Attempted to perform an unauthorized operation error
57
href: error-set-up-update-instances.md
68
- name: Cannot install on Windows case-sensitive servers

0 commit comments

Comments
 (0)