When downloading the results of an export process that uses an ad-hoc query, a user may notice that all of the records are not exported and the file eventually ends with a run time error such as the one below:
<b> Description: </b>An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could however be viewed by browsers running on the local server machine. <br><br>
<b>Details:</b> To enable the details of this specific error message to be viewable on remote machines please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".<br><br>
<b>Notes:</b> The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.<br><br>
<location path="Download/CustomFileDownload.ashx"> <!-- The download page will timeout if a report takes longer to generate than the executionTimeout. --> <system.web> <!-- The execution timeout is in seconds. By default it is 110. --> <httpRuntime executionTimeout="7200" /> </system.web> </location>
Steps to Duplicate
1. Log-in to CRM. 2. Go to Administration, Export, and go to one of your export processes. 3. Click Download output to CSV or XLSX. Open the file and notice all of the records were not exported successfully. Scroll down and you will see that the file eventually ends in a run-time error.