Error printing html format e-mails

I have tried all the solutions mentioned so far but still I cannot get
Outlook to print an html email. We use Exchange, and if I go offline then I
can get it to print but it takes a while before it prints. If I go back
online I get the error message that Outlook is not able to connect to the
Exchange Server. Yet is shows that its connected. I believe this problem has
something to do with Network communications and the printer likewise is a
network printer.

So there is something either messed up in the TCPIP settings or the Spooler
Settings or Both.

This problem has been going on long enough now that Microsoft should have
posted a fix by now. But apparently they are too lazy to provide any
guidance and assistance in sloving this problem.

I have just finished doing the complete Office 2003 Service Pack 3 update so
all Office drivers and dll should be correct as of that time.

Ay additional guidance would be appreciated.

Cole
--
Never enough time to do it right but always enough time to do it over again
and again. Especially in Windows.




"s.duin" wrote:

> When I want to print an e-mail directly from outlook 2003 I get an error.
> The error discription :
>
> An error has occurred in the script on this page
>
> Line: 1829
> Char: 1
> Error: Unspecified error.
> code: 0
> URL: res://ieframe.dll/preview.dlg
>
> Do you want to continue running scripts on this page?
>
> Option : Yes / No
>
> Sometimes it works but sometimes it doesn't. I tried shutting down the error
> message reporting but didn't work out.
>
> Anyone with an proboble solution?

In searching through other similar printing problems on this discussion board
I found reference to the following MS Article ID: Q281679 dated 15 Nov 2007
Revision 7.13 -- Titled: You cannot open a new Internet Explorer window or
nothing occurs after you click a link.

See http://support.microsoft.com/kb/281679

It was the last part of the title that intrigued me because printing an HTML
email is kind of like clicking a link.

Upon reviewing the article and registering the DLL files it listed one of
them came back with an error. It was the Mshtmll.dll file.

The error message was "c:\windows\system32\mshtml.dll was loaded, but the
Dll Register Server entry point was not found. FILE CANNOT BE REGISTERED.

So how does one solve this problem of registering the mshtml.dll file?
HELP!!!

Thanks

Cole

--
Never enough time to do it right but always enough time to do it over again
and again. Especially in Windows.




"Cole" wrote:

> I have tried all the solutions mentioned so far but still I cannot get
> Outlook to print an html email. We use Exchange, and if I go offline then I
> can get it to print but it takes a while before it prints. If I go back
> online I get the error message that Outlook is not able to connect to the
> Exchange Server. Yet is shows that its connected. I believe this problem has
> something to do with Network communications and the printer likewise is a
> network printer.
>
> So there is something either messed up in the TCPIP settings or the Spooler
> Settings or Both.
>
> This problem has been going on long enough now that Microsoft should have
> posted a fix by now. But apparently they are too lazy to provide any
> guidance and assistance in sloving this problem.
>
> I have just finished doing the complete Office 2003 Service Pack 3 update so
> all Office drivers and dll should be correct as of that time.
>
> Ay additional guidance would be appreciated.
>
> Cole
> --
> Never enough time to do it right but always enough time to do it over again
> and again. Especially in Windows.
>
>
>
>
> "s.duin" wrote:
>
> > When I want to print an e-mail directly from outlook 2003 I get an error.
> > The error discription :
> >
> > An error has occurred in the script on this page
> >
> > Line: 1829
> > Char: 1
> > Error: Unspecified error.
> > code: 0
> > URL: res://ieframe.dll/preview.dlg
> >
> > Do you want to continue running scripts on this page?
> >
> > Option : Yes / No
> >
> > Sometimes it works but sometimes it doesn't. I tried shutting down the error
> > message reporting but didn't work out.
> >
> > Anyone with an proboble solution?