'IExplorer Script Error' when attempting to print from IExplorer

[Navin R. Johnson]

I'm receiving the following error message when trying to print a web
page:

Internet Explorer Script Error
Line 639
Car: 1
Error - Invalid argument
Code - 0
URLC\WINNT\system 32\shdoclc.dll/preview.dlg
do you want to continue running scripts on this page: Yes No


It doesn't matter whether I click 'Yes' or 'No'. It still won't print.

This started happening after NAV found a virus called W32.Randex.gen in
a file called Winupdate32.exe. NAV couldn't delete it so I went into
Safe Mode and deleted it myself, and also the reference to the file in
my registry. That's when the print problem showed up. The system is
running W2K Pro and I can print from Word and other apps without a
problem. I also get the same error when printing from Outlook Express.

I did a search on the error and didn't really find anything definitive
to try. I did try disabling third-party browser extensions but it didn't
help. As I see it, my other options are: deleting cookies, deleting
temporary Internet files, reloading IExplorer, reloading the printer
driver, runing a Spyware removal program, and lastly reloading W2K.

Any guidance on this issue would be greatly appreciated.

TIA,
Navin R. Johnson




"Very funny Scottie...... Now beam down my clothes!"

 

[roger]

Hi,

Go to IE > Tools > Internet Options > Advanced

Uncheck: Enable third-party browser extensions


If that works, you need to check for strange BHOs
BHODemon
http://www.definitivesolutions.com/bhodemon.htm

Good luck

 

[Navin R. Johnson]

Hi,

Go to IE > Tools > Internet Options > Advanced

Uncheck: Enable third-party browser extensions


If that works, you need to check for strange BHOs
BHODemon
http://www.definitivesolutions.com/bhodemon.htm

Good luck

First, thanx for the response. As I said in my original post, "I did try
disabling third-party browser extensions but it didn't help." Also, I
don't let any 'Browser Helpers' infest my system so that's definitely
not the cause..... FYI, I did already fix the problem by reloading
IExplorer. Worked like a charm.

NRJ