Unable to deliver image to Box.com via API due to [InternalServerError]

Hi Team,

We currently have a mutual customer who is having some files fail when being delivered to Box.com via API. The issue seems to be intermittent and only affecting some files.

We are getting a [InternalServerError] response when trying to send the files, however no specifics as to what the issue in the response callback.

Example file below that was returning the error message.

General Details:

Box Package: https://www.nuget.org/packages/Box.V2.Core/3.26.0
Function call: Box.V2.Managers.BoxFilesManager.UploadAsync
Exception Message: The API returned an error [InternalServerError]
File: 13676-096-waypoints-jacket-Model-4.psd
File size: 225 MB (236286163 bytes)

Time sent (tried 4 times)
[{
"EndTime": "2022-08-26T21:47:13.7068147Z",
"StartTime": "2022-08-26T21:46:02.8607047Z"
}, {
"EndTime": "2022-08-26T21:48:38.0533689Z",
"StartTime": "2022-08-26T21:47:24.2993767Z"
}, {
"EndTime": "2022-08-26T21:50:00.6496881Z",
"StartTime": "2022-08-26T21:48:48.5546676Z"
}, {
"EndTime": "2022-08-26T22:07:24.4064707Z",
"StartTime": "2022-08-26T22:06:11.3798125Z"
}
]

Pseudocode in C#

fileStream: The binary stream of 13676-096-waypoints-jacket-Model-4.psd

async Task Pseudocode_DeliveryAsset_Fail(Stream fileStream){
try
{
var fileRequest = new BoxFileRequest
{
Name = "13676-096-waypoints-jacket-Model-4.psd",
Parent = new BoxRequestEntity() { Id = 170666980060 } // plain full folder "Simms S23/2022-08-26/Model/13676-096/"
};

var result = await boxClient.FilesManager.UploadAsync(fileRequest, fileStream);

} catch(Exception ex){
// ex.Message = The API returned an error [InternalServerError]
}
}

What would be the best way to troubleshoot this issue? As the error message does not give any additional context around the issue.

Alex Novotny

22 septembre 2022 16:46

Hi,

Are you still having this issue? Apologies for the delay. We cannot answer forum questions rapidly.

Alex, Box Developer Advocate

Ian Mitchell

22 septembre 2022 17:36

HI Alex Novotny

Yes the issue is still taking place, but the error call back does not specifically say what the issue is so it is hard to Debug.

Any insights would be super.

Commentaires