Can't Print/Print Preview/Page Setup from IE after 6/16/2006 updat

I am getting the following message if I try to print/print preview from IE:

==========================================
An error has occured in the script on this page (!)
Line: 639
Char: 1
Error: Invalid Argument
Code: 0
URL: res://C:\Windows\system32\shdoclc.dll\preview.dlg

Do you wish to continue running scripts on this page?
[Yes] [No]
===========================================

Here is the list of updates that were installed:

Cumulative Security Update for Internet Explorer for Windows XP (KB916281)
Windows Malicious Software Removal Tool - June 2006 (KB890830)
Security Update for Windows Media Player 9 (KB917734)
Security Update for Word 2002 (KB917335)
Security Update for Windows XP (KB918439)
Security Update for Windows XP (KB917344)
Security Update for Windows XP (KB917953)
Security Update for PowerPoint 2002 (KB916519)
Security Update for Windows XP (KB911280)
Cumulative Security Update for Internet Explorer for Windows XP (KB916281)
Security Update for Windows XP (KB914389)
------------------------------

If I attempt to Page Setup, I get the following:

=========================================
(!) An error has occured raising the Page Setup Dialog.

Error: 19
Object does not support this property or method.
=========================================

I can print/preview from other applications...

If it matters, I have Earthlink Total Access installed and was using the
Popup blocker that comes with that. The Popup blocker broke as well and I
have had to disable it.

Zathras,

Try this, go to Start, Run, type in ( or copy and paste )

regsvr32 iepeers.dll

Click OK ( NOTE the space between the 2 and the i )
If that doesn't resolve the issue, go to Start, Run, type in

regsvr32 ole32.dll
Click OK

MowGreen [MVP 2003-2006]
===============
*-343-* FDNY
Never Forgotten
===============


Zathras wrote:

> I am getting the following message if I try to print/print preview from IE:
>
> ==========================================
> An error has occured in the script on this page (!)
> Line: 639
> Char: 1
> Error: Invalid Argument
> Code: 0
> URL: res://C:\Windows\system32\shdoclc.dll\preview.dlg
>
> Do you wish to continue running scripts on this page?
> [Yes] [No]
> ===========================================
>
> Here is the list of updates that were installed:
>
> Cumulative Security Update for Internet Explorer for Windows XP (KB916281)
> Windows Malicious Software Removal Tool - June 2006 (KB890830)
> Security Update for Windows Media Player 9 (KB917734)
> Security Update for Word 2002 (KB917335)
> Security Update for Windows XP (KB918439)
> Security Update for Windows XP (KB917344)
> Security Update for Windows XP (KB917953)
> Security Update for PowerPoint 2002 (KB916519)
> Security Update for Windows XP (KB911280)
> Cumulative Security Update for Internet Explorer for Windows XP (KB916281)
> Security Update for Windows XP (KB914389)
> ------------------------------
>
> If I attempt to Page Setup, I get the following:
>
> =========================================
> (!) An error has occured raising the Page Setup Dialog.
>
> Error: 19
> Object does not support this property or method.
> =========================================
>
> I can print/preview from other applications...
>
> If it matters, I have Earthlink Total Access installed and was using the
> Popup blocker that comes with that. The Popup blocker broke as well and I
> have had to disable it.

Didn't help... Any other ideas any one?

Zathras

"MowGreen [MVP]" wrote:

> Zathras,
>
> Try this, go to Start, Run, type in ( or copy and paste )
>
> regsvr32 iepeers.dll
>
> Click OK ( NOTE the space between the 2 and the i )
> If that doesn't resolve the issue, go to Start, Run, type in
>
> regsvr32 ole32.dll
> Click OK
>
> MowGreen [MVP 2003-2006]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
> Zathras wrote:
>
> > I am getting the following message if I try to print/print preview from IE:
> >
> > ==========================================
> > An error has occured in the script on this page (!)
> > Line: 639
> > Char: 1
> > Error: Invalid Argument
> > Code: 0
> > URL: res://C:\Windows\system32\shdoclc.dll\preview.dlg
> >
> > Do you wish to continue running scripts on this page?
> > [Yes] [No]
> > ===========================================
> >
> > Here is the list of updates that were installed:
> >
> > Cumulative Security Update for Internet Explorer for Windows XP (KB916281)
> > Windows Malicious Software Removal Tool - June 2006 (KB890830)
> > Security Update for Windows Media Player 9 (KB917734)
> > Security Update for Word 2002 (KB917335)
> > Security Update for Windows XP (KB918439)
> > Security Update for Windows XP (KB917344)
> > Security Update for Windows XP (KB917953)
> > Security Update for PowerPoint 2002 (KB916519)
> > Security Update for Windows XP (KB911280)
> > Cumulative Security Update for Internet Explorer for Windows XP (KB916281)
> > Security Update for Windows XP (KB914389)
> > ------------------------------
> >
> > If I attempt to Page Setup, I get the following:
> >
> > =========================================
> > (!) An error has occured raising the Page Setup Dialog.
> >
> > Error: 19
> > Object does not support this property or method.
> > =========================================
> >
> > I can print/preview from other applications...
> >
> > If it matters, I have Earthlink Total Access installed and was using the
> > Popup blocker that comes with that. The Popup blocker broke as well and I
> > have had to disable it.
>

"Zathras" <ZathrasOne2001(AT)Yahoo(DOT)com> wrote in message
news:32BB210D-4C7C-45A0-A9A0-
....
> Didn't help... Any other ideas any one?


To continue on the re-registration tack it would be really useful
if IE Repair had been left in XP. Unfortunately that is usually
not the case. E.g. unless the user installed IE6sp1 before
installing an XP service pack setupwbv.dll will not exist on that OS.

In XPsp2 they tried to provide a substitute with the /rereg command
line switch but unfortunately botched the list of modules and the their
parameters. I have documented a necessary edit if you want to try
that route. Search my posts for reference to ieuinit.inf


However, a simpler more general repair procedure is available here
courtesy of German MVP Kai Schaetzl:

http://iefaq.info/index.php?action=a...=31&artlang=en

That procedure is similar to the old IE Repair (ref. KB194177)
which used to be done at boot time after a (very cursory) verification.
This procedure is not done at boot time and there is no verifcation,
so it is up to the user to ensure that there are no interfering apps
running and to determine that a compatible set of modules are present
to be re-registered at the same time. Obviously a normal user can't
do much about the latter, except hope that everything is consistent
module-wise or perhaps try using sfc /scannow if some discrepancies
are suspected. In any case, I would strongly suggest establishing
minimal operating conditions before trying either procedure.


HTH

Robert Aldwinckle
---

Re-running the last cumulative security patch for IE6 fixed it. Doing the fix
to the .inf file and re-running /rereg did not. Running the security patch
was a little trickier then it should have been because the pop-up blocker was
stuck on, so I could not reapply the patch from the Windows Update history. I
had to find it by KB number in the online technet and run from there.

Thanks!

"Robert Aldwinckle" wrote:

> "Zathras" <ZathrasOne2001(AT)Yahoo(DOT)com> wrote in message
> news:32BB210D-4C7C-45A0-A9A0-
> ....
> > Didn't help... Any other ideas any one?
>
>
> To continue on the re-registration tack it would be really useful
> if IE Repair had been left in XP. Unfortunately that is usually
> not the case. E.g. unless the user installed IE6sp1 before
> installing an XP service pack setupwbv.dll will not exist on that OS.
>
> In XPsp2 they tried to provide a substitute with the /rereg command
> line switch but unfortunately botched the list of modules and the their
> parameters. I have documented a necessary edit if you want to try
> that route. Search my posts for reference to ieuinit.inf
>
>
> However, a simpler more general repair procedure is available here
> courtesy of German MVP Kai Schaetzl:
>
> http://iefaq.info/index.php?action=a...=31&artlang=en
>
> That procedure is similar to the old IE Repair (ref. KB194177)
> which used to be done at boot time after a (very cursory) verification.
> This procedure is not done at boot time and there is no verifcation,
> so it is up to the user to ensure that there are no interfering apps
> running and to determine that a compatible set of modules are present
> to be re-registered at the same time. Obviously a normal user can't
> do much about the latter, except hope that everything is consistent
> module-wise or perhaps try using sfc /scannow if some discrepancies
> are suspected. In any case, I would strongly suggest establishing
> minimal operating conditions before trying either procedure.
>
>
> HTH
>
> Robert Aldwinckle
> ---
>
>
>