Finder crashes when entering time machine

Since the upgrade to el capitan, I've been unable to enter time machine. The initial screen is displayed for a few seconds and then it disappears. The console reports that Finder has crashed and a crash log is produced. In a nutshell the error being reported is:


Application Specific Information:

*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[__NSArrayM objectAtIndex:]: index 0 beyond bounds for empty array'

terminating with uncaught exception of type NSException


I have since run first aid on the drive in question (and it is a network drive). It seems like backups are happening, but I can't see them and if I can't restore from them, they're rather pointless !!!


Any one with any ideas and/or clues as to what I should be looking for ?

iMac, OS X El Capitan (10.11)

Posted on Oct 2, 2015 8:39 AM

Reply
30 replies

Oct 9, 2015 10:33 PM in response to joe.dmello

Just a "me, too", although in my case I have no network drives. Other than that I have the identical problem with the identical crash report.


I've run Disk Utility first aid on all drives (including the Time Machine drive) and even tried dismounting the not-startup drives. No difference.


This is a mid-2012 Macbook Pro, just updated from Yosemite to El C[r]apitan.

Oct 13, 2015 4:08 AM in response to Michael Rosenstein

Yes, I've done the same (in that I've used a new user to enter time machine). However, I'm not sure exactly how that works because I am assuming that Time Machine is backing up changes made to a specific user's files. Therefore, if I normally am logged in as user A, and then log in as user B, I am not sure if user B can access or restore files from user A's backup. I've also found issue with my iPod (in that iTunes refuses to sync telling me there isn't enough room on it) - but that may be a separate issue altogether. I am resigned to (eventually) doing a clean install and I suspect that when I've done that all my VMWare Fusion machines are going to break.


What I (we) really need is an explanation as to what is causing the problem because I cannot understand what the crash log is telling me.

Oct 14, 2015 12:10 PM in response to joe.dmello

The following fixed the same problem for me:


1. log off your user-account

2. when the login-screen appears, log in while pressing the SHIFT key.

This will prevent applications, etc. to start

3. open a finder window showing your home-folder (SHIFT-CMD-H)

4. use "view options" (CMD-J) to make sure that you can see your Library-folder

5. open the terminal (under Application -> Utilites)

6. type "ls -l" to make sure, that this is your user-account and that you see a folder named "Library"

7. type "sudo -s" and enter the password.

8. type "ls -l" to make sure, that this is your user-account

9. type "mv Library Library_old"

10. wait until the system recreates a new Library-folder

11. log off and log in again while pressing the SHIFT-key

12. MacOSX tells you the usual stuff when creating a user-account. Don't panic. 😉

13. open the terminal again

14. type "sudo -s" and enter the password.

15. type "ls -l" to make sure, that this is your user-account

16. type "mv Library Library_new;mv Library_old Library"

17. log off and log in again while pressing the SHIFT-key

18. Your time-machine should work now

19. log off and log in again as usual

20. Your time-machine should still work

21. You can now delete Library_new


Why i did this as root?

Because i wasn't able to move the Library-folder by using the finder or renaming it using the Terminal-programm

Oct 14, 2015 10:06 AM in response to Yannis Haralambous

I'm not sure what triggered this problem, but the problem seems to have its roots in something, El Capitan changes during the initial account-setup.

So I triggered a new account-setup with a fresh Library-folder while conserving the existing Library-folder.


I did this, because time-machine did work with other or newly created user-accounts.


I don't understand why you still lost your iStat-menus:

I tried to prevent such effects by using the SHIFT-key during login, which should prevent apps, etc. from starting and causing problems like the one you noticed.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Finder crashes when entering time machine

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