Files cannot be unlocked on AFP Share on Lion Server

I have an environement with a Mac Pro Server (10.7.4) running as an Open Directory Master, DNS, with AFP file sharing enabled. All clients are running 10.7.4, none are bound to the domain and all home folders are local on the users machine. The users simply have an account in OD that they use to access a file share. The file share is "Public" in that the permissions are fully liberalized so that all users in the domain have read/write access. Whenever a user edits a Pages, Keynote, Numbers, Text Edit (anything that supports versions) and then saves the file, the next user to access the document finds that the document is locked. They cannot unlock it and must create a duplicate. Only the original user that opened the document can reopen it without facing the lock and having to duplicate it. Anyone have any ideas as to what might be causing this? Thank you.

How about setting ACL's for the share?

Similar Messages

Spotlight/Searching does not work for afp shares in Lion

Hi
I cannot search for files in Finder on my afp shares. The server and client are both running Lion 10.7. Anything I am missing? Should this work or not? I'm so used to Spotlight I would really hate it if this isn't supported for afp shares.
Thanks NEI

Acrobat catalog, PDX, files only work from local or network drives.
From Acrobat's Help;
"Moving collections and their indexes"
"You can develop and test an indexed document collection on a local hard drive and then move the finished document collection to a network server or disk."

Trouble connecting to Lion server AFP shares after changing server's hostname

Hello everyone,
I recently changed hostname of my Lion server box (via Server application) and now my clients are having a problem when trying to connect to its AFP shares via aliases. It takes 160 seconds of "resolving alias to <sharename>" before it finally works. Aliases were created by navigating to the server, connecting with "Connect As", providing valid credentials, then navigating one level up and dragging the share icon (blue disk with three white people outlines) to the Desktop with Option-Command.
What is interesting, if I create a new account on a client machine, create an alias, and click on it - it works without any delay, as it was for the clients that are having problems now; so I'm assuming some details about the previous server name got cached somewhere.
The clients with long delay problems can access the shares quickly if they click on the server in the Finder window drawer, then "Connect As" and provide their login credentials - it works instantly then.
I've been digging around quite a bit (deleting Keychain saved Network passwords for any and all references to the server I could find), and also by looking at kerberos logs on the server. What is interesting, the newly created clients I mention above who don't have delay with connecting, don't leave any records in the kerberos log file; but the ones that have 160 second delay do - there's nothing for 160 seconds, and then there is a flurry of activity, as the connection is finally established.
When a client who has trouble connecting uses the "Connect As" method described above, entries in the Kerberos log are created instantly when client clicks connect.
Probably also worth noting that renaming of the server was related to me setting up Open Directory on it.
Any pointers would be greatly apprecited.

I experienced almost exactly the problems you described. I also found that connecting via command line using mount_afp worked right away... and once the connection is established, mounting via finder was super fast.
Tried all kinds of craziness on the client, even a full Time Machine restore.
Tried fixing Open Directory.
I was absolutely stumped by what was happening, but then thought, Hmm. I'm wondering if it's related to MobileMe going down? I noticed it started to happen after July 31...
Success! That was it! Signing out of MobileMe in System Preferences made everything work the way it should!
CDPlayer2: check if the clients are signed in to MobileMe, and if signing out fixes things - I'd appreciate it if you could post your results. Thanks.

Windows can't connect to shares on Lion Server

I can't connect any windows machines (XP, Vist, or 7) to a Mac Pro running Lion Server. When attempting to connect, the windows user is prompted for credentials, and nothing entered in this box works even the server admin account info, once entering account credentials, it comes back with NAMEOFWINDOWSCOMPUTER\USER as if it's trying to sign into a domain, which we don't have domains.
I can't seem to find anything relevent when searching...

There are a couple things you can try:
1.\ go to the apple server, sys prefs, sharing, selct file sharing and then select option. from there make sure the both check boxes are selected. then select done.
2.\ while you are there, in the shared folders section, selct the folder you would like to share (or add if its not) and make sure the user is in the users pane that you want to share the folder with.
3.\ restart your windows machine to make sure it forgets any passwords you may have put in.
4.\ if it still doesnt ask for a user account go to map network drive. and select the option to put another username and password in. for the user name user SERVERNAME\username - ensure the servername is in CAPITAL letter...
hope this helps...

Save as dialog not showing files on a AFP share in CS2

I have a user who is not able to see any files or folders on an AFP share (SFM on Windows 2003) when attempting to Save As. The files are visible in the finder, terminal, it is not a permissions issue, and I have trashed permissions. Any ideas? Are there hidden files on the share that need to be trashed?
10.4.10, 2.66 Mac Pro, AD user
Thanks!

Open the Script Editor in the /Applications/AppleScript/ folder, and use this script to make all files visible.
(22547)

User can't access afp shares

About once every other day one of my users losses the ability to log onto afp shares on the server.
In the Server App under Users his "Allow user to log in" tick box has become unticked. If I tick that and save, everything is fine for a day or so then it becomes unticked on its own again. As usual with computers in generally becomes unticked at a crucial point when everyone is busy !!
Any help would be appreciated. I can see nothing unusual in the logs and I have tried reseting his password.

I just went from 10.8.5 to 10.9.2 and have this same problem. I first noticed in DNS 127.0.0.1 was removed during install and not put back. From there I got everyhting working except afp.
Error message is:
Kerberos fail: gss_acquire_cred major status_value <458752> minor status_value <0>
major error <1>: No credentials were supplied, or the credentials were unavailable or inaccessible.
minor error <1>: unknown mech-code 0 for mech unknown
Trying:
sudo sso_util configure -r REALM_NAME -a diradmin afp
/Local/Default
/LDAPv3/127.0.0.1
Creating the service list
Creating the service principals
OSStatus CreateKerberosPrincipals(CFStringRef, CFStringRef, const char *, CFMutableDictionaryRef, Boolean): unable to find admin record: -1
Creating the keytab file
Configuring services
Any solutions out there? This is pretty critical for TM backups around the office.

AFP automount sharing broken in Lion Server?

Network rundown:
Mac Mini running Server
two MBPs (one upgraded to Lion, the other still running Snow Leopard)
The Mini is the OD Master for the three Macs and runs a number of services (Mail, Web, Wiki, VPN, etc.). The important service for this thread is that it serves out three shares via AFP, configured to be automounted on the two laptops. Normally all three shares are set up (via Workgroup Manager / Directory Utility) to use the Kerberos v2 UAM; however, for testing purposes I've temporarily adjusted the UAMs as follows:
/Groups -> afp://myserver/Groups
/Volumes/Attic -> afp://;AUTH=No%20User%20Authent@myserver/Attic
/Volumes/Multimedia -> afp://;AUTH=Client%20Krb%20v2@myserver/Multimedia
When the Mini is running Snow Leopard Server (10.6.8), the automounting behavior works as expected when connecting from a laptop without a valid Kerberos ticket:
lionmbp:~>klist -f
klist: krb5_cc_get_principal: No credentials cache file found
lionmbp:~>ls /Groups
ls: Groups: Invalid argument
lionmbp:~>ls /Volumes/Attic
[snip - file listing]
lionmbp:~>df -h /Volumes/Attic
Filesystem                                Size   Used Avail Capacity Mounted on
afp_000000004oMw0oYHtK4AvcMP-1.2d00010a 466Gi 277Gi 189Gi    60%    /Volumes/Attic
lionmbp:~>ls /Volumes/Multimedia
ls: Multimedia: Invalid argument
and then with a valid Kerberos ticket:
lionmbp:~>sudo umount /Volumes/Attic
Password:
lionmbp:~>df -h /Volumes/Attic
Filesystem    Size   Used Avail Capacity Mounted on
map -static    0Bi    0Bi    0Bi   100%    /Volumes/Attic
lionmbp:~>klist -f
[snip]
Sep 19 23:27:17 Sep 21 23:27:17 FPRIA krbtgt/DOMAIN@DOMAIN
lionmbp:~>ls /Groups
[snip - file listing]
lionmbp:~>ls /Volumes/Attic
[snip - file listing]
lionmbp:~>ls /Volumes/Multimedia/
[snip - file listing]
However, after upgrading the Mini to Lion Server (10.7.1), attempting to automount the same shares does not work at all, regardless of whether a valid Kerberos ticket exists or not
lionmbp:~>klist -f
klist: krb5_cc_get_principal: No credentials cache file found
lionmbp:~>ls /Groups
ls: Groups: Authentication error
lionmbp:~>ls /Volumes/Attic
ls: Attic: Input/output error
lionmbp:~>ls /Volumes/Multimedia/
ls: : Invalid argument
lionmbp: /usr/bin/kinit
[snip - provide password]
lionmbp:~>klist -f
[snip]
Sep 19 23:15:09 Sep 21 23:15:09 FPRIA krbtgt/DOMAIN@DOMAIN
lionmbp:~>date
Mon Sep 19 23:17:03 CDT 2011
lionmbp:~>ls /Groups
ls: Groups: Authentication error
lionmbp:~>ls /Volumes/Attic
ls: Attic: Input/output error
lionmbp:~>ls /Volumes/Multimedia/
ls: : Invalid argument
Anyone else encountering the same issues with AFP on Lion Server? Is AFP simply broken, or is there some poorly documented configuration/troubleshooting procedure that can resolve this issue?
Notes:
I only tried the automounting from the Lion MBP, I would expect that a Lion <-> Lion AFP connection would have fewer issues than Snow Leopard <-> Lion
The issue originally presented itself several weeks ago when I atttempted to upgrade the server; this AFP problem was a showstopper so I restored SL from a backup. I have since been testing by cloning the server drive to a USB drive, booting from it, and running the upgrade there.
In performing the Lion Server upgrade, I follow all the defaults. The server is booted off the USB drive to ensure it is in a working state before starting the upgrade. The only post-upgrade changes are to run Software Update (mainly to capture the recent security update) and then to follow the single signon instructions posted here

Some more testing hints in the direction of the problem:
aragorn:~>kinit -l 48h -r 48h -p -f [email protected]
[email protected]'s Password:
aragorn:~>klist -fCredentials cache: API:1501:10
        Principal: [email protected]
Issued           Expires        Flags    Principal
Oct 1 17:05:53 Oct 3 17:05:50 FPRIA krbtgt/[email protected]
aragorn:~>ls /Volumes/Multimedia
ls: Multimedia: Invalid argument
aragorn:~>mkdir /tmp/test; chmod 777 /tmp/test
aragorn:~>sudo mount_afp "afp://;AUTH=Client Krb [email protected]/Multimedia" /tmp/test
mount_afp: AFPMountURL returned error -50, errno is -50
Looking in MacErrors.h reveals
paramErr                      = -50, /*error in user parameter list*/
That both ways of mounting AFP seem to be complaining of argument/parameter errors indicates something isn't being passed across the network correctly or is not being parsed properly on one end or the other. At the moment my dtrace-fu isn't strong enough to delve into this more deeply.
With 10.7.2 due out soon, I think I'll wait to see if Apple engineering caught this already. If not, I'll raise a bug ticket.

Files copied from AFP share point are unwriteable by client

This is the same issue as: http://discussions.apple.com/thread.jspa?messageID=8044984
Has anyone found a fix yet? Basically, when copying files from an AFP server, Leopard is not having the file inherit the permissions of the parent folder. It is inheriting the permissions of the file within /Volumes.
I am accessing an AFP share point on a server that has files that are 644 (readable by everyone, but only writable by the owner). I am not the owner. When viewing the AFP volume on my client within /Volumes/whatever the permissions appear to be 400 (unwriteable by the owner, no access to anyone else). When I copy the file over to desktop, the permissions remain as 400 when they should obviously be 600.
What does this mean? Even though I am NOW the owner, and it is on MY desktop, I am unable to write to the file unless I chmod it. Very, very annoying and this behavior is unique to Leopard. Tiger does not mangle the permissions.
The server is ubuntu-8.10-server running Netatalk.
The test clients are Leopard 10.5.5 and Tiger 10.4.11
On the server:
$ pwd
/srv/www
$ ls -l
-rw-r--r-- 1 www-data www-data 1024 2008-11-23 23:29 test.doc
On the Leopard client:
$ pwd
/Volumes/www
$ ls -l
-r-x------@ 1 sauce staff 1024 Nov 23 23:29 test.doc
$ cp test.doc ~/Desktop
$ ls -l ~/Desktop/test.doc
-r-x------@ 1 sauce staff 1024 Dec 7 00:21 /Users/sauce/Desktop/test.doc
Message was edited by: iSauce

I don't believe this is a problem of leopard in general. i can not reproduce this behavior with any of my afp shares. no matter how i connect (as an owner or as a guest) after I copy something to the desktop it gets standard 644 (not 600) permissions.

I have an old mpg video file, taken with a very early model "smart phone", that opens and plays fine in my newly "rebuilt" iPhoto library. I cannot open, edit it or share it with any other software. How can I fix it, to be able to do anything with it?

I have an old mpg video file, taken with a very early model "smart phone", that opens and plays fine in my newly "rebuilt" iPhoto library. I cannot open, edit it or share it with any other software. How can I fix it, to be able to do anything with it?
Detail:
I've recently purchaced a 4TB Thunderbolt drive to store my "vast" music and photo libraries. iPhoto had an issue reading the moved library, so I bought and used iPhoto Library Manager to "rebuild" it. Apart from much of the original data such as date taken & camera used etc, it appears to be working well. The aforementioned mpg video was taken some 9 years ago, using an early model "iMate" smart phone, and opens and plays fine on iPhoto, but I cannot open it with anything else, (I've tried iMovie, VLC players, Wondershare and Handbrake) nor can I share it. I just want to edit it, and share it with family.
Any help would be appreciated...

No - not iMovie, VLC, Wondershare or Handbrake... Quick time starts with a "CONVERTING", then I get
I've looked at the "tell me more" links, tried downloading some of the movie players there. I'm begining to think the file is corrupt.
Thanks for getting back to me again though - appreciate it...

Files Placed on AFP Shares Create Accompanying "._" Files

We have several new iMacs running Snow Leopard, all patched up to 10.6.5. They connect to our OS X Server 10.3.9 using AFP. Whenever they place, say, an EPS file on the server...
Some_File.eps
...an invisible companion file will be placed in the same directory, beginning with a "dot-underscore":
.SomeFile.eps
I've read of similar things happening with SMB shares (something about alternative data streams), but this is AFP, and it's only our Snow Leopard clients that behave this way.
This is more than an inconvenience; we have automated processes that are getting bogged down by these files.
Extensive searching of these forums and elsewhere has revealed no clues.

Similar problem with more detail. Very frustrating.
A few weeks ago, we upgraded most of our workstations from Leopard to Snow Leopard. We have a G5 XServe running OS X Server 10.3.9 (Panther) with HFS-enabled mounts. We connect to it via AFP. SMB is not enabled. It's been running for years without issue.
After upgrading clients, any file we download from a website via any 10.6.6 Mac and either copy to or save directly to the server results in an invisible (hidden) "._.ext" file. (This may be happening to other files copied from the Snow Leopard workstations, but it definitely does not happen to all of them.)
Further, I did a test comparing the only remaining client that is still on Leopard (10.5) with clients on Snow Leopard. The 10.5 client test does not yield the invisible file, while the 10.6 client test does.
I have found that downloading a file and duplicating it before copying it to the server does not solve the problem. However, opening the file and doing a Save As... before copying it to the server does solve the problem.
Is this a compatibility issue between 10.6 clients and 10.3 server? Is there a fix? Any ideas?
EDIT - I forgot to mention that it is causing problems within SVN versioning repository working copies. Otherwise I wouldn't worry about it.
Any help appreciated. Pulling my hair out here.
Thanks, Fritz
Message was edited by: Fritz Green

Copy from AFP share to AFP share (via VPN-Connection) - stupid?

Hi there
We set up an OS X server in a remote facility and are connecting to it over a VPN connection (Netgear Firewall).
Everything works fine, there's only one annoying issue: if I want to copy a file from a mounted AFP share (share1) to another mounted AFP share (share2) - both of them residing on the same server - it seems to me that the files are being copied first to my local client and then back to the server again - instead of being copied directly from and to the server...
Is there anything I can do about this issue or am I wrong? Is this a so called "feature" of the Finder itself?
Thanks for any suggestions and regards
Roman

Thanks for your thoughts about higher vs. lower latency networking - I totally agree. It might be a quite uncommon setup; as the server is being "housed" in a datacenter with quite tough restrictions: not only do they charge us for the power consumption, but also for the traffic being generated - which is 250 GB a month. They're providing an uplink with 10mbps (guaranteed), burstable to 100mbits.
Anyway, we're interested in keeping traffic low - hard to do if we cannot let end users do "common" tasks like moving files from one folder to another (of course, its a sharepoint - but they don't care).
What I'm looking for? Well, I think it will take hours to find out which part of the setup (AFP implementation of the server, AFP on the local machines, either of them on a particular version, the Finder in general...) actually might be responsible for this behavior. And maybe there's a "solution" (if you agree that this is actually a problem" buried somewhere
Regards
Roman

Importing from camera with iMovie onto computer with home on AFP share ...

I am trying to import a movie from a Sony Handycam into iMovie '08. iMovie can see the camera. The problem is that I cannot choose where to save the movie. I am only offered the choice of one of the two disks in my machine but am not given a chance to choose the actual folder location. Furthermore, the only choices are not write accessible to me.
I am guessing that iMovie doesn't want to import to my home/Movies because it is on an AFP share but why can't I choose the /Users/Shared folder (or any other location)?
Does the user that imports video into iMovie have to be an admin user?
The dialog that opens when I choose to import says "Save To:" but is not a proper (usual) file selection dialog. I only get two choices and they are internal disks not folders.
I know that Apple loves to work from the premise that they know best how I should do what I want to do but in this case I am actually totally prevented from doing what I want to do. I could actually log in as the admin user, import the movie (I'm assuming that would work) and then copy the files to my account. Any other suggestions would be welcome. Is there a way to specify the path for the import dialog?
(I am sitting on a gigabit ethernet network with a recent XServe and XServe RAID serving my home. I find it hard to believe that this couldn't handle a simple video import. It's not even HD.)

I am only offered the choice of one of the two disks in my machine but am not given a chance to choose the actual folder location. Furthermore, the only choices are not write accessible to me.
Other than the start-up drive user's account "Movies" folder, iMovie '08 only allows access to the "root" level of non-start-up drives which are the only areas it scans for "iMovie Events" folders during initialization. In addition, in order to access non-start-up drives, they must be formatted as "Mac Extended OS" drives.
I am guessing that iMovie doesn't want to import to my home/Movies because it is on an AFP share but why can't I choose the /Users/Shared folder (or any other location)?
See above.
Does the user that imports video into iMovie have to be an admin user?
No.
The dialog that opens when I choose to import says "Save To:" but is not a proper (usual) file selection dialog. I only get two choices and they are internal disks not folders.
See first answer.
I know that Apple loves to work from the premise that they know best how I should do what I want to do but in this case I am actually totally prevented from doing what I want to do. I could actually log in as the admin user, import the movie (I'm assuming that would work) and then copy the files to my account. Any other suggestions would be welcome. Is there a way to specify the path for the import dialog?
Finder level file operations performed external to iMovie '08 tend to corrupt pointers/reference paths unless they emulate what iMovie itself does in which case the initialization scan may be able to fix some problems.
I am sitting on a gigabit ethernet network with a recent XServe and XServe RAID serving my home. I find it hard to believe that this couldn't handle a simple video import. It's not even HD.
Not familiar with such use so I don't know if this would automatically limit your access to root level storage area.

Automounting AFP shares... no seriously

I simply cannot get my head around the file sharing capabilities of Leopard/Snow Leopard. Sure it has NFS support, but from time to time it dies and one have to reboot in order to remount. So I (try to) switch to native AFP. Again I cannot mount manually using mount_afp nor can I mount using auto_master file syntax.
I have checked several tutorials and they do it exactly the same way I do it. I can mount my shares from "Connect to server..." no problemo, but automounting is never working.
I just can't understand why Apple has made it so difficult to get a basic file sharing up and running AND to make it automatic. Why on earth it this so problematic all the time. Ridiculous.
If anyone at all has SL running with automatic AFP shares mounted on boot (not using Login items, I don't want them in my face every time I boot) please tell me your syntax. And Apple, come on... why make it so difficult?

I agree that the lack of documentation and of GUI options to do this is quite puzzling and frustrating.
I guess they want you do it using login items.
I'm not an expert on the issue (I wish somebody who IS one would pop in) but I sort of managed to do it using /etc/fstab as described here
http://blogs.sun.com/lowbit/entry/easyafp_autmount_onos
It works but I'm not sure if did it completely correctly because I have to drill in quite deep before i get to the actual share when I start on "All" in the sidebar. also, the mounted share does not show up on the desktop even when I have the option to do so checked in finder preferences.

Backup 'from' an afp share..?

Is this possible...?
I bought a wirless hard drive so that I could use half to save space on my macbook and the other half for time machine backups..
so need to somehow get time machine to include an afp share in the files it chooses to backup, does anyone know how this can be done...?
thanks..

Hi, and welcome to the forums.
Sorry, no. Time Machine cannot back up network drives.

Finder crashing in AFP share

Hello,
We're having some really strange issues at work with an AFP share.
Setup:
Mac OS X 10.4.7 clients (including a G5, MacBook Pro, iMac G4)
Mac OS X Server 10.4.7 sharing files via AFP
How to replicate:
User's login to the AFP share, navigate to a certain folder, and then finder "locks" (spinning beachball). All attempts to relaunch finder fail. The only things that fixes finder is restarting the machine. This does not fix getting to the folder.
Every directory in this part of the AFP share have the same permissions. I have not tried to navigate to the directory on the server because we would have to get everyone to log off and stop working.
Thanks for help in advance,
Rob
Mac OS X (10.4.7)

All of the users are connecting via ethernet. We typically have about 10-15 users connected to a Mac OS X server with unlimited clients. Everyone in the office connects to this machine, but this happens even when we do not
Initially we were having trouble with a folder that had photoshop files (.psd), but now we're having trouble with the folder up from that (which is basically a project folder that then has several folders beneath it).
I copied the files that one of our employees needed in Windows to another folder (created in Windows) above the directory we are having trouble with. She was able to access the folder and the files. Windows connections are through SMB (and all the windows machines that we have are able to navigate to these folders).
For the clients, unforunately, force quit doesn't seem to handle finder correctly.
Mac OS X (10.4.7)
Mac OS X (10.4.7)

Files cannot be unlocked on AFP Share on Lion Server

Similar Messages

Maybe you are looking for