NXPowerlite for Microsoft Exchange throws a fatal error and stops processing prematurely.
The log in the Neuxpower program data area will show that a ServiceRequestException with error 'Insufficient storage' has been thrown specifically when calling 'Update' while creating new attachments. The error in the log will look like this:
NXExchangeOptimiserService, Fatal, Microsoft.Exchange.WebServices.Data.ServiceRequestException: ServiceRequestException thrown when calling 'Update' on item when creating new attachments. The request failed. The remote server returned an error: (507) Insufficient Storage.
NXPowerlite for Microsoft Exchange uses the Exchange Web Services (EWS) managed api to access Exchange from outside of the Exchange organisation. When EWS requests are sent to the Exchange Server from outside of the organisation, a check of the request size is made against a value in the EWS web.config file. This value is in the 'requestLimits' subsection of the 'requestFiltering' section and is called 'maxAllowedContentLength'.
If NXPowerLite for Microsoft Exchange is sending a request that is larger than 'maxAllowedContentLength', then the ServiceRequestException as described above is thrown. If 'maxAllowedContentLength' is significantly lower than the maximum allowed in the Transport Service of the Exchange Server (e.g the 'maxSendSize' and 'maxReceiveSize' values) then this is very likely to occur.
It is important to note that the original request that is sent by NXPowerLite is always encoded using base64 encoding before sending over http. So this increases the size of the original request by around a third.
Alter the size of the 'requestFiltering.requestLimits.maxAllowedContentLength' value in the EWS web.config file to match the 'maxReceiveSize' in the Transport Service configuration.
IMPORTANT: Please note that we do not have knowledge of your specific Exchange setup and can't know if this solution is best for you. We advise you only to carry out this solution if you are happy to do so.
Although this solution is satisfactory for some users, for others this may not be the case. If this does not solve your problem please get in touch with us.