RE: OMA-ActiveSynch broken - HTTP_403 and Cat: 1000 error: 0 error

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Jenny,

I tried the steps in your latest post to no avail, so here are the data and
log files that you request.

Yes, OWA is working fine. It is just OMA and ActiveSync that are no longer
working.

I have emailed you the data and log files as requested.

Thanks for the help. Looking forward to hearing from you soon.
Randy

""Jenny wu [MSFT]"" wrote:

Hi,

Thanks for your update.

For current situation, let us check the following settings:

1. Go to Start/Administrative Tools/Internet Information Services (IIS)
Manager.
2. Navigate to node Web Sites -> Default Web Site -> exchange-oma, right
click it to open its Properties page.

3. Under Virtual Directory tab, please double confirm the content of the
Local Path box is the same with the content of the Local Path box on the
Exchange virtual directory.

The local path content like this:
<\\.\backofficestorage\primaryemaildomainname.com\mbx> (should be able to
copy/paste it from the Properties of the Exchange virtual directory)

4. Then please run command "iisreset" (no quotation mark) from a command
prompt to refresh the IIS server.

5. Restart the Microsoft Exchange System Attendant service.

Then please test to see if the issue is resolved.

If the issue persists, I suggest that you try to create a secondary virtual
directory for Exchange that does not require SSL, and then add a registry
value to point to the new virtual directory.

Please refer to KB article 817379 -Method 2 to get detail steps to create
secondary VD and registry value.

Exchange ActiveSync and Outlook Mobile Access errors occur when SSL or
forms-based
authentication is required for Exchange Server 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;817379

Then please test to see if the OMA works.

If the issue persists, please help me collect the following information to
further analyze the issue:

1. Please capture a screen shot of the error message and send to my working
mailbox:v-yanniw@xxxxxxxxxxxxxx

2. Can you access the OWA site properly?

3. Please enable IIS logging and reproduced the issue (sync with the SBS
server, access the OMA site) and collect IIS log and IIS metabase.

-To enable IIS log:

a. Open IIS MMC, right click Default Web Site and then click Properties.
b. Click Website tab and then check Enable logging.
c. Stop the Default Website and rename the existing IIS log files under
C:\WINDOWS\system32\LogFiles.
d. Restart the Default Website and try to open OMA site and setup Server
Activesync to reproduce the problem.
e. Wait about 15 minutes, then go to the following folder:
C:\WINDOWS\system32\LogFiles and send them to me.

-To collect the IIS Metabase:

a. Download the IIS Resource Kit tools from the following page:
http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-
B628-ADE629C89499&displaylang=en
b. Install it, run MBExplorer (Metabase Explorer)
c. Right click the "LM" node and choose "Export to file".
d. Specify a file name, specify the password and finish the export.
e. Send the file and the password to me.

3. Save me a text copy of application and system log for analyze.

To save a text copy of Application /System log:

A. Open Event Viewer: Start -> All Programs -> Administrative Tools ->
Event Viewer.
B. Right-click on Application/System log and select "Save Log File As?".

Please compress all files and mail them to my working mailbox:
v-yanniw@xxxxxxxxxxxxx

I appreciate your time!

Have a nice day!

Sincerely,

Jenny Wu
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.

--------------------
Thread-Topic: OMA-ActiveSynch broken - HTTP_403 and Cat: 1000 error: 0
error
thread-index: Acafc9IdS7Eo/o/yRkSz7EUl8GgKsg==
X-WBNR-Posting-Host: 75.1.15.146
From: =?Utf-8?B?TTJC?= <M2B@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <CC8B6F56-8C3D-4F13-A0E7-D61DC23D9CB4@xxxxxxxxxxxxx>
<bCjUFopnGHA.4188@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: OMA-ActiveSynch broken - HTTP_403 and Cat: 1000 error: 0 error
Date: Tue, 4 Jul 2006 07:12:02 -0700
Lines: 229
Message-ID: <9704224F-F802-41E7-9277-09A2D1D8AF32@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 8bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.sbs
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:279061
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.sbs

Hi Jenny,

Followed your steps and had no success. The errors remain the same
results
403 errors on activesync and 'Item no longer exists ...' errors from oma.

It is interesting that ActiveSync returns a 200 for the OPTIONS verb on
the
users account but a 403 for the POST that actually attempts to access the
users MBX data. I am not sure what to make of this but it seems like it
could be important in diagnosing the problem.

Looking forward to any other ideas you may have.

Thanks for the help,
Randy


""Jenny wu [MSFT]"" wrote:

Hi,

Thanks for using the SBS newsgroup.

I am sorry for the delayed response due to weekend. Please understand
that
the newsgroups are staffed weekdays by Microsoft Support professionals
to
answer your systems and applications questions. Your understanding is
greatly appreciated!

For time critical issues (not business down), we encourage you to
contact
CSS directly for more immediate assistance:
International Support (non-US/Canada):
http://support.microsoft.com/common/international.aspx

US and Canada:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone

To continue working with me in the newsgroups, please see the following:

For current situation, let us perform the following test to see if it
helps:

First of all, please refer to the following Knowledge Base Article to
backup the Metabase first:
HOW TO: Create a Metabase Backup by Using IIS 6.0 in Windows Server 2003
http://support.microsoft.com/?id=324277

1. Go to Internet Services Manager and delete the following virtual
directories:
Microsoft-Server-ActiveSync,
OMA,
Exchange,
Public,
ExchWeb.

2. Download and install Metabase Explorer from the following URL:

"http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73
-B628-ADE629C89499&displaylang=en"

NOTE: This link can be wrapped. Please make sure that you have included
the
entire contents between the quotation marks when you download this tool.

3. Open Metabase Explorer and expand LM > DS2MB > HighWaterMarks > GUID

4. Double click the entry which has a 5-digit number in the data folder
in
the right pane of the GUID folder.
5. Replace the number in the Data field with 0 (zero) and then click
OK.
Close Metaedit
6. Run services.msc and right click IIS Admin Service, and then click
Restart to restart the service.

7. Restart the System Attendant. After that, these virtual directories
can
be created.

8. Then please test to see if the issue resolved.

If the issue persists, please to do the following steps:

1. Stop the System Attendant Service.

2. Open command window. Run

Cd c:\inetpub\adminscripts
cscript adsutil delete SMTPSVC/1/domain

3. Run command:
Cscript adsutil delete DS2MB

4. Restart the System attendant, SMTP services. Wait some time to see if
the issue persists.

If the issue persists, you can perform test according to steps you
listed
to see if it helps.

Hope above information helps. I am happy to be of assistance to you and
look forward to your reply.

Have a nice day!

Sincerely,

Jenny Wu
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.

--------------------
Thread-Topic: OMA-ActiveSynch broken - HTTP_403 and Cat: 1000 error: 0
errors.
thread-index: AcaccNNGW3M/oCWrSICrNlY2ditk5g==
X-WBNR-Posting-Host: 68.165.107.44
From: =?Utf-8?B?TTJC?= <M2B@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: OMA-ActiveSynch broken - HTTP_403 and Cat: 1000 error: 0
errors.
Date: Fri, 30 Jun 2006 11:13:02 -0700
Lines: 68
.

Relevant Pages

  • RE: SBS 2003 stand, useage report file
    ... Thanks for updates. ... IIS log, you can check the log files, we have no option to check it in ISA, ... IIS pages. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: problem with DefaultAppPool in IIS
    ... I list the default companyweb and Remote virtual directory settings in IIS. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: OMA Activesync issues
    ... Please verify Authentication settings in IIS by the following steps. ... Open properties of virtual directory Exchange/Exchange-oma ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: OMA-ActiveSynch broken - HTTP_403 and Cat: 1000 error: 0 error
    ... Go to Start/Administrative Tools/Internet Information Services (IIS) ... Under Virtual Directory tab, please double confirm the content of the ... copy/paste it from the Properties of the Exchange virtual directory) ... Restart the Microsoft Exchange System Attendant service. ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook Mobile Access(OMA) not functional
    ... Please verify Authentication settings in IIS by the following steps. ... Open properties of virtual directory Exchange/Exchange-oma ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.exchange.admin)