Sharepoint 2.0 causing problems with .NET applications?

From: Damian (grwghow_at_yahoo.com)
Date: 02/19/04 

Date: 19 Feb 2004 05:52:29 -0800

Hi

I'm having trouble getting our .NET applications to run on IIS web
sites that have been extended with Sharepoint. The same applications
run just fine if I move them to another web site that hasn't been
extended.

I of course had to add the application paths to Sharepoint's managed
paths as excludes to get to get the applications to load at all.

I compared the properties of the two web sites and they're essentially
the same with minor, non-important differences. The only thing I
thought important was that the Sharepoint site had Sharepoint's ISAPI
filter on it, but I added it to the non-extended site and that didn't
stop it from working.

I also compared the application pools and it's the same, only very
minor differences regarding worker process recycling and such. Both
app pools are running under the Network Service account.

I did find KB article 828810 and tried the suggested code on the
web.config file, with no change whatsoever (even after restarting
IIS). I did all of the above changes one at a time, and undid them
when there were no differences (order above all).

That's as much as I can remember, .. I'm pasting the error below to
see if any of you can help me (please!).
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Server Error in xxxxxxxxxxxxxxxx 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: Security error.

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: Security error.]
   xxxxxx._default.Page_Load(Object sender, EventArgs e) +0
   System.Web.UI.Control.OnLoad(EventArgs e) +67
   System.Web.UI.Control.LoadRecursive() +35
   System.Web.UI.Page.ProcessRequestMain() +2106
   System.Web.UI.Page.ProcessRequest() +217
   System.Web.UI.Page.ProcessRequest(HttpContext context) +18
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
+179
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step,
Boolean& completedSynchronously) +87

 

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.573;
ASP.NET Version:1.1.4322.573

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Thanks a lot in advance, regards

Damián

Relevant Pages

  • Sharepoint 2.0 causing problems with .NET applications?
    ... I'm having trouble getting our .NET applications to run on IIS web ... thought important was that the Sharepoint site had Sharepoint's ISAPI ... Exception Details: System.Security.SecurityException: Security error. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: RPC over HTTPS fails following install of SharePoint Services
    ... Did you find any solution to keep SharePoint ... Service 3.0 on the same server and have it working? ... An unhandled exception has occurred. ... Thread account name: NT AUTHORITY\NETWORK SERVICE ...
    (microsoft.public.exchange.admin)
  • Re: NT AUTHORITYNetwork Service cant write to .NET Directory?
    ... thats how ASP.NET works - pages are compiled to classes, these classes go into assemblies and these assemblies have to be stored somewhere. ... Developing More Secure Microsoft ASP.NET 2.0 Applications ... Exception Details: System.Web.HttpException: The current identity ... compilationSection) +3482379 ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Installing a SharePoint Site breaks OMA
    ... At our organisation we use OMA heavily and we recently purchased SharePoint ... It appears to have changed some security settings. ... To grant this application the required permission ... Exception Details: System.Security.SecurityException: Request for the ...
    (microsoft.public.exchange.setup)
  • RE: Excluding the path of web application
    ... I'd like to recommend that you rethink web applications and how they are ... With SharePoint we deploy WebParts ... it in an excluded path as you would with ASP.NET with some configuration ...
    (microsoft.public.sharepoint.windowsservices)