Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Calendar Crashing on Startup

When I try to light up Calendar on my MB Pro, it tries to update subscriptions. It goes through a few and then crashes the program. I never have the chance to review or remove a subscribed calendar. I tried reloading the system software but that didn't help. I'm not sure where to find the subscribed files to remove them manually. Any suggestions would be appreciated.


Running 10.10.3 software.


Thanks,

Bruce

MacBook Pro (Retina, 13-inch, Late 2013), OS X Yosemite (10.10.3)

Posted on Jul 2, 2015 10:37 AM

Reply
Question marked as Best reply

Posted on Jul 2, 2015 12:29 PM

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES All Messages

from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Some private information, such as your name, may appear in the log. Anonymize before posting.

Step 2

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION User Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

6 replies
Question marked as Best reply

Jul 2, 2015 12:29 PM in response to brucefromboca raton

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES All Messages

from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Some private information, such as your name, may appear in the log. Anonymize before posting.

Step 2

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION User Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

Jul 2, 2015 2:06 PM in response to Linc Davis

Thanks, Linc. Here's the Crash log code:


Process: Calendar [714]

Path: /Applications/Calendar.app/Contents/MacOS/Calendar

Responsible: Calendar [714]

9 com.apple.ical.EventKit 0x00007fff914cf1c6 -[EKCalendarStoreBackingStore _emptyCache] + 47

10 com.apple.ical.EventKit 0x00007fff9150d7b2 -[EKCalendarStoreBackingStore initWithSourceFilters:includeEnabledDelegates:asyncWithCompletion:orWithExistin gStore:] + 717

11 com.apple.ical.EventKit 0x00007fff9150d495 -[EKCalendarStoreBackingStore initWithSourceFilters:includeEnabledDelegates:asyncWithCompletion:] + 60

9 com.apple.CalendarFoundation 0x00007fff8b31e4b1 -[CalLogASLWriter write:] + 201

10 com.apple.CalendarFoundation 0x00007fff8b30057d __30-[CalLogNode processEnvelope:]_block_invoke + 418

13 com.apple.CalendarFoundation 0x00007fff8b3003b6 -[CalLogNode processEnvelope:] + 127

16 com.apple.CalendarFoundation 0x00007fff8b3002f0 __32-[CalLogMaster processEnvelope:]_block_invoke + 126

0x10f6b5000 - 0x10f940fff com.apple.iCal (8.0 - 2034.9) <6220C57E-7240-3AD7-8CB2-A912B9258FE8> /Applications/Calendar.app/Contents/MacOS/Calendar

0x7fff862c6000 - 0x7fff862eeff7 com.apple.iCalendar (7.0 - 201) <9E2DD3B2-9A7A-30A2-9C66-4080B49AAA95> /System/Library/PrivateFrameworks/iCalendar.framework/Versions/A/iCalendar

0x7fff88027000 - 0x7fff88141fff com.apple.CalendarUI (8.0 - 306.9) <1602697E-EBBA-30D4-A40E-BA89B53DC720> /System/Library/PrivateFrameworks/CalendarUI.framework/Versions/A/CalendarUI

0x7fff8b2fd000 - 0x7fff8b32fff7 com.apple.CalendarFoundation (8.0 - 295.1) <E61E3EB8-6278-34E0-A0A7-C553F0E7BB9F> /System/Library/PrivateFrameworks/CalendarFoundation.framework/Versions/A/Calen darFoundation

0x7fff8c5a5000 - 0x7fff8c5beff7 com.apple.CalendarAgentLink (8.0 - 250) <0F3CCA9C-645D-3A1A-A959-F4F8D31F9B1A> /System/Library/PrivateFrameworks/CalendarAgentLink.framework/Versions/A/Calend arAgentLink

0x7fff8fc21000 - 0x7fff8fe7fff7 com.apple.CalendarPersistence (8.0 - 321.7) <8AC7AA48-6722-3A59-ADDE-FB76EFD75FF5> /System/Library/PrivateFrameworks/CalendarPersistence.framework/Versions/A/Cale ndarPersistence

0x7fff93ac2000 - 0x7fff93addff7 com.apple.CalendarUIKit (1.0 - 66) <D5E3AEDC-3B86-3A54-9E89-CDB9E6F3B1B6> /System/Library/PrivateFrameworks/CalendarUIKit.framework/Versions/A/CalendarUI Kit

0x7fff94c14000 - 0x7fff94c2bfff com.apple.iCal.CalendarDraw (8.0 - 1833) <6D6BA2D0-BBC7-355F-B693-C420988DDB92> /System/Library/PrivateFrameworks/CalendarDraw.framework/Versions/A/CalendarDra w

Jul 2, 2015 3:13 PM in response to brucefromboca raton

Back up all data. If you have iCloud calendars, archive them by following the instructions on this page under the heading "Downloading a calendar from iCloud.com." All you need is a web browser, not the Calendar application. Do the same with any other network calendars you have, if possible.

Before taking each of these steps, quit (force quit if necessary) the application. After taking the step, relaunch and test. When the problem is resolved (or when you complete Step 3 without resolving it), stop and close the Library folder.

Step 1

Hold down the option key and select

Go Library

from the Finder menu bar. From the folder that opens, move these items (some may not exist) to the Trash, leaving the Library folder open:

Calendars/Calendar Cache

Calendars/Calendar Cache-shm

Calendars/Calendar Cache-wal

Step 2

Move these files from the Library folder to the Desktop (again, some may not exist):

Containers/com.apple.CalendarAgent (and any others with a name beginning in "com.apple.Calendar")

Containers/com.apple.iCal (and any others with a name beginning in "com.apple.iCal")

Preferences/com.apple.CalendarAgent.plist

Preferences/com.apple.iCal.plist

If the problem is resolved, you may be able to put back some of the items you moved in this step, relaunching and testing after each one. Eventually you may find the one that caused the problem; delete it. Recreate your settings as necessary.

If the problem still isn't solved, put back each of the items you moved in this step, overwriting the one that may have been created in its place. You don't have to put back the files you moved in Step 1.

Step 3

Move this folder to the Desktop:

Calendars

Note: you're not moving the Calendars application; you're moving a folder named "Calendars". If there's no change, put the folder back where it was.

If the problem is resolved after you move the Calendars folder, the event database is corrupt. You have these choices:

Restore the folder from a Time Machine snapshot or other backup that predates the corruption.

Use a third-party application such as Calendar Cleaner to try to repair the database.

For network calendar accounts, such as iCloud, all you should need to do is re-enter them in the preferences. For subscribed calendars, you only need to re-subscribe.

Calendar Crashing on Startup

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.