View Single Post
  #5   Report Post  
Posted to microsoft.public.excel.setup
RWN RWN is offline
external usenet poster
 
Posts: 104
Default Excel 2003 crashing everytime user goes to save document.

Sorry to be so long (vacation), esp. when I can't offer any sure-fire solution.
I our work environment I've had this happen from time to time and it's usually been the
case that the network connection has been interrupted.
Can't say that is the cause of your woes but the results are identical.
That's about all I can offer.

--
Regards;
Rob
------------------------------------------------------------------------
"R1 Psycho" wrote in message
...
Yes they are saving to a network drive. I thought maybe at 1st that it had
something to do wth the location they were saving to, possibly permissions or
a corrupt drive but they are different locations. The problem seems to be bad
some days and then not so much other days. No consistency, very strange.

Do you have any ideas?
--
Matt


"RWN" wrote:

Are they saving to a network drive?


--
Regards;
Rob
------------------------------------------------------------------------
"R1 Psycho" wrote in message
...
Anyone out there have any ideas? This must have happened before to someone.
If so, please chime in.

Regards,
Matt
--
Matt


"R1 Psycho" wrote:

Several of the users we support are now experiencing Excel 2003 crashing when
they attempt to save an excel doc. A Microsoft dialogue box then asks them if
they want to auto recover the document and send Microsoft an error report.
this is now starting happen to more and more users, and no clue as to why.
I have a copy/paste of an event in the application log if this helps;

Faulting application excel.exe, version 11.0.8142.0, stamp 465f142b,
faulting module excel.exe, version 11.0.8142.0, stamp 465f142b, debug? 0,
fault address 0x0002a99c.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

and

Hanging application EXCEL.EXE, version 11.0.8142.0, hang module hungapp,
version 0.0.0.0, hang address 0x00000000.

This is causing a tremendous amount of work for users and an unstable Excel.

Can anyone out there help? PLEASE!!!

thank you in advance

--
Matt