Downloading Excel File

Last post 06-08-2009 4:58 AM by XIII. 1 replies.

Sort Posts:

  • Downloading Excel File

    06-08-2009, 4:05 AM
    • Member
      2 point Member
    • carlsky33
    • Member since 07-30-2007, 12:50 PM
    • Posts 6

    i am having a problem in opening excel file (downloading) in my program after i have published it in the IIS. But it is working when i run in my pc (LocalHost). And it gives me this error:

     

    Server Error in '/ABCSYS' Application.

    Runtime Error

    Description: 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.

    Details: 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".

    <!-- Web.Config Configuration File -->
    
    <configuration>
        <system.web>
            <customErrors mode="Off"/>
        </system.web>
    </configuration>

    Notes: 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.

    <!-- Web.Config Configuration File -->
    
    <configuration>
        <system.web>
            <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
        </system.web>
    </configuration>

     

     

     

     

  • Re: Downloading Excel File

    06-08-2009, 4:58 AM
    Answer
    • All-Star
      123,530 point All-Star
    • XIII
    • Member since 07-01-2002, 3:59 AM
    • Essen, Belgium
    • Posts 13,660
    • ASPInsiders
      Moderator
      TrustedFriends-MVPs

    Hi,

    apparently something goes wrong but at the moment you don't get to see the real exception. Just do as this message tells you and change your web.config file to have this in it at the correct place:

    <customErrors mode="Off"/>

    Mind that this is case sensitive so it should be written exactly like this.

    Then upload the web.config file again and request your page/file again to get a much more detailed explanation of what goes wrong.

    Grz, Kris.

Page 1 of 1 (2 items)