Using a network folder from a WATS Client converter

The WATS Client can pull source files from a network (UNC) share, but the computer account need read/write access to the share.

Recommended method

The recommended method for pulling source files from is to use an external tool to move files to the local WATS Client computer. This is to reduce issues related to network security and isolate problems that can be caused by shared access to files on network shares.

Alternative method

Important!
Directly referencing UNC paths from a service on the client may cause unforeseen problems for a number of reasons. We strongly advice against this, and recommend using the file-move approach whenever possible.

The WATS Client Service runs default logged inn as "NETWORK SERVICE" on the local computer. This user usually does not have access to network fileshares. If the local computer is member of a local active directory domain, the network service account identifies itself as "domain\COMPUTERNAME$".

There are two ways to grant access to a network share:

1. Grant access to network service on the network folder. (AD Domain join required)
   • Grant read/write access to "domain\COMPUTERNAME$" on the network share and the files/folders
2. Change the user that runs the service and grant that user write permissions
   • If the station and server is in a domain, a service user must be created
   • If the client is not in a domain, you must create a local user on both client and server with the same password

Then, in converters.xml change the <Parameter name=Path"> element to the UNC Path ie. "\\servername\sharename\wats_reports"

WATS Client Service must be restarted after changing these settings.