With Duet Reporting Management scenario, you can have reports with up-to-date SAP backend data sent to the Outlook Inbox. If these reports contain multiple megabytes of data, delivery to the Duet client might fail. So let’s follow the path of a report through the Duet landscape and see the “gates” where the report might get stuck. h5. Gate 1: SAP backend The first gate to be passed in the SAP backend itself. In the master system of Duet Reporting Management, go to *transaction SIMGH*. In the Edit IMG Structure screen, place your cursor in the IMG Structure field and press F4 to search. In the Title field, enter Duet, and click the Execute icon. Double click *Duet Implementation Guide*, then click the Display IMG Structure icon, and select Duet. Expand *Application Flow Settings*, and click the activity icon for Define *Application Behavior Settings*. Under Solutions select Duet and double click on Applications, then select Reporting Management and double click on Application Behavior. Increase parameter *REPORT_MAX_SIZE* of type Number above the default value of 4096 kilobytes. If the report size exceeds the value specified here, the report is not generated.*/duet*. Go to* System Environment ->General Settings and Tools -> Duet Items*. Increase the maximum size of email messages that Duet can transmit above the default value of 4.000.000 bytes. h5. Gate 3: JMS Provider Service This step is part of the regular Duet installation, see Installation Guide section “Setting the Size for Messages in the Application Server Java”. In case of stuck Duet items double check the JMS (Java Message Service) size limit on the Duet Server. Start the *Visual Administrator* Console by running \j2ee\admin\go.bat file on the Duet server.0.1. In the logon window, type the administrator user and password and then click *Connect*. 0.1. From the *Cluster tab*, click *Server | Services *and then select *JMS Provider*. 0.1. Select the *Properties *tab and change the value for *sizeLimitInMasterQueue *to 4194304 bytes (equals 4 MB).