Faulting application excel.exe, version 11.0.6560.0, stamp 4296b6f2, faulting
module excel.exe, version 11.0.6560.0, stamp 4296b6f2, debug? 0, fault
address 0x00410362.

So far I've done the following: Repaired then when that didn't work I
reinstalled Excel.

Than spreadsheets that die have a lot of VB that call other apps.

One of the things that excel does when it's closing is to update the *.xlb file
(where excel stores toolbar customizations).

If you close excel
then use windows search to find all the *.xlb files
and rename them all to *.xlbOLD

Then reopen excel and close excel to test it.

If it works ok, you can delete those *.xlbOLD files.

If that wasn't the solution, then just rename them back to the original names
(with excel closed).

scott wrote:

Faulting application excel.exe, version 11.0.6560.0, stamp 4296b6f2, faulting
module excel.exe, version 11.0.6560.0, stamp 4296b6f2, debug? 0, fault
address 0x00410362.

So far I've done the following: Repaired then when that didn't work I
reinstalled Excel.

Than spreadsheets that die have a lot of VB that call other apps.

--

Dave Peterson

Dave, thanks for the fast post.


Removed all *.xlb files. No difference.

What else can I try?

Scott



"Dave Peterson" wrote:

One of the things that excel does when it's closing is to update the *.xlb file
(where excel stores toolbar customizations).

If you close excel
then use windows search to find all the *.xlb files
and rename them all to *.xlbOLD

Then reopen excel and close excel to test it.

If it works ok, you can delete those *.xlbOLD files.

If that wasn't the solution, then just rename them back to the original names
(with excel closed).

scott wrote:

Faulting application excel.exe, version 11.0.6560.0, stamp 4296b6f2, faulting
module excel.exe, version 11.0.6560.0, stamp 4296b6f2, debug? 0, fault
address 0x00410362.

So far I've done the following: Repaired then when that didn't work I
reinstalled Excel.

Than spreadsheets that die have a lot of VB that call other apps.

--

Dave Peterson

I've been playing with this alittle more and have narrowed it down to the
manner in which we exit the application.

If we close the 'Book' we're working on then close Excel -- no error
If we use, on the tool bar, File-Exit or just the 'X' in the upper right
corner -- ERROR


Why is that and how can I work arount this issue?

Scott



"scott" wrote:

Dave, thanks for the fast post.


Removed all *.xlb files. No difference.

What else can I try?

Scott



"Dave Peterson" wrote:

One of the things that excel does when it's closing is to update the *.xlb file
(where excel stores toolbar customizations).

If you close excel
then use windows search to find all the *.xlb files
and rename them all to *.xlbOLD

Then reopen excel and close excel to test it.

If it works ok, you can delete those *.xlbOLD files.

If that wasn't the solution, then just rename them back to the original names
(with excel closed).

scott wrote:

Faulting application excel.exe, version 11.0.6560.0, stamp 4296b6f2, faulting
module excel.exe, version 11.0.6560.0, stamp 4296b6f2, debug? 0, fault
address 0x00410362.

So far I've done the following: Repaired then when that didn't work I
reinstalled Excel.

Than spreadsheets that die have a lot of VB that call other apps.

--

Dave Peterson

The work-around is to not use the things causing excel to blow up.

But this isn't usual behavior for excel--so don't stop looking for the answer.

One test to help isolate the problem...

Open excel in Safe mode
close excel
windows start button|Run
excel /safe

Do a few things (open a couple workbooks) and do a few tests closing excel.

If it works ok, then maybe it's not excel itself--maybe it's an addin or another
workbook that causing the trouble.

Chip Pearson has some notes on how to diagnose startup errors at:
http://www.cpearson.com/excel/StartupErrors.htm

And Jan Karel Pieterse has more notes at:
http://www.jkp-ads.com/Articles/StartupProblems.htm

Maybe you can disable all other addins/workbooks and open excel normally and do
some more testing.

(and if worse comes to worse--maybe reinstall????)

scott wrote:

I've been playing with this alittle more and have narrowed it down to the
manner in which we exit the application.

If we close the 'Book' we're working on then close Excel -- no error
If we use, on the tool bar, File-Exit or just the 'X' in the upper right
corner -- ERROR

Why is that and how can I work arount this issue?

Scott

"scott" wrote:

Dave, thanks for the fast post.


Removed all *.xlb files. No difference.

What else can I try?

Scott



"Dave Peterson" wrote:

One of the things that excel does when it's closing is to update the *.xlb file
(where excel stores toolbar customizations).

If you close excel
then use windows search to find all the *.xlb files
and rename them all to *.xlbOLD

Then reopen excel and close excel to test it.

If it works ok, you can delete those *.xlbOLD files.

If that wasn't the solution, then just rename them back to the original names
(with excel closed).

scott wrote:

Faulting application excel.exe, version 11.0.6560.0, stamp 4296b6f2, faulting
module excel.exe, version 11.0.6560.0, stamp 4296b6f2, debug? 0, fault
address 0x00410362.

So far I've done the following: Repaired then when that didn't work I
reinstalled Excel.

Than spreadsheets that die have a lot of VB that call other apps.

--

Dave Peterson


--

Dave Peterson

Dave,
We have gotten the following error:

Faulting application excel.exe, version 11.0.6355.0, stamp 40aa979f, faulting
module excel.exe, version 11.0.6355.0, stamp 40aa979f, debug? 0, fault
address 0x006c34c7
We can't seem to solve the problem......
Can you help???

I have the IT people trying to figure it out....so far no luck..... Could
be a corrupted file or????

The error usually happens after we have opended a shared file, made some
changes and hit save.... There are about 7 different people working in these
workbooks.... I have tried creating ne workbooks, but we still get the
"encountered problem, needs to shut down"...... Any suggestions?


"Dave Peterson" wrote:

The work-around is to not use the things causing excel to blow up.

But this isn't usual behavior for excel--so don't stop looking for the answer.

One test to help isolate the problem...

Open excel in Safe mode
close excel
windows start button|Run
excel /safe

Do a few things (open a couple workbooks) and do a few tests closing excel.

If it works ok, then maybe it's not excel itself--maybe it's an addin or another
workbook that causing the trouble.

Chip Pearson has some notes on how to diagnose startup errors at:
http://www.cpearson.com/excel/StartupErrors.htm

And Jan Karel Pieterse has more notes at:
http://www.jkp-ads.com/Articles/StartupProblems.htm

Maybe you can disable all other addins/workbooks and open excel normally and do
some more testing.

(and if worse comes to worse--maybe reinstall????)

scott wrote:

I've been playing with this alittle more and have narrowed it down to the
manner in which we exit the application.

If we close the 'Book' we're working on then close Excel -- no error
If we use, on the tool bar, File-Exit or just the 'X' in the upper right
corner -- ERROR

Why is that and how can I work arount this issue?

Scott

"scott" wrote:

Dave, thanks for the fast post.


Removed all *.xlb files. No difference.

What else can I try?

Scott



"Dave Peterson" wrote:

One of the things that excel does when it's closing is to update the *.xlb file
(where excel stores toolbar customizations).

If you close excel
then use windows search to find all the *.xlb files
and rename them all to *.xlbOLD

Then reopen excel and close excel to test it.

If it works ok, you can delete those *.xlbOLD files.

If that wasn't the solution, then just rename them back to the original names
(with excel closed).

scott wrote:

Faulting application excel.exe, version 11.0.6560.0, stamp 4296b6f2, faulting
module excel.exe, version 11.0.6560.0, stamp 4296b6f2, debug? 0, fault
address 0x00410362.

So far I've done the following: Repaired then when that didn't work I
reinstalled Excel.

Than spreadsheets that die have a lot of VB that call other apps.

--

Dave Peterson


--

Dave Peterson

I have no idea what that error means.

But I'd guess that if it only happens with that one workbook, then it's the
workbook that's the problem. I wouldn't think that each of 7 different people
would have excel (the actual program) get corrupted at the same time.

If they share a common addin, maybe it's that, too.

Maybe someone else has seen this error and can post what they did to fix/avoid
it.

I searched google within the *excel* newsgroups for: 40aa979f

and got about 16 hits.

Maybe one of them would help you.


http://groups.google.co.uk/groups?q=... 05&safe=off&

or

http://snipurl.com/ir2u



Dar wrote:

Dave,
We have gotten the following error:

Faulting application excel.exe, version 11.0.6355.0, stamp 40aa979f, faulting
module excel.exe, version 11.0.6355.0, stamp 40aa979f, debug? 0, fault
address 0x006c34c7
We can't seem to solve the problem......
Can you help???

I have the IT people trying to figure it out....so far no luck..... Could
be a corrupted file or????

The error usually happens after we have opended a shared file, made some
changes and hit save.... There are about 7 different people working in these
workbooks.... I have tried creating ne workbooks, but we still get the
"encountered problem, needs to shut down"...... Any suggestions?

"Dave Peterson" wrote:

The work-around is to not use the things causing excel to blow up.

But this isn't usual behavior for excel--so don't stop looking for the answer.

One test to help isolate the problem...

Open excel in Safe mode
close excel
windows start button|Run
excel /safe

Do a few things (open a couple workbooks) and do a few tests closing excel.

If it works ok, then maybe it's not excel itself--maybe it's an addin or another
workbook that causing the trouble.

Chip Pearson has some notes on how to diagnose startup errors at:
http://www.cpearson.com/excel/StartupErrors.htm

And Jan Karel Pieterse has more notes at:
http://www.jkp-ads.com/Articles/StartupProblems.htm

Maybe you can disable all other addins/workbooks and open excel normally and do
some more testing.

(and if worse comes to worse--maybe reinstall????)

scott wrote:

I've been playing with this alittle more and have narrowed it down to the
manner in which we exit the application.

If we close the 'Book' we're working on then close Excel -- no error
If we use, on the tool bar, File-Exit or just the 'X' in the upper right
corner -- ERROR

Why is that and how can I work arount this issue?

Scott

"scott" wrote:

Dave, thanks for the fast post.


Removed all *.xlb files. No difference.

What else can I try?

Scott



"Dave Peterson" wrote:

One of the things that excel does when it's closing is to update the *.xlb file
(where excel stores toolbar customizations).

If you close excel
then use windows search to find all the *.xlb files
and rename them all to *.xlbOLD

Then reopen excel and close excel to test it.

If it works ok, you can delete those *.xlbOLD files.

If that wasn't the solution, then just rename them back to the original names
(with excel closed).

scott wrote:

Faulting application excel.exe, version 11.0.6560.0, stamp 4296b6f2, faulting
module excel.exe, version 11.0.6560.0, stamp 4296b6f2, debug? 0, fault
address 0x00410362.

So far I've done the following: Repaired then when that didn't work I
reinstalled Excel.

Than spreadsheets that die have a lot of VB that call other apps.

--

Dave Peterson


--

Dave Peterson


--

Dave Peterson

Shared Workbook handling in Excel is riddled with bugs, and I think you're just unlucky in that you've given it more than it can chew - simple as that. I don't think you've done anything wrong. It appears to work fine on simple and small workbooks, but give it a lot of data to handle (and a lot of shared editors) and there's no away around it falling over.

A similar fault is that if one person opens a workbook (that's not shared), then somebody ELSE opens it (which will of course be a Read-Only copy), if that OTHER person then does a 'Save As' to create their own Read-Write copy, the first person to open it (in Read-Write), if they are running any macros that call a DialogSheet, then receives an 'Illegal Operation' error or a 'Microsoft Excel has encountered a problem and needs to close' error.

BizMark