Re: OMA on SBS is not working
- From: "Neil Hoskins" <NeilHremovethisbit@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 4 Jan 2007 08:37:35 -0000
It may not be related, but I discovered that to get OMA to work on a WAP
browser, you need to have a public certificate; a self-signed one won't do
the job.
<jan.pieters@xxxxxxxxx> wrote in message
news:1167865254.315187.207120@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a SBS 2003 running for over 1 year with no problem, but not
using the OMA/ActiveSync feature.
When I want to 'activate' this feature, everything is configured
correctly on a PocketPC-device I'm still not able to connect. It's
always keeps asking for the account-password....
When I use Internet Explorer to navigate to the https://server/OMA
site, I get following Error. I found lots of people havving the same
problem when Exchange and SharePoint are on the same server, bu seeing
the fact that it is a SBS, there must be a way to let it work. I pretty
much sure that it has something to do with ACL, but I don't know
exactly where to start....
Any help would be a great. Thanks ....
THE ERROR MSG:
------------------------------
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
.
- References:
- OMA on SBS is not working
- From: jan . pieters
- OMA on SBS is not working
- Prev by Date: Re: Connecting a second Server
- Next by Date: Re: Mailbox Management Policy Not deleting emails
- Previous by thread: OMA on SBS is not working
- Next by thread: Client computer internet connection problems
- Index(es):
Relevant Pages
|
