Word frequently crashing on a terminal server

I've got a terminal server (server 2003 standard) that has office 2003 (w/ SP3, but it also did it on SP2) on it. over time, word has started crashing (over the past few weeks) and has been getting worse. it's always only one user at a time, but lately, as soon as i fix it for that one user, another user has the same problem immediately. the fix is a removal of normal.dot for that user. i can even recreate the problem by copying that user's normal.dot to another profile and watch the crashes happen. the crash occurs immediately on startup of Word, causing the user not to be able to do any of their work..

i can have more details later, as far as the crashing, since i'm not onsite, but wanted to see if anyone has experienced anything similar.
dniconsultingAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PlaceboC6Commented:
Try this:

Open the boot.ini file:

control panel
System
Advanced tab
Startup and recovery
Click edit button to open boot.ini
find the /noexecute= statement and change it from saying optin or optout to  alwaysoff
/noexecute=always off
Save the file in notepad (overwrite boot.ini)
Reboot

See if you still have the problem.
0
dniconsultingAuthor Commented:
ah, DEP. i'll give that a shot, but i won't be able to reboot until later tonight (it's 12pm here). any other suggestions?
0
PlaceboC6Commented:
I've seen issues with office, DEP, and terminal server.  That's high on my list of suggestions for sure.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

SLFuquaCommented:
Have you tried running "Repair and Detect" for Office on the TS? If so, or if it doesn't help, have you tried replacing the default normal.dot on the server that users pull from?

Best,
sl
0
dniconsultingAuthor Commented:
Alright, i've got DEP turned off, ready for a reboot, but that won't happen until tonight. it was set to "all programs and services" and not "only essential programs and services". likely that this is the problem, but i'll post some more info anyway.

Here is the event in app logs:
Event Type:      Error
Event Source:      Microsoft Office 11
Event Category:      None
Event ID:      1000
Date:            1/24/2008
Time:            11:08:44 AM
User:            N/A
Computer:      TS
Description:
Faulting application winword.exe, version 11.0.8169.0, stamp 465f2a40, faulting module winword.exe, version 11.0.8169.0, stamp 465f2a40, debug? 0, fault address 0x008dd0ac.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 00 70 00 70 00 6c 00   A.p.p.l.
0008: 69 00 63 00 61 00 74 00   i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00   i.o.n. .
0018: 46 00 61 00 69 00 6c 00   F.a.i.l.
0020: 75 00 72 00 65 00 20 00   u.r.e. .
0028: 20 00 77 00 69 00 6e 00    .w.i.n.
0030: 77 00 6f 00 72 00 64 00   w.o.r.d.
0038: 2e 00 65 00 78 00 65 00   ..e.x.e.
0040: 20 00 31 00 31 00 2e 00    .1.1...
0048: 30 00 2e 00 38 00 31 00   0...8.1.
0050: 36 00 39 00 2e 00 30 00   6.9...0.
0058: 20 00 34 00 36 00 35 00    .4.6.5.
0060: 66 00 32 00 61 00 34 00   f.2.a.4.
0068: 30 00 20 00 69 00 6e 00   0. .i.n.
0070: 20 00 77 00 69 00 6e 00    .w.i.n.
0078: 77 00 6f 00 72 00 64 00   w.o.r.d.
0080: 2e 00 65 00 78 00 65 00   ..e.x.e.
0088: 20 00 31 00 31 00 2e 00    .1.1...
0090: 30 00 2e 00 38 00 31 00   0...8.1.
0098: 36 00 39 00 2e 00 30 00   6.9...0.
00a0: 20 00 34 00 36 00 35 00    .4.6.5.
00a8: 66 00 32 00 61 00 34 00   f.2.a.4.
00b0: 30 00 20 00 66 00 44 00   0. .f.D.
00b8: 65 00 62 00 75 00 67 00   e.b.u.g.
00c0: 20 00 30 00 20 00 61 00    .0. .a.
00c8: 74 00 20 00 6f 00 66 00   t. .o.f.
00d0: 66 00 73 00 65 00 74 00   f.s.e.t.
00d8: 20 00 30 00 30 00 38 00    .0.0.8.
00e0: 64 00 64 00 30 00 61 00   d.d.0.a.
00e8: 63 00 0d 00 0a 00         c.....  



The information in the various event entries are identical.

I have tried running "detect and repair" on the TS, to no avail. I don't know where the default normal.dot is to replace. i'd be glad to try that prior to the reboot to see what happens. is it in the "default user" profile?
0
PlaceboC6Commented:
I'll stand by and see how the DEP thing worked for you.
0
dniconsultingAuthor Commented:
Alright, DEP is disabled (I double checked), and the same crashing is still happening. the event log is exactly the same as the one posted prior.
0
PlaceboC6Commented:
Hmmm

Have you tried using MSCONFIG to kill all non MS services?
0
dniconsultingAuthor Commented:
I have done that, and killed startup processes that weren't needed (which was all of them). the problem didn't get any worse or any better as a result.
0
dniconsultingAuthor Commented:
anyone have the info about the location of the default normal.dot?

i'm looking for any suggestions here...
0
PlaceboC6Commented:
Have you tried reinstalling Officing according to:

http://support.microsoft.com/default.aspx?scid=kb;en-us;828955



0
SLFuquaCommented:
the normal.dot location can be found by opening a TS client, and in Word, click on Tools | Options | File Location and check out the path next to User Templates. If you delete it from the default location it should be recreated the next time Word runs.

Best,
sl
0
dniconsultingAuthor Commented:
Well, I think I may have found the problem. A user notified me yesterday that the "Attach as PDF" button in Outlook/Word wasn't working. Testing it myself, the user was correct.  After doing a repair install of Acrobat 8, the button still wouldn't work. I have removed that button from Word (and Outlook) by doing the "Modify" install/uninstall for Acrobat 8, and removing "Word" from the "PDFMaker" section. After that, I renamed all "normal.dot" files for all users, and so far, nobody has crashed.

I'll cross my fingers and hope that was the fix.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dniconsultingAuthor Commented:
it was the PDF plugin to office causing the issue. uninstalled the piece of crap plugin ("modify" installation) to resolve the issue. hasn't returned since.
0
Vee_ModCommented:
Closed, 500 points refunded.
Vee_Mod
Community Support Moderator
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.