Hello! I'm testing the Aspose.Grid.Web control to view Excel files in my ASP.NET pages. In my machine i don't have any kind of problem. All works fine. When I move my web site, in a test server, I can't use the control anymore. I try to describe my situation:
- The server is a Windows 2003 SP1 and run on a virtual machine. My application runs on a web site that have the application pool identity set to NT Service. - When I access to the page and try to view an Excel file I obtain the classic window popup for the credential (username and password). - I think that the popup prompt is caused by the faulting of the w3wp process. I see many errors in the eventviewer.
I think that the error is caused by the wrong file access right settings. Please show me the messages in the event log here. And you may check the security settings of the application folder. Make sure that the files can be accessed by the default asp.net user "ASPNET".
Hi, I'm not at work in this moment and I can't post the exact event log message, but it's something like: "faulting w3wp.exe process .......".
First of all I checked for the permissions. I set the everyone group permission for the files and folders. In my server I don't use the ASPNET user. In the server I have many Application Pools and the one that I'm using runs under the NT Service Account.
In the application web.config I set the identity tag, but with the Everyone permission I think that every user must read the file. Infact if I try to access the excel files directly from browser I can open them.Moreover I don't obtain a 401 error, but something else. When I return to work I'll post the exact error. I think that for some reasons, the ASP.NET worker process (w3wp.exe) fail (and this is confirmed by the event log) and so the username/password popup is shown.
Is there a "debug" execution mode for the Aspose.Grid.Web component? What kind of test I can do to check the problem?
The code it's a little complex. The stream is returned from a file that is saved into SharePoint, but it's the same with a file that is save locally. And it's not the particular excel file the problem. I have the same problem, with every excel file! I'm trying two way to open Excel files:
The first one use streams and cause the stackoverflow problem. The second one use the path of the file and cause the other problem. If i test in my machine i don't have problems. Both of them works and they works with the same files that cause problems in my server, so i don't think it's a problem of excel files.