Hi Team,
We are using a File Operation snap with file:// protocol and Basic Auth Account. We have a groundplex running on windows server.
We are getting the following error.
Please guide us how to resolve the error.
File_Operation error0_json.txt (3.5 KB)
The file protocol is for working with the groundplex’s file system. Is that what you’re intending to do? From the URL and the mention of Basic Auth, it is looking like a bit like a file hosted on a different server. Is that the case? If so, then you’ll need to know the file servers protocol and configure the snap based on that.
Hello there,
Yes. We are trying to access files from shared drive and move it to a different location on the same server.
Have couple of following questions.
Source : file:////somedirectory/somfile.csv
Target : file:////somedirectory/somfile.csv
vs
Source : file:////somedirectory/somfile.csv
Target : file:////somedirectory/
Do we need to use any accounts for accessing share drive files using file protocol.
Do you have any screen shots for how do we configure the share drives on windows server for accessing with file protocol.
Whats the difference between file:///Z:/somedirectory/somefile.csv (if you have a Groundplex on Windows) and * file:////somedirectory/somfile.csv (if you’re using the Universal Naming Convention). When can we use Universal Naming Convention and can we use it with Windows server configuration.
If we have not mapped our network drive to any of the Drives on the server and using generic network access user; can we still use the Groundplex on Windows configuration file path specifications.
It would be highly appreciable if we get some working pipelines with sample values. Thanks
hi, some sample values:
local c:\temp file:
file:///C:\temp\test.json
mapped drive Z:
file:///Z:\Testing\test.json
another machine using unc path (there are 4 / before host):
file:////host/Testing/test.json
Please ensure the read/write operations work on Windows Explorer first
then start jcc manually jcc.bat and test above from the snaps.
If jcc runs as a Windows Service, the Logon Account on that service
will need to have privs to access all of the above path.
