JavaScript Error

[Guest]

Hi, I'm encountering an error that is driving me crazy!
My work email is "netscape messenger" based but can be browed with either
IE or Netscape (go to: http://mail.uth.tmc.edu/ to see what i mean). I can
log on and browse my incoming mail but for some reason I can not compose or
reply mail. This happens ONLY with my home PC and not any other PC. In other
PCs, a window pops-up to write the new mail.
No error message appear after I click the compose (or reply) button even I
wait for a while, however when I click logout an error message pops-up before
i am logged out. The error message reads as follows:
" JavaScript Error
http://oac40.hsc.uth.tmc.edu/.........(long address), Line 211
Object doesn't support this property or method"

I tried a lot of things including changing the Java settings in the advanced
options of IE and updating my IE by adding SP1. I have IE 6.0 and windows XP
and I have installed SP2.
I also tried looking up multiple Java error database and other support
groups on the web but nothing helped!
and by the way the exact same error occur when I use Netscape navigator.

Do you have any ideas? Thanks in advance!

 

[Hans Le Roy]

Hi Firas:

It might help to reinstall Windows Scripting Host from
www.microsoft.com/scripting.

Kind regards

Hans Le Roy
MS MVP Win/IE-OE

 

[Guest]

Hi Hans,

I installed the MW Script 5.6
Nothing changed and the problem persisted.

Thanks for the try but any other ideas!

Firas

 

[Robert Aldwinckle]

No error message appear after I click the compose (or reply) button even I

wait for a while, however when I click logout an error message pops-up before
i am logged out.

Why are you doing that? Have you tried Refresh instead?

Try pressing Ctrl-F5 (to ensure you aren't using some old version
of the scripts that a caching server knows about.)

Can you use https: instead of http: for the protocol?
(If the problem is caching but the caching is being done by a caching
server sometimes even Ctrl-F5 can't bypass it and the only way
to avoid it is to change the request.)

Do you have an account with an alternate ISP you could try?
(Another way of bypassing a problem assumed to be due
to your connectivity path: change the path.)


The validity of the ideas really depends on the implementation
of the web application. You could learn more about that by taking
a packet trace of the problem.

Since it clearly isn't a public site you are having trouble with
I suspect if you need more help you are going to have to ask
for support there. The fact that you have the problem with
more than just IE should make that more possible.


Good luck

Robert Aldwinckle