How do i evaluate which is really leading to the next error? The page is equivalent to other pages but for whatever reason only this site is getting this error. Additionally, it only happens about the Web service provider (GoDaddy) that has a trust degree of Medium and that i can't set a breakpoint and then try to catch it.
Server Error in '/' Application.
Description: The applying tried to perform a surgical procedure not permitted through the security policy. To grant this application the needed permission please speak to your system administrator or alter the application's trust level within the configuration file.
Exception Particulars: System.Security.SecurityException: Request the permission of type 'System.Security.Permissions.EnvironmentPermission, mscorlib, Version=2..., Culture=neutral, PublicKeyToken=b77a5c561934e089' unsuccessful.
An unhandled exception was produced throughout the execution from the current web request. Specifics of the foundation and placement from the exception could be recognized while using exception stack trace below.
Stack Trace: [SecurityException: Request the permission of type 'System.Security.Permissions.EnvironmentPermission, mscorlib, Version=2..., Culture=neutral, PublicKeyToken=b77a5c561934e089' unsuccessful.] System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMark& stackMark, Boolean isPermSet) + System.Security.CodeAccessPermission.Demand() +59 System.IO.Path.GetTempPath() +54 hh.a(Int32 A_, Boolean A_1, Boolean A_2) +20 jg.b(c A_, UInt64 A_1) +234 ei.b(c A_, UInt64 A_1) +18 jg.a(c A_, UInt64 A_1, Boolean A_2) +61
Version Information: Microsoft .Internet Framework Version:2..50727.1433 ASP.Internet Version:2..50727.1433
For those who have had this problem or simply understand how I'm able to fix or trace it please add the way to go. Trust degree of Medium is needed through the Web service provider.
Perhaps you have attempted utilizing a local demonstration of IIS and setting the trust level to medium? That will assist you to debug and check out stuff just a little faster.
(And is a great habit to get involved with anyway. You need to test within an atmosphere as near to production as you possibly can. And also the Versus web server certainly includes a couple of important variations that may enable you to get if you do not test in IIS too.)
The phone call stack just before that's obfuscated, so my prediction is it's from the component vendor. Look for an update or treatment for partial trust from their store, or change it.
Setting breakpoints in obfuscated, non-debug devices are difficult. It'll likely lead you nowhere.
Discover why the obfuscated component is attempting to gain access to the temp path.