Failed Testing Connection to ECMA Application

Question

I've been trying to follow this guide: https://learn.microsoft.com/en-us/entra/identity/app-provisioning/on-premises-sql-connector-configurein order to test provisioning users to an SQL-based server, I've been using the ECMA connector host for this case and an ECMA enterprise application on Entra.

I have an SQL Server set up on my virtual machine running Windows Server 2022 and followed all steps up to test credentials successfully.

Whenever I test credentials, it tells me my credentials are wrong on entra, even though I've ensured they aren't. I've restarted the provisioning service multiple times and recreated connectors to try to resolve this issue to no avail, please help!

Answer 1

Hi David8822,

Thank you for posting in the Microsoft Community Forums.

In response to your description of the problem you encountered when testing the configuration of users to an SQL-based server using the ECMA Connector Host and the ECMA Enterprise Application on Microsoft Entra, where credentials were incorrectly recognized on Entra, here are some possible resolution steps and suggestions for you to consider:

Confirm that the credentials are correct:

Double-check that the credentials (username and password) you entered are completely correct, including case and special characters.

Make sure that the credentials you are using match the credentials set up on SQL Server.

Check the SQL Server configuration:

Verify that the SQL Server authentication mode is set up correctly.SQL Server provides two authentication modes: Windows authentication and SQL Server authentication (mixed mode). Make sure you select the correct authentication mode and configure the appropriate credentials.

If you are using mixed mode, make sure that the SQL Server login and password have been set up correctly and that SQL Server has granted the appropriate access rights to the login.

Check the ECMA connector configuration:

Double-check the ECMA connector configuration to ensure that the SQL Server domain name, instance name, port number, and authentication credentials have been correctly specified.

If possible, try testing the connection using a different authentication method such as Windows authentication.

Check the Microsoft Entra configuration:

Verify that you have properly configured the ECMA Enterprise application in Microsoft Entra and that the connection information to SQL Server is set up correctly.

Check if there are any authentication-related policies or settings that might be preventing the connection.

Review the logs and error messages:

Check the logs of the ECMA connector host and Microsoft Entra for more detailed information about credential errors.

Look for any possible error codes or messages that may help diagnose the problem.

Restart the service and reconfigure:

Although you have restarted the on-premises service and recreated the connector several times, make sure that you have performed adequate testing after each configuration change.

If possible, try resetting the SQL Server and ECMA connectors on a different virtual or physical machine to troubleshoot any environment-specific issues.

Best regards

Neuvi