Re: OWA 2003 only works in Basic from some clients
From: Tristan (Tristan_at_nospam.com)
Date: 02/27/04
- Next message: Tristan: "DNS error"
- Previous message: MCSE_in_PA: "RE: Vanished"
- In reply to: Damian N Leibaschoff [MSFT]: "Re: OWA 2003 only works in Basic from some clients"
- Next in thread: Damian N Leibaschoff [MSFT]: "Re: OWA 2003 only works in Basic from some clients"
- Reply: Damian N Leibaschoff [MSFT]: "Re: OWA 2003 only works in Basic from some clients"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 27 Feb 2004 14:15:13 +1300
What is OfficeScan? Is it a third party product?
I'm having a similar problem, installed GZIP hotfix, cleaned cache on Server
and client. Still getting scripting errors when loading, but not if I log
in using Basic mode.
Thanks
Tristan
"Damian N Leibaschoff [MSFT]" <damianl@online.microsoft.com> wrote in
message news:uXQxisL$DHA.4060@TK2MSFTNGP10.phx.gbl...
> Hi,
> A number of things to check:
> First, make sure you have installed the GZIP hotfix for IIS 6, you will
also
> need to clean up a number a number of folders and the IE cache.
> Also check to see if Officescan is installed in the default web site. Let
me
> know if it is since we will have top remove a MIME entry done by the
> software.
>
> The instructions and link to the hotfix for IIS 6 are here:
>
> 831464 FIX: IIS 6.0 Compression Corruption Causes Access Violations
> http://support.microsoft.com/?id=831464
>
> In regards to OfficeScan:
>
> The MIME type added is for ".*" and defines it as Octet/Stream.
>
> To remove this custom MIME type:
> Open the Default Web Site properties, HTTP Headers tab,
> MIME Types and to remove the entry. The same should be done on all the
> virtual directories, but the OfficeScan one.
>
> After that, IISRESET should be run and the IE cache (temp files) should be
> deleted before using OWA again.
>
> Regards,
> Damian
>
> --
> Damian N. Leibaschoff, MS IST, MCSE
> Microsoft Corporation
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
>
> When responding to posts, please "Reply to Group" via
>
> your newsreader so that others may learn and benefit
>
> from your issue.
>
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Rich Farkas" <anonymous@discussions.microsoft.com> wrote in message
> news:2e0001c3fcb3$b45daf50$a101280a@phx.gbl...
> > I upgraded from SBS 2000 to SBS 2003. On some remote
> > clients and on at least one local client, OWA only works
> > in Basic mode. On other clients, it works fine in
> > Premium mode. For example, if I access OWA from one
> > computer with WIN XP Professional across an internet
> > connection to the SBS system, I can get it to work in
> > Premium mode. On another Computer, also running XP
> > Professional, I cannot get it to load in Premium mode. I
> > get the message "loading" and it never loads. But on
> > that same computer than cannot load the page in Premium
> > mode, I can get the page to load just fine in Basic
> > mode. I have found several references to this problem
> > but none that offered a real solution. Microsoft seems
> > to be mute about it. There seem to be enough people
> > reporting exactly the same issue. Anyone with ideas out
> > there?
>
>
- Next message: Tristan: "DNS error"
- Previous message: MCSE_in_PA: "RE: Vanished"
- In reply to: Damian N Leibaschoff [MSFT]: "Re: OWA 2003 only works in Basic from some clients"
- Next in thread: Damian N Leibaschoff [MSFT]: "Re: OWA 2003 only works in Basic from some clients"
- Reply: Damian N Leibaschoff [MSFT]: "Re: OWA 2003 only works in Basic from some clients"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
