Vista - printing in Windows mail

I cannot print any of my email messages in Windows mail. I could yesterday
but do not know what happened today. I keep getting an "Internet Explorer
Script error"
error: Library not registered
code: 0
URL: res://ieframe.dll/preview.dlg

Has anyone gotten this error and does anyone know how to fix this?

Try clearing your Temporary Internet Files in IE. Can you print a webpage?
Can you print a test page on the printer?

steve

"Sarah Witherow" <sarahwitherow@sbcglobal.net> wrote in message
news:7A8B2170-05B5-4576-93AB-8AC686A1AA44@microsoft.com...
>I cannot print any of my email messages in Windows mail. I could yesterday
>but do not know what happened today. I keep getting an "Internet Explorer
>Script error"
> error: Library not registered
> code: 0
> URL: res://ieframe.dll/preview.dlg
>
> Has anyone gotten this error and does anyone know how to fix this?

Check your printer, it may not be communicating to your computer.
that said, even when I have corrected it, I find it doesn't print right away.
Actually, it prints after I have closed down my computer, and then start it
back up. That could be after a few minutes, or a day or two. go figure.

"Sarah Witherow" wrote:

> I cannot print any of my email messages in Windows mail. I could yesterday
> but do not know what happened today. I keep getting an "Internet Explorer
> Script error"
> error: Library not registered
> code: 0
> URL: res://ieframe.dll/preview.dlg
>
> Has anyone gotten this error and does anyone know how to fix this?
>

I have been experiencing exactly the same error with the same error message.
It started from about the date Sarah gave. I can no longer print Windows Mail
email messages or web pages unless I switch to "Run as Administrator" mode.

"Sarah Witherow" wrote:

> I cannot print any of my email messages in Windows mail. I could yesterday
> but do not know what happened today. I keep getting an "Internet Explorer
> Script error"
> error: Library not registered
> code: 0
> URL: res://ieframe.dll/preview.dlg
>
> Has anyone gotten this error and does anyone know how to fix this?
>