MacOS 10.12 Sierra AFP Errors

[Tayler]

I just installed Sierra 10.12.1 (beta 1) and time machine is back up and running.

So did I and don't think it has fixed it

[mindphunk]

The only issue that could come up is people using invalid characters that only AFP supports for whatever god-awful reason.

To be honest: thats the only thing why I stick to AFP. I would love to change to SMB, but dont know what to consider when doing this step. SMB mangles some names of folders and files. I dont think that this setting is a truly legit solution.

I would prefer renaming all invalid names.

Or doing whatever to not risk data loss or corrupting anything...

Please tell me more about this naming issue. Helps me a lot, thanks!

[yawho]

Errors seems depending on Apps trying on writing data over AFP on Thirdparty Network-Storages. Obviously Apple has changed AFP Protocol Standards that aren't implemented by Synology and co by now.

No issues by writing files over AFP on macOS 10.12 clients peer to peer.

Can't comprehend the hole system crashing in a public release after all beta releases without any official information about this bug neither by apple nor by synology.

Meanwhile back on 10.11.

[teinsporn]

I just installed Sierra 10.12.1 (beta 1) and time machine is back up and running.

So did I and don't think it has fixed it

I also just tried 10.12.1 Beta (16B2327e) and the crashing issue is still present. It's not fixed for me.

[hvarink]

I have seen this error starting with many users when upgrading to El Capitan.
Using RS18016+ with BtrFS with snapshots. Macs crash when saving Numbers, Pages, TextEdit and other files.

There is however one reason for sticking to AFP. We have LDAP on Mac OS servers and Synology has a bug that will not allow LDAP users to use SMB, only AFP. (Local users are OK though). So I either have to wait for Synology to fix the LDAP/SMB error or replace my LDAP servers.

[PAIRaDICE]

I am having the same issues. Any application that attempts to save a file to my Synology drive will immediately cause the application and Finder to hang. By force quitting the application and relaunching the Finder, I am able to restart my Mac.

This only started when I upgraded to Sierra. I have also upgraded to today's beta release 10.12.1 (16B22333a) and the problem is still present.

I'm not an expert with networking so I will research how to switch from AFP to SMB. These are already files stored on OneDrive so I am hoping the file naming restrictions are already in place. I do recall renaming hundreds of files when I first switched to OneDrive.

[eaz]

My Mac is pretty useless right now!

Any MSoffice document or app that access the synology via afp will crash the mac and restart is required.
Terrible situation! wish I could go back. This feels like a piece of rubbish, unbelievable this passed the launch gate!
Apple/synology: Please please fix it.
SMB: I can connect, but as soon as I make a favourit, it replaces smb in afp: anyone knows how to change that?

[mindphunk]

SMB: I can connect, but as soon as I make a favourit, it replaces smb in afp: anyone knows how to change that?

I suggest deleting the login data for afp in the keychain app. Better everything which is related to the DS.
After that you will have to log in again, you can save the log in data in keychain again.

This did the job for my mac computers.

[mindphunk]

First:
Apple contacted me regarding my question in the apple discussion board. The iWork team asked me to share system diagnostics and how to reproduce the issue. Hopefully this might help for the future.

Second:
I found a workaround which helped me out of this situation.

Long story short:
Switch to SMB3. It is the new standard of macOS.

Long story long:
I had trouble with just launching SMB because a lot of directories and files were named with special characters like a slash. And I had a lot of folders with a space at the end or a period at the end of the name. This caused SMB to show these files and directories with so called mangled names. (There are workarounds to disable name mangling, but this caused my affected folders to be empty.) The files were named via AFP, which didn't cause any issues at all so far.
Of course it is impossible to seek and change the Terrabytes of files and directories manually.
I reseachred like 3 entire days, tested a lot and finally learned a lot:
I created a bash script which lists all the files and directories with bad names. I ran it via SSH. The list is formatted and saved to a .csv file which allowed me as a human to catch the paths and names easily to get an overview of the situation.
After that I changed the script, that it actually created another bash script which sequentially replaced the characters in the file and directory names with underscores and added a random number at the end to prevent overwriting data.
I created a .csv file again to check whether my plan worked – with an empty result.

I now have AFP and SMB running.
AFP is used for Time Machine backups, there is one single share on the DS for time machine backups only. Besides the admin accounts, only one time machine user has access to that share. The login data for that time machine user is saved on all Macs keychains. This is working perfectly.
All other network shares are accessed via SMB, the macOS default. I can just click the DS in the Finder's sidebar. Login data are stored in keychain as well, but obviously only for smb://synology.local.
Make sure to delete any login details related to the DS from keychain to ensure that Finder is only connecting via SMB.

That's it. Numbers, Word, TextEdit, Preview and the others are working perfectly again via SMB without the problem of crashing Finder while the process of saving a file.
The irony:
Connected via SMB, files and folders named with the same special characters which drove me crazy days ago, are not shown mangled. No Problems at all now. (I guess its because smb uses another character coding ..., what ever)


I hope this helped anyone. If you are facing the same problems just ask me. I can describe the procedure more detailed.

[eaz]

Thanks for the post, I cleared keychain and switched to smb, switched off mac protocol in the synology network settings.

System is stable, but I still have not solved the fact that upon logging in, for each share the name and password are requested (8 times enter in my case). Any suggestions how to solve this?

[mindphunk]

Thanks for the post, I cleared keychain and switched to smb, switched off mac protocol in the synology network settings.

System is stable, but I still have not solved the fact that upon logging in, for each share the name and password are requested (8 times enter in my case). Any suggestions how to solve this?

Did you delete your previous login details from keychain? If not: do it. After that you will be able to store it again in keychain and wont be asked again.

[dehsgr]

Yeah! Switching over to SMBv3, disabling smb signing and deleting all credentials did the trick. Further I had to change my password for NAS, as used special chars were preventing connection via SMBv3 from automounts.

But how to use TimeMachine with SMBv3 instead of afp? Am I missing sth? Think afp is prerequisite here?!

[eaz]

Did you delete your previous login details from keychain? If not: do it. After that you will be able to store it again in keychain and wont be asked again.

Yes, deleted all references from keychain, still it asks to confirm the password. Every time I login.

[dehsgr]

Yes, deleted all references from keychain, still it asks to confirm the password. Every time I login.

I noticed that it may be necessary to perform a reboot after deleting all passwords...

[dwmreg]

i thought about writing some bash or AppleScript scripts, but I'm rusty with that sort of thing these days. My coding focus led me elsewhere.
Can someone share their scripts for finding and correcting files or folders with odd characters or ones with spaces or periods at the end?