Finder search results are broken aliases

Got it I was looking at yours and not the entire thing, Thanks got it i think.

Michael Ewing Owner/Marketing Guy Brand Strategy & Creative EwingWorks Marketing & Promotions m: 404-307-1981 Atlanta, GA 30318 w: www.ewingworks.com e: michael@ewingworks.com

I can't seem to turn on indexing so get stuck with it displaying as disabled.

Am i missing something?

my-laptop:~ Homer$ mdutil -s /Volumes/companydata2

/Volumes/companydata2:

Indexing disabled.

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

/Volumes/companydata2:

Indexing disabled.

Two possibilities:

Erase any index that may exist and is corrupt by issuing the mdutil -E /Volumes/companydata2 command and then repeat the mdutil -i on /Volumes/companydata2 command to turn on indexing.

The other possibility, repeat the above commands BUT add the sudo command before it to gain higher privileges like this:

sudo mdutil -E /Volume/compnaydata2

sudo mdutil -i on /Volume/companydata2

The first time you issue the sudo command it will ask for your password (admin password). It DOES NOT type as you enter the password. That is normal and may confuse you. Just type it and press <return> to execute.

Good luck!

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.

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.

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.

Update - It looks like version 10.13.4 has fixed this issue. It is currently just in public beta though and I'm not sure when it will be released. Anyone have this kind of knowledge?

Other workarounds here have not worked for me.

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.

I opened a case with Apple Enterprise Support about this (see my previous post in the thread). The engineer on my case confirmed that it should be fixed in 10.13.4. Thanks for letting us know that the Beta fixed it already.

Hi I had the same problem! I managed to solve with the following procedure:

To fix this issue, create the following directory as root:

sudo mkdir -p / private / var / db / Spotlight-V100 / Volumes /

And then re-enable Spotlight indexing of that Volume:

sudo mdutil -i on / Volumes / name_of_your_volume

subsequently I managed to enable the search for spotlight on the network path!

Before any attempt to enable it using mdutil -i on / Volumes / myvolumes the result was always indexing disabled!

now if I look for a file and open it, it opens correctly!

Installed osx version: 10.13.3

Hi Emanuel.za,

What is the purpose of the command (creating the folder)?

sudo mkdir -p / private / var / db / Spotlight-V100 / Volumes /

Hi,

This response/solution is new to me. Can you explain what is the intent of the command?

sudo mkdir -p / private / var / db / Spotlight-V100 / Volumes /

You're in good hands... mine!

Luis T. Martell

Your Allstate agent

Remote

the only plausible reason I can think of is that spotlight uses that folder to insert indexes.
If I do not create that folder, I can not enable indexing on network locations. Creating that folder I can enable it !!

Hi

Just to say now I have downloaded the latest update from App Store 10.13.4 it has now fixed the issue.

Pleased it's done... Such a shame Apple took over half a year to fix.. Cleary not an OS to rely on for Business or critical home use at the present time.

Hi Paul,

I've experienced a similar problem with my Synology, but only with the "home" shared folder that actually redirects to /volume1/homes/username. If I mount homes/username directly, then I can open spotlight results correctly. I spoke with Synology support and they indicated this is a known issue with macOS but they have no intention of fixing it. The confusing part is that Synology support indicated that the problem is with network locations called "home" rather than with any other details of how they implemented the "home" network volume.

This problem is not only when operating on spotlight results in the "home" folder, but anytime Finder tries to alias anything in "home", e.g. when working with file/folder aliases in AppleScript.

Unfortunately, Synology sounds uninterested in a fix for this problem.

Here's my conversation with Synology support:

Them:

...

This is likely related to other known issues with the home directory in regards to the macOS. Because of the way that the macOS treats the home directory there are some network features that simply won't work.

For example Microsoft Office for Mac can't access files in the "home" shared folder.

Unfortunately, the only work around in cases like this is to simply not use the "home" shared folder.

Me:

... The KB article you linked to says '...Microsoft Office 2011 for Mac has problems accessing files stored in any network shared folder named “home”’. Regarding the “…any network shared folder named “home…” part, is it really the name of the network volume that is causing the problem? If that’s the case, then a custom name for each user’s “home” would suffice as a workaround, right?

Has Synology looked deeper into this issue?

...

Them:

In cases like this, yes the issues is simply the name of the network volume. You can create your own Custom Shared folders and name that whatever you'd like, and they should work. However, there is no way to change the name of the default home/homes shared folders.