Azure Form Recognizer returns status 200 "InternalServerError"

Javier 0 Reputation points
2023-01-17T09:11:58.8266667+00:00

Hello

We have recently started having inconsistencies with Azure's Form Recognizer service.

From yesterday, our integration with Azure's Form Recognizer is sometimes returning the following response:

Exception: {'status_code': 200, 'error_message': '(InternalServerError) An unexpected error occurred.\nCode: InternalServerError\nMessage: An unexpected error occurred.\nException Details:\t(InternalServerError) An unexpected error occurred.\n\tCode: InternalServerError\n\tMessage: An unexpected error occurred.'}

As it's returned as a status 200, Azure doesn't consider it as a failed execution, but we are not receiving any response appart from the internal server error.

It looks like it's somehow happening randomly, only sometimes.

  • We have checked the input images (we usually use jpg or png images) and it's happening both with small images (50KB) and big images (8MB), even if it looks more frequent with big ones.
  • The images are OK.
  • When we try multiple requests with the same image that has received the 200 internalservererror message, the same image is failing sometimes and working correctly other times.

Does anyone have any idea of what could be happening?

Thank you in advance.

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
36,308 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Jonathan Sailer 76 Reputation points
    2023-01-31T18:46:52.19+00:00

    Hi Javier,

    It sounds as though there's an issue on the Cloud Server that's running the Azure Form Recognizer service, or there are intermittent communication issues between your client and the server. I would agree with Ramr-msft's answer of getting in touch with Azure support if you have a support plan, but if you don't or before you do contact them, I would try just refreshing your Azure instance and making sure that the client doesn't have another instance or application running that could be trying to access the same resource.

    To do this, if it's possible, I would restart the client device, and refresh the log in by signing out and then back in to Azure.

    0 comments No comments