Re: OWA Access stops / Outlook ok
- From: George Sang <GeorgeSang@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 29 Nov 2006 22:50:00 -0800
Hi Craig,
You may consider to reset the default virtual directories. Here is the link
http://support.microsoft.com/kb/883380
I tried it once. After doing that, the OWA started working like a charm. By
the way, I used Method 2.
Hopefully this helps.
Regards,
George
"craigontour" wrote:
Ed.
I am sorry if you do not like the term "does not work" or "not working", but
if you use a computer enough I would have thought you could tell the
difference between a software application working and not working. If you can
suggest a more accurate term then I would happily use it.
Anyway, answers below...
What happens when they no longer work as described?In the case of Entourage the user's InBox says "Not connected".
What does the page say?For Webmail the browser displays the message "Cannot connect to the Server",
just as if it cannot find the page.
What exactly isn't working?As already stated, Entourage cannot connect to Exchange to send/receive
email - does not work by the definition - and browser cannot display
Web-based mail.
Are there any messages?This morning when it showed the same symptoms yet again I logged in and saw
this message for the first time:
"IIS Worker Process encountered a problem and needed to close".
Examination of the error report revealed:
"Error signature: szAppName: w3wp.exe
szAppVer: 6.0.3790.1830
szModName: davex.dll
szModVer: 6.5.7638.1"
Exchange continues to be the bane of my life right now.
Regards
- References:
- Re: OWA Access stops / Outlook ok
- From: Ed Crowley [MVP]
- Re: OWA Access stops / Outlook ok
- Prev by Date: Re: Exchange Server 2003 Standard- Event ID 447 Database Corruptio
- Next by Date: Re: Exchange Clusters
- Previous by thread: Re: OWA Access stops / Outlook ok
- Next by thread: Re: OWA Access stops / Outlook ok
- Index(es):
Relevant Pages
|