Cannot upload/download Document Image documents larger than 200KB.
Problem: Cannot export/upload/download files over a certain size from CAMS Enterprise or the Portals. Document Image files that are larger than 200KB only display a red X.
Possible Solution: Windows 2003 (and later) server customers may have trouble uploading large documents. This applies to any file that is uploaded/downloaded and is not only related to document images.
Windows 2003 Server
First, stop IIS service. Using a plain text editor such as Notepad, open your metabase.xml which is located in C:\Windows\System32\Inetsrv. Locate the line "AspMaxRequestEntityAllowed" and change it to "67108864". This is 64 MB (megabytes) but you can enter a different value to meet your needs. Save changes and then start IIS.
Regardless of how large you make AspMaxRequestEntityAllowed in the IIS metabase.xml file, the maximum upload size that is allowed is 65536 KB (64 megabytes). The download size of a file is also limited in the meta base. By default, the metabase.xml file has this entry:
AspBufferingLimit = "4194304"
This limits download size to 4,194,304 bytes (4 MB), and larger files will be silently truncated with no message from IIS. You can change that to a larger value (such as 67108864 for 64 megabytes) to allow your Windows server to send large downloads.
The AspMaxRequestEntityAllowed and AspBufferingLimit MUST have the same number entered on the CAMS IIS server and the Portal IIS server (if using a separate portal server). The metabase.xml AspMaxRequestEntityAllowed and AspBufferingLimit entries are in bytes.
You may need to stop the IIS service before the changes will take effect.
If you are using web services you will also need to change the httpRuntime maxRequestLength web service configuration setting in the web.config located in the CAMSServices\PortalService sub-folder inside the folder where CAMS Enterprise is installed on the CAMS Enterprise IIS box.
This setting is in KB (kilobytes) and the default is 4096. For example, this is a line from the web.config showing it set to 64 MB:
<httpRuntime maxRequestLength="65536" />
This setting MUST be the same size as the settings in the metabase.xml and MUST be in kilobytes.
Windows 2008 Server
If you are using Windows 2008 server (IIS 7.0), you will need to change the Maximum Requesting Entity Body Limit [maxRequestEntityAllowed] and the Response Buffering Limit [bufferingLimit]in the Limits Properties in the ASP settings in the IIS Manager for the IIS box running the portals.
Note: IIS 7 displays Friendly Names by default on the ASP properties page (displayed in bold above). Change the “Display” drop-down in the ASP section to “Configuration Names” or “Both Names” in order to see the configuration label names (in square brackets above).
Note: The Request Filtering feature is not present by default in the IIS Manager on Windows Server 2008. Install “Administration Pack for IIS 7.0” available from the Microsoft downloads site.
You may need to stop the IIS service before the changes will take effect.
Web Services
If you are using web services you will also need to change the httpRuntime maxRequestLength web service configuration setting in the web.config located in the CAMSServices\PortalService sub-folder inside the folder where CAMS Enterprise is installed on the CAMS Enterprise IIS box.
This setting is in KB (kilobytes) and the default is 4096. For example, this is a line from the web.config showing it set to 64 MB:
<httpRuntime maxRequestLength="65536" />
This setting MUST be the same size as the settings in the IIS Manager and MUST be in kilobytes.