Outlook Web Access (OWA) 2003 displays “Loading…” when users login

This patch Tuesday after reboots we had users trying to login to OWA on our Exchange 2003 servers. They would authenticate fine and see their folder list but could not see the contents of their inbox or interact in anyway with the OWA interface.

Users that chose the ‘Basic’ OWA interface could see their e-mail but certain things wouldn’t work like sending e-mails.

Some quick Googling turned up this article: http://support.microsoft.com/?kbid=280823

Which I followed but found no resolution to my problem.

After digging through the IIS log files on our Front-end Exchange server did I find the cause of the problem:

Every time IIS tried to serve up a JavaScript (.js) file a 404.3 event would be logged.

According to Microsoft 404.3 is an error with MIME Types in IIS. More information can be found here: http://support.microsoft.com/kb/942032

In the end the fix was:

  1. Login to our Exchange Front-end Server
  2. Open the IIS MMC
  3. Right click on the server name in the IIS MMC and choose ‘Properties’
  4. Click ‘MIME Types’
  5. Click ‘New’
  6. Enter the following information:
    Extension: .js
    MIME Type: application/x-javascript
  7. Click ‘Ok’
  8. Click ‘Ok’
  9. Click ‘Apply’ and ‘Ok’
  10. Restart IIS either via the Services MMC or by running ‘iisrestart’ from command prompt.



How to remove old NICs in CentOS 5 or 6

I did a V2V conversion of a CentOS 6 machine from Hyper-V to vSphere.

After the migration I was left with a legacy NIC that would throw up a warning when ever I tried to vMotion the CentOS 6 VM. It didn’t prevent me from moving the machine around our cluster but it was an annoyance.

To solve this problem I did the following:

1. From vCenter I added a new VMXNET 3 NIC to the VM and removed the legacy NIC

2. I then logged in to the virtual machine using the vCenter console and deleted the following:
/etc/udev/rules.d/70-persistent-net.rules (CentOS 6 only)

3. I reboot the VM and then connected back into it using the vCenter console and ran ‘system-config-network’ and created a new eth0 device, assigned the proper IP to it and saved my changes

4. A quick ‘service network restart’ and the system was back up with just the new NIC