Outlook problem

[Eric Pardue]

I just tryed to load Office 2003 and when I try to open a
word document created from a .dot (template) it gave me a
script error.

So, I uninstalled 2003 and loaded Office XP Pro. Now I am
getting 2 odd problems. When I try to print fro outlook, I
get a script error:
A runtime error has occured
Do you wish to debug?
Line 1343
Error: Unspecified error

I have always used XP pro and printed in the past. I have
installed all of the Updates and Service packs

Second problem is when I select Word as my email editor
and try to send a message, I get the following error:
Interface Not Registered

Any suggestions would be welcome to prevent reloading
totally or paying $ 245 for an incedent.

 

[Andre Da Costa]

Install the latest Service Packs and Patches for Office XP. I would also
recommend doing a detect and repair from the Help menu of the Office XP
applications that are having issues.

Andre Da Costa
Jamaica W.I.

Hello,

I spent a multitude of hours today trying to solve the following problems with Office:
1) Could not print from Outlook - always got a script error on line 1343
2) Could not use Send To from Word or Excel and send the documents in Email
3) Could not use Word as the default Email editor

The usual error was "Interface not Registered".

I performed the Repair installation (no help), and also removed Office

completely and reinstalled (no help).

(Note that my setup is Win2000 with Office XP)

After combing through all the postings/microsoft solutions(fantasies), and

web info, I arrived at the following procedure that I would follow. This are
in increasing difficulty and complexity:

1) regsvr32 C:\WINNT\SYSTEM32\OLE32.DLL
2) regsvr32 C:\WINNT\SYSTEM32\MSRDO20.DLL
3) Add a new profile using control panel - mail - profiles
4) Regclean from ZDNet
5) Repair windows installation
6) Reinstall windows

In my instance, after performing the first 2 steps all the problems were

gone and everything works fine again (thus I did not have to perform steps
3-6). Other users reported that simply doing the re-registration did not fix
their problem. For other users, I would suggest checking the problem after
each step to see if it fixed it before proceeding to the next.