Views:

Applies to Product - Dynamics 365 Business Central

What’s happening?
Customers encounter an "OLE DB or ODBC error: [DataSource.Error] Dynamics365BusinessCentral: Request failed: The remote server returned an error: (400) Bad Request (User not found)" when attempting to access the Users page or refresh reports in Business Central.
 

Reason:
This arises when users are removed from the Active Directory (AD) but still exist in the Business Central Users page. This situation often occurs when users are moved to a non-synced Organizational Unit (OU) in on-premises AD, leading to their accounts being soft-deleted in Entra ID for 30 days before permanent deletion.
 

Resolution:

  • Confirm whether the user IDs from the error match the GDAP users in the Users page.
  • If the users are no longer being used, delete them from the Users page in Business Central and check if the error persists.
  • Remove the user from Microsoft 365 if they are not going to be used.
  • Ensure that any roles or permissions assigned to the user are noted before deletion.
  • Users can be restored in Microsoft 365 for 30 days, and updates from Microsoft 365 to Business Central can be performed as long as they have a license.
  • If the issue continues, further investigation may be required, including checking the OLE DB or ODBC setup and the general setup for the users.