Print - Solving an IE 6.0 Printing Problem

Ever since I upgraded to Microsoft Internet Explorer (IE) 6.0, I've had trouble printing from a browser window. I usually get an IE Script Error message that states An error has occurred in the script on this page. Line: 508, Char: 1, Error: Permission denied, Code: 0, URL:res://c:\winnt\system32\shdoclc.dll/preview.dlg. Do you want to continue running scripts on this page? The message prompts me to click Yes or No, but whichever button I choose, I still can't print. I never had this problem with IE 5.x. Do you have any idea what's wrong?

I've run across this problem on more than one occasion (usually with IE 6.0, although I have seen it occur with IE 5.x as well). You can try several things to resolve the problem. First, if you have more than one printer installed, determine whether the problem is printer-specific—that is, if you get the mystery message only when a particular printer is set as the default printer. If so, download and install the most recent printer driver from your printer manufacturer—even if the driver isn't signed. I've found that even many Microsoft-provided signed drivers cause the problem you describe.

If the problem isn't printer-specific or if a new driver doesn't help, try repairing IE. Open the Control Panel Add/Remove Programs applet, select Microsoft Inter-net Explorer 6 and Internet Tools, click Change/Remove (on your system, the option might be Add/Remove), then select the Repair Internet Explorer option. If for some reason the repair option is unavailable, you can access it manually. To do so, click Start, Run from the toolbar and enter the following case-sensitive command:

rundll32 setupwbv.dll,IE5Maintenance

I hate to say it, but my experience with IE 6.0 thus far has been poor. The product seems awfully rough around the edges and seems to be more prone to crashes, printing problems, and other odd behaviors than IE 5.x. Hopefully, Microsoft will have addressed some (or all) of IE 6.0's problems by the time you read this answer.

i had the same problem with my own website (http://www.proxeed.de) and solved it in the following way: i commented and uncommented everything until i found the error: internet explorer doesn't like objects with the name 'all'. i had an 'img src'-tag in my website with the name="all". after ich renamed it to 'allx' the printing process passed without any errors! same thing with forms that are named 'all'. there are surely more tags that must not be named 'all' but i didn't figure them out yet.

WHat????????????????????? The advice in this article looks haphazard. There are some KB articles on this. And there are a lot of people with this problem and the KB articles manage to miss the point.

FYI Below is a link to MS Technet highlighting this issue. Microsoft Knowledge Base Article - 303360 http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B303360

Apparently a permissions issue. Gave the user local admin rights and it solved the problem. Not the right solution but it works in a pinch.... will figure out why in future.

I have tried both of your suggestions reinstalling my printer drive and repairing internet, but nothing has worked. I am getting the same IE script error message. I have cut and paste into Wordpad and it prints then, but when I try to print my emails or off the internet; that's when I get the error message. Any other suggestions? The last message I get is: URL:res://C:\WINDOWS\SYSTEM\SHDOCLC.DLL/preview.dlg

I get the same problem when printing from IE6. CRASH-O-RAMA! It then procedes to send an error report to Microsoft. You would think by now after receiving thousands of reports (and this is from only myself!), that they would have a fix by now!!

Uncheck "Enable 3rd party party browser extensions" from Tools -> Internet Options -> Advanced Tab and then restart Internet Explorer and Outlook Express. Alternatively, you can use the far less buggy Mozilla, if you don't mind installing your own browser.

U. Kassner's "allx" fix did it for me! Great help! I could have searched for ages I guess ... Thanks!

I am getting that infamous error message 508. I got it when I put up IE6.0. I have now gone back to IE5.5 but am still getting the problem.I have tried to repair it but to no success. How do I give local user admin rights? I'll give anything a try. Thanks for your help.

I finally fixed this problem after reading a TON of useless articles on this. Two things I did finally fixed it. Logging in as local admin(although the user was admin enabled it DID NOT WORK, i had to login as true administrator), I replaced the rhaenh.dll file AND reinstalled the "NO LIABILITY ACCEPTED.." cert in the mmc. Do a search for EVENT ID 64033 to find the walkthroughs to doing that. I had several problems including the printing one that ALL occured at the same time. Fixing both of those files corrected ALL of the errors i was getting, including NetLogon not starting and Windows Update no longer connecting. I dont know what is up but only 1 machine out of at least 35 here completely freaked out after a round of MS updates on 4/4/2003. I had SO much working on this machine, a complete reload would have been a nightmare. I am glad I found the sources of the issues. I am now afraid to SP update this machine any further, it must be a specific problem to hardware/software is my best guess. MS doesn't seem to know the problem is widespread, I am seeing quite a few people with the same errors though.

Delgx260 Solution is only for: Microsoft Internet Explorer 5.5 for Windows Millennium Edition Microsoft Internet Explorer 5.5 for Windows 98 Second Edition SP 1 Microsoft Internet Explorer 5.5 for Windows 98 SP 1 Microsoft Internet Explorer 5.5 for Windows 95 SP 1 Microsoft Internet Explorer 5.5 for Windows 2000 SP 1 Not for Windows Xp

I have read the entire article, and this is exactly what I am going through. I am not computer literate at all, so I don't dare fix it by myself. Need step by step directions. Excellent article

Thanks Ryan !!!....We had that problem wide spread all over our Southeastern offices and Ryan Grange's solution fixed 623 DeskTops.... Ryan are you married?

Happily married March, 2004, Alice. You may want to also install Spybot S&D on those 623 desktops. Seems some malware out there will re-check the box for your users since they couldn't possibly want to block out their advertising. Spybot 1.3 is out and can monitor the system for registry changes, getting a user's okay before allowing them (with an option to remember the decision as well).

Ryan's fixed seemed to work for know, but I did repair IE as well. Thanks for info everyone.

Ryan was right, disableing the 3rd party browser extentions did fix the printing problem, however, by disabling 3rd party party browser extensions, Browser Helper Objects (BHO's) also get disabled, and such things as Google Toolbar will no longer run. After becoming aware of this problem I decided to use HijackThis to discover what BHO's were actually installed on the machine in question. The idea being that perhaps a BHO might be responsible for the original printing issue. HijackThis turned up a BHO for Newdotnet 6.9. Luckily uninstalling this from Control Panels/Add Remove Software completely removed this version of Newdotnet. (In the past, Newdotnet was notorious for being one of the hardest Spyware programs to get rid of). After it's removal and re-checking "Enable 3rd party party browser extensions" from Tools -> Internet Options -> Advanced Tab, and a reboot of the computer, I tested the printing issue and found that it was still corrected. So in conclusion, if Unchecking "Enable 3rd party party browser extensions" does fix the problem, use HijackThis to locate any un-reputable BHO's such as Newdotnet, and remove them. This may well cure the problem without disabling all programs that utilize BHO's like Google Toolbar and Adobe Acrobat.

for me the message was in Dutch but it came down to me editing my frames script for it to work. my message (translated ofcourse): An error has occurred in the script on this page Line: 1387 Sign: 1 Error: Object required Code: 0 URL: res://C:\WINDOWS\System32\shdolc.dll/preview.dlg Since this happened on only my documentation system (worked everywhere but there) lead me to believe there was an error in my primary frames script. Closer inspection thereof revealed an easily missed "missing tag". Inserting the missing close tag did the trick. Good luck