Installing a SharePoint Site breaks OMA
- From: "robinwilson16" <robinwilson16@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 19 Dec 2005 15:57:02 -0800
At our organisation we use OMA heavily and we recently purchased SharePoint
Portal Server
When the default website was extended with SharePoint and all the
directories were excluded from being managed by SharePoint it caused Outlook
Mobile Access along with all other .net framework based web applications to
fail.
It appears to have changed some security settings.
I know the solution is probably simple but I cannot find an answer after
having searched the knowledge base etc.
Please can someone help
Thanks
Robin
N.B After disabling custom errors, the following error is displayed:
******************************************
Server Error in '/OMA' 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: Request for the
permission of type System.Security.Permissions.RegistryPermission, mscorlib,
Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 failed.
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: Request for the permission of type
System.Security.Permissions.RegistryPermission, mscorlib, Version=1.0.5000.0,
Culture=neutral, PublicKeyToken=b77a5c561934e089 failed.]
System.Security.CodeAccessSecurityEngine.CheckHelper(PermissionSet
grantedSet, PermissionSet deniedSet, CodeAccessPermission demand,
PermissionToken permToken) +675
System.Security.CodeAccessSecurityEngine.Check(PermissionToken permToken,
CodeAccessPermission demand, StackCrawlMark& stackMark, Int32 checkFrames,
Int32 unrestrictedOverride) +0
System.Security.CodeAccessSecurityEngine.Check(CodeAccessPermission cap,
StackCrawlMark& stackMark) +88
System.Security.CodeAccessPermission.Demand() +62
Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable) +159
Microsoft.Win32.RegistryKey.OpenSubKey(String name) +27
Microsoft.Exchange.OMA.UserInterface.Global..cctor() +48
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET
Version:1.1.4322.2300
.
- Follow-Ups:
- Re: Installing a SharePoint Site breaks OMA
- From: Mark Arnold [MVP]
- Re: Installing a SharePoint Site breaks OMA
- Prev by Date: Re: Would this work as a quick and dirty migration?
- Next by Date: Re: Why SMTP Connector?
- Previous by thread: Re: Would this work as a quick and dirty migration?
- Next by thread: Re: Installing a SharePoint Site breaks OMA
- Index(es):
Relevant Pages
|