Finder search results are broken aliases

When I use finder search in High Sierra to search files on remote volumes ( I have tried AFP, SMB and NFS), the search results seem to be broken aliases.

When I double click on one of the results I get a popup with the error "The alias “Filename.txt” can’t be opened because the original item can’t be found.".


When I select "Fix Alias" button and select the original file I get an error popup :The operation can’t be completed.

An unexpected error occurred (error code -8060).


This used to work fine on Sierra.


Paul

iMac, iOS 11

Posted on Oct 6, 2017 5:41 AM

Reply
Question marked as Top-ranking reply

Posted on Jan 23, 2018 3:00 PM

I had the exact same problem and I could fix it by erasing and rebuilding the spotlight index for all network shares affected.


What I did was:


1 - Rebooted my mac.

2 - After a clean boot, I connected to one of my network shares.

3 - Launched Terminal and checked the spotlight indexing status for the share using "mdutil -s /Volumes/networksharename".

If it's on, proceed to step 4.

If it's off, you have to enable it using "mdutil -i on /Volumes/networksharename". Once you do so, it'll start indexing, but I recommend performing the next step anyway.

4 - Still in Terminal, executed "mdutil -E /Volumes/networksharename" to erase and rebuild the spotlight index for that share.

5 - Launched Activity Monitor to check the indexing processes (mds, mdworker, etc). Once they were done, the problem was solved.


Hope it helps 😉

75 replies

Nov 10, 2017 9:38 AM in response to garz75

If anyone has contacted Apple Support on this can you share your case#? We should all create cases with Enterprise support and site the other customers that have this issue to put more pressure on Apple, which apparently doesn't see this as a big deal. When I talk to them they tell me to call Microsoft, because it must be a Microsoft error. I can't seem to find the number for enterprise support. Does anyone have it?

Dec 12, 2017 4:19 PM in response to paulz42

I have a Mac that is having the same issue with seeing search results from a brand new Windows server. The OS. on the iMac is. 10.13.1.


Not updating to 10.13.2 because another client is having issues moving folders on the server via SMB with 10.13.2. Finder crashes and has to be hard restarted to get the computer to work again.


Let me know if anyone finds a solution.

Jan 23, 2018 9:35 AM in response to paulz42

Ugh :-( Just discovered I have the same problem after moving all my documents and files to a Synology NAS, connected via SMB. Will try if the suggested tool works. Don't know why Apple doesn't repair this, it's asked around all over the internet. Also I notice that SMB is way slower then AFP; both are slower then using SMB from Windows or Linux machines. Oh well, I guess I have to learn to live with it... :-/

Feb 9, 2018 3:37 AM in response to JakemeisterGeneral

I am not a IT guy just a user, I have this issue myself: when you say run this: "sudo mdutil -E /Volumes/sharedvolumename" is that the thing to run in terminal or is there a name that I replace "sharedvolumename" with, because I get "

Michaels-MBP:~ EwingWorks$ "sudo mdutil -E /Volumes/sharedvolumename"

-bash: sudo mdutil -E /Volumes/sharedvolumename: No such file or directory

Michaels-MBP:~ EwingWorks$


so I ahve not idea waht this means or if I am doing it right.

Feb 9, 2018 4:16 AM in response to EWINGWORKS

Sorry I am going to ask one more question of you if it is okay: did it and this is result:

/Volumes/BIGDADDY:

2018-02-09 07:05:43.519 mdutil[37936:1089482] mdutil disabling Spotlight: /Volumes/BIGDADDY -> kMDConfigSearchLevelFSSearchOnly

Indexing disabled.

Michaels-MBP:~ EwingWorks$


Is says indexing disabled, will it dtart itself or do i need to do something to make it index again?

Feb 19, 2018 4:57 PM in response to ClicoMan

Hi ClicoMan

Much appreciated for helping out. : )

I tried with the sudo command and it does accept my password but still no success enabling indexing. see below.

Am I missing something?

Thanks


my-laptop:~ Homer$ sudo mdutil -E /Volumes/companydata2

Password:

/Volumes/companydata2:

2018-02-20 11:54:33.314 mdutil[2443:539960] mdutil disabling Spotlight: /Volumes/companydata2 -> kMDConfigSearchLevelFSSearchOnly

Indexing disabled.

my-laptop:~ Homer$ sudo mdutil -i on /Volumes/companydata2

/Volumes/companydata2:

Indexing disabled.

Feb 20, 2018 6:15 AM in response to homerjsimpson8

Hi homerjsimpson8,


Do you have read, write and execute privileges to this share? What file system is this share using? How do you connect to it? I ask that you think what other factors may be in play. For me the technique we have discussed resolved the problem for direct attached external drives and a few NAS devices I am connecting to using iSCSI. All these devices are using the NTFS file system. I run "Paragon NTFS for Mac" all my Macs.


But, I have one share drive inside a box called a "DVDFab Media Server" and that one will not work. It is a specialized device running the Android OS so I can understand that there has to be a supported infrastructure also for the indexing to work. I wish I could help more. Good luck.

Feb 20, 2018 12:47 PM in response to ClicoMan

Hi Clickman

I really appreciate your follow-up and can understand that the same conditions may not apply to all.

If there is anyone else in the community that can help that would be great.


It's an NTFS share on on Windows 2008 SBS server. Yes it is that old.

We have connected to the share using both SMB and CIFS protocols, connection is via Finder | Go | Connect to Server smb://server or cifs://server

We get the same results with either of the 2 protocols in the following 2 scenarios.


1st scenario: is a user's imac OS 10.13.3 without Paragon for NTFS and only Read & Execute, List Folder contents and Read access to share.


2nd scenario: my macbook pro OS 10.13.3 with Paragon for NTFS and Full Control to the same share logging on as Domain Administrator.

Mar 6, 2018 2:00 PM in response to paulz42

This is quite atrocious. Think about it. The only reason a Macbook user would need to connect to a windows server file share is because they are in a business environment. If Macbook users can no longer reliably access windows fileshares, do you think business will keep using Macbooks Pros? We have two Mac users, If they can no longer reliably use fileshares, then I will not be getting any more.

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 search results are broken aliases

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