This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 70%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGR%3C/text%3E%3C/svg%3E)
When using the FormsRecogniser in .net the sdk returns the below error when attempting to process documents.
An unexpected error occurred.\r\nStatus: 200 (OK)\r\nErrorCode: InternalServerError\r\n\r\nAdditional Information:\r\nAdditionInformation: InternalServerError: An unexpected error occurred.\r\n\r\nDetails:\r\nInterna
We are sending one request per second on the standard tier.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 32%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBG%3C/text%3E%3C/svg%3E)
I had this problem earlier today as well and opened a ticket with support. The endpoint worked fine yesterday, but then today it failed with the SDK and their web app. It did start working a few minutes later.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 4%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVM%3C/text%3E%3C/svg%3E)
Hello @Gill, Ricky , Thanks for using Microsoft Q&A Platform.
Could you please check again? Are you still experiencing this issue? May I know the Azure resource region you are using?
Hi,
The region in use is Uk South. The strange thing is it process one in every 10 documents. So credentials and connectivity is fine. Just the errors outlined in the original comment occur.