|
Rank: Newbie Groups: Member
Joined: 1/11/2008 Posts: 5
|
We installed MS patches and are now getting this. Any suggestions????
Server Error in '/' Application.
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: Your application is not running with full trust. Please call AspxLab.WebControls.Runtime.Initialize to manually initialize AspxLab Controls runtime environment.
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: Your application is not running with full trust. Please call AspxLab.WebControls.Runtime.Initialize to manually initialize AspxLab Controls runtime environment.] a..ctor() +377 ay..cctor() +111
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,194
|
|
|
Rank: Newbie Groups: Member
Joined: 1/11/2008 Posts: 5
|
This did not help the problem. We already had these lines in the web.config before the problem.
I uninstalled ALL of the patches, repaired the IIS and am still broken. Any ideas? Any support people I can call??
Thanks.
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,194
|
Hi Dan,
Please check the version of your DLL. Also can you post your web.config? This is a rather old issue and nobody else was having problem after applied the changes in web.config.
Thanks
|
|
Rank: Newbie Groups: Member
Joined: 1/11/2008 Posts: 5
|
dll=2.7.3.0
<?xml version="1.0"?> <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"> <appSettings> </appSettings> <system.web> <trust level="Full" originUrl="" />
<httpRuntime executionTimeout="1200" maxRequestLength="102400" useFullyQualifiedRedirectUrl="false" minFreeThreads="8" minLocalRequestFreeThreads="4" appRequestQueueLimit="100"/> <compilation debug="false" strict="false" explicit="true"> <assemblies> <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> <add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> <add assembly="System.Configuration.Install, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/></assemblies></compilation> <pages> <namespaces> <clear/> <add namespace="System"/> <add namespace="System.Collections"/> <add namespace="System.Collections.Specialized"/> <add namespace="System.Configuration"/> <add namespace="System.Text"/> <add namespace="System.Text.RegularExpressions"/> <add namespace="System.Web"/> <add namespace="System.Web.Caching"/> <add namespace="System.Web.SessionState"/> <add namespace="System.Web.Security"/> <add namespace="System.Web.Profile"/> <add namespace="System.Web.UI"/> <add namespace="System.Web.UI.WebControls"/> <add namespace="System.Web.UI.WebControls.WebParts"/> <add namespace="System.Web.UI.HtmlControls"/> </namespaces> </pages> <!-- The <authentication> section enables configuration of the security authentication mode used by ASP.NET to identify an incoming user. Attribute Description name This is the name of the HTTP cookie from which we will store our authentication ticket and information, respectively. loginURL This is the URL from which your unauthenticated client will be redirected. In most scenarios, this would be your login page, where the client is required to provide their credentials for authentication. protection This is used to set the method from which to protect your cookie data. The following valid values can be supplied: All: Specifies to use both data validation and encryption to protect the cookie. Triple DES is used for encryption, if it is available and if the key is long enough (48 bytes). The All value is the default (and suggested) value. None: Used for sites that are only using cookies for personalization and have weaker requirements for security. Both encryption and validation can be disabled. This is the most efficient performance wise, but must be used with caution. Encryption: Specifies that the cookie is encrypted using Triple DES or DES, but data validation is not done on the cookie. It's important to note that this type of cookie is subject to chosen plaintext attacks. Validation: Specifies to avoid encrypting the contents of the cookie, but validate that the cookie data has not been altered in transit. To create the cookie, the validation key is concatenated in a buffer with the cookie data and a MAC is computed/appended to the outgoing cookie. timeout This is the amount of time (in integer minutes) that the cookie has until it expires. The default value for this attribute is 30 (thus expiring the cookie in 30 minutes). The value specified is a sliding value, meaning that the cookie will expire n minutes from the time the last request was received. path This is the path to use for the issued cookie. The default value is set to "/" to avoid issues with mismatched case in paths. This is because browsers are case-sensitive when returning cookies.
--> <authentication mode="Forms"> <forms loginUrl="/secure/login.aspx" protection="All" path="/" timeout="540"/> </authentication> <authorization> <!-- <deny users="?"/>--> <allow users="*"/> </authorization> <!-- The <customErrors> section enables configuration of what to do if/when an unhandled error occurs during the execution of a request. Specifically, it enables developers to configure html error pages to be displayed in place of a error stack trace.
<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm"> <error statusCode="403" redirect="NoAccess.htm" /> <error statusCode="404" redirect="FileNotFound.htm" /> </customErrors> --> <customErrors mode="RemoteOnly" defaultRedirect="anomaly.aspx"> </customErrors> <!-- <httpModules> <add name="AspxLabRuntime" type="AspxLab.WebControls.Runtime,AspxLab.WebControls"/> </httpModules> --> <httpHandlers> <add verb="*" path="BusyBoxDotNet.axd" type="BusyBoxDotNet.ResourceHttpHandler, BusyBoxDotNet"/> </httpHandlers>
</system.web> </configuration>
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,194
|
Hi, Can you try to update to 2.7.4? http://www.aspxlab.com/builds/AspxLab_Controls_274.exeAlso try to create a blank test app and see if it works. Thanks
|
|
Rank: Newbie Groups: Member
Joined: 1/11/2008 Posts: 5
|
installed new version with no change. still a problem.
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,194
|
Have you just insalled the new version or also changed the DLL in your bin folder? If you have also done that, then I am not sure what else it could be. Version 2.7.4 is the last build for AspxLab and it is an very old build. All newer builds are under the new EO.Web name. In that case you might want to try our latest build but you will need to try it in a separate project. They are not compatible since the name change.
|
|
Rank: Newbie Groups: Member
Joined: 1/11/2008 Posts: 5
|
I dropped an old web.config on and it all started working again......
crazy.....
thanks for the attention.
|
|