http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660I had a similar problem in a Sharepoint project. The SecurityException was thrown because of a missing permission. In order to find the permission I did the following: I've surrounded the code that caused the error with a try catch block and caught the security exception. Then I've set a breakpoint in the catch block and had a look at the exception object in the quickwatch window. The security Exception has a private field called m_demanded (among some other interesting fields), which finally told me what the missing permission was. Maybe this helps in your case, too.http://ayende.com/73729/debugging-security-exceptions#comment12http://ayende.com/73729/debugging-security-exceptions#comment12Wed, 31 Aug 2011 07:59:04 GMTDirk, Not giving me details means _I can't fix this_. It is incredibly hard to figure out what is going onhttp://ayende.com/73729/debugging-security-exceptions#comment11http://ayende.com/73729/debugging-security-exceptions#comment11Tue, 30 Aug 2011 00:54:27 GMTIsn't this by design? As it is a security exception it could be the result of someone probing trying to footprint the code. Not giving any details might be annoying but it ticks the securtiy box.http://ayende.com/73729/debugging-security-exceptions#comment10http://ayende.com/73729/debugging-security-exceptions#comment10Tue, 30 Aug 2011 00:47:40 GMTHmm, at least from a debugging scenario, could CodeAccessPermissions.Assert possibly loosen up the restrictions enough to get a stack-trace without compromising the security restriction causing the exception? Really not something I've ever been in this situation. http://ayende.com/73729/debugging-security-exceptions#comment9http://ayende.com/73729/debugging-security-exceptions#comment9Tue, 30 Aug 2011 00:29:14 GMTIt doesn't tell me what caused the error (what line of code in the method)http://ayende.com/73729/debugging-security-exceptions#comment8http://ayende.com/73729/debugging-security-exceptions#comment8Mon, 29 Aug 2011 22:43:36 GMTCan you catch the exception and use that to help you find the bug? SecurityException has several properties which should help you to find out why it was raised. This is turn may point to the code which caused it. http://msdn.microsoft.com/en-us/library/system.security.securityexception_properties.aspxhttp://ayende.com/73729/debugging-security-exceptions#comment7http://ayende.com/73729/debugging-security-exceptions#comment7Mon, 29 Aug 2011 22:35:14 GMTDamien, Try that :-) It wouldn't get into the method / line that is causing it. It would stop when the JIT processed the method, not when executing it.http://ayende.com/73729/debugging-security-exceptions#comment6http://ayende.com/73729/debugging-security-exceptions#comment6Mon, 29 Aug 2011 19:03:23 GMTTobi, With the exception of things that are actually "if this fails, a restart is required"http://ayende.com/73729/debugging-security-exceptions#comment5http://ayende.com/73729/debugging-security-exceptions#comment5Mon, 29 Aug 2011 19:02:41 GMTSteve, Nope, the line number was actually the function header, not any line in the method itselfhttp://ayende.com/73729/debugging-security-exceptions#comment4http://ayende.com/73729/debugging-security-exceptions#comment4Mon, 29 Aug 2011 19:01:56 GMTAttach to web app, throw on exception? [)amienhttp://ayende.com/73729/debugging-security-exceptions#comment3http://ayende.com/73729/debugging-security-exceptions#comment3Mon, 29 Aug 2011 16:01:00 GMTSide note: never ever put anything that could remotely fail in a static constructor. Failing a static constructor causes the entire application to be effectively permanently unavailable until someone recycles the process. Only pure computations are suited for cctors. Use a static threadsafe lazy for anything else (but not the default one because it stores the exception! what an evil design choice).http://ayende.com/73729/debugging-security-exceptions#comment2http://ayende.com/73729/debugging-security-exceptions#comment2Mon, 29 Aug 2011 12:44:31 GMTDoesn't the stack trace give you the detail you need to find the offending statement by line #? The culprit from the original code was Line 166 inside DocumentDatabase.cs After your changes to track it down, the line was 185. Or was the point that Line 166 was merely pointing at the constructor declaration, not the line that triggered the security exception?http://ayende.com/73729/debugging-security-exceptions#comment1http://ayende.com/73729/debugging-security-exceptions#comment1Mon, 29 Aug 2011 12:35:44 GMT