Cant Access files errors
Hi
I'm using bartender 2016R2 and I'm attempting to use a txt file to load the template file and read the data from the remaining txt file.
When I test the file using the Integration builder utility. and I trigger the process by putting the file in the trigger folder.
The process kicks off ok and it reads the file and decodes it. but it error with a file is not accessible or readable, in addition it complains it cant rename the file, the data file in the trigger folder.
lastly it complains about the printer.
What I'm confused about is that bartender designer reads the data file, find the data and reads and printes it perfectly, this is the same template file I sue for the command script.
Its a domain PC the user, me is a user not an admin although I have local admin rights on the PC.
I have changed the security on the folder to allow anyone to change anything (Full) in the local trigger folder.
lastly does the command script accept file names and folder paths with spaces in. I didn't seem to like the UNC network path to the folder where the template resides ?
regards
Jerry Barrett
-
Since it does not look like the moderators are watching these folders often I will attempt a few things that might solve your issue (I'm new to BarTender 2016 so I don't have all the answers, but I'm learning fast).
What I have found is if you have your drop folder on a different computer than the one running the software, you will have issues with the service account being able to access files outside of it's own hard drives. Try the following:
In Integration Builder, click on the "Integration" level in the File Integration section. Change the User Account to "Specify User Credentials" and enter an account other than [NT AUTHORITY\SYSTEM]. You can use your username and password for testing, but you will most likely want to set this to a proxy account where the password does not change. This account will then be used for all other sections unless you override them. As long as that account has access to the drop folder, it should work fine.
As far as having spaces in your file paths, it shouldn't matter and it should use UNC paths without any issues (this is only a guess as I have not tested it).
I'm hoping this fixes the printing issues as well, but if not, make sure the printer is set up on the computer where the services are running.
Good luck
0 -
I can confirm @Trey Holst answer is a top answer! In order for the integration to access a network path outside the local machine, it will need User Credentials which have access to the network path.
example screenshots of this scenario below ..
0 -
Hi
The permissions fixed this back then, thank you.
However, the Windows 10 update to 1809 has caused more issues, the printing one in the integration file fixed that. However, something else when wrong with the 1809 update. Access to a central server with shares of the templates we use now fails.
I have tried the the path to the server in a UNC formate \\servername\folder\file and mapping the drive and using the absolute path x:\folder\file neither work.
PCs that have been rolled back to Win 10 v1803 use the same integration file and access the files from the server UNC path perfectly
If I setup a local copy of the template the same integration file prints the template perfectly. I have even upgrated to version 8 or R2016 to no avail.
Unfortunately my PC was built after 1803 and never had that version to enable me to roll it back. so I'm suck on post 1803 Windows 10 versions.
If anyone has a work around for this Id appreciate the details please.
I have looked at upgrading to R2019 but the trial didnt seem to work for me and upgrading is so complicated now :(
many Thanks
Jerry Barrett
0 -
Any fixes for this yet?
This still seems to be an issue even in R2019
Thanks,
Chris DePaola
0 -
Hi Chris, thanks for your post! Generally, these 'file access' errors relate to permissions-based issues, whether it may/may not be specified in the Integration file, the actions, if the user has access to a certain directory, and so on. Basically, without more information about the environment, it would be very difficult to tell you how to resolve it if you're experiencing something similar. I cannot confirm that this is an 'ongoing' bug, but let's not speculate either.
It would be best for you to open a case with Tech Support at Get Support and submit your files and a summary of the issues you're experiencing. Thanks again!
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
5 commentaires