cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
AMoorePin
New Member

Stored Procedure Flow failing with large string insert, Data Gateway reports 404

Hello,

 

In PowerApps I have an attachment control where users can upload PDFs, these are converted to BASE64 and inserted into a database  (Azure SQL Managed Instance) using Patch. Everything seems to work fine until the PDF size gets roughly above 3MB in size. When this happens PowerApps delivers a non-sensical error saying it cannot find the record.  

 

I decided to try the insert using a stored procedure using Flow and manage to hit the same limit but with more visibily over what's going on. PowerApps is indeed passing the full string via the input but it's the Data Gateway reporting an error:

 

 

 

{
  "status": 404,
  "message": "The gateway is either offline or could not be reached.\r\n     inner exception: Gateway on endpoint '<ii>sb://wabi-canada-central-relay33.servicebus.windows.net/c57d88f9-8455-4b84-a61e-f583e470a334/</ii>' is unreachable.\r\n         inner exception: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'. TrackingId:0a91ae1a-4888-479e-ae59-86a8c3ec94c7, SystemTracker:wabi-canada-central-relay33.servicebus.windows.net:c57d88f9-8455-4b84-a61e-f583e470a334, Timestamp:2022-08-10T19:35:00\r\n             inner exception: The write operation failed, see inner exception.\r\n                 inner exception: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'. TrackingId:0a91ae1a-4888-479e-ae59-86a8c3ec94c7, SystemTracker:wabi-canada-central-relay33.servicebus.windows.net:c57d88f9-8455-4b84-a61e-f583e470a334, Timestamp:2022-08-10T19:35:00\r\n                     inner exception: An existing connection was forcibly closed by the remote host\r\nclientRequestId: 81946f28-5615-4470-ac8b-b61334a0f779",
  "error": {
    "message": "The gateway is either offline or could not be reached.\r\n     inner exception: Gateway on endpoint '<ii>sb://wabi-canada-central-relay33.servicebus.windows.net/c57d88f9-8455-4b84-a61e-f583e470a334/</ii>' is unreachable.\r\n         inner exception: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'. TrackingId:0a91ae1a-4888-479e-ae59-86a8c3ec94c7, SystemTracker:wabi-canada-central-relay33.servicebus.windows.net:c57d88f9-8455-4b84-a61e-f583e470a334, Timestamp:2022-08-10T19:35:00\r\n             inner exception: The write operation failed, see inner exception.\r\n                 inner exception: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'. TrackingId:0a91ae1a-4888-479e-ae59-86a8c3ec94c7, SystemTracker:wabi-canada-central-relay33.servicebus.windows.net:c57d88f9-8455-4b84-a61e-f583e470a334, Timestamp:2022-08-10T19:35:00\r\n                     inner exception: An existing connection was forcibly closed by the remote host"
  },
  "source": "sql-ce.azconn-ce.p.azurewebsites.net"
}

 

 

 

I have attempted splitting the string in 2 and sending in the same Flow but the error remains, is there a body size limit somewhere I am not aware of? I've not been able to find anything on this. I have no issues inserting the data manually.

 

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
AMoorePin
New Member

The size doesn't quite fit but this seems to be the issue:

https://docs.microsoft.com/en-us/connectors/sql/#general-known-issues-and-limitations

 

  • The response size limit is 8 MB through on-premises SQL Server.
  • The request size limit is 2 MB through on-premises SQL Server.

 

 

View solution in original post

1 REPLY 1
AMoorePin
New Member

The size doesn't quite fit but this seems to be the issue:

https://docs.microsoft.com/en-us/connectors/sql/#general-known-issues-and-limitations

 

  • The response size limit is 8 MB through on-premises SQL Server.
  • The request size limit is 2 MB through on-premises SQL Server.

 

 

Helpful resources

Announcements
Register for a Free Workshop.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

September Events 2022

Check out all of these events

Attend in person or online, there are incredible conferences and events happening all throughout the month of September.

Users online (2,349)