Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PutFile not being called for files above 1MB #427

Open
luis-figueiredo opened this issue Nov 24, 2020 · 1 comment
Open

PutFile not being called for files above 1MB #427

luis-figueiredo opened this issue Nov 24, 2020 · 1 comment

Comments

@luis-figueiredo
Copy link

luis-figueiredo commented Nov 24, 2020

I am struggling with getting the putFile endpoint to work for files with more than 1MB.

When I edit a regular wopi document, everything works fine and I get the request on the /wopi/files/[fileID]/contents endpoint.
If, however, the file has anymore than 1MB, I never get the request. I've been digging around the documentation and can't find any mention of this anywhere. If I check the network tab in my browser, I can find a request with an error:

image

in the response for this request, I get:
{ "ErrorId":"5243067","ErrorName":"WordSave_FileTooLarge","Pillars":[{"PillarName":4}],"Impact":1,"CauseIsInternalToWac":false,"IncludedInOverallFailureRateForAlerting":true,"IsIntentional":false,"IsSessionEndingError":true,"Notes":"","OwnershipInfo":null,"Vetos":["ICE"],"IsV2Error":true}

The error message changes abit if it's an excel or powerpoint file but the problem is present for all files.

the only reference to file sizes being too big I can see on the documentation is maximum file size documentation, but the files I am using are well within these parameters (I'm testing with a 2MB word file, for example).

Any help would be appreciated, and if this is the wrong place to ask this, could you tell me where to find support for this?

@RobRol
Copy link
Contributor

RobRol commented Nov 25, 2020

Howdy, I'm sorry that you're running into trouble. If you're able to reproduce the issue, and can share the Session ID, then the investigation will be a lot smoother.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants