Word 2003 not recognized by Outlook 2003

[Hal Hostetler [MVP P/I]]

Nice article reference, thanks!

Hal
--
Hal Hostetler, CPBE -- (e-mail address removed)
Senior Engineer/MIS -- MS MVP-Print/Imaging -- WA7BGX
http://www.kvoa.com -- "When News breaks, we fix it!"
KVOA Television, Tucson, AZ. NBC Channel 4
Live at Hot Licks - www.badnewsbluesband.com

 

[Brian Tillman]

I cannot find a "Normal.DOT" File the only file i can find is
Normal.FMT is this the same thing?

Open Windows Explorer and enter

%AppData%\Microsoft\Templates

in the Address Bar. Click Go.

 

[Richard Goodchild]

Dear Tech Exec,

Thank you for summing up the feelings of what I am sure is a huge number of
people when it comes to Microsoft issues.

I am not suggesting for a minute that Microsoft can predict the interactions
of every 3rd party application out there with any of their software and I am
grateful for the MVPs and the time and effort they put in on these
newsgroups, but time and again, I am amazed by Microsoft's blase attitude to
supporting their own software when it fails (which it does often). Let's be
honest, the only reason any of us are on these forums is because Microsoft
charge a small fortune for direct telephone support and this is usually a
good place to get an answer in the absence of getting it "from the horse's
mouth".

I have also experienced this issue a couple of times recently and have tried
the other suggestions in the help message, short of full un- and
re-installation. None have provided a permanent fix, so thanks Tech Exec for
another suggestion to try. Both times it happened to me, there were no
installations of 3rd party applications prior to the issue occurring, so that
may just be coincidence.

I agree with Jules too: why the hell should I have to carry out a system
restore with its inherent risks, simply to correct something as trivial as
this?

Thanks guys.

 

[Richard Goodchild]

Just a quick note to say to anyone out there experiencing this problem that
the re-registering of the dll described below worked for me.

Thanks very much, Tech Exec: you have eased my frustration and saved me from
hours of searching fruitlessly for answers!

Richard.

Hmm...

Wow. You seem defensive. There are cases where locking things down make
sense. There is certainly an argument for letting anyone write any code they
want, but neither of these extremes is necessary. Good quality controls would
be prudent. Certain locking down might be highly advisable. Why should
Microsoft allow a 3rd party application to trounce the registry settings for
a critical productivity application like Office?

Additionally, the obvious truth to this matter is that there IS NO EASY FIX.
It took me many hours to finally get the system back to where it should be.
It could have been many more, but I was able to find one note somewhere (not
here) about re-registering OLE32 (Start > Run > regsvr32.exe
%windir%\system32\ole32.dll) and that finally corrected the problem.

In any event, Office is Microsoft's application. Not the third party's. If
they are going to offer APIs to the Office applications such as Word and
Excel and Outlook, then they should write them in such a way as to control
the effectiveness of the components being written for them by the other
members in the industry.

Finally, Microsoft should not think that they should "lock down your
computer". They can and should lock down their applications. Those with
responsibility for security (technologists in an organization or an
individual in their home) should take care of locking down the computers.

___________________________________________________________________

The Microsoft experts don't have control over the 3rd party utilities you
install and how they interact with word and outlook - so how do you expect
them to prevent problems or have a quick fix answer for you? The only way
they can prevent such problems is to lock your computer down so you can't
install anything without their permission - would you really want that?

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)
Author, Google and Other Search Engines (Visual QuickStart Guide)



Join OneNote Tips mailing list: http://www.onenote-tips.net/

I just started experiencing this today. I am suspicious of two applets that
I
downloaded from a rather well-known CRM solution provider. Either way, I'm
pretty frustrated by all of this. Why do we accept this type of corruption
to
our environment and simply shrug it off as a casual event???

This causes me (and I'm sure many others that get into this predicament) a
significant number of unplanned hours to "hopefully" repair this
problem --
at my own risk according to the Google groups answer.

Why is it that the Microsoft "experts" are not able to answer the question
quickly and easily or, better yet, help to prevent this type of problem
from
happening in the first place??

I have yet to find a simple means of correcting this corruption (I have NO
desire to uninstall and reinstall Office) and am frankly incredibly
frustrated by the casual approach to this issue by the MS folks.

________________________________________________________________________

:

Thank you. It seems after I ran the detect and repair I only had a
problem
with one message and none of the others in my inbox. If the problem
persists
I will remove and reinstall.

:


I am also having the exact same problem.

And here's the standard answer:
http://groups-beta.google.com/group/microsoft.public.outlook/msg/c17bb52a846760e5?dmode=source&hl=en

 

[Richard Goodchild]

Alternatively, if deleting normal.dot does not work or is only a short-term
fix (as I found), try the re-registering of ole32.dll described in Tech
Exec's second email above - it certainly worked for me.

Richard.