Page not found error usually are permission related errors if the resource called is already installed/created on a web server. Make sure that all the resources that are used by CR to run the reports have the appropriate permissions for the user that starts the web server.. Joe
----- Original Message ---- From: William Rentfrow <[EMAIL PROTECTED]> To: [email protected] Sent: Tuesday, August 5, 2008 11:54:30 AM Subject: BOXI users with large data quantities ** Is anyone else using BOXI or CE to print reports on the web in an environment with large data quantities? We have it set up and working - users can print an Incident just fine once they get the Active X control installed. However - this customer does about 3000 Incidents/day. Consequently the data adds up fast. If we run a report like "All open incidents" or something it just times out and goes to a 404/Page not found screen. We've checked all the timeouts we could. I set my workstation browser registry "keepalive" session setting to 600,000 MS (10 min) and everything on the BOXI server is set to 20 minutes. The IIS settings are the same as well for "keepalive". Anyone have any ideas? William Rentfrow, Principal Consultant [EMAIL PROTECTED] C 701-306-6157 O 952-432-0227In the WUT the report takes 3-4 minutes to run - so I believe adequate time is allowed. However, the timeout screen happens after 5 minutes (roughly) instead of the 10+ I'd expect. Clearly something is just giving up - but I have no idea what. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
