× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



We recently installed the client version of Symantec AntiVirus 9.0. Three of our Dell XP machines had problems with the installation (they were running Norton 2003 which had to be removed first, while all the other machines with Norton 2002 had successful installations). After the installation, on all three of these machines, running the Windows Search or using Windows Update would result in a blank screen. Also JavaScript code would no longer work (various browsers). The Media Player would also not work.

I ran both Ad-Aware and Spy-Bot on all the machines before the client installation and removed all objects found. After the successful installation and updating of definition files, I manually scanned for viruses and found none. I ran Ad-Aware and Spy-Bot again but the machines were clean.

I Googled and <http://leovilletownsquare.com/ubbthreads/showflat.php?Cat=0&Number=623181&an=&page=0> appeared to have the answer - download and run Windows Script 5.6. That solved the problem on two of the machines. On the third machine, when I sign on as administrator, everything works fine. When the user signs on as administrator (yes, we have two administrative users - it was set up that way before I arrived), all but the Windows Search works. <http://service1.symantec.com/SUPPORT/nip.nsf/docid/2003020515162736?Open&src=&docid=2001110112423636&nsf=nip.nsf&view=pfdocs&dtype=&prod=&ver=&osv=&osv_lvl <http://service1.symantec.com/SUPPORT/nip.nsf/docid/2003020515162736?Open&src=&docid=2001110112423636&nsf=nip.nsf&view=pfdocs&dtype=&prod=&ver=&osv=&osv_lvl>=> suggested the Windows Search problem “is caused by file corruption of the Microsoft Windows Script (also known as the Script Host). The problem is typically not seen until after you install Norton SystemWorks or another program because the file corruption has no effect on the computer until a program attempts to use the Script Host.” I tried running Windows Script 5.6 again under the other user profile, but received the “Error registering the OCX C:\WINDOWS\system32\jscript.dll” message. <http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/pfdocs/2004021112313539?Open&ExpandSection=1.4%2C1.2%2C1.1%2C1.3 <http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/pfdocs/2004021112313539?Open&ExpandSection=1.4%2C1.2%2C1.1%2C1.3>> also had suggestions for the fix and I tried them without success.

Now for the strange part. After running Windows Script 5.6 again under the other user profile, all profiles have the problems I'm posting about. But, if I run Windows Script 5.6 again under my user profile, only the Window Search for the other user does not work correctly. I've removed and reinstalled Symantec and retried running Windows Script 5.6.

Do you have any other suggestions I could try? The only recent changes to these machines were installing the Symantec client the day of or day before the problems arose, and installing Ad-Aware and Spy-Bot a week or so before the problems were noticed.

Thanks.
Mark Plank


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.