Azure Document Intelligence Model Training Error - InternalServerError

Jarvis Wong (HK) 5 Reputation points
2024-01-10T03:59:45.7566667+00:00

I recently encountered an error while training a custom model using Azure Document Intelligence under the template built mode . The training process had been running smoothly until this point, but now I am facing an unexpected issue.

More context:

  • Labeled 13 PDF samples for the model with table, field, signature and selection marks
  • Which I clicked on the "train" button, the system instantly returned an error message indicating a model training failure.

As the training had been progressing without any issues before. I have double-checked my labeled samples and made sure they comply with the required format and guidelines.

To help diagnose the problem, I have attached a screenshot of the error message that I received. It would be greatly appreciated if anyone could shed some light on the possible causes of this error and suggest potential solutions.

User's image

Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
3,168 questions
Azure AI Document Intelligence
Azure AI Document Intelligence
An Azure service that turns documents into usable data. Previously known as Azure Form Recognizer.
2,050 questions
{count} votes

1 answer

Sort by: Most helpful
  1. santoshkc 14,505 Reputation points Microsoft External Staff Moderator
    2024-01-10T08:33:43.2566667+00:00

    Hi @Jarvis Wong (HK),

    Based on the error message you received, it seems that an unexpected error occurred while training your custom model. This error message is not very specific, so it can be difficult to determine the exact cause of the issue. However, there are a few potential solutions that you can try to resolve this error:

    • Ensure that your Azure subscription is active and that you have sufficient resources to train your custom model.
    • Please make sure all input requirements as mentioned here.
    • Try training your custom model again and see if the error persists. If the error persists, try reducing the number of labeled samples (possibly 5).

    If you still face the issue, I request you to raise a support case through Azure portal.

    I hope this helps! Thank you.

    0 comments No 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.