Azure Sql Ledger Deployment Failed

Question

Azure Sql Ledger Deployment Failed

Mike-E-angelo 611

I am attempting to deploy an Azure SQL Ledger deployment (Sqlledgerdeployment-UpdateDigeststorageSettings) and it is failing with the following:

{
    "status": "Failed",
    "error": {
        "code": "Failed",
        "message": "The delegate executed asynchronously through TimeoutPolicy did not complete within the timeout."
    }
}

Note that this is for Microsoft.ConfidentialLedger/ledgers

Help. :P

Saurabh Sharma 23,866 Reputation points Microsoft Employee Moderator

2022-01-06T23:50:10.343+00:00

Hi @Mike-E-angelo ,

Thanks for using Microsoft Q&A!!
Are you trying to enable ledger on existing database or creating a ledger as part of new database creation on Azure portal? Also, in which region you are trying to deploy the ledger?

I have tried to create a ledger and it worked fine for me.

Thanks
Saurabh
Mike-E-angelo 611 Reputation points

2022-01-07T06:44:24.013+00:00

Thank you very much for looking into this @Saurabh Sharma . I tried it while creating a new database and then afterwards after it was created, and both times it resulted in the reported failure. For further context, this appears to be in the Digest storage component, creating a Confidential ledger:

There does not appear to be region associated with this setting.
Mike-E-angelo 611 Reputation points

2022-01-07T06:51:30.727+00:00

Nevermind @Saurabh Sharma I tried again and it worked! Posted an answer below. Thank you again for your assistance and paying attention to these posts. :)
Saurabh Sharma 23,866 Reputation points Microsoft Employee Moderator

2022-01-11T21:40:36.647+00:00

Hi @Mike-E-angelo ,

Great. Thanks for the confirmation. Please feel free to accept your answer.

Thanks
Saurabh
Mike-E-angelo 611 Reputation points

2022-01-12T11:18:06.28+00:00

Thank you for the suggestion @Saurabh Sharma . Unfortunately, while it appears I can create my own answers, I cannot mark them as the accepted answer. Add another bug to the list!
Mike-E-angelo 611 Reputation points

2022-01-13T23:41:06.39+00:00
Hi again @Saurabh Sharma ... as luck would have it, I decided to start over from scratch and rebuild my Sql Server from the beginning. I have everything setup with the exception of the Confidential Ledger. This time I am creating it directly rather than from the Sql Server interface above. This is what occurs with each attempt:

{ "status": "Failed", "error": { "code": "ResourceCreationFailed", "message": "ResourceCreationFailed: Forbidden" } }

Sample tracking id for you if interested: 2665cd8b-1127-4459-9f00-668c9d834a25

Thank you for any assistance you can provide.

1 answer

Your answer

Saurabh Sharma 23,866 Reputation points Microsoft Employee Moderator

2022-01-06T23:50:10.343+00:00

Hi @Mike-E-angelo ,

Thanks for using Microsoft Q&A!!
Are you trying to enable ledger on existing database or creating a ledger as part of new database creation on Azure portal? Also, in which region you are trying to deploy the ledger?

I have tried to create a ledger and it worked fine for me.

Thanks
Saurabh
Mike-E-angelo 611 Reputation points

2022-01-07T06:44:24.013+00:00

Thank you very much for looking into this @Saurabh Sharma . I tried it while creating a new database and then afterwards after it was created, and both times it resulted in the reported failure. For further context, this appears to be in the Digest storage component, creating a Confidential ledger:

There does not appear to be region associated with this setting.
Mike-E-angelo 611 Reputation points

2022-01-07T06:51:30.727+00:00

Nevermind @Saurabh Sharma I tried again and it worked! Posted an answer below. Thank you again for your assistance and paying attention to these posts. :)
Saurabh Sharma 23,866 Reputation points Microsoft Employee Moderator

2022-01-11T21:40:36.647+00:00

Hi @Mike-E-angelo ,

Great. Thanks for the confirmation. Please feel free to accept your answer.

Thanks
Saurabh
Mike-E-angelo 611 Reputation points

2022-01-12T11:18:06.28+00:00

Thank you for the suggestion @Saurabh Sharma . Unfortunately, while it appears I can create my own answers, I cannot mark them as the accepted answer. Add another bug to the list!
Mike-E-angelo 611 Reputation points

2022-01-13T23:41:06.39+00:00

Hi again @Saurabh Sharma ... as luck would have it, I decided to start over from scratch and rebuild my Sql Server from the beginning. I have everything setup with the exception of the Confidential Ledger. This time I am creating it directly rather than from the Sql Server interface above. This is what occurs with each attempt:

{ "status": "Failed", "error": { "code": "ResourceCreationFailed", "message": "ResourceCreationFailed: Forbidden" } }

Sample tracking id for you if interested: 2665cd8b-1127-4459-9f00-668c9d834a25

Thank you for any assistance you can provide.

Answer 1

Mike-E-angelo 611

Woohoo! I just now tried again and everything works as expected. I am wondering if this is due to the Active Directory-only Authentication setting that I had applied before earlier in the day, or some other transient issue.

The error was very vague and did not say what was wrong. It would be ideal to have it report the cause of the error, but otherwise I am set now.

Share via

Azure Sql Ledger Deployment Failed

1 answer

Your answer