In the RoleTailored client, operations such as RENAME and COPY fail if the destination for the file operation is not on the computer running Microsoft Dynamics NAV Server. One solution is to configure Microsoft Dynamics NAV Server to delegate on behalf of the RoleTailored client as described in this topic. In this case, you may also need to configure Microsoft Dynamics NAV Server to delegate to the cifs service on the destination computer. To avoid this complication entirely, define file operations so that the destination is always on the computer running Microsoft Dynamics NAV Server. You can then use a shared folder on the computer running Microsoft Dynamics NAV Server and share it with all users who require access to the files.
If you have deployed Dynamics NAV 2009 R2 in a 3-tier configuration then you can follow steps below.
In order to work with UNC link/Network share you must follow 2 stages of delegation the Middle Tier to the machine where the share is and choose the CIFS (Common Internet File System (CIFS) File Access Protocol or CIFS) from the list of services available, as per the images below on the three-tier environment:
You need to delegate from the Middle Tier Service Account to the CIFS service running on the machine where the file share is located.
In the image above, the service account is called navservice under which the middle tier is running. The delegation has been setup for Service Type cifs on the machine where the file share is located; in this case the machine is called NAV-CLIENT.
(please ignore the fact that constraint delegation is missing. Image used to show CIFS)
Set up Constraint delegation on the MACHINE ACCOUNT (machine name of NAV Server) of the NAV Server machine to the CIFS Service of the machine where the file share is located. It is the same process you followed earlier to add CIFS delegation for the Service Account but we are doing this now from NAV machine account toNetwork Share destination machine account.
It is paramount that you reboot the NAV Server and File Share Server after this change!
The Microsoft Dynamics NAV Support team
This article resolved our problem but it came back the next day. What could happen that would not make the changes "stick"?
Steve - first time I am hear of this.
Did you purge all the Kerberos Tickets using 'klist purge' on NAV Server and File Shre Server and restart the NAV Server and the File share server after making the delegation changes?