Office hangs saving to network, please help!

jfunk

Golden Member
Oct 16, 2000
1,208
0
76
Ok, brand new dell P4 machine this lady has at work. XP Pro.

The only things to have been installed on it out of the box are Netware, Groupwise, and Office2000.

All service paks and windows updates are in without error.

Everything works fine, except there are application hangs in WINWORD that causes her to have to reboot.

I haven't actually seen anyone of them happen yet, but they all show the same error in the app log.

Any ideas what is causing this? Office has been removed and reinstalled and repatched with the same results.

TIA.

Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: 6/24/2003
Time: 2:09:18 PM
User: N/A
Computer: DHW2P721
Description:
Hanging application WINWORD.EXE, version 9.0.0.6926, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 48 61 6e 67 ion Hang
0010: 20 20 57 49 4e 57 4f 52 WINWOR
0018: 44 2e 45 58 45 20 39 2e D.EXE 9.
0020: 30 2e 30 2e 36 39 32 36 0.0.6926
0028: 20 69 6e 20 68 75 6e 67 in hung
0030: 61 70 70 20 30 2e 30 2e app 0.0.
0038: 30 2e 30 20 61 74 20 6f 0.0 at o
0040: 66 66 73 65 74 20 30 30 ffset 00
0048: 30 30 30 30 30 30 000000








j




 

jfunk

Golden Member
Oct 16, 2000
1,208
0
76
Oh come on, you guys are better than that! Not a single idea? Somebody at least throw something stupid out there to bump the thread. :)





Thanks


j

 

alocurto

Platinum Member
Nov 4, 1999
2,174
0
76
did Norton anit-virus get installed on the machine? I know u didn't mention it but I thought maybe it could be an oversight.
 

jfunk

Golden Member
Oct 16, 2000
1,208
0
76
Oh yea, I did forget anti-virus is on there, but its McAfee, not Norton.


j


 

jfunk

Golden Member
Oct 16, 2000
1,208
0
76
Ok, I've narrowed the problem down.

It affects any office program (at least word, excel, and access). It occurs when attempting to save a file to a mapped network drive.

Runs fine the rest of the time. When you try to save the doc you are working to the network (all users have their own directory on the server for docs, which is mapped at boot), it just hangs. Machine must be rebooted, nothing will respond except the task manager, and nothing will end task or anything, no start menu, no nothing. Can't even shut down from the task manager.

This doesn't happen EVERY time you try to save. Sometimes it just sits there for a few seconds (like 10) then saves normally. About 1 in 3 times it hangs for good though.

No problems accessing, reading/writing to the network for any other programs, just Office progs.

Ideas?


j

 

idgaf13

Senior member
Oct 31, 2000
453
0
0
I belive your problem is related to a windows update.
It causes 100% CPU utilization ,forget the exact # think it is Q889143.
The MS suggested remedy is to uninstall the update.

Search the MS Knowledgebase for "CPU Utilization".
 

skace

Lifer
Jan 23, 2001
14,488
7
81
Have you attempted to save anything outside of office products to the network? IE: open notepad and make some changes and then save them to the network. Fluke her network port. Try another network port if there is a second one. Try saving somewhere else and then copy to the network share and see how it performs. Attempt the same process under your account on the same machine.
 

jfunk

Golden Member
Oct 16, 2000
1,208
0
76
Well, figured it out. (BTW, other writing to network outside office products was working fine).

There were two settings in the Netware layer that had to be changed. file caching had to be turned off, and file something else on (can't remember it off the top of my head at the moment. They were right next to each other in the list). These properties defaulted to this way on all the older machines (ME, 9x), but for some reason the defaults for these two options were reversed on the XP client install.

Once those two were changed, all problems went away.

Funky...especially that it only seemed to affect office apps....

Thanks for the suggestions, all.


j