Computer Vision Form Recognizer Signature Field

Question

Trying to add signature detection to our Microsoft Computer Vision Forms, and whenever I try to query a model that has a signature field I'm getting an InternalServerError.

HTTP Methods:

var postDocuri = $"{endpoint}/documentModels/{modelName}:analyze?api-version=2022-08-31&";
var getStatusUri = $"{endpoint}/documentModels/{modelName}/analyzeResults/{requestId}?api-version=2022-08-31";
Response:

{
"status" :"failed",
"createdDateTime" :"2022-09-03T00:40:06Z",
"lastUpdatedDateTime":"2022-09-03T00:40:06Z",
"error":{
"code" :"InternalServerError",
"message":"An unexpected error occurred.",
"details":[ {
"code" :"InternalServerError",
"message":"An unexpected error occurred."
} ]
}
}
Everything is working great and processing my models just fine so long as I don't include any signature fields on any of my forms, but the minute I add a signature field that model stops working.

I see an error guide at the website below - but this is assuming I'm getting any sort of an error code in the response. The GET to return the process results returns an HTTP status code success 200 - OK, but the Json body payload doesn't really reflect that truth.

https://learn.microsoft.com/en-us/azure/applied-ai-services/form-recognizer/v3-error-guide

Does anybody have any advice on how I can begin to troubleshoot this error? Another log somewhere? Somewhere in the Azure blob storage that holds the training data?

Both the HTTP API and also the online Form Recognizer Studio test page fail with the same error when processing pages - InternalServerError - An Unexpected Error Has Occurred.

Answer 1

Jeff I have the same issue for REST API, I finally give it up. Forum can not debug internal error, there is no clue

I make it in Studio - https://learn.microsoft.com/en-us/azure/applied-ai-services/form-recognizer/concept-custom?view=form-recog-3.0.0#try-signature-detection

Try the codeless UI

Answer 2

I am getting the same issue. The model was working on the 2022-06-30-preview version. I updated to 2022-08-31 and I started getting this error, but only on this model. The error persists if I fall back to the previous version and create a new model as well. It is very strange.

Answer 3

I am having the same issue, was there any resolution to this?