WINWORD.exe errors....

[odinfire]

Greetings all!

Ok I have a W2K workstation with Office 2000 installed & sr-1 installed. The user on this machine is having issues whenever she tries to open up a word doc attachement in Outlook. The message states the following:

"WINWORD.EXE has generated erross and will be closed. A log file is being created."

I checked the KB on microsoft's site, but to no avail. I have reinstalled the whole office suite w/sr-1 & still get the same problem. I also checked the attachment, which she forwarded to me, and I was able to open it. I have the same setup. Anyone out there experience this? Where is the location of this log file it creates?
Any help would be greatly appreciated.

Odin

 

[carrr]

"To view the error log in Microsoft Windows 2000, follow these steps:
Click Start, point to Search, and then click For Files or Folders.
In the Search for files or folders named box, type Drwtsn32.log.
Click Search Now.
Right-click the file, and then click Open on the menu that appears.
NOTE: The Drwtsn32.log file is located in the following folder by default:

C:\Documents and Settings\All Users\Documents\DrWatson"

 

[RexNoctis]

I've heard that when you remove Word (or Office), the normal.dot template is not removed.

Close Word, do a search for normal.dot and delete it. Reopen word and it will recreate the normal.dot file. This may help your problem.

Let us know how you get on.

Danny.

 

[carrr]

There are a number of possible causes for this. One is a corrupt normal.dot file. Deleting the existing one on the machine and letting Word recreate the file may solve the problem. Another is that WinFax Pro is installed on the pc. Removing it could solve the problem. Also, believe it or not, changing the default printer has also been known to remedy the situation.

 

[odinfire]

Will try the posted tips. Thanks guys. I will give you an update asap.

Odin

 

[odinfire]

1) No winfax on machine.
2) Did a search for normal.dot, erased it, & started up word. Then went into outlook & attempted to open document again, but no luck. Did I miss any steps?
3) Changed default printer & no luck.

Anything else out there I could try?

 

[carrr]

What's your error log saying?

 

[odinfire]

Sorry about that here you go:
I extracted this particular nugget of info as it seems to pertain to my problem:

Application exception occurred:
App: (pid=1224)
When: 9/4/2002 @ 23:06:01.789
Exception number: c0000005 (access violation)

*----> System Information <----*
Computer Name: ***********
User Name: ********
Number of Processors: 1
Processor Type: x86 Family 6 Model 11 Stepping 1
Windows 2000 Version: 5.0
Current Build: 2195
Service Pack: 2
Current Type: Uniprocessor Free
Registered Organization: **********
Registered Owner: ******

*----> Task List <----*
0 Idle.exe
8 System.exe
144 smss.exe
168 csrss.exe
188 WINLOGON.exe
216 services.exe
228 LSASS.exe
400 svchost.exe
428 spoolsv.exe
500 ati2evxx.exe
520 svchost.exe
556 ntrtscan.exe
588 regsvc.exe
628 mstask.exe
660 tmlisten.exe
760 winmgmt.exe
944 explorer.exe
948 atiptaxx.exe
1168 pctspk.exe
1180 PccNTMon.exe
1196 HOTSYNC.exe
1092 MAPISP32.exe
1224 WINWORD.exe
1300 agentsvr.exe
1560 OUTLOOK.exe
1000 drwtsn32.exe
0 _Total.exe

I **** out personal information that was not relevant to problem resolution. It appears there is an access violation, but I am not sure how to address this particular violation. Any suggestions?

Thanks again,

Odin

 

[carrr]

We've run down a few of these already, but there are two other fixes in here that may pan out for you (the &quot;bad template&quot; fix and the VB6.dll fix...

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q316033&

 

[odinfire]

Ok it has been fixed. Thanks for that link Carr...
Apparently it was a *.dll file which is mentioned in the KB article. Once again all thanks for your help.

For any others having a similar problem consult the link above to the MS KB.

Odin

 

[purpleski]

Hi

Had the same problem on one of my computers yesterday and when none of the tips at

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q316033

cured the problem I searched Google again for Exception number: c0000005 (access violation)and found a mention that a corrupt profile can cause the same problem. So logged in as somebody else and voila no more problem.

So I deleted the problem profile and am in the process of reinstalling the necessary bits but one bit at a time.

Hope this helps.