Error message

[wessnyder]

I am using MS 2002 and MS Word. I keep getting an error message as follows
"Microsoft Word has encountered a problem and needs to close, we are sorry fo
the inconvence". So am I!!
I have done everything that MS has advised and others, about Normal.dot, I
have deleated the origional Normal.dot and let Word make a new one, however,
the error keeps coming back. can you help please? I am getting very
discouraged and it seems that MS only wants me to upgrade to 2007 to solve
the problem.

 

[Herb Tyson [MVP]]

Have you tried deleting Word's Data key in the registry?

 

[wessnyder]

No, I haven't done this and I am not sure I know how to do it, I am just
smart enough to be dangerious when it comes to working with the regustery.
Could you give me some direction?
Thanks
--
Thanks for your help.
Wes

Have you tried deleting Word's Data key in the registry?

 

[Herb Tyson [MVP]]

The following page has instructions for editing the registry to delete the
Data key:

http://word.mvps.org/FAQs/AppErrors/MissingMenusEtc.htm

If you're squeamish, you can rename it, instead, if you prefer (e.g., as
Datax). Either way, Word will no longer see the errant entries when you
start Word.


--
Herb Tyson MS MVP
Author of the Word 2007 Bible
Blog: http://word2007bible.herbtyson.com
Web: http://www.herbtyson.com

No, I haven't done this and I am not sure I know how to do it, I am just
smart enough to be dangerious when it comes to working with the regustery.
Could you give me some direction?
Thanks

 

[wessnyder]

Herb:
Thanks for your help, I will give it a try and hope this will solve the
problem as it has really been a headache for me.

 

[wessnyder]

I did what yu suggested and it still gives me the error message.
It shows the error as follows: "AppName: winword.exe AppVer: 10.0.6829.0
ModName:mso.dll ModVer: 10.0.6830.0 OffSet: 006fcefe".
When I go the suggested fix and I get the following: "Word failed to start
correctly last time, starting in safe mode will help correct or isolate a
start up problem".
Then they suggest the following: "The problem was caused by WS 2002 in its
and fix is in "extended suport" phase". Which is no longer available, upgrde
to 2007.
If this helps any let me know, if not, we tried.
Wes