Have you tried looking at traces between the front-end and back-end systems, and between the client and the front-end server? Also, if you compare them to a working OWA session (i.e., client directly to the back end server) do you see any differences when the failure occurs (you should)? None of this is enlightening stuff, just basic troubleshooting, but that's where I would go next. Oh, and of course, what do the event logs on all systems show when the failure happens, especially on the front-end server? Any events worth noting? There does appear to be an issue with IIS 6.0 compression, and a fix is posted on support.microsoft.com, have you taken a look at that to see if it applies? Finally, your next steps really depend on how willing you are to spend time troubleshooting - one thing I would try is installing another system as a front-end server, patch it identically, and see if that is working, to verify that it isn't simply some sort of issue on that particular system (I suspect it is or there would be information all over the place about this issue). If that works, you are probably looking at rebuilding the production front-end server. Alternately, you can always call PSS and see if they have any internal fixes for this issue that don't appear on the Microsoft web site yet. Or have them walk you through troubleshooting further. And my apologies for the delayed reply - I was tied up yesterday! On 1/16/05 5:22 AM, "Mustafa Cicek" <mbcicek@xxxxxxxxx> wrote: > http://www.MSExchange.org/ > > Hi Rick, > I can log on also successfully with "basic" on OWA browser. I can also > read any messages and it doesn't appear any "LOADING..." message on > browser. > > BUT: if I try to create a new object (for example creeate new mail), the I > have again the error on browser "obeject expected". It is definetly > JavaScript problem in OWA. > > I have the same results if I start OWA on the front-end machine. > I have applied all patches & hotfixes on all internal servers (back-end, > front-end, active directory). > I have no problem if I log on the back-end exchange by using OWA. The > problem is on front-end. > > Any other ideas??? > Plase response me.. > > Thanks > Mustafa > > ------------------------------------------------------ > List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist > Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp > Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ > ------------------------------------------------------ > Other Internet Software Marketing Sites: > World of Windows Networking: http://www.windowsnetworking.com > Leading Network Software Directory: http://www.serverfiles.com > No.1 ISA Server Resource Site: http://www.isaserver.org > Windows Security Resource Site: http://www.windowsecurity.com/ > Network Security Library: http://www.secinf.net/ > Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com > ------------------------------------------------------ > You are currently subscribed to this MSEXchange.org Discussion List as: > rickb@xxxxxxxxxxx > To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist > Report abuse to listadmin@xxxxxxxxxxxxxx