Windows 2008, 2008 R2, or 2012
*IIS 7.0, 7.5, 8.0 or 8.5.
- Retention is turned on in GroupWise and messages up to a certain date can't be deleted.
- Errors on retrieving attachments show in the Worker log.
- Can see messages that don't have all the attachments in Retain.
- You may also have difficulty getting larger exports through the web interface (exports larger than 28.6 MB).
- When logging is set to diagnostic for the Worker you can see errors like this:
15:15:15,668 RetainServerCommunication - Attempt to connect, but Server returned HTTP status (404): Not found (this line is typically repeated several times over the course of 5 minutes) 15:15:15,668 RetainServerCommunication - Giving up...too many retries! 15:15:15,668 ArchiveAttachment - Send a nice healthy blob:Archive: ERROR: Fatal Error Result=AddedEMails: 0, emailID=null, parentID=null 15:15:15,691 JobUtilities - HandleArchivingException
This may not be as much of an issue in Retain installations that were created with 3.x and newer. The RetainWorker will now communicate, by default, directly to the RetainServer on port 48080 thereby bypassing IIS. If you'd like to change this for an older installation, change the connection address of the worker. See the manual (look up "Worker Configuration") for your particular installation for more information. You may still have this be an issue on your Exchange server when Retain tries to collect from it if there are message attachments or messages that are larger than whatever ISS is set to allow through. This would be a setting on the Exchange side that would need to be changed. Default is 30000000 bytes.
For getting exports out of Retain you can also choose to bypass IIS and use http://(RetainIP):48080/RetainServer. IIS integration is more of a convenience to point users at Retain so that you don't have to deal with port information in a URL and other advantages that this can provide.
IIS, by default, limits the amount of data that can be imported by Retain. You can remove, or at least mitigate, this limitation by changing 4 settings. This example will be assuming you'd like to archive files up to 931 MB.
1. You'll need to increase the limit on how much data the RetainWorker and RetainServer can push/pull through IIS. You can do that using the following command*:
a. ** %windir%\system32\inetsrv\appcmd set config "Default Web Site/RetainWorker" -section:requestFiltering -requestLimits.maxAllowedContentLength:1000000000
b. %windir%\system32\inetsrv\appcmd set config "Default Web Site/RetainServer" -section:requestFiltering -requestLimits.maxAllowedContentLength:1000000000
c. Current testing indicates that you'll also have to do a blanket statement: %windir%\system32\inetsrv\appcmd set config -section:requestFiltering -requestLimits.maxAllowedContentLength:1000000000
*Note: the number at the end of the command is the size you'd like to have as the max in bites.
**Note: the "Default Web Site/RetainWorker" piece may vary depending on your server setup. See the picture in the next section.
2. If you don't like command line you can also change it through the IIS manager.
a. Bring up the IIS manager and highlight "Default Web Site"
b. Double click on "Configuration Editor" as shown in the figure above.
c. Use the "Section" area drop down box to go to "requestFilterg" as shown in the following figure.
d. Expand the "requestLimits" section. Change the "maxAllowedContentLength" shown in the next figure to the size (in bytes) you would like to be able to pass though.
e. Repeat for both RetainServer and RetainWorker.
3. You may also need to change the timeouts in IIS. To do this:
a. Open the IIS manager.
b. Highlight "Default Web Site".
c. Click on "Limits"
d. Change "Connection time-out (in seconds):" to the desired time.
*Note: IIS is not supported by GWAVA. These are suggested methods for allowing Retain to archive large emails through IIS. For further information visit the MicroSoft support pages: http://www.iis.net/configreference/system.webserver/security/requestfiltering/requestlimits
Some other useful information can also be found on the IIS forums: http://forums.iis.net/t/1066272.aspx