By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,903 Members | 1,410 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,903 IT Pros & Developers. It's quick & easy.

FYI: System.Security.SecurityException: Failure decoding embedded permission set object.

P: n/a
Hi everyone,

Today we hit a problem when we rolled a new web-site are were
presented with a error on our page that looked like:

Security Exception
Description: The application attempted to perform an operation not
allowed by the security policy. To grant this application the required
permission please contact your system administrator or change the
application's trust level in the configuration file.

Exception Details: System.Security.SecurityException: Failure decoding
embedded permission set object.

Source Error:

An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of
the exception can be identified using the exception stack trace below.

Stack Trace:
[SecurityException: Failure decoding embedded permission set object.]
System.Reflection.Assembly.nLoad(AssemblyName fileName, String
codeBase, Boolean isStringized, Evidence assemblySecurity, Boolean
throwOnFileNotFound, Assembly locationHint, StackCrawlMark& stackMark)
System.Reflection.Assembly.InternalLoad(AssemblyNa me assemblyRef,
Boolean stringized, Evidence assemblySecurity, StackCrawlMark&
stackMark) +300
System.Reflection.Assembly.InternalLoad(String assemblyString,
Evidence assemblySecurity, StackCrawlMark& stackMark) +68
System.Reflection.Assembly.Load(String assemblyString) +19
System.Web.UI.CompilationConfiguration.LoadAssembl ies(Hashtable
original) +200
Well we looked on the Web and didn't really find an answer to what
caused this problem. Well we worked it out :) This post is really just
here to help generations that follow.

The problem is that we didn't have the .NET 1.1 framework deployed on
a web-server.

It was pretty obvious afterwards actually but we developed the new
Web-site with VS.NET 2003, where the old version was developed on

The error message wasn't as helpful as we would have liked though.
I hope this little addendum helps.

Mark Rodrigues
Jul 21 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.

Browse more .NET Framework Questions on Bytes