jesus4u Posted October 6, 2003 Posted October 6, 2003 I have a strange problem. I get an "Access Denied Error" when I try to instantiate a Word.Application in my custom vb.net class from an ASPX page. Dim wrdApp As New Word.Application How can I fix? Here is the error: Access is denied. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.UnauthorizedAccessException: Access is denied. ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user. To grant ASP.NET write access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access. Source Error: Quote Alex Polajenko
*Gurus* Derek Stone Posted October 6, 2003 *Gurus* Posted October 6, 2003 ASP.NET applications are not allowed to interop with unmanaged code by default. Quote Posting Guidelines
jesus4u Posted October 6, 2003 Author Posted October 6, 2003 What I don't understand is that the code that does this is actually a Class apart from the ASP.NET project. Quote Alex Polajenko
jesus4u Posted October 6, 2003 Author Posted October 6, 2003 Maybe I can isolate the call through an Async call on another thread? Quote Alex Polajenko
*Gurus* Derek Stone Posted October 6, 2003 *Gurus* Posted October 6, 2003 That's not how security in .NET works, thank God. You can't just get around it as your attempting to do. You need to change the assembly's policy or you'll keep getting the same security exception. Quote Posting Guidelines
jesus4u Posted October 7, 2003 Author Posted October 7, 2003 You need to change the assembly's policy or you'll keep getting the same security exception. Would you mind explaining how to do this? I am not clear... :confused: Thanks Quote Alex Polajenko
*Gurus* Derek Stone Posted October 8, 2003 *Gurus* Posted October 8, 2003 Administrative Tools > Microsoft .NET Framework Configuration There are several ways to accomplish what you're aiming for however, and you need to take the time to read up on which is the most appropriate option for your application. [mshelp]ms-help://MS.NETFrameworkSDKv1.1/cpguidenf/html/cpconsecuritypolicyconfiguration.htm[/mshelp] Quote Posting Guidelines
WebJumper Posted October 8, 2003 Posted October 8, 2003 or this way: web.config: <system.web> <identity impersonate="true" userName="Administrator" password="admin"/> </system.web> Quote
*Gurus* Derek Stone Posted October 8, 2003 *Gurus* Posted October 8, 2003 I'm sorry, but impersonating an administrator is the worst thing one can do in terms of security. I strongly suggest against doing so. Quote Posting Guidelines
jesus4u Posted October 8, 2003 Author Posted October 8, 2003 I'm sorry, but impersonating an administrator is the worst thing one can do in terms of security. I strongly suggest against doing so. yep I agree Quote Alex Polajenko
WebJumper Posted October 8, 2003 Posted October 8, 2003 I'm sorry, but impersonating an administrator is the worst thing one can do in terms of security. I strongly suggest against doing so Worst: No!!! No solution is the worst case! While no other solution works it's tempoary the best way and you can still develope on your project! Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.