Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Internet Explorer Script Error in NAV

Dec 18, 2006 7:12PM PST

In Norton AntiVirus 2006 - Activity Log/Log Viewer/Worm Protection/Connections,Activities,Worm Detection,System and Alerts all report - Internet Explorer Script Error. - An error has occurred in the script on this page. Line: 2, Char: 1, Error: Invalid Character, Code: 0, URL: about;blank. Do you want to continue running scripts on this page?

How do I resolve this please? I did not have this problem a week ago but since then I have installed IE7. Is that someting to do with it?

I contacted Symantec support and I was told to download Windows Script 5.6 for XP and that would solve the problem. It hasn't and I am not surprised as I suspect that this might be a registry job and I don't fancy playing about in the registry. Any help would be appreciated.

Discussion is locked

- Collapse -
script error
Dec 19, 2006 2:46AM PST

This is a know issue,click HERE and scroll down to PROBLEM #2

If you want to stop these messages:From IE>tools>internet options>advanced>check "disable script debugging" & uncheck display a notification about every script error.

Tom

- Collapse -
In addition...
Dec 19, 2006 3:21AM PST

Norton software is not yet supported with IE7. Script errors are being experienced by users, so you may have to choose between Norton,and IE7.

In this LINK,click Troubleshooting Internet Explorer after installation scroll down to bottom of page.

Tom

- Collapse -
Thanks Tom, I think it is best just to accept the
Dec 19, 2006 7:32PM PST

errors and leave things as they are. Presumably this does no affect the security of NAV and the problem will resolve itself when Norton get their act together?

Why didn't Symantec tell me this when they replied to my query, you would think that they would have understood the problem.

- Collapse -
Reinstall IE7 is what Symantec is telling me to do now in
Dec 19, 2006 7:49PM PST

response to my contact with them when I told them that the new script file solution didn't work. Presumably a reinstall will not work. Do you agree? I really don't want to try this!

- Collapse -
Can't say for sure...
Dec 19, 2006 8:49PM PST

This is what it said in the link i provided.

"Norton software is not yet supported with IE7. Script errors are being experienced by users, so you may have to choose between Norton,and IE7".

A lot of people use FF and just keep IE for updating windows,including myself.Why put your self through this with IE,why not just use FF.

Tom

- Collapse -
(NT) I may go back to IE6, meanwhile many thanks for your help.
Dec 19, 2006 9:48PM PST
- Collapse -
(NT) Welcome,thanx for posting back
Dec 19, 2006 9:56PM PST
- Collapse -
Tom, in my reply to Symantec I included your link.
Dec 20, 2006 7:54PM PST

I am copying below their reply:

"Welcome back to Symantec Authorized Technical Support.

Please allow me to apologize for any difficulties you have encountered due to this issue.

Peter, due to scripts being used in IE7 are different then the one supported by Norton programs, you have been facing this issue.

Thank you for bringing to our notice, we appreciate your patronage. I will forward your comments to our technical team."

I can't believe that they don't know about this. I have asked them to let me know if the script error affects the way Norton protects my computer fron viruses.

- Collapse -
(NT) Thanx for sharing this
Dec 21, 2006 4:02AM PST
- Collapse -
2005 / 2006 scripting errors
Jan 4, 2007 4:57AM PST

I contacted Symantec almost a month ago and got the same answer... change back to IE6 for Norton AV to work properly again. Considering I'd have to revert dozens of PCs here at work that's out. Its amazing more people haven't complained. If you use the Internet Worm protection in NAV 2005 and you need to open a port you're only option is to disable the entire NAV worm protection as the script error prevents any modifications. The scripting error also affects some of NAV 2006. Considering our company paid for the subsription updates on both 2005 + 2006 versions we should have a properly functioning product an not a 'BRUSH OFF' from Symantec. Looks like we'll be changing AV programs...

- Collapse -
Thank you teb863. Symantec assure me that the script error
Jan 4, 2007 6:50PM PST

will not affect the protection provided by NAV. Unless you know different of course. I like IE7 and don't want to go back to IE6. I have NAV 2006 and what annoyed me was all the suggestions Symantec made to resolve the problem when none of them worked. Their support staff should have known about this. It seems from looking around the internet that all they have to do is issue an update. Why don't they? GRRRR! When my sub is up for renewal I am thinking of switching to AVG if that is what it is called but I don't know much about it and I think there are problems removing NAV from the computer.

I don't understand your comment about opening a port for worm protection. Is there something I should be doing here?

- Collapse -
NAV port blockage
Jan 5, 2007 3:54AM PST

There are some instances when 2005 NAV's Internet Worm Protection (which is usually set up as a firewall instead of XPs firewall) will block a valid port being used by an aplication. Dreamweaver is an example that comes to mind. One of the Trojan rules blocks a port Dreamweaver uses to transfer files (ftp) on occassion. A work around is to disable that individual trojan rule. Since NAV is screwed up and unmodifiable the only other option is to disable ALL trojan rules (hence no PC firewall). Also, using a router/firewall, I route things to specific ports on different PCs. In so doing NAV blocks those ports thinking its an attack. When working properly you can 'open' the port and allow the data transfer needed by writing a 'General Rules' exception. This is useful for multiple VPNs. The scripting error prevents ANY modification to the generic settings Symantec provides. Hope this helps.

- Collapse -
(NT) teb863: Many thanks. I think it is up to Symantec now.
Jan 5, 2007 4:25AM PST