Friday, August 27, 2010

OWA broken after installing Rollup 9 for Exchange 2007 SP1

PROBLEM: After installing Rollup 9 for Exchange 2007 SP1 many parts of OWA are broken.

Here is list of problems I know of so far.

1. Basic view(Outlook Web Access Light): when users will double click on the message they cannot open it. There will be error message thrown by the browser.

Line: 63
Char: 1
Error: Object expected
Code: 0
URL: https//ExchangeServer/owa

2. Basic View (Outlook Web Access Light): Logoff button do not work in OWA. There will be error message thrown by the browser.

Line: 39
Char: 1
Error: Object expected
Code: 0
URL: https//ExchangeServer/owa

3. Premium view: Preview of the message body would not work. The page cannot be found will be displayed.

4. Graphics not working in OWA, all graphics replaced with red cross (X).

CAUSE: ROLLUP 9 - do not come with all the files for OWA folders just the updated files.

FIX: Since rollup executable only installs updated files and OWA virtual directory points to new folder, it would have problems due to missing files from the folders. You will have to copy missing files from folders that were created in past. Look into the following folders and make sure it has all the files in it:

C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\8.1.393.1\scripts\premium
C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\8.1.393.1\scripts\basic
C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\8.1.393.1\themes\base

Exchange 2007 SP1 OWA do not display images after installing Rollup 9

PROBLEM After Exchange 2007 SP1 Rollup 9 is installed users will not see any graphics while accessing emails from OWA.

CAUSETheme file are missing from the "C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\8.1.393.1\themes\base" directory.

SOLUTION: Copy the files from the earlier install folder e.g. from "C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\\themes\base"

Saturday, June 26, 2010

Windows XP/2003 lost Admin/Hidden shares for SAN attached drives

Problem Description: When SAN storage drives are introduced to Windows machine which could be a windows XP/ Windows 2003 Server /Windows 2008 Server, in some cases admins might find that newly introduced drives are missing admin shares e.g. D$, E$ F$....

Cause: It is believed that some times due to some environment issues drives might not be found by operating system on startup time.

Fix: One should be looking to fix the underlaying cause then on how to get these shares back but still I would mention how to get these back after machine is already rebooted.

To get the admin shares re-created by MS Windows please restart "Server" service from services.msc (services applet)

Server service has another service called Computer Browser that is dependent on it. In case you are using command line e.g. "net stop server" please remember to start back Computer Browser service back again.