Qlik Community

Qlik NPrinting Discussions

Discussion Board for collaboration on Qlik NPrinting.

riccardozenere
Contributor III

NPrinting 17.2.2 - Error: message file too big

Hi everyone,

today I'm coming for your help regarding this issue:

Failed to send e-mail for bucket (...). Exceeded storage allocation. The server response was: 5.3.4 Error: message file too big


The installed version of NPrinting is 17.2.2, and we are given this error when trying to send a specific mail report.

We tried to publish the file on NewsStand and it is only 8MB, so It shouldn't be an issue to send it through email. Am I wrong?

From the SMTP side I was told that the limit is far higher than this (and in the mail there is only this report with a few lines of mail).

On the (NPrinting) server side seems all ok.

Follows the complete error logged:

Qlik.NPrinting.Repo 17.2.2.0 Qlik.NPrinting.Repo.Service.ReportPublishingService 20170719T124315.920+02:00 ERROR (NPrinting server name) Nprinting Task Identity 0 0 0 0 0 0 0 0 Failed to send e-mail for bucket (...). Exceeded storage allocation. The server response was: 5.3.4 Error: message file too big ↵↓=============↵↓      _printStack↵↓      Error↵↓      MoveNext↵↓      RunInternal↵↓      Run↵↓      Run↵↓      RunOrScheduleAction↵↓      FinishContinuations↵↓      Finish↵↓      TrySetException↵↓      TrySetException↵↓      HandleCompletion↵↓      OnSendCompleted↵↓      RunInternal↵↓      Run↵↓      System.Threading.IThreadPoolWorkItem.ExecuteWorkItem↵↓      Dispatch↵↓↵↓=============↵↓

Do you have any hints on what could be the issue and how to solve it?

Many thanks,

Riccardo

1 Reply
Lech_Miszkiewicz
Honored Contributor III

Re: NPrinting 17.2.2 - Error: message file too big

Hi,

would you be able to upgrade to June 2017? 17.2 was guite "buggy"!

Also double check the exact limit for email size on SMTP side. Note that your attachemnt is not the only thing which contributes to size of an email!

cheers

Lech

cheers Lech
When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution.
Please LIKE threads if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem.
Community Browser