G
George T
I have 3 users out of 45 who have constant spates of Word crashes. I thought
I had ended the crash problem for these 3 a while back by turning off all
sharing services but it is still there.
The crashes are not while saving or printing or at any particular time or
any particular event. Word may lock up on a brand new doc or after a saved
doc created by others is opened. It may happen within a few seconds or after
an hour or typing. It may happen repeatedly all day or just for a short time
or not occur for days.
The Office 2007 installation, other apps and hardware are identical to the
42 users who have no such problem. There is no virus issue. I even swapped
out computers of the three troubled users but the same problems happened for
them on new machines but did not recur for those lucky 3 among the 42 who
received their old machines.
It is pretty clearly related to these 3 users and not the config or
condition of the software.
Most of the time, the event viewer info is useless, mostly just a generic
“the app crashed†code. However, lately I see more of this bizarre
"officelifeboathang" message. What the bloody hell is a 'life boat hang'?
Why is there no reference data anywhere on Microsoft.com? Do I have to pay
to get access to basic support information?
One of the 3 users gave up on me and brought a Mac to work yesterday. (By
the way, thanks a pantload for that, Microsoft. I have been defending the
product and patching holes and all I ask is enough information to let me keep
the product working. I have made to look like a fool for sticking with this
product.)
Where can I go to get information? I am willing to do the research but I
gotta have information.
Is there a repository of known crash causes? Is there some protocol I can
follow? I have renamed Normal.Dotm, run in safe mode, ruled out add-ins,
etc. and done everything I can find on every techie site. Office
Diagnostics is unbelievably useless—it has never found any problem on any
machine at any time.
Is there a list of known ways to intentional crash Word so I can determine
the magic screw-up method common to these 3 users?
I had ended the crash problem for these 3 a while back by turning off all
sharing services but it is still there.
The crashes are not while saving or printing or at any particular time or
any particular event. Word may lock up on a brand new doc or after a saved
doc created by others is opened. It may happen within a few seconds or after
an hour or typing. It may happen repeatedly all day or just for a short time
or not occur for days.
The Office 2007 installation, other apps and hardware are identical to the
42 users who have no such problem. There is no virus issue. I even swapped
out computers of the three troubled users but the same problems happened for
them on new machines but did not recur for those lucky 3 among the 42 who
received their old machines.
It is pretty clearly related to these 3 users and not the config or
condition of the software.
Most of the time, the event viewer info is useless, mostly just a generic
“the app crashed†code. However, lately I see more of this bizarre
"officelifeboathang" message. What the bloody hell is a 'life boat hang'?
Why is there no reference data anywhere on Microsoft.com? Do I have to pay
to get access to basic support information?
One of the 3 users gave up on me and brought a Mac to work yesterday. (By
the way, thanks a pantload for that, Microsoft. I have been defending the
product and patching holes and all I ask is enough information to let me keep
the product working. I have made to look like a fool for sticking with this
product.)
Where can I go to get information? I am willing to do the research but I
gotta have information.
Is there a repository of known crash causes? Is there some protocol I can
follow? I have renamed Normal.Dotm, run in safe mode, ruled out add-ins,
etc. and done everything I can find on every techie site. Office
Diagnostics is unbelievably useless—it has never found any problem on any
machine at any time.
Is there a list of known ways to intentional crash Word so I can determine
the magic screw-up method common to these 3 users?