Re: Can't get OMA going
From: Tim Kowal (tim_at_nospam.com)
Date: 07/08/04
- Next message: Paulo Borges: "OWA browsing problems"
- Previous message: Jamelia: "Re: OWA Spell Check, how to add?"
- In reply to: Alan Sun [MSFT]: "Re: Can't get OMA going"
- Next in thread: Alan Sun [MSFT]: "Re: Can't get OMA going"
- Reply: Alan Sun [MSFT]: "Re: Can't get OMA going"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 08 Jul 2004 15:18:17 GMT
The extension was already set to "Allow." The listed Extensions are:
All Unknown CGI Extensions Prohibited
All Unkonwn ISAPI Extensions Prohibited
Active Server Pages Allowed
ASP.NET v1.1.4322 Allowed
FrontPage Server Extensions Allowed
Internet Data Connector Allowed
Microsoft Exchange Server Allowed
Server Side Includes Allowed
WebDAV Allowed
Windows SharePoint Services Allowed
What should be my next step? Thanks for your continued help with this.
Tim
"Alan Sun [MSFT]" <v-asun@online.microsoft.com> wrote in message
news:bZ6efiLZEHA.2804@cpmsftngxa06.phx.gbl...
> Hi Tim,
>
> Thanks for your posting back.
>
> As the issue persists, please check the permission for "ASP.NET
v1.1.4322"
> extension. To do so:
>
> 1. Open IIS.
> 2. Expand the server name.
> 3. Click on Web Service Extensions
> 4. Right-click on the "ASP.NET v1.1.4322" extension, and choose "Allow".
>
> Note: No IIS services or web sites need to be restarted in order for the
> above steps to take effect.
>
> I am looking forward to hearing from you.
>
> Thanks & Regards
> Alan Sun
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
>
> --------------------
> |From: "Tim Kowal" <tim@nospam.com>
> |Newsgroups: microsoft.public.exchange.clients
> |References: <PiCGc.12096$TX3.11958@newssvr27.news.prodigy.com>
> <aH5sAX8YEHA.1580@cpmsftngxa06.phx.gbl>
> |Subject: Re: Can't get OMA going
> |Lines: 221
> |X-Priority: 3
> |X-MSMail-Priority: Normal
> |X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
> |X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
> |Message-ID: <SiZGc.12438$PJ4.8414@newssvr27.news.prodigy.com>
> |NNTP-Posting-Host: 67.127.249.122
> |X-Complaints-To: abuse@prodigy.net
> |X-Trace: newssvr27.news.prodigy.com 1089233202 ST000 67.127.249.122
> (Wed, 07 Jul 2004 16:46:42 EDT)
> |NNTP-Posting-Date: Wed, 07 Jul 2004 16:46:42 EDT
> |Organization: SBC http://yahoo.sbc.com
> |X-UserInfo1:
>
OH\ARXKDZZSQBPH]]RKB_UDAZZ\DPCPDLXUNNH\KMAVNDQUBLNTC@AWZWDXZXQ[K\FFSKCVM@F_N
>
_DOBWVWG__LG@VVOIPLIGX\\BU_B@\P\PFX\B[APHTWAHDCKJF^NHD[YJAZMCY_CWG[SX\Y]^KC\
> HSZRWSWKGAY_PC[BQ[BXAS\F\\@DMTLFZFUE@\VL
> |Date: Wed, 07 Jul 2004 20:46:42 GMT
> |Path:
>
cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.s
>
ul.t-online.de!t-online.de!news.glorb.com!prodigy.com!prodigy.com!newsmst01a
>
news.prodigy.com!prodigy.com!postmaster.news.prodigy.com!newssvr27.news.pro
> digy.com.POSTED!7f2df3f6!not-for-mail
> |Xref: cpmsftngxa06.phx.gbl microsoft.public.exchange.clients:85507
> |X-Tomcat-NG: microsoft.public.exchange.clients
> |
> |I already had all those paths excluded.
> |
> |I followed the steps to make the change for Kerberos, but I receive
> the same
> |error message. Is there something else I could be missing?
> |
> |
> |"Alan Sun [MSFT]" <v-asun@online.microsoft.com> wrote in message
> |news:aH5sAX8YEHA.1580@cpmsftngxa06.phx.gbl...
> |> Hello Tim,
> |>
> |> Thanks for your posting here.
> |>
> |> Based on my knowledge, this problem may occur after you install
> Microsoft
> |> Windows SharePoint Services on a server that is running Microsoft
> Exchange
> |> Server. The Windows SharePoint Services ISAPI filter handles all
> incoming
> |> URLs. When you browse one of the Exchange Server 2003 virtual
> directories,
> |> the ISAPI filter does not locate the URL path of the folder.
> |>
> |> To resolve this problem, and to have Windows SharePoint Services
and
> |> Exchange Server 2003 both function correctly, you must enable
> Kerberos
> |> authentication and exclude the folders (directories) that
Microsoft
> |> Exchange Server 2003 uses. To do so, follow these steps:
> |>
> |> 1. Configure the virtual server that is running Windows SharePoint
> |Services
> |> and Exchange Server 2003 programs to use Kerberos authentication.
> |>
> |> When a virtual server is extended with Windows SharePoint
Services,
> |> Kerberos authentication is disabled Integrated Windows
> authentication is
> |> enabled. For Exchange Server 2003 to work correctly, you must
> configure
> |the
> |> virtual server to use Kerberos authentication.
> |>
> |> For additional information about how to configure Windows
SharePoint
> |> Services to Use Kerberos authentication, look into the following
> Knowledge
> |> Base article:
> |>
> |> 832769 HOW TO: Configure Windows SharePoint Services to Use
Kerberos
> |> http://support.microsoft.com/?id=832769
> |>
> |> 2. Exclude the following folders (directories) that Microsoft
> Exchange
> |> Server 2003 uses:
> |>
> |> - Public
> |> - Exchange
> |> - Exadmin
> |> - OMA
> |> - Microsoft-Server-ActiveSync
> |> - ExchWeb
> |> To do so, follow these steps:
> |>
> |> a. On the server that is running Exchange Server 2003 and Windows
> |> SharePoint Services, click "Start", click "Administrative Tools",
> and
> |then
> |> click "SharePoint Central Administration".
> |>
> |> b. In the "Virtual Server Configuration" area, click "Configure
> virtual
> |> server settings".
> |>
> |> c. On the "Virtual Server List" tab, click the virtual server that
> you
> |> have to add the excluded paths to.
> |>
> |> d. Under "Virtual Server Management", click "Define Managed
Paths".
> |>
> |> e. In the "Add a New Path" section, type the path to exclude in
the
> "Path"
> |> box.
> |>
> |> f. Click "Excluded Path", and then click "OK".
> |>
> |> g. Repeat steps 4 through 6 for each folder that you want to
> exclude.
> |>
> |> For more information, refer to the following article:
> |>
> |> 823265 "Page Not Found" Error Message When You Browse Exchange
> Server 2003
> |> http://support.microsoft.com/?id=823265
> |>
> |> Hope this helps. Have a nice day!
> |>
> |> Thanks & Regards
> |> Alan Sun
> |> Microsoft Online Partner Support
> |>
> |> Get Secure! - www.microsoft.com/security
> |> =====================================================
> |> When responding to posts, please "Reply to Group" via your
> newsreader so
> |> that others may learn and benefit from your issue.
> |> =====================================================
> |>
> |> This posting is provided "AS IS" with no warranties, and confers
no
> |rights.
> |>
> |>
> |>
> |> --------------------
> |> |From: "Tim Kowal" <tim@nospam.com>
> |> |Newsgroups: microsoft.public.exchange.clients
> |> |Subject: Can't get OMA going
> |> |Lines: 72
> |> |X-Priority: 3
> |> |X-MSMail-Priority: Normal
> |> |X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
> |> |X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
> |> |Message-ID:
<PiCGc.12096$TX3.11958@newssvr27.news.prodigy.com>
> |> |NNTP-Posting-Host: 67.127.249.122
> |> |X-Complaints-To: abuse@prodigy.net
> |> |X-Trace: newssvr27.news.prodigy.com 1089138991 ST000
> 67.127.249.122
> |> (Tue, 06 Jul 2004 14:36:31 EDT)
> |> |NNTP-Posting-Date: Tue, 06 Jul 2004 14:36:31 EDT
> |> |Organization: SBC http://yahoo.sbc.com
> |> |X-UserInfo1:
> |>
>
>
|SCSYASVG\JUERQT[OBHD]_\@VR]^@B@MCPWZKB]MPXHBTWICYFWUQBKZQLYJX\_ITFD_KFVLUN[
> D
> |>
>
>
|OM_A_NSYNWPFWNS[XV\I]PZ@BQ[@CDQDPCL^FKCBIPC@KLGEZEFNMDYMKHRL_YYYGDSSODXYN@[
> \
> |> BK[LVTWI@AXGQCOA_SAH@TPD^\AL\RLGRFWEARBM
> |> |Date: Tue, 06 Jul 2004 18:36:31 GMT
> |> |Path:
> |>
>
>
|cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!news-out.cwix.com!newsfeed.cwix.c
> o
> |>
>
>
|m!prodigy.com!newsmst01a.news.prodigy.com!prodigy.com!postmaster.news.prodi
> g
> |> y.com!newssvr27.news.prodigy.com.POSTED!7f2df3f6!not-for-mail
> |> |Xref: cpmsftngxa06.phx.gbl
> microsoft.public.exchange.clients:85476
> |> |X-Tomcat-NG: microsoft.public.exchange.clients
> |> |
> |> |I'm trying to setup OMA on my Exchange 2003 Standard server
> on a
> |> Windows
> |> |2003 Standard server. The error is at the bottom.
> |> |
> |> |- I did the basics already, enabling it under Mobile
Services
> |> Properties in
> |> |the System Manager and for each user under ADUC.
> |> |
> |> |- This is a single Exchange server -- not a FE or BE.
> |> |
> |> |- I am also running OWA with FBA and encryption, but for
> |> troubleshooting, I
> |> |have disabled both for now. (Though in the end I will need
to
> turn
> |> them back
> |> |on.)
> |> |
> |> |- I tried uninstalling and reinstalling .NET Device Update
> 4.0.
> |> |
> |> |- I do have Sharepoint installed, but I have all Exchange
> websites -
> |> |including OMA - excluded under the administration.
> |> |
> |> |- I have setup OMA successfully on another Windows 2000
> server, and
> |> have
> |> |compared all settings between the two. They look the same.
> |> |
> |> |ERROR:
> |> |What happens is that when I bring up the page, it asks me
for
> |> user/pass as
> |> |per normal, but then when I log on I get this page:
> |> |
> |> |
> |> |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) +666
> |> |
> 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.573;
> |> ASP.NET
> |> |Version:1.1.4322.573
> |> |
> |> |
> |> |
> |>
> |
> |
> |
>
- Next message: Paulo Borges: "OWA browsing problems"
- Previous message: Jamelia: "Re: OWA Spell Check, how to add?"
- In reply to: Alan Sun [MSFT]: "Re: Can't get OMA going"
- Next in thread: Alan Sun [MSFT]: "Re: Can't get OMA going"
- Reply: Alan Sun [MSFT]: "Re: Can't get OMA going"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
