![]() When I asked her to open the file in question, Word instantly crashed with an EXC_BAD_ACCESS error. My user had been editing a file when Word initially crashed. After that, Word launched without a single error. Then I went into /Users/username/Library/Saved Application State and moved the folder to the folder on the user’s desktop where I had been storing the other files that I had moved. I stopped at that point and just thought through the process for a minute or so. Why? How? All the work I had done should have cleared out Word’s listing of recent files. But this time, I caught a small “opening file” screen that was gone in an eyeblink because Word crashed immediately after the screen appeared. While still booted from the utility NetBoot, running DiskWarrior and a permissions repair on the user’s boot drive to make sure all my bases were covered.Īfter rebooting from NetBoot back to the user’s boot drive, I asked my user to log in again and relaunch Word. Booting from a NetBoot utility disk and clearing the contents of the following cache folders on the user’s boot drive:ĥ. Renaming /Users/username/Library/Application Support/Microsoft to /Users/username/Library/Application Support/Microsoft_backup to force the OS to create a new /Users/username/Library/Application Support/Microsoft folder with default settings.Ĥ. Moving all of the various com.microsoft preference files and the Microsoft folder from /Users/username/Library/Preferences to the folder I had set up on the Desktop.ģ. Result: Word launched fine and without errors while logged in from the local admin.Ģ. Logging in as my local administrator to confirm that issue seemed to be confined to the user’s account. I then spent the next hour doing the following:ġ. They hadn’t, Word had crashed before being able to detect that those files were not there. I double-checked to make sure that both the files I had moved had not recreated themselves. Then I logged the user out, asked them to log back in and had them relaunch Word. Users/username/Library/Application Support/Microsoft/Office/User Templates/Normal.dotm So this time, I moved the following files to a new folder that I created on the user’s desktop: When this error has cropped up in the past, I’ve fixed it in the past by removing Word’s Normal.dotm template from /Users/username/Library/Application Support/Microsoft/Office/User Templates or removing the com.microsoft preference files for the affected application from /Users/username/Library/Preferences. None of her other Office 2011 applications were exhibiting the behavior it was specific to Word 2011. One of our users sent in a ticket to report that Word 2011 on her laptop kept crashing with an EXC_BAD_ACCESS error. I try to open either WOrd or Excel and get a dialog box informing me that "Microsoft Excel (or Word) has encountered a problem and needs to close." The Error Report displays as follows, "Microsoft Error Reporting log version: 2.0Error Signature: Exception: EXC_ARITHMETIC Date/Time: 21:07:00 +0000 Application Name: Microsoft Excel Application Bundle ID: Application Signature: XCEL Application Version: 14.25 Crashed Module Name: Microsoft Excel Crashed Module Version: 14.25 Crashed Module Offset: 0x00122309 Blame Module Name: Microsoft Excel Blame Module Version: 14.I had an interesting issue crop up yesterday. For a while now, maybe 2 weeks, I have been unable to retrieve my documents in these appications. I recently (maybe 8 - 12 weeks ago) updated my Operating System (OS) to macOS High Sierra 10.13.3. I am using Microsoft Office For Mac on my MacBook Pro (MacBook Pro Retina, 15-inch, Mid 2014). Technician's Assistant: Anything else you want the Phone Expert to know before I connect you? Microsoft Error Reporting log version: 2.0Error Signature: Exception: EXC_BAD_ACCESS Date/Time: 15:57:11 +0000 Application Name: Microsoft Word Application Bundle ID: Application Signature: MSWD Application Version: 14.19 Crashed Module Name: Microsoft Word Crashed Module Version: 14.19 Crashed Module Offset: 0x00278fc3 Blame Module Name: Microsoft Word Blame Module Version: 14.19 Blame Module Offset: 0x00278fc3 Application LCID: 1033 Extra app info: Reg=en Loc=0x0409 Crashed thread: 0 Technician's Assistant: What application are you using? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |