OWA display problem after applying patch KB924334

Good evening!

We've recently started to implement windows 7 on any new machines we purchase. Problem is that our webmail hosted with MS exchange 2003 (sp2) has issues with a combination of windows 7/vista and IE7 or 8. We were unable to compose emails before, as it would simply appear with a red x. where your text editing field was supposed to be.

I applied KB924334 hotfix on one of our front end servers (we have two) in order to test it. Of course, the result was that we could finally see the text editing field, provided the new S/MIME was downloaded and installed. However, IE would then instantly crash when you attempted to send an email. The recommendation from another website was to apply kb924334 on the back end server as well. Immediately after this was done, OWA now appears with graphical glitches. The buttons aren't functional, both in basic and premium mode.

I mentioned earlier that we had two front end servers. The second one I hadn't touched, and it seems to work perfectly fine, only because I moved the latest exchweb folder version from the back end server to it. The same attempt to the defective front end server didn't bare the same results, sadly.

I've also tried restarting the app pools in IIS management, as well as the IIS service itself and its dependencies. None of this of course, has worked.

What I find odd is that this all started when I installed kb924334 on the back end server, while an installation of the same hotfix did nothing when installed on the front end server only.

As a result of all this, I've removed the hotfix on both servers and all is well. Google doesn't have much on this issue except that the reason windows7/vista with ie 7/8 doesn't work for my current setting is because DHTML is no longer used for OWA.

Any ideas would be much appreciated.
jqhhitAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mohammedkasim21Commented:
Check the Build Version of "C:\Program Files\Exchsvr\Exchweb " of both FE and BE, also make sure that Either both FE and BE should have same build numbers or FE can have higher than BE.
0
oztrodamusCommented:
Hi Jghhit,

The problem isn't because MS removed DHTML. It's because it extracted the funtionality contained in the dhtmled.ocx file from being an Active X control to being an IFrame. I believe all you need to do is install the update Kb911829 on both your back-end and front-end Exchange servers, and your problem should be resolved.

http://support.microsoft.com/kb/911829

Cheers
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Shreedhar EtteCommented:
Hi,

Run SBS 2003 Best Practise Analyser and fix the errors reported.

Also Run Exchange 2003 Best Practise Analyse and fix the errors reported.

Hope this helps,
Shree
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

jqhhitAuthor Commented:
mohammedkasim21,

I tried that. All three servers (both FE and the one BE) have the latest version 6.5.7651.60 in the exchweb folder.

oztrodamus,

That may help. I'll have to try either tonight or this weekend depending on my schedule. Thanks.

shreedhar,

I'll probably have to if the above mentioned KB doesn't work.
0
mohammedkasim21Commented:
Is it possible for you to share the latest IIS Log file so that we can analyze.....
0
jqhhitAuthor Commented:
Problem solved!

KB911829 fixed the red "X" issue. I installed it on one of the FE servers, then the BE. Strangely enough, the FE server on which the KB was installed on made OWA mess up again, while the other FE server (one that didn't have the KB installed) was fine. Including the ability to see the email body text field again.

However, the messed up OWA display ended up being a permissions issue with the latest folder (6.5.7651.60) in exchweb. The security properties didn't have "inherited permissions" enabled and therefore wasn't accessible to users other than administrators.

Thanks for the help!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.