AFP FPGetFileDirParms: error 20407

We are running OES2SP2,
the aftcp log is filling up with:
Code:
FPGetFileDirParms: GetInfo call is failed with error 20407
I have searched the forums but do not found a solution, can anyone help on this ?
best regards

Originally Posted by heinsohn-wibo
We are running OES2SP2,
the aftcp log is filling up with:
Code:
FPGetFileDirParms: GetInfo call is failed with error 20407
I have searched the forums but do not found a solution, can anyone help on this ?
best regards
The FPGetFileDirParms is an AFP call to fetch information about a file. The error 20407 while accessing NSS translates to 'NAME_NOT_FOUND_IN_DIRECTORY'. MAC clients send FPGetFileDirParms request to AFP server to fetch information about a file/folder. Apart from the files that exist on the volume, the client request to get information about special files/folders named Contents, .metadata_never_index, .metadata_index_homes_only, mach_kernel etc., that exist by default on a MAC volume. These files contain metadata information. Furthermore, these files are not maintained on NSS volume and hence the error file does not exist. The absence of these files should not cause any problem with the AFP server behaviour.
The grammatical error in the above log message will be corrected in SP3.
Junaid

Similar Messages

  • Tiger AFP Server "Error code -5000"

    Hi,
    I've made yesterday the last security update for Tiger server and since yesterday I connot connect anymore to the AFP server.
    I've tried to restart the server twice, deleted all shares, I can connect from PC with SMB but not from Mac with AFP.
    Error code -5000
    Any ideas ?
    Thanks

    OK, I finally found the problem, I had a folder instead of the real HD into /Volumes...
    AFP is now working fine again...

  • How do i fix an AFP Lock Error?

    Ok so i rented some films from iTunes, but they didn't properly process once finished downloading due to an AFP lock error. How do i fix the error?

    AFP relates to sharing of resources such as files or computers.  Take a look in Finder’s Help menu for AFP references and see if any are relevant to you?  If that’s all Greek to you, perhaps just rebooting will cure the lock.

  • "An AFP System Error Occurred"

    We have a new intel Xserve:
    10.4.10
    7 GB RAM
    +All software updated+
    Periodically, when people try to connect via AFP (10.4.10 intel+ppc macs), we get the dreaded "An AFP System Error Occurred" message...the only way to fix it seems to be to restart AFP services or reboot the server.
    Ideas?
    Thanks,
    j

    I know I seem stuck on an idea, but if new sessions can't be started and this message is coming up, my gut says that the max threads is a real possibility. Have a look at these articles and make your own decision: http://www.afp548.com/article.php?story=20060329213629494&query=maxthread and http://www.afp548.com/article.php?story=20060905144209269&query=maxthread
    Roger

  • AFP System Error

    Hi folks,
    I have an OS X server running 10.4.11. For the past week or so, I have to restart AFP services every morning. When users try connecting to AFP shares, they are getting an "AFP system error". The only thing that fixes it is restarting the service (or the server, obviously).
    When this first started, the system was at 10.4.8. Odd thing was when trying to install the 10.4.11 combo update, it said that it couldn't install. I had to do the 10.4.9 combo update, then the 10.4.11 combo update. Unfortunately, despite this being a bug with 10.4.8 the updates didn't change anything.
    I've tried changing the authentication method from 'Any' to 'Standard' and back to 'Any' with no change.
    Had a look at the AFP logs. When attempting to connect the access log reports the user logging in, and then three seconds later logging out. In the AFP error log, there are a few lines of 'The server wasn't able to start (Unable to register IPC port)' which are from the afternoon (the AFP system errors happen in the morning). Not sure if that is relevant or not.
    Hoping someone can shed some light on this, thanks!

    I know I seem stuck on an idea, but if new sessions can't be started and this message is coming up, my gut says that the max threads is a real possibility. Have a look at these articles and make your own decision: http://www.afp548.com/article.php?story=20060329213629494&query=maxthread and http://www.afp548.com/article.php?story=20060905144209269&query=maxthread
    Roger

  • OES2SP1 + AFP + -1659 error

    I'm having trouble getting Macs (with OSX 10.6) to connect to our OES2SP1 Linux server (with all the current patches installed). The Macs can connect to our NWSP8 servers without any problems.
    We have Universal Passwords configured & I have installed AFPTCP on the server & configured it using YaST.
    In the Universal Password polices we use, the AFP proxy user is listed as able to retrieve passwords for each policy that applies to the various groups of users.
    I also tried reconfiguring it with a new proxy user in case there was something wrong with my
    The afptcpd log file show the following error when a user tries to connect:
    afptcpd[3631]: [error] Proxy user failed to obtain user credentials. Ensure that proxy user has rights and the user is assigned to the appropriate policy. nmasldap_get_password error: <-1659>
    I've tried a number of users with various password policies including the AFP Default Policy but none of them can attach to the server except Admin.
    The Authentication Mode is set to Diffie-Hellman in the AFP configuration in iManager.
    I've searched this forum for other info, but can't seem to find anything else to try.

    Originally Posted by imoore
    I'm having trouble getting Macs (with OSX 10.6) to connect to our OES2SP1 Linux server (with all the current patches installed). The Macs can connect to our NWSP8 servers without any problems.
    Presumably you've installed the nw65sp8_mac106_ftf patch on your NW65SP8 servers since your Snow Leopard clients can connect to those.
    Which version of novell-afptcpd is installed on your OES2 SP1 Linux servers? Use 'rpm -qa | grep novell-afptcp' to check.
    Originally Posted by imoore
    We have Universal Passwords configured & I have installed AFPTCP on the server & configured it using YaST.
    In the Universal Password polices we use, the AFP proxy user is listed as able to retrieve passwords for each policy that applies to the various groups of users.
    I also tried reconfiguring it with a new proxy user in case there was something wrong with my
    The afptcpd log file show the following error when a user tries to connect:
    afptcpd[3631]: [error] Proxy user failed to obtain user credentials. Ensure that proxy user has rights and the user is assigned to the appropriate policy. nmasldap_get_password error: <-1659>
    I've tried a number of users with various password policies including the AFP Default Policy but none of them can attach to the server except Admin.
    The Authentication Mode is set to Diffie-Hellman in the AFP configuration in iManager.
    I've searched this forum for other info, but can't seem to find anything else to try.
    What does 'CASAcli -l' report?
    HTH.

  • Failure to Login Netwoprk Account | AFP EIO Error

    Hi,
    I'm running SLS 10.6.6 and clients SL 10.6.6. My account is a network account. It has started, recently, to fail to log in because the HomeDirec tories shared users home folder is unavialable (I presume). The console of the client is chocka with:
    11/01/2011 14:35:03 /usr/libexec/mount_url[527] AFP error -5018 mapped to EIO
    The client looks like it's logging in but actually it is stuck at the login window (not frozen though). The only way out is to hard restart.
    If I restart the server the problems goes away and I can log in network accounts. This isn't the only login problem I get but the other one goes after multiple login attempys (message about user being unavailable).
    Any ideas?

    The same thing happened to me this morning. Both (Server and Client) are on 10.6.6. Home Directories are mounted via AFP over Airport from the Server. After rebooting the Server the Error disappeared. Is there any other way to fix it without rebooting the Server?
    Message was edited by: charmides

  • LogMeIn Hamachi: AFP Connection Error

    Hi Community,
    I'm currently trying to set up an AFP connection between two computers that are both connected to my Hamachi Server. I have three computers on the free server, the two I need to connect, and the third being my personal computer. Whenever I try to connect the two computers (either way, from computer A to computer B or vice versa), I get the error:
    "The server "x.xx.xxx.xx" may not exist or is unavailable at this time. Check the server name or IP address, then check your network connection, then try again."
    Both computers are returning a ping regularly, so I'm not sure why this is happening. Furthermore, both computers can connect to my personal computer via AFP, but my personal computer can not connect to either of these computers. All three computers are on different networks, so I'm suspecting a network-side firewall issue, but after going about opening ports on the 2wire and Netopia 3000 (the two routers I'm dealing with), I'm still getting the same error. Does anyone know where this error is originating from? Or even better yet how I can fix it? Thank you so much,
    ~Josh

    Hamachi provides a VPN connections between the system, which unless the firewall (and or router) is actually blocking Hamachi, will NEVER see your AFP traffic and ports on the Hamachi network, except as encrypted packets using the Hamachi port(s).
    Hamachi tends to use a 5.x.x.x based IP address.  Have you tried finding the Hamachi assigned IP address for the remote servers and connecting using that?
    Finder -> Go -> Connect to server -> afp://5.x.x.x
    I think Hamachi will distribute Bonjour messages, so in theory you should be able to use a utility such as Bonjour Browser to see if the remote Hamachi system's Bonjour services are visible.

  • Mount AFP volume error [-5002 (AFP Bad UAM)]

    After reading many complaints about AFP in Leopard, I just have to ask again if anybody has a workaround for the “Connection Failed” error -5002 when trying to mount an AFP volume in Leopard. Does anybody have any more info about fixes, workarounds or info about this problem with Leopard? And what is UAM??

    UAM == user authentication method
    Each AFP server, depending on its version, will have a set of UAMs that it supports by default. These are essentially authentication capabilities such as "no authentication", "cleartext passwords", "kerberos auth", etc. There are several others.
    That error code would imply that your client is trying to authentication in a way that the server doesn't know how to handle. Is this another Leopard box you are trying to mount?

  • AFP Mount Error -5002

    Something broke recently and I'm struggling to figure out what may have happened...
    When logging into client machines (that have been bound to the server) the server appears in the Finder sidebar under "Shared" as usual. But when clicking on the server's name to mount some sharepoints we are seeing "Connection Failed" errors.
    System.log notes:
    +Mar 28 15:55:01 mymac /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[178]: SharePointBrowser::handleOpenCallBack returned -5002+
    Strangely it's possible to use the menu item "Connect to Server..." to select the server then the sharepoint and no password is required as sharepoints mount as expected. I assume "Connect to Server..." is correctly using "single sign-on" whereas simply clicking on the server's icon in the Finder's sidebar is not?!?
    Kerberos is fine and running...and everything appears to be ok with OD.
    Anyone seen this or have some ideas what might be going on?
    Thanks!

    I have a similar issue, that started the day after I applied the latest Apple Security update 2008-002 on a client's Mac OS X 10.4.11 server. I have a mixed client base of Leopard and Tiger users, and they are all bound to the Apple OD Server, and access to all home directories on the server work just fine for all users, but these users connect to other share points on the server by going to the Finder's Go Menu and selecting Connect to server (actually they all have alias to this share points). Since the update none of these clients can access some of the departmental shares, they just don't appear in the Connect to Server window as an option. Leopard users on the other hand, can access these shares by using the sidebar option to connect to the server. I have reviewed all privileges and user groups on the server, and have found that some users were no longer listed in the group (they were before). After adding these user again, they still can not see those file server shares. I turned off and on AppleShare, I restarted the server, and I unshared the directories and shared them out again, but my problem continues.
    My users do not get an error message when they connect. My AFP authentication method was set to Any Method, and I changed it to Standard (No Kerberos) at which time they could access there shares again, but when I do this some (not all ) Leopard clients fail to login at all. Kerberos is running just fine, and it has been for years now.
    I have spent ours researching this issue, and have not found any other usres with this same problem. One user had a similar problem, but his user did get an error message that username or password are incorrect. He did spent a couple of hours on the phone with Apple Care, and they were unable to duplicate this issue.
    I was not using ACL's on this server, but this week I gave it a try, but my users can still not see their shares.

  • AFP protocol error

    I have some older macs and I also have G-5's, iMacs, eMac's as well. When we try to go thru the network to get files from another hard drive we get this message. "This file server uses an incomplete version of the AFP protocol. You cannot connect to it".
    G-5's are using OS 10.4.10 and the older units are OS 9.
    We had no issues prior to upgrading to Tiger. We are also using TCP/IP, and appletalk on the older units. We need to transfer files between computers, and are currently using sneaker net. Any ideas???
    Thanks.
    Ken

    You're not missing something... OSX.4.x IS!
    OSX.4.x lost the file transfer ability of Appletalk... 10.1.5 thru 10.3.9 had it!
    http://docs.info.apple.com/article.html?artnum=301183
    With OS9 set with Appletalk to using TCP/IP, and or Chooser>AppleShare+IP, you can connect to the 10.4.8, (maybe higher, not sure), machine.
    Another solution is OpenDoor's $39 Shareway IP, (some OS7, 8, 9 releases had a limited version included)...
    http://www.opendoor.com/shareway/
    Which makes OS9 partially Tiger compatable. (Last I tried it was with 10.4.9,and communication was limited to Reads in either direction, Writes causing crashes on the OS9 machine, errors on the OSX ones).

  • Lion: don't work  time machine with NAS Buffalo or Thecus (AFP error)

    backup with Time machine, does not recognize the disk, used with the previous version. The AFP system error that is not compliant, with both NAS.
    bye
    Alex

    If your NAS/TimeMachine manufacturer doesn't provide an update, you could probably revert to the old ways:
    http://www.alexanderwilde.com/2011/04/os-x-lion-connection-error-with-afp-and-wo rkaround/
    This has solved AFP issues for some but I haven't been able to verify it for TM.

  • AFP login not possible, OD error?

    Dear all,
    since Monday some of our users have the problem that they cannot access the file server with their user credentials. This does not affect all users, only 3 out of 18.
    The setup is:
    Mac OS X Server 10.6.8 running on an Xserve 1.1 (file server)
    Mac OS X Server 10.6.8 running on an Xserve 2.1 (OD server)
    Clients (Mac mini, iMac) running 10.9.4
    The user accounts are managed on the OD server, the OD is replicated on the file server. This affects one newly created account (on Friday, login was then possible) and two accounts that already existed for half a year or more.
    When I log in with a working account, /Library/Logs/AppleFileService/AppleFileServiceAccess.log shows up the following line:
    IP xxx.xxx.xxx.xxx - - [04/Sep/2014:11:08:21 0100] "Login [user name]" 0 0 0
    When I log in with a working account using a wrong password, the following lines appear:
    IP xxx.xxx.xxx.xxx - - [04/Sep/2014:11:10:30 0100] "Login [user name]" -5023 0 0
    IP xxx.xxx.xxx.xxx - - [04/Sep/2014:11:10:30 0100] "Logout [user name]" -5023 0 0
    AFP error 5023 means "AFP User not authorized" which makes perfect sense.
    When I log in with one of the accounts that now don't work, only the following line appears:
    IP xxx.xxx.xxx.xxx - - [04/Sep/2014:11:15:53 0100] "Logout [user name]" -5023 0 0
    So there is no login logged.
    However, in the log I can find the following lines:
    IP xxx.xxx.xxx.xxx - - [03/Sep/2014:22:11:08 0100] "Logout [user name]" -5023 0 0
    IP xxx.xxx.xxx.xxx - - [03/Sep/2014:22:11:29 0100] "Logout [user name]" -5023 0 0
    IP xxx.xxx.xxx.xxx - - [03/Sep/2014:22:11:50 0100] "Logout [user name]" -5023 0 0
    IP xxx.xxx.xxx.xxx - - [03/Sep/2014:22:12:10 0100] "Login [user name]" -5019 0 0
    IP xxx.xxx.xxx.xxx - - [03/Sep/2014:22:12:10 0100] "Logout [user name]" -5023 0 0
    IP xxx.xxx.xxx.xxx - - [03/Sep/2014:22:12:31 0100] "Logout [user name]" -5023 0 0
    This happened obviously after the user has logged out and Mac OS is trying to sync the mobile account with the credentials that have problems. Error 5019 means "AFP Parm error". I manually aborted the sync after hours. When the users tried to log in the next morning, also an error -5019 followed by a -5023 appeared in the log. Error or warning messages did not appear to the users while logging into their accounts.
    Changing the passwords did not help. Disabling and re-enabling the accounts in the OD did not help. Restarting AFP services did not help. As for AFP, the users can use different credentials, but for the mobile accounts this way is not appropriate.
    What I did on Sunday was shutting down the file server, removing the hard disks and testing a spare Xserve 2.1 with the system. Then I put back the drives into the Xserve 1.1, which is running as the file server since then. Could that be the cause? Other changes (system updates, config changes) have not happened.
    Thanks in advance,
    Andreas

    Andreas,
    Did you ever find a solution to this?
    I have pretty much the exact same issue.
    Regards
    Ben

  • OS 10.4 - Network - OS 9.1: AFP-Protocol incomatible

    Hi,
    i have a OS 10.4 G5 and a OS 9.1 G4 in my Network. When i try to connect from the G5 to the G4 i get the message that the "AFP protocol" on the G4 is incompatible.
    I've searched at google for hours and now i can connect from the G4 to the G5 via TCP/IP. But i need to connect from the G5 to the G4. Is this possible?
    I also need to connect to a Windows NT-PC but untill now i haven't tried if this works, i think it wont!?
    Greetings from Germany

    Yesterday we downloaded a trial version of ShareWay, which worked on the one G4 OS9.2.2 that we tried last night.
    http://www2.opendoor.com/shareway/shareway3.html
    Our situation prior to trying Shareway:
    1) From G5 Tiger, we want to connect to OS9.2.2 installed on two iMacs and one G4.
    2) The connection works fine to only one iMac.
    3) The other iMac and G4 report the AFP protocol error.
    4) All three connection work fine from G5/10.3.9.
    This morning I found these rather confusing articles, which we'll try next week. I'd appreciate reading about your experiences.
    http://docs.info.apple.com/article.html?artnum=60353
    http://docs.info.apple.com/article.html?artnum=106121
    http://docs.info.apple.com/article.html?artnum=90013
    http://docs.info.apple.com/article.html?artnum=16145

  • 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.

Maybe you are looking for