Excel Crashes After Autosum or Sum

V

Vulocity

Version: 2008 Operating System: Mac OS X 10.6 (Snow Leopard) Processor: Intel Mac OS X 10.6.2
Excel Version 12.2.3

My Excel crashes every time I try to use the sum feature. It doesn't matter if I manually type in the formula and hit enter to sum, or if I hit the Autosum button to add up cells, it crashes every time. I only started to do this recently. I haven't made any changes or added any programs to my computer lately that I know of. Any help that you can offer would greatly be appreciated. Excel is basically useless to me at the moment without this feature.

The Error Report is as follows:

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2010-03-06 19:25:18 -0500
Application Name: Microsoft Excel
Application Bundle ID: com.microsoft.Excel
Application Signature: XCEL
Application Version: 12.2.3.091001
Crashed Module Name: MicrosoftComponentPlugin
Crashed Module Version: unknown
Crashed Module Offset: 0x00036d80
Blame Module Name: MicrosoftComponentPlugin
Blame Module Version: unknown
Blame Module Offset: 0x00036d80
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x01494d80 in _McpDestroyTooltip + 0x0000000C (MicrosoftComponentPlugin + 0x00036d80)
# 2 0x001e5671 in __mh_execute_header + 0x001E4671 (Microsoft Excel + 0x001e4671)
# 3 0x002146f1 in __mh_execute_header + 0x002136F1 (Microsoft Excel + 0x002136f1)
# 4 0x001cd184 in __mh_execute_header + 0x001CC184 (Microsoft Excel + 0x001cc184)
# 5 0x001cd2ea in __mh_execute_header + 0x001CC2EA (Microsoft Excel + 0x001cc2ea)
# 6 0x0063c2c6 in __mh_execute_header + 0x0063B2C6 (Microsoft Excel + 0x0063b2c6)
# 7 0x0063c806 in __mh_execute_header + 0x0063B806 (Microsoft Excel + 0x0063b806)
# 8 0x0063cb51 in __mh_execute_header + 0x0063BB51 (Microsoft Excel + 0x0063bb51)
# 9 0x00a3f2c5 in __mh_execute_header + 0x00A3E2C5 (Microsoft Excel + 0x00a3e2c5)
# 10 0x00a3f3c8 in __mh_execute_header + 0x00A3E3C8 (Microsoft Excel + 0x00a3e3c8)
# 11 0x00a4164a in __mh_execute_header + 0x00A4064A (Microsoft Excel + 0x00a4064a)
# 12 0x014fa2bc in MEventHandler::FRemoveHandler(unsigned long, unsigned long) + 0x000001DE (MicrosoftComponentPlugin + 0x0009c2bc)
# 13 0x94d05e29 in .objc_class_name_IMKInkInputSession + 0x949C14D1 (HIToolbox + 0x00007e29)
# 14 0x94d050f0 in .objc_class_name_IMKInkInputSession + 0x949C0798 (HIToolbox + 0x000070f0)
# 15 0x94d27981 in .objc_class_name_IMKInkInputSession + 0x949E3029 (HIToolbox + 0x00029981)
# 16 0x94d397df in .objc_class_name_IMKInkInputSession + 0x949F4E87 (HIToolbox + 0x0003b7df)
# 17 0x94d0627a in .objc_class_name_IMKInkInputSession + 0x949C1922 (HIToolbox + 0x0000827a)
# 18 0x94d050f0 in .objc_class_name_IMKInkInputSession + 0x949C0798 (HIToolbox + 0x000070f0)
# 19 0x94d27981 in .objc_class_name_IMKInkInputSession + 0x949E3029 (HIToolbox + 0x00029981)
# 20 0x94d8985a in .objc_class_name_IMKInkInputSession + 0x94A44F02 (HIToolbox + 0x0008b85a)
# 21 0x94d891d7 in .objc_class_name_IMKInkInputSession + 0x94A4487F (HIToolbox + 0x0008b1d7)
# 22 0x94d88de1 in .objc_class_name_IMKInkInputSession + 0x94A44489 (HIToolbox + 0x0008ade1)
# 23 0x94d79de2 in .objc_class_name_IMKInkInputSession + 0x94A3548A (HIToolbox + 0x0007bde2)
# 24 0x94dc758f in .objc_class_name_IMKInkInputSession + 0x94A82C37 (HIToolbox + 0x000c958f)
# 25 0x94d01bae in .objc_class_name_IMKInkInputSession + 0x949BD256 (HIToolbox + 0x00003bae)
# 26 0x94d05e29 in .objc_class_name_IMKInkInputSession + 0x949C14D1 (HIToolbox + 0x00007e29)
# 27 0x94d050f0 in .objc_class_name_IMKInkInputSession + 0x949C0798 (HIToolbox + 0x000070f0)
# 28 0x94d04f4f in .objc_class_name_IMKInkInputSession + 0x949C05F7 (HIToolbox + 0x00006f4f)
# 29 0x94d39713 in .objc_class_name_IMKInkInputSession + 0x949F4DBB (HIToolbox + 0x0003b713)
# 30 0x94d0627a in .objc_class_name_IMKInkInputSession + 0x949C1922 (HIToolbox + 0x0000827a)
# 31 0x94d050f0 in .objc_class_name_IMKInkInputSession + 0x949C0798 (HIToolbox + 0x000070f0)
#
 
J

John McGhie

Well, this could be a pain... Looking at your crash dump, I have a sneaking
suspicion that the update has not applied to one of the software modules on
your computer.

Just to ensure we have a level playing field, is this one single workbook,
or "any" workbook? If it's "any" workbook, then:

1) Delete the preferences and see if that fixes it.

Go to /Users/~/Library/Preferences/Microsoft/Office 2008 and blow away the
entire folder.

2) Repair permissions and see if THAT fixes it.

Start Disk Utility and choose Repair Permissions.

3) Perform a full Remove/Replace/Re-update of Office

Make sure you have your DVD and Product Key handy, we're going to blow it
away.

In the Microsoft Office 2008 folder of your Applications folder, you will
find the "Office Remover" tool. Run it.

Blow away the Preferences (as in 1) above).

Re-install. Apply updates 12.1.0, 12.2.0 and 12.2.3 from the Microsoft
website.

One of those should fix it.

Hope this helps

Version: 2008 Operating System: Mac OS X 10.6 (Snow Leopard) Processor: Intel
Mac OS X 10.6.2
Excel Version 12.2.3

My Excel crashes every time I try to use the sum feature. It doesn't matter if
I manually type in the formula and hit enter to sum, or if I hit the Autosum
button to add up cells, it crashes every time. I only started to do this
recently. I haven't made any changes or added any programs to my computer
lately that I know of. Any help that you can offer would greatly be
appreciated. Excel is basically useless to me at the moment without this
feature.

The Error Report is as follows:

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2010-03-06 19:25:18 -0500
Application Name: Microsoft Excel
Application Bundle ID: com.microsoft.Excel
Application Signature: XCEL
Application Version: 12.2.3.091001
Crashed Module Name: MicrosoftComponentPlugin
Crashed Module Version: unknown
Crashed Module Offset: 0x00036d80
Blame Module Name: MicrosoftComponentPlugin
Blame Module Version: unknown
Blame Module Offset: 0x00036d80
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x01494d80 in _McpDestroyTooltip + 0x0000000C (MicrosoftComponentPlugin
+ 0x00036d80)
# 2 0x001e5671 in __mh_execute_header + 0x001E4671 (Microsoft Excel +
0x001e4671)
# 3 0x002146f1 in __mh_execute_header + 0x002136F1 (Microsoft Excel +
0x002136f1)
# 4 0x001cd184 in __mh_execute_header + 0x001CC184 (Microsoft Excel +
0x001cc184)
# 5 0x001cd2ea in __mh_execute_header + 0x001CC2EA (Microsoft Excel +
0x001cc2ea)
# 6 0x0063c2c6 in __mh_execute_header + 0x0063B2C6 (Microsoft Excel +
0x0063b2c6)
# 7 0x0063c806 in __mh_execute_header + 0x0063B806 (Microsoft Excel +
0x0063b806)
# 8 0x0063cb51 in __mh_execute_header + 0x0063BB51 (Microsoft Excel +
0x0063bb51)
# 9 0x00a3f2c5 in __mh_execute_header + 0x00A3E2C5 (Microsoft Excel +
0x00a3e2c5)
# 10 0x00a3f3c8 in __mh_execute_header + 0x00A3E3C8 (Microsoft Excel +
0x00a3e3c8)
# 11 0x00a4164a in __mh_execute_header + 0x00A4064A (Microsoft Excel +
0x00a4064a)
# 12 0x014fa2bc in MEventHandler::FRemoveHandler(unsigned long, unsigned
long) + 0x000001DE (MicrosoftComponentPlugin + 0x0009c2bc)
# 13 0x94d05e29 in .objc_class_name_IMKInkInputSession + 0x949C14D1
(HIToolbox + 0x00007e29)
# 14 0x94d050f0 in .objc_class_name_IMKInkInputSession + 0x949C0798
(HIToolbox + 0x000070f0)
# 15 0x94d27981 in .objc_class_name_IMKInkInputSession + 0x949E3029
(HIToolbox + 0x00029981)
# 16 0x94d397df in .objc_class_name_IMKInkInputSession + 0x949F4E87
(HIToolbox + 0x0003b7df)
# 17 0x94d0627a in .objc_class_name_IMKInkInputSession + 0x949C1922
(HIToolbox + 0x0000827a)
# 18 0x94d050f0 in .objc_class_name_IMKInkInputSession + 0x949C0798
(HIToolbox + 0x000070f0)
# 19 0x94d27981 in .objc_class_name_IMKInkInputSession + 0x949E3029
(HIToolbox + 0x00029981)
# 20 0x94d8985a in .objc_class_name_IMKInkInputSession + 0x94A44F02
(HIToolbox + 0x0008b85a)
# 21 0x94d891d7 in .objc_class_name_IMKInkInputSession + 0x94A4487F
(HIToolbox + 0x0008b1d7)
# 22 0x94d88de1 in .objc_class_name_IMKInkInputSession + 0x94A44489
(HIToolbox + 0x0008ade1)
# 23 0x94d79de2 in .objc_class_name_IMKInkInputSession + 0x94A3548A
(HIToolbox + 0x0007bde2)
# 24 0x94dc758f in .objc_class_name_IMKInkInputSession + 0x94A82C37
(HIToolbox + 0x000c958f)
# 25 0x94d01bae in .objc_class_name_IMKInkInputSession + 0x949BD256
(HIToolbox + 0x00003bae)
# 26 0x94d05e29 in .objc_class_name_IMKInkInputSession + 0x949C14D1
(HIToolbox + 0x00007e29)
# 27 0x94d050f0 in .objc_class_name_IMKInkInputSession + 0x949C0798
(HIToolbox + 0x000070f0)
# 28 0x94d04f4f in .objc_class_name_IMKInkInputSession + 0x949C05F7
(HIToolbox + 0x00006f4f)
# 29 0x94d39713 in .objc_class_name_IMKInkInputSession + 0x949F4DBB
(HIToolbox + 0x0003b713)
# 30 0x94d0627a in .objc_class_name_IMKInkInputSession + 0x949C1922
(HIToolbox + 0x0000827a)
# 31 0x94d050f0 in .objc_class_name_IMKInkInputSession + 0x949C0798
(HIToolbox + 0x000070f0)
#
Click to expand...

This email is my business email -- Please do not email me about forum
matters unless you intend to pay!
 
X

XinXin

Hi, I did a search in our database with the crash log you provided - there are other users running into the same crash. Could you please send me ([email protected]) a repro (workbooks + detailed repro steps)? I will investigate to see whether we can get it fixed in future updates.

Thanks,
XinXin Liu
Test Lead, Macintosh Business Unit, Microsoft
 
V

Vincent

Only by destroying the microsoft user data file in ~/documents/
The other methods did not work.
Best,
Vincent
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Excel crashes when entering numbers and formulas into cells 1
Excel crashes on deleting a number 1
Excel Crashing shortly after launch 3
Excel Instant Crash 9
Excel Crashes Very often 17
Excel 2008 and Apple Mail (Snow Leopardversion) - Crash when closing file 4
repeated crash when I start excel 7
CRASHING EXCEL :( 4

Top