RE: OWA bug

Hi Matt,

Thank you for your kind update.

Based on my experience, this issue can occur if the content of the
"%SystemRoot%\IIS Temporary Compressed Files" folder is corrupted. To
resolve the issue, perform the following steps:

At the server side:

a. Apply the 831464 hot fix (Note: If you have applied SBS 2003 SP1 or the
version of the W3core.dll file is 6.0.3790.99 or later and if so you do not
need to apply the fix again):

http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=0bc9
b5bc-a094-49bf-89a5-c8a2d32345a2&displaylang=en

b. Clear the IIS server files. To do so, follow these steps:

1) Go to your "%SystemRoot%\IIS Temporary Compressed Files" (C:\WINDOWS\IIS
Temporary Compressed Files or C:\WINNT\IIS Temporary Compressed Files)
directory.

2) Select all of the content in this directory and delete it.

3) Click Start->Run, type "iisreset" (without the quotes) and click OK to
restart the IIS services.

At the client side:

a. Open IE, and go to Tools -> Internet Options.

b. Select Delete Files, check "Delete all offline files" and click OK to
confirm that you want to delete the content. Then check if the issue
disappears. Please also delete Cookies and then try again.

3. This issue can also be caused by TrendMicro Officescan installed. If so
please try the suggestions in the following KB article and check if the
issue can be fixed:

842470 The contents of your Inbox and your Calendar are not displayed when
you
http://support.microsoft.com/?id=842470

4. Also check if you have URLSCAN installed. If so, make sure URLSCAN is
configured per the Exchange 2003 OWA template for URLSCAN. See::

325965 The URLScan tool may cause problems in Outlook Web Access
http://support.microsoft.com/?id=325965

309508 - XCCC: IIS Lockdown and URLscan Configurations in an Exchange
Environment:
http://support.microsoft.com/default.aspx?scid=kb;en-us;309508

823175: Fine-Tuning and Known Issues When You Use the Urlscan Utility in an
Exchange 2003 Environment
http://support.microsoft.com/?id=823175

5. If you have ISA installed on the SBS server, take the following steps to
clear the ISA cache.

A. Stop the Web Proxy service.
B. Locate the Urlcache folder.
C. From the multiple files in this folder, locate the *.cdat file in this
folder.
D. Delete the *.cdat file.
E. Start the Web Proxy service.

Related Knowledge Base article:

301471 How to Delete the Web Cache on Internet Security and Acceleration
Server
http://support.microsoft.com/?id=301471

6. Do you use some anti-virus software on the server side? If so, please
temporarily stop your anti-virus software on the server side, and then test
if the problem occurs. In case the incorrect configuration about anti-virus
may cause the emails damaged.

7. Did you install the SBS 2003 SP1 and Exchange 2003 SP2?


If the issue persists, please kindly help me collect the following
information for further analysis:

1. Please make some screen shots when you are experiencing the OWA issue,
and then attach them in your reply.

2. Are there any event logs related to this issue?

I appreciate your time and cooperation. If anything is unclear, please feel
free to let me know. I am looking forward to hearing from you.

Best regards,

Nathan Liu (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.


--------------------
>Thread-Topic: OWA bug
>thread-index: AcX/sL5eANQb5QuiT7e1HZ5uG8GXXg==
>X-WBNR-Posting-Host: 61.8.97.25
>From: "=?Utf-8?B?TWF0dCBDYXJvbGFuIFtTQlMgVUdNXQ==?="
<MattCarolanSBSUGM@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <CBE52EFA-CA08-4415-B82B-14D7C170E4ED@xxxxxxxxxxxxx>
<Pi6KOMY#FHA.4000@xxxxxxxxxxxxxxxxxxxxx>
<4CAC361C-7889-4562-A470-F021548ED768@xxxxxxxxxxxxx>
>Subject: RE: OWA bug
>Date: Mon, 12 Dec 2005 22:45:02 -0800
>Lines: 195
>Message-ID: <2D60C6BA-02F3-4519-939A-BB3788A4E737@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>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.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:229728
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>I forgot to mention that I have read that errors can occur when sending
and
>receiving in owa due to mailbox size restrictions but I have checked that
>this isn't the case. I have also created a new fresh account and had the
same
>problem.
>
>thanks
>
>"Matt Carolan [SBS UGM]" wrote:
>
>> Hi Nathan
>> I have alot more detail to provide now on this problem.
>> It looks like the problem is the sbs 2003 server.
>> From any workstation inside or outside the network the same problem
happens.
>> For any user including administrator the same problem happens.
>> I have from home logged into the clients problem server using owa and
have
>> had the issue but then logged into our company's server using owa and
had no
>> problem so the workstation isn't the issue.
>>
>> Now the problem is that you can get into owa fine but when you go to
create
>> a new email, it will come up with a new window like normal but all the
fields
>> except the body of the email field, like to:, subject: etc, all display
2
>> lines but you can't click on the top line, only the bottom line. And
this
>> same thing happens no matter what pc you use remotely to access owa. The
when
>> you click on the send button it loads the main area of owa in that same
>> window so that your left with 2 internet explorer windows showing the
main
>> owa screen. This would all be fine except no email is sent. Nothing
appears
>> in exchange ques or message tracker. Nothing in the send, outbox or
draft
>> items folders.
>>
>> If I go into owa as basic mode instead of premium then hovering over
send
>> shows an error at the bottom and clicking on it pops up on the screen
with an
>> error - "line38, char1, error:object expected, code:0,
>> url:https://clientsowaaddress.com.au/exchange/username/drafts/?cmd=new
>>
>> for security reason I have above replaced the mail server domain with
>> clientsowaaddress.com.au and the real username replaced with username
>>
>> any help u can provide would be great
>>
>> ""Nathan Liu [MSFT]"" wrote:
>>
>> > Hello Matt,
>> >
>> > Thank you for posting in the SBS newsgroup.
>> >
>> > My sincerest apologies for the delay in responding, please note the
partner
>> > managed newsgroups are staffed weekdays by Microsoft Support
professionals.
>> > Our goal is to provide a one business day response to all posts.
>> >
>> > 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:
>> >
>> > According to your description, I understand that you cannot send email
when
>> > you are using OWA from an specific location. If I have misunderstood
the
>> > problem, please don't hesitate to let me know.
>> >
>> > To narrow down this issue, please kindly answer and perform the
following
>> > questions and steps:
>> >
>> > 1. Does this issue occur with all users or certain users? Please try
>> > again from other locations and then check if the issue can be
reproduced.
>> >
>> > 2. Did these outgoing emails stay in the "Outbox" or "Sent Items"
>> > folders? What's the exact problem symptom?
>> >
>> > 3. Reproduce this issue, please check in which queue the emails
stays
>> > (you may not see it if it is delivered). To check this:
>> >
>> > 1). Start Exchange System Manager.
>> >
>> > 2). Use the following path to locate the queues you want to check:
>> >
>> > Servers\<ServerName>\Protocols\SMTP virtual Server\<SMTP virtual
>> > server>\Queues\<Queue>
>> >
>> > 4. Enable message tracking, reproduce this issue, and then check the
email
>> > message under Tools->Message Tracking Center (you can make a screen
capture
>> > of the tracking result and attach the picture in your reply).
Regarding how
>> > to enable Message Tracking, please refer to the following MS KB
article:
>> >
>> > 246856 XADM: How to Enable Message Tracking in Exchange 2000 Server
>> > http://support.microsoft.com/?id=246856
>> >
>> > 5. Enable SMTP logging and gather SMTP log to troubleshoot the issue:
>> >
>> > A. Open Exchange System Manager, expand Servers -> <Server name> ->
>> > Protocols -> SMTP, right-click "Default SMTP Virtual Server" and click
>> > Properties.
>> >
>> > B. Under the General tab, check the option "Enable Logging".
>> >
>> > C. With "W3C Extended Log File Format", click "Properties".
>> >
>> > D. Under "General Properties", make sure "Use local time for file
naming
>> > and rollover" is CHECKED.
>> >
>> > E. Switch to the "Extended Properties", and then select to enable All
the
>> > logging Options.
>> >
>> > F. Click OK to apply the modification.
>> >
>> > G. Right-click Default SMTP Virtual Server and click Stop.
>> >
>> > H. Right-click Default SMTP Virtual Server and click Start to restart
the
>> > SMTP server.
>> >
>> > I. Reproduce the issue, repeat step G to stop Default SMTP Virtual
Server,
>> > copy out or zip the SMTP log files in the
>> > "%systemroot%\system32\logfiles\SmtpSvc1" folder, and then restart the
>> > "Default SMTP Virtual Server".
>> >
>> > I appreciate your time and cooperation. If anything is unclear, please
feel
>> > free to let me know. I am looking forward to hearing from you.
>> >
>> > Best regards,
>> >
>> > Nathan Liu (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.
>> >
>> >
>> >
>> >
>> > --------------------
>> > >Thread-Topic: OWA bug
>> > >thread-index: AcX5L9H5SZRF0rotRWu23gKnBUeQwg==
>> > >X-WBNR-Posting-Host: 202.173.149.15
>> > >From: "=?Utf-8?B?TWF0dCBDYXJvbGFuIFtTQlMgVUdNXQ==?="
>> > <MattCarolanSBSUGM@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> > >Subject: OWA bug
>> > >Date: Sun, 4 Dec 2005 16:07:03 -0800
>> > >Lines: 12
>> > >Message-ID: <CBE52EFA-CA08-4415-B82B-14D7C170E4ED@xxxxxxxxxxxxx>
>> > >MIME-Version: 1.0
>> > >Content-Type: text/plain;
>> > > charset="Utf-8"
>> > >Content-Transfer-Encoding: 7bit
>> > >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.0
>> > >Newsgroups: microsoft.public.windows.server.sbs
>> > >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> > >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> > >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:227651
>> > >X-Tomcat-NG: microsoft.public.windows.server.sbs
>> > >
>> > >Hi all
>> > >Using sbs 2003 I have a user that can get into outlook web access
from
>> > >outside their office perfectly. Everything works fine but when they
try to
>> > >send an email it doesn't work.
>> > >They are using a window xp pro PC.
>> > >If I connect to my server on the same PC via owa I can send fine.
>> > >On their server itself if I use owa for his account it works fine as
well
>> > >
>> > >Anyone who can shed some light on this for me - that would be great
>> > >-thanks in advance
>> > >
>> > >Matt
>> > >
>> >
>> >
>

.