How do I get rid of stubborn Error 403?

Question

Level 1

0 points

How do I get rid of stubborn Error 403?

I am setting up an iPad to be used in an out-of-the-house office where I see clients but need to use iCloud to be able to share certain functions with my home-office iMac. I did get it to the point where Events are shared (by deleting NetworkInterfaces.p.ist and com.apple.network.capdclient.configuration.plist) but the iMac iCal continues to have problems with Error 403. I have tried unchecking it is System Preferences and clicking the Delete this mac button and restarting (also tried shutting down) and rechecking the Calendar but as soon as I get the indication that the files are being moved to iCloud I get the errors. This next to last time iCal also "unexpectedly quit" and when I tried again it just let me know that again and asked if I wanted to reopen it which it wouldn't actually do and I had to Force Quit iCal to get out of it.

Would love to get help if I can dig through this myself as it is pretty difficult to drag the iMac into the Macstore (in the city no car). Any ideas on possible next steps?

Anita

iMac, OS X Mavericks (10.9.2)

Posted on Mar 6, 2014 7:27 PM

Reply

Answer 1

Linc Davis

Level 10

209,547 points

Mar 6, 2014 8:51 PM in response to almanuelnw

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. Click Utilities, then Console in the icon grid.

Step 1

Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select

View ▹ Show Log List

from the menu bar.

Enter the name of the crashed application or process in the Filter text field. 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 (command-V).

When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.

Please do not indiscriminately dump thousands of lines from the log into this discussion.

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

Step 2

In the Console window, look under User Diagnostic Reports (not "Diagnostic and Usage Messages") for crash reports related to the crashed process. The report name starts with the name of the process, and ends with ".crash". Select the most recent report and post the entire contents — again, the text, not a screenshot. 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 not helpful.

Reply

Answer 2

almanuelnw Author

Level 1

0 points

Mar 6, 2014 9:22 PM in response to Linc Davis

Step 1:

3/6/14 7:12:39.679 PM Calendar[529]: Unable to simultaneously satisfy constraints:

(

"<NSLayoutConstraint:0x6000004835c0 H:|-(2)-[canvasFrame] (Names: canvasFrame:0x6000001af7a0, '|':CalUIWeekContentView:0x600000323ac0 )>",

"<NSLayoutConstraint:0x600000483570 H:[canvasFrame]-(12)-| (Names: canvasFrame:0x6000001af7a0, '|':CalUIWeekContentView:0x600000323ac0 )>",

"<NSLayoutConstraint:0x608000483a20 'NSView-Encapsulated-Layout-Width' H:[CalUIWeekContentView:0x600000323ac0(0)]>"

)

Will attempt to recover by breaking constraint

<NSLayoutConstraint:0x600000483570 H:[canvasFrame]-(12)-| (Names: canvasFrame:0x6000001af7a0, '|':CalUIWeekContentView:0x600000323ac0 )>

Set the NSUserDefault NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints to YES to have -[NSWindow visualizeConstraints:] automatically called when this happens. And/or, break on objc_exception_throw to catch this in the debugger.

3/6/14 7:19:44.909 PM com.apple.launchd.peruser.501[160]: (com.apple.iCal.27312[529]) Exited: Terminated: 15

Step 2:

Identifier: com.apple.iCal

Build Info: iCal-1841000000000000~2

21 com.apple.iCal 0x000000010b46f09d 0x10b46d000 + 8349

8 com.apple.CalendarUI 0x00007fff8b296310 __71-[CalUIMigrationController periodicallyCheckForLocalToServerMigration:]_block_invoke + 224

Logical CPU: 0

0x10b46d000 - 0x10b75ffff com.apple.iCal (7.0 - 1841) <7DF2A368-E65F-340C-9F82-F5940B01EC12> /Applications/Calendar.app/Contents/MacOS/Calendar

0x7fff8b229000 - 0x7fff8b24ffff com.apple.iCalendar (7.0 - 162) <2B270453-6FFD-3AD3-B40B-51715BE66B33> /System/Library/PrivateFrameworks/iCalendar.framework/Versions/A/iCalendar

0x7fff904fe000 - 0x7fff90551ff7 com.apple.ical.EventKit (2.0 - 154) <34C0DAD6-763D-3760-93BA-54C5DC7D81DA> /System/Library/Frameworks/EventKit.framework/Versions/A/EventKit

0x7fff9212b000 - 0x7fff9213efff com.apple.iCal.CalendarDraw (7.0 - 1726) <F60180A8-4EFC-3A4C-859D-9411ADCAF9C5> /System/Library/PrivateFrameworks/CalendarDraw.framework/Versions/A/CalendarDra w

Reply

Answer 3

Linc Davis

Level 10

209,547 points

Mar 6, 2014 9:57 PM in response to almanuelnw

Please post the whole crash report.

Reply

Answer 4

almanuelnw Author

Level 1

0 points

Mar 6, 2014 10:57 PM in response to Linc Davis

What I posted as Step 2 was the entire text of the first of 3 crash reports under User Diagnostic Reports. It was titled: Calendar_2014-03-06-190830_Anitas-Imac.crash

In addition there were the two following reports:

Finder_2014-03-02-214353_Anitas-iMac.crash which said only:

LogicalCPU: 1

Finder_2014-03-02-214954_Anitas-iMac.crash which said only:

LogicalCPU: 0

Reply

Answer 5

Linc Davis

Level 10

209,547 points

Mar 7, 2014 6:44 AM in response to almanuelnw

Please take each of the following steps that you haven't already tried. Stop when the problem is resolved. Back up all data before making any changes.

Step 1

Delete the calendar account and add it back. If it's an iCloud account, all you have to do is uncheck and recheck the box marked Calendars & Reminders in the iCloud preference pane.

Step 2

You may be trying to access an invited event that you declined, or one that was rescheduled after you accepted it. The error message should give you a clue as to what it is. If the calendar is on iCloud, you can bring up the Calendar on the website and select

Show Declined Events

from the popup menu with the gear icon in the upper right corner of the page. The declined events will appear in gray, and one of them should match what's shown the error message. [Credit for this solution to ASC member Psi.]

Step 3

If you get the error when trying to accept an invitation in an email attachment, it's because the organizer didn't properly create the event.

Step 4

Follow the instructions in this support article.

Reply