Hi,
the easiest is to not use mapped network drives, but rather
UNC paths.
David
David,
Thanks for the response. However, I am using a UNC path already... it is the space in the UNC path that is causing it to error out; but renaming the folder is not an option due to the fact there are multiple software programs referencing these folders...
Regards,
N8
Hi N8,
This sounds more like a permissions issue for the "user" of the machine that is running FME Server. It has been awhile since I used FME Server but I had the same issue.
Check the permissions on the server and make sure the user has access to the mapped drive.
Regards,
Mitch
Folks,
Thanks for the tips, one and all. Good news!!! Its fixed. It ended up being a "compound" problem consisting of permissions and the spaces.
1) The spaces in the path - - I used UNC paths as advised; and from now on, I simply enclose the path inside quotes (i.e. "\\\\server\\folder with spaces\\file.tab")
2) The permissions - - uninstalled FME server on the server; then reinstalled FME server (with new SP3) being logged into network admin instead of local admin account. Finally, in the Admin Tools \\ Services --> configured the FMEServer service to run under the network admin account instead of Local System.
As they say, all's well that ends well. The reinstall may or may not have been necessary, but I figure it never hurts to upgrade.
Nate / N8