Hints & Tips on using network drive (UNC or mapped drive) to send or receive files with CFT

If CFT is launched as a service, we may face the fact that even the network drive or mapped drive is not defined at service start time.
Also, network files may have right restriction depending how customer issue the send command (Copilot or batch ?) when Copilot is used, by default, the right used will be the user logoned on the Copilot.

A good step to diag an issue with mapped drive (or UNC file access) is to verify if it still doesn''t work when CFT is launch manually after a user known for having righ on the network drive have open the Windows session? (before launching CFT ensure the user can see/access to the network drive)

If mapped drive is to be used ensure the UCONF file is set accordingly, collect the result of a listuconf command and check the rootdirs values for the mapped drive.

Some more information that can help to solve such an issue:

Windows Service failed to connects to the UNC path files. This is a permission issue, as the Windows Service isn''t logged in as a user (even when a specific user has been set for that service).
You must set the logon type to use assigned user credentials. (see bottom of that note)
(ServiceProcessInstaller.Account = System.ServiceProcess.ServiceAccount.LocalService) .
Me.ServiceProcessInstaller1. (Account, Username, Password properties)...

You can also arrange to have the share mapped on a letter drive in a user logon script, so that drive will be available for the service started using that user (see "net use" usage)

A Windows service is an application that starts when Windows is booted and runs in the background as long as Windows is running. Windows services by default are run as a virtual user: "LocalSystem" that has administrative rights on the system. The working directory will be the Windows system directory.
LocalSystem also has no access to network file shares and similar resources
if a service needs to access files on the network, it generally needs to be configured to run as a domain user with access to those files.
So if your windows service needs to access files from shared drive which is in another domain, then you need map the drive using the built-in user credentials through program.

If you logon using the user used to start the service, launch the program: "rundll32.exe keymgr.dll, KRShowKeyMgr" and add the network information for the share drive you want to use.