AX1001
Troubleshooting file access
When running an import or performing certain file processing actions, an error may occur when attempting to access the specified file or folder location. The most common reasons for this error are:
- Using a mapped drive instead of a UNC path
- Not having the appropriate permissions to the specified file or folder
UNC path
When specifying the file or folder location, you must use a UNC path (Universal Naming Convention). A UNC path identifies the location using a server name instead of a mapped drive. For example:
UNC path: \\servername\foldername\filename
Mapped drive: I:\foldername\filename
Mapped drives cannot be used because they may vary by computer. The mapped drives that you see may be different than the mapped drives your co-workers see, and different from the mapped drives seen by the Axiom servers. The UNC path is the only way to universally identify a location within your organization's network.
File/Folder Permissions
The Axiom server that is performing the process must have the proper folder share and security permissions to access the specified file or folder location. The exact configuration depends on what process you are trying to perform.
Task being performed | Where to configure permissions |
Account |
Required permissions |
---|---|---|---|
Import: Source files located on network share local to the Axiom server |
|
Network Service Account |
|
Import: Source files located on network share not local to the Axiom server |
|
Application Server Computer Account |
|
File processing: Running via Scheduler |
|
Scheduler Service Computer Account |
|
File processing: Running in Desktop Client |
Desktop |
User's Domain Account |
|
NOTE: On-premise installations can use an optional system configuration setting, ETLAccessibleFolders, to further control access to folders when running imports. If this setting is used, then any folder location in the import settings must also be listed in the ETLAccessibleFolders. If it is not, then an error occurs when attempting to access files in the folder. Keep in mind that the error message does not differentiate whether the folder is inaccessible due to general network permissions or due to the ETLAccessibleFolders setting.