Network Share
We've been using the Commander to print labels from our PeopleSoft system for some time now. An process in PeopleSoft runs on the client creating a file for Commander. This works fine.
We're in the process of upgrading PeopleSoft. The new version doesn't run on the client computer so we need to have the Commander file generated on a network share.
I have it all set up and Commander seems to be reading the shared folder, but the status is gooing from "Scanning" to "File Found" and back again. But the file is not getting processed.
I looked through other threads and Commander troubleshooting, but nothing is working. There are no errors showing in the Commander log.
I'm using Bartender 9.3 on Windows 7.
The network share is a Windows Server.
I have the share set to Full access for everyone.
I'm using a Domain Admin account for my Bartender and Commander services.
Thanks in advance.
We're in the process of upgrading PeopleSoft. The new version doesn't run on the client computer so we need to have the Commander file generated on a network share.
I have it all set up and Commander seems to be reading the shared folder, but the status is gooing from "Scanning" to "File Found" and back again. But the file is not getting processed.
I looked through other threads and Commander troubleshooting, but nothing is working. There are no errors showing in the Commander log.
I'm using Bartender 9.3 on Windows 7.
The network share is a Windows Server.
I have the share set to Full access for everyone.
I'm using a Domain Admin account for my Bartender and Commander services.
Thanks in advance.
0
-
Make sure you specify a UNC path to the network share and avoid using a mapped drive letter which will not work when Commander is running in a service context.
Example: \\ServerName\SharedFolderName
If the immediate detection method doesn't seem to work correctly, which can happen over the network depending on latency issues, then switch to polling instead, but be careful not to poll at too highe a frequency.0 -
Legacy Poster
★ BarTender Hero ★
[quote name='Ian C - Seagull Support' timestamp='1331206203' post='1937']
Make sure you specify a UNC path to the network share and avoid using a mapped drive letter which will not work when Commander is running in a service context.
Example: \\ServerName\SharedFolderName
If the immediate detection method doesn't seem to work correctly, which can happen over the network depending on latency issues, then switch to polling instead, but be careful not to poll at too highe a frequency.
[/quote]
I'm using the UNC. I over came this problem. Now the file is getting processed, but nothing is printing. I'm printing to a local printer. It works when Commander reads the file from the local computer, but not when it reads it from a network share.
Thanks0 -
Legacy Poster
★ BarTender Hero ★
[quote name='VinnyF' timestamp='1331218921' post='1941']
I'm using the UNC. I over came this problem. Now the file is getting processed, but nothing is printing. I'm printing to a local printer. It works when Commander reads the file from the local computer, but not when it reads it from a network share.
Thanks
[/quote]
I deleted and recreated my Commander project and task. Everything started working.
??????
Thanks for your help. I guess I'm all set.0 -
Glad to hear that you got it running.
Note that you might need to make sure that the BarTender command handler setup is configured to login with a particular Windows account. Check this by stopping detection and then selecting this option via the "Detection" menu.0 -
Pieter Teirlynck
★ BarTender Hero ★
Could you tell me how to access a shared folder in the integration file? When I browse folder to scan, I can go to the shared folder.
But when I deploy the script, it gets an error that it cannot find the specified folder.I assume that I might have to add credentials to the path?
Thanks in advance.
0 -
Pieter: I trust you are using a UNC path to the shared folder, as explained in the previous posts, as opposed to the drive letter of the network connected share? If you still have problems then you'll need to modify the log on credentials for the Commander Windows service itself.
0
Please sign in to leave a comment.
Comments
6 comments