afterlife
30th December 2005, 07:05 AM
Hi all,
Need help on the following issue.
I have install Exchange 2003 on Server 2003 and is working well, OWA & OMA
on my O2 XDA IIi. But when i install the Windows Sharepoint Service on the
same server and configure as per the documentation
(http://support.microsoft.com/kb/823265/en-us).
With the article i'm able to get my OWA up and running but not able for
OMA, maybe i do not really understand the last portion of the article. Can
someone kindly advice me on what i should be doing to get my OMA up and
running.
I believe that it's pointing to my root of the IIS which is the Windows
Sharepoint service.
Error from my Activesync
**************************
Your account does not have permission to sync with your current settings.
Contact your Microsoft Exchange administrator.
An error occurred, and scheduled synchronization had to be disabled. To
start synchronizing on a schedule again, use the Mobile Schedule tab in
ActiveSync Options.
Error code: HTTP_400
**************************
Thanks.
************************************************** ******************************
If you must use Outlook Mobile Access with Microsoft Windows SharePoint
Services, you must complete an extra step, in addition to not including
the OMA path, to make this virtual directory accessible. Open the OMA
Web.config file located at the following path
\Program Files\Exchsrvr\OMA\browse\Web.config
and add the following directives in the Web.config between
<system.Web></system.Web>. Add these directives immediately after
<system.Web> to keep it as simple as possible:
<!--
Clear out the WSS ASP.Net handler and specify the default ASP.Net
handler for all pages
-->
<httpHandlers>
<clear />
<add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory,
System.Web, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a" />
</httpHandlers>
<!--
Set the trust back to Full. WSS configures a very restrictive
trust policy that does not allow OMA to run correctly.
-->
<trust level="Full" originUrl="" />
<!--
Enable the session module. This can also be enabled on the WSS
Web.config, but is not enabled by default.
If you receive the following message:
Parser Error Message: The module 'Session' is already in the
application and cannot be added again
You can remove the following <httpModules></httpModules> section as
session is already enabled on the virtual server
-->
<httpModules>
<add name="Session"
type="System.Web.SessionState.SessionStateModule"/>
</httpModules>
<pages enableSessionState="true" enableViewState="true"
enableViewStateMac="true" validateRequest="false" />
After you add the directives to the Web.config, save the file.
************************************************** ******************************
Need help on the following issue.
I have install Exchange 2003 on Server 2003 and is working well, OWA & OMA
on my O2 XDA IIi. But when i install the Windows Sharepoint Service on the
same server and configure as per the documentation
(http://support.microsoft.com/kb/823265/en-us).
With the article i'm able to get my OWA up and running but not able for
OMA, maybe i do not really understand the last portion of the article. Can
someone kindly advice me on what i should be doing to get my OMA up and
running.
I believe that it's pointing to my root of the IIS which is the Windows
Sharepoint service.
Error from my Activesync
**************************
Your account does not have permission to sync with your current settings.
Contact your Microsoft Exchange administrator.
An error occurred, and scheduled synchronization had to be disabled. To
start synchronizing on a schedule again, use the Mobile Schedule tab in
ActiveSync Options.
Error code: HTTP_400
**************************
Thanks.
************************************************** ******************************
If you must use Outlook Mobile Access with Microsoft Windows SharePoint
Services, you must complete an extra step, in addition to not including
the OMA path, to make this virtual directory accessible. Open the OMA
Web.config file located at the following path
\Program Files\Exchsrvr\OMA\browse\Web.config
and add the following directives in the Web.config between
<system.Web></system.Web>. Add these directives immediately after
<system.Web> to keep it as simple as possible:
<!--
Clear out the WSS ASP.Net handler and specify the default ASP.Net
handler for all pages
-->
<httpHandlers>
<clear />
<add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory,
System.Web, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a" />
</httpHandlers>
<!--
Set the trust back to Full. WSS configures a very restrictive
trust policy that does not allow OMA to run correctly.
-->
<trust level="Full" originUrl="" />
<!--
Enable the session module. This can also be enabled on the WSS
Web.config, but is not enabled by default.
If you receive the following message:
Parser Error Message: The module 'Session' is already in the
application and cannot be added again
You can remove the following <httpModules></httpModules> section as
session is already enabled on the virtual server
-->
<httpModules>
<add name="Session"
type="System.Web.SessionState.SessionStateModule"/>
</httpModules>
<pages enableSessionState="true" enableViewState="true"
enableViewStateMac="true" validateRequest="false" />
After you add the directives to the Web.config, save the file.
************************************************** ******************************