RE: OMA Error 1503



Hello Chace,

Thanks for the reply.
When I type in http://localhost/oma in a web browser and use
domainname\administrator with the administrator password I still get the same
error.

CEICW shows everything checked except the business root website. I do not
use the Windows firewall, rather I use an external firewall.

Basic Authentication is the only checkbox selected for the OMA VD.

I do have forms based authentication enabled for OWA.


I will email you the logs requested.

Thank You.

--
__________________________
Richard Young, SBSC, CNE
http://www.relyonit.com



"chace zhang" wrote:

Hi Richard,

Thanks for posting here.

I understand that you can not access exchange via OMA. The event ID is 1503

Please perform the following steps to solve this issue:
1. Re-run the CEICW on your SBS box and ensure Outlook Mobile Access is
selected:

Click Start on your SBS server, click Server Management.
Click To Do List and then click "Connect to the Internet".
Click Next, select connection type and click Next.
Select Enable firewall and click Next.
Click Next, go through the steps until the Web Services Configuration page
shows, make sure that "Outlook Mobile Access" is selected.
Click Next, and follow the instructions to finish.

Test it again.


2 Please make sure only Basic Authentication is enabled on the /OMA virtual
directory:
- Open IIS MMC.
- Right click /OMA VD and click Properties.
- Click Directory Security tab.
- Click Edit in the Authentication section.
- Make sure only Basic Authentication is checked.

3. 2. On the SBS server, browse to http://localhost/oma, when you are
prompted to enter user name and password please use your
domainname\administrator, where domainname is your server's NetBIOS
domainname. Does the issue occur?

4. Do you enable FormsBasedAuthentication
When you try to connect to an Outlook Mobile Access Web site on an Exchange
2003 computer, you may receive the "A System error has occurred while
processing your request" error message
http://support.microsoft.com/?id=898131

If the issue persists, please collect the following info for further
research

Metabase
=======
a. Install .NET Framework Version 1.1:
http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-
8157-034d1e7cf3a3&DisplayLang=en.
b. Install MBExplorer by installing IIS 6 Resource Kit Tools:
http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-
B628-ADE629C89499&displaylang=en.
c. Once it is installed, access it from Start, Programs, IIS Resources,
Metabase Explorer.
d. In the left pane, right click ''LM'' (under your server computer name)
to choose ''Export to file'', and then save it as IIS.mbk.
e. Compress this mbk file and send it to me for analysis.

IIS logs
======
1. Open IIS.
2. Locate Default web site. Right-click it and then click Properties.
3. Click to selected Enable logging and then click properties.
4. Click Advanced.
5. Click to select every checkbox here.
6. Click OK to close these windows.
7. Reproduce this issue and send the logs to me.

NOTE: The log files are located at %systemroot%\System32\LogFiles by
default.

E-mail address: v-chacez@xxxxxxxxxxxxx

Hope this helps, I look forward to your update.

Have a nice day!


Best Regards,

Chace Zhang (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.


.



Relevant Pages

  • RE: OMA Error 1503
    ... Re-run the CEICW on your SBS box and ensure Outlook Mobile Access is ... Install MBExplorer by installing IIS 6 Resource Kit Tools: ... This newsgroup only focuses on SBS technical issues. ... you may want to contact Microsoft CSS directly. ...
    (microsoft.public.windows.server.sbs)
  • RE: Newbie question: Basic auth works, Chall/Resp fails?
    ... Subject: Newbie question: Basic auth works, Chall/Resp fails? ... patched up to date and IIS 4. ... I'm not worried about the clear text issue that Basic authentication ... > account domain and normally authenticates against ...
    (microsoft.public.inetserver.iis.security)
  • Re: Passing credentials
    ... > I have two web sites on the same IIS ... > server. ... Site B is set with 'Basic Authentication' mode. ... Tom Kaminski IIS MVP ...
    (microsoft.public.inetserver.iis.security)
  • Re: Client certificate private key prompt
    ... Are you running on IIS 5 or 6? ... before the GetResponse call, I will only get one prompt. ... > I also try to use the Basic Authentication only, ... > the problem persists. ...
    (microsoft.public.dotnet.framework)
  • Re: IIS With Basic Authentication Set/FormsAuthentication - HELP PLS!?
    ... IIS does... ... When you use Forms authentication you have to set IIS to Anonymous ... > Basic Authentication set. ... > again, trying to avoid the browser prompt, and add the authentication to ...
    (microsoft.public.dotnet.security)