cancel
Showing results for 
Search instead for 
Did you mean: 

File Writer and Accounts

robert_parks
New Contributor III

Hi Snap Community,

I’m a new user and I’m trying to set up File Write/File Read to a shared local directory.

I set up an SMB account and a Basic Authorization Account.

I’m getting the following errors (blanked out the server on purpose):

SMB – got the same using port 445 as well:
Failed to write to smb://xxxxx.xxxxx.xx:139/Banner/IT/test.csv
Resolution
Check for URL syntax and file access permission
Reason
Possible reasons can be failure in URL connection or file access denial, detail: Logon failure: unknown user name or bad password.

Simillar error when I tried Basic Authorization:
Failed to write to file:///xxxxx.xxxxx.xx/Banner/IT/test.csv
Resolution
Check for URL syntax and file access permission
Reason
Possible reasons can be failure in URL connection or file access denial, detail: An error occurred while creating the parent directory: /xxxxx.xxxxx.xx/Banner/IT/test.csv

Any thoughts as to what I’m doing wrong? Anything I can check?

Thanks,

Bob

1 ACCEPTED SOLUTION

robert_parks
New Contributor III

Never mind!
I had my account set up incorrectly.

Thanks!

View solution in original post

5 REPLIES 5

robert_parks
New Contributor III

Never mind!
I had my account set up incorrectly.

Thanks!

I’m trying to set up a File Writer snap with an SMB account to access our local shared drive

I created an account → Binary → SMB, provided the
domain = domain.xxx.xxx
username = username
password = password

In the file writer settings, I have the file name set with a path of
smb://domain.xxx.xxx//winfile02/depts$/FinancialAid/DeptShared/FA%20Net/PowerFAIDS/Data/Integrations/Slate%20to%20PF/test.txt

I’ve tried various changes to the path and keep encountering errors. Can anyone provide me with proper syntax for the filename when using smb://

Thanks!

Any luck? Get it working?

Yes, finally got the syntax of the smb:// string correct with help from a
sys admin. I had the server portion wrong, I was using the domain and not
the server name.