Share via

Azure Data Sync: SqlError Number:18456, Message: Login failed.

Igarki 31 Reputation points
2021-01-20T10:39:52.533+00:00

Hi,

I am new in Azure environment and I have following error:

I have finished configuring Data Sync functionality in Azure for two SQL data bases. One is in Azure as central DB and the other one is in a local instance as a member.
After finished configuring data Sync following this link

https://learn.microsoft.com/es-es/azure/azure-sql/database/sql-data-sync-sql-server-configure

I have this error on my Sync Group page:

Database provisioning failed with the exception "SqlException ID: 15fe0018-3622-4854-80e7-3d4d5aad53f3,
Error Code: -2146232060 - SqlError Number:18456, Message: Login failed. For more information, provide tracing ID ‘b1ac6b27-ba93-49fb-84e3-5df49504404e’ to customer support."

Through Microsoft SQL Management I have access to both data bases without problems but it seems Azure synchronization doesn´t work fine.

Thanks for your help in advance.

Azure SQL Database
0 comments
Accepted answer
  1. Alberto Morillo 34,676 Reputation points MVP Volunteer Moderator
    2021-01-20T15:17:17.673+00:00

    Could you please try to verify if the SQL user you used to configure the hub database (the database in Azure) on the sync group has been disabled or the password has changed?

    On the Azure Database (the Hub database), make sure you provide the SQL Admin login with its current password as as explained in this article.

    1. Click on Azure DB
    2. Click "Sync to other database".
    3. Click on the sync group which you have created.
    4. Click on the Databases
    5. Click your hub server.
    6. Enter your username and current password.
    7. Try to sync.

    
    On the section named "To add a SQL Server database" on the same article, please configure the Sync Agent correctly as explained on the article. On step #3, please provide the "sa" login and password of the on-premises SQL Server instance (not located in Azure). Review all steps on that article.

    Hope this helps.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-08-15T02:09:28.92+00:00

    I have issues with this.

    • This may be an existing AD password of some complexity, but generated using conflicting rules. In my case my credentials were verified as good outside of this dialogue. However they did not contain the required numeric. This was a show-stopper for us. It is neither trivial nor convenient to change an Admin password.
    • Whilst it is obvious that the fields are an issue, it is not obvious "which" fields. I would expect a green tick next to the SQL Server AD Admin user name.
    • There is no field level validation, it accepted our password. NB. - you have to save changes to update.
    • It is also not obvious where we might update the password for the META database, and in my case it is under the same SQL Server and therefore has the same credentials.
    • If we are supposed to be using the Admin credentials and we have an AD Admin, why not prefill?
    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.