Issue with OWA compose and replies...

[Clay Cleverly]

On a couple of clients in our Outlook 2003 environment, using OWA
allows people to read messages, but replying or composing a new
message results in the textarea where the body of the message is to be
typed, shows only a broken link red X. One is on Windows XP SP1, the
other SP2. On the SP2 clients, I have run SFC, reinstalled SP2,
repaired, and then removed office 2k3, removed and reinstalled Java
(Sun's 1.4.2_5). In IE 6, this is a problem, also have the same
problem with creating a signature for use in OWA. In Firefox, there's
no problem, it works fine, but IE 6 it's no go. This issue is only
client-side, different mchines work properly, these two clients have
this problem, but every user account on the machines has the problem,
so it's not a profile problem. Caches have been cleaned out, set all
settings to default, cookies removed. Any ideas/suggestions?

Thanks for any help!

 

[Milly Staples [MVP - Outlook]]

Ask in an Exchange group - OWA is a part of Exchange, not Outlook.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.

After furious head scratching, Clay Cleverly asked:

| On a couple of clients in our Outlook 2003 environment, using OWA
| allows people to read messages, but replying or composing a new
| message results in the textarea where the body of the message is to be
| typed, shows only a broken link red X. One is on Windows XP SP1, the
| other SP2. On the SP2 clients, I have run SFC, reinstalled SP2,
| repaired, and then removed office 2k3, removed and reinstalled Java
| (Sun's 1.4.2_5). In IE 6, this is a problem, also have the same
| problem with creating a signature for use in OWA. In Firefox, there's
| no problem, it works fine, but IE 6 it's no go. This issue is only
| client-side, different mchines work properly, these two clients have
| this problem, but every user account on the machines has the problem,
| so it's not a profile problem. Caches have been cleaned out, set all
| settings to default, cookies removed. Any ideas/suggestions?
|
| Thanks for any help!