500 Internal Server Error while hitting azure prebuilt-document sync analyse endpoint. Async endpoint works just fine.

Persistent Coder 20

Facing the same issue with general document api as here

Async endpoint works but sync endpoint throws

errorResponseHttpStatus='500' errorCode='UnhandledEndpointException'

Using mcr.microsoft.com/azure-cognitive-services/form-recognizer/document-3.0 along with

mcr.microsoft.com/azure-cognitive-services/form-recognizer/layout-3.0

I have checked the CPU and memory both are under control. Im not sure what additional configurations are required, i just followed the offical tutorial from here :

https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/containers/install-run?view=doc-intel-4.0.0&tabs=general-document

romungi-MSFT 47,206 Reputation points Microsoft Employee

2024-11-12T08:46:14.04+00:00
@Persistent Coder I think the error could be related to a scenario where sync call is not supported for the container endpoints. Which method are you trying to call from your client in this case?

One setting that you could try is to enable Debug level logs as mentioned here while starting the container. Which essentially means updating the YAML file for the containers with logging info under environment and restarting them. This should give more information on the failure.

environment: - EULA=accept - billing={FORM_RECOGNIZER_ENDPOINT_URI} - apiKey={FORM_RECOGNIZER_KEY} - Logging:Console:LogLevel:Default: Debug
Persistent Coder 20 Reputation points

2024-11-13T07:23:26.49+00:00

@romungi-MSFT I have changed log level to Debug, but i don;t see any specific details as such. Sharing the log which got printed.

Caught Endpoint POST API [Analyze] exception SubscriptionId='' RequestId='9c0b808f-6d52-4b1f-8a16-230c88505f32' Timestamp='' buildVersion='1.2.1187.0-20241022.6-786a24c3#' hostId='b98cc4949cfd' serviceName='formrecognizerkvp' namespace='vdi' Namesapce='vdi' operationId='9c0b808f-6d52-4b1f-8a16-230c88505f32' errorResponseHttpStatus='500' errorCode='UnhandledEndpointException'
romungi-MSFT 47,206 Reputation points Microsoft Employee

2024-11-13T07:47:01.2933333+00:00

@Persistent Coder what is the method that you are calling in this case? Since you mentioned another async call worked with the container setup, it would be helpful to check and understand if the method that fails is supported by container endpoints.
Jason 0 Reputation points

2024-11-13T07:56:53.0866667+00:00

@romungi-MSFT The endpoint which works is :

/formrecognizer/documentModels/prebuilt-document:analyze?api-version=2022-08-31

the one which fails is

formrecognizer/documentModels/prebuilt-document:syncAnalyze?api-version=2022-08-31
romungi-MSFT 47,206 Reputation points Microsoft Employee

2024-11-13T08:40:27.74+00:00

@Persistent Coder Can you try the earlier image before 11/07/2024 and check if it works?

For Document image:

For Layout Image:
romungi-MSFT 47,206 Reputation points Microsoft Employee

2024-11-14T12:14:32.4666667+00:00

@Persistent Coder Did you get a chance to review the above and try a different or older image?
romungi-MSFT 47,206 Reputation points Microsoft Employee

2024-11-15T12:54:33.57+00:00

@Persistent Coder Did you get a chance to check if older images worked with the setup?
Jason 0 Reputation points

2024-11-18T15:22:58.4+00:00

@romungi-MSFT Sorry i was away from work. Btw I'm using general document. So i checked this catalog and tried using "2022-08-31.20241022.6-786a24c3" for general document and 2022-08-31.20241022.6-786a24c3 image for layout. I got the same error.
Persistent Coder 20 Reputation points

2024-11-18T17:53:04.9+00:00

@romungi-MSFT I'm just setting up for the first time. Good news is 2022-08-31.20240808.1-d7499e4c2b8a2802977c570508a77efb62dae609 seems to work just fine. I have checked both async and sync versions and they are working.

For 3.1, I can see Layout images here but I couldn't find corresponding general document 3.1 images .

All I see is https://mcr.microsoft.com/en-us/artifact/mar/azure-cognitive-services/form-recognizer/document-3.0/tags
romungi-MSFT 47,206 Reputation points Microsoft Employee

2024-11-19T08:08:14.54+00:00

@Persistent Coder That's great!! For v3.1 document ID check these tags. I think you can use 2023-07-31.20240515.3-0ce53ef9ee2a500693542870b1f4c74dc7ac23bf
Persistent Coder 20 Reputation points

2024-11-19T13:27:25.8633333+00:00

@romungi-MSFT No not Id document . What we are looking for is "general document" which extracts key value pairs. Something like below but version 3.1

https://mcr.microsoft.com/en-us/artifact/mar/azure-cognitive-services/form-recognizer/document-3.0/tags
romungi-MSFT 47,206 Reputation points Microsoft Employee

2024-11-19T14:23:49.4166667+00:00

@Persistent Coder I think 3.1 does not support general document. It is documented in the original document you referred in the initial post.

Read, Layout, ID Document, Receipt, and Invoice models are supported by Document Intelligence v3.1 containers.

Since it also documented that layout container can perform capabilities of general document do you think using layout container for v3.1 works in your case to analyze a general document?
Persistent Coder 20 Reputation points

2024-11-19T17:35:24.5666667+00:00

@romungi-MSFT I have tested layout 3.1 in Document Intelligence Studio, it does not return key-value pairs. See the screenshot below. Only layout 4.0 has that option to return key-value pairs

But 4.0 is not yet available for containers. So i have no option but to pick 3.0?

Also, If i understand correctly, the screenshot you shared is trying to say that general document requires layout model as supporting model? Right now to make 3.0 general document model work, I am also spinning up layout model along with it as per the documentation.
Persistent Coder 20 Reputation points

2024-11-19T19:35:12.78+00:00

I have checked Layout 3.1 in the Document Intelligence Studio, and it does not return key-value pairs. However, the preview version, Layout 4.0, includes an option to return key-value pairs. Unfortunately, Layout 4.0 is not yet available for containers, which leaves me stuck with Layout 3.0.

If I understand correctly, the screenshot you shared indicates that the General Document Model requires the Layout Document Model as a supporting container. It seems like the General Document Model processes the output generated by the Layout Model. Is that correct? This aligns with the initial tutorial, which sets up both the General Document Model and the Layout Model together in the YAML file.
romungi-MSFT 47,206 Reputation points Microsoft Employee

2024-11-20T05:43:36.2766667+00:00

Persistent Coder Yes, 4.0 version is not available for containers yet.

Layout model is used by almost all the other containers in the setup and in this case also it is a dependency. It looks like for your scenario 3.0 would only work since v3.1 does not provide a general document container.
Persistent Coder 20 Reputation points

2024-11-20T08:41:57.7533333+00:00

@romungi-MSFT Thanks for the clarification. Do you know potential date when 4.0 will be available for containers?
romungi-MSFT 47,206 Reputation points Microsoft Employee

2024-11-20T08:58:48.7566667+00:00

@Persistent Coder v4.0 cloud version is still in preview. GA version is yet to be released. Once GA version is released, container support will be added in subsequent months. AFAIK no timeline has been published for v4.0 GA release yet.
romungi-MSFT 47,206 Reputation points Microsoft Employee

2024-11-21T06:16:07.7+00:00

@Persistent Coder I have moved one of the comment from this conversation to answer, where you are able to confirm the older image worked for sync endpoint. I will update this thread later whenever v4.0 GA announcement is made. Thanks for your support.

Accepted answer

romungi-MSFT 47,206 Reputation points Microsoft Employee

2024-11-18T17:25:51.06+00:00

Thanks @Persistent Coder

I am curious to check if any of the containers you used earlier with this setup worked? If this is the first time I understand you must be pulling latest and it failed with the latest and the one before that.

I noticed a similar error was reported with v3.1 and it is advised to use earlier versions for v3.1 like the artifact published on 02/06/2024

2023-07-31.20240203.1-b0c0f5500a46efc1634694ae85c20587fa5d7ab0

I was hoping the same scenario would work from v3.0, the version you are using. Do you mind checking if 2022-08-31.20240808.1-d7499e4c2b8a2802977c570508a77efb62dae609 might work for v3.0 published on 08/09/2024?

You can also try v3.1 which is the newer version of the API with the version I mentioned above.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

500 Internal Server Error while hitting azure prebuilt-document sync analyse endpoint. Async endpoint works just fine.

0 additional answers

Your answer