• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 685
  • Last Modified:

Problem with OWA on Exch 2003 - red x in body of new message

I just setup a new server and migrated 35 users to it. It is windows server 2003 r2 sp2 with Exchange 2003.

Now when you login to OWA and start a new email you get a red x where the body of the message used to be.

I found an MS kb that says go to options and install the S/Mime plug-in from OWA - I did that and the red x goes away but now my browser crashes every time I send a message with OWA. I found out that that is a bug with the s/mime plugin and that there is an Exchange patch to fix it. I have installed the patch from MS on the server but now I have to reboot the production server to apply it and have not done that yet.

Is there someway to fix this issue without rebooting the server? So far I have not had any of the users install the s/mime plugin from OWA except for me.

thanks,
Bobby
0
ob1_
Asked:
ob1_
  • 2
  • 2
  • 2
  • +2
4 Solutions
 
James MurrellProduct SpecialistCommented:
As far as I am aware you have to reboot the server....
0
 
ob1_Author Commented:
Ok - also then I would need to direct all the end users to install the s/mime plug-in? I am wondering why this is because I have never had to install this plug-in when using OWA on any server in the past.
0
 
James MurrellProduct SpecialistCommented:
sorry unsure about that part,  i think not
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
dr00r00Commented:
You can try restarting IIS. I had the luxury of having more than one server with a DNS failover so I rebooted when I installed that. The good news is that it will fix our problem.
0
 
MesthaCommented:
The S/MIME plugin thing is not really a solution. You shouldn't need to do that at all.
I have never installed S/MIME on any of my or my client machines.

Was the server fully patched? That includes post SP2 updates. Have you run the Exchange best practises tool against the system?

A new system should work straight out of the box - red X normally means one of the virtual directories isn't configured correctly.

Simon.
0
 
Narayan_singhCommented:
Are you using S /MIME to get rid of those red x or you are getting those red x after implementing S/MIME .

If you want get rid of red x follwo method 2 of KB 883380 and reset the virtual directory.
check the authentication type as below:

1) Default website : Annonymous and integrated auth   NO SSL
2) Exadmin : Integrated authentication              NO SSL
3) Exchange : Basic and                   SSL Optional
4) Exchweb : Annonymous authentication      NO SSL
5) Microsoft-Server-ActiveSync: Basic authentication    SSL Optional
6) Public : Basic and Integrated authentication           SSL Optional
0
 
ob1_Author Commented:
I thought it was fully patched - this patch that fixed it after a reboot but was not suggested by Windows Update so I didn't realize I had to install it until there was a problem.
Are there other patches like that that I should know about for a new Exchange install?
Thanks!!
0
 
MesthaCommented:
Windows Update doesn't cover Exchange. You need to switch to Microsoft Update for other products.
The Exchange Best Practises tool would have flagged it up as well.

Simon.
0

Featured Post

Take Control of Web Hosting For Your Clients

As a web developer or IT admin, successfully managing multiple client accounts can be challenging. In this webinar we will look at the tools provided by Media Temple and Plesk to make managing your clients’ hosting easier.

  • 2
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now