REST error: The file is too large to be stored within this calendar

Hi Robert, what version are you on? 

We did have a recent hotfix resolving some issues with setting MaxFileSize to 0, but it would likely not apply in your situation because it did not affect Calendar files and was also resolved by setting the maxes to very large numbers.

What permissions does the user making the REST calls have? There is a site-level Bypass Validation permission that would allow the user to ignore these file validation checks.

Hi Steven Heffner , sorry, just getting back to this issue.

Steven Heffner said:

it would likely not apply in your situation because it did not affect Calendar files and was also resolved by setting the maxes to very large numbers

Great.  I set the file max to 99999999 and the per calendar to 999999999.

Steven Heffner said:

What permissions does the user making the REST calls have? There is a site-level Bypass Validation permission

For troubleshooting I am running it as a user in the Administrators Role.

And this is the error, which is different from the one I reported above.

{"":null,"Errors":["The file would cause this calendar to be over its allowed file storage quota."]}

Is there anywhere else I should be looking?

Thanks.

What is your full version number from Administration > About?

Hi Ben Tiedt 

The version is 11.1.7.15705

I can verify that in that version, Calendar does not honor the site permission to bypass validation. The file size and total quota are always checked. That said, the logic appears to be correct and 0 should be honored as unlimited. 

That said, there appears there may be an issue that causes the configuration change to not take effect until the application restarts. Could you try restarting your site and retesting? It's likely validating against the original configuration from the last restart.

I've logged this issue as:

I can verify that in that version, Calendar does not honor the site permission to bypass validation. The file size and total quota are always checked. That said, the logic appears to be correct and 0 should be honored as unlimited. 

That said, there appears there may be an issue that causes the configuration change to not take effect until the application restarts. Could you try restarting your site and retesting? It's likely validating against the original configuration from the last restart.

I've logged this issue as:

Problem solved, many thanks!