Print Station 2022 "A connection to database could not be made"
Bartender 2022 R4
Database and Label are on Network Share
Database is an Excel file
While Designer can connect and print labels, the Print Station when selecting the Preview or Print options with the following message:
Print Job Aborted. The record set could not be created due to the following:
A connection to database "Sack Label Data" could not be made.
Is there a workaround, other than providing Users with access to print via Designer?
-
Hello Stuart,
Thank you for reaching us via our Community Forums!
What you're seeing is an error letting you know that the label's database connection could no longer be found. Check out the link for more information about the database connection setup. This error often happens when the label is linked to a CSV, Excel, or another type of dataset that's easy to move from one location to another. In this case, the label can no longer find your Sack Label Data database.
To fix this problem, open your label in BarTender Designer, select File>Database Connection Setup and relink the database to where the Sack Label Data file is currently located. Once it has been relinked, save the file to save the connection. You can then continue to print in Print Station.
Let us know if you have any issues.-1 -
Hi
I have relinked the database file within designer and saved the file, however Print Station still gives the same error.
Throughout the process Designer has been able to access the database and print without issue.
I have checked the permissions on the file, and confirmed that the user account used for the Print Scheduler Service is explicitly declared with Full Control to the database file, so it doesn't look to be a permissions issue.
At the moment I am having to run labels via the Designer, which works as a very short term workaround, but isn't sustainable for more than a day or two.
TIA
0 -
This sounds like it could be a permissions type issue potentially. There was an issue reported in earlier versions of 2022 where this occurred but this was supposed to have been fixed in R4 I believe as the comment:
You may encounter an error that Print Station is unable to find or load a document when printing a document stored in a network share location. A Windows user account with permissions will have to be explicitly set on the BarTender Print Scheduler Windows service.
no longer appears on page https://support.seagullscientific.com/hc/en-us/articles/4406151930775-Updates-to-Print-Station-and-Print-Portal-in-BarTender-2022 since the page was updated.
It maybe worth trying to use a different user account to run the BarTender Print Scheduler service and see if that fixes it.
0 -
Hello,
I am having the same issue as Stuart described when I try to print via the Print Station, is there a way to fix this?
Thanks
0 -
One thing you may want to check first is that, if you are using Excel the same as Stuart above, is that the file is closed elsewhere. If it is then look at running the Print Scheduler Service using a different (admin) account that has sufficient permissions to access network locations and files
1 -
I'm having the same problem. Both the Bartender file and the Excel file are in network storage. I'm the only one using both files in the company currently. Designer software has no problem printing, even if the spreadsheet is open, as long as the data I want to access has been saved. Print Station is unable to connect to the spreadsheet even when I place the files are in the same folder, regardless of whether the spreadsheet is open or closed. Any suggestions on how to resolve this?
0 -
I'm having the same issue here using ODBC connection to SQL database. Works fine from Designer but I get the following error when I try to print the same label (using the same ODCB link) from PrintStation: Connection to the database could not be made due to the following: A user name and/or password was incorrect or missing.
This is a blocker for me. I have to keep using 2021 version because of this issue. Any progress on this problem, because apparently 2022 R4 hasn't fix it completely. I'm using2022 R5 for your info
0 -
I checked user accounts on the file and those on the print scheduler service and still had the issue.
In the end I reverted back to 2019 version at which point the issue went away. Obviously that's not a long term solution, but its allowing us to function.
0 -
I have made some tests and I think I understand now how it works in Designer compare to Print Station.
In BT Designer 2022, the credential used to preview the label, connect to external DB (including Excel) and print is the one of the current windows user (logged on)
In Print Station 2022, it uses the "Bartender Print Scheduler" service account. By default, this service runs using Local System account. If you are in a domain, this local system account will not work, except if you have everything installed locally on the same computer (print spooler, DB, excel files, ...). So you have to run "Bartender Print Scheduler" service with a domain account (kind of dedicated service account) having local admin right on the Print Station computer and at least Read access to the external DB (SQL , Excel, txt file, ...). In addition to that, most surprising requirement, every required printer has to be installed in service account's Windows profile. Having the printer installed in the normal user profile is not enough for the PREVIEW function.
@Bartender expert: Do you have any documentation on this? How come it was not like that in previous version ?
2 -
I'm experiencing the same issue as Dominique. I had to roll back to 2021 because of this issue with how things are executed through Print Station.
0 -
Hi,
Have experienced the same issue with Print Sation R5, R8, R9 instances. The only solution I have found the works is to copy the file locally be it a exel file or access datbase file. I created a directory on the local C:\ copied the required database there. In Bartender designer opended the offending templates, re-linked the database path to local instance. Saved the label and the problem was ressolved.
However this is really a workaround and Seagull Bartender developers really need to stop being so lazy and patch the problem with a fix.
In my instances the business uses workgroups and the shared access database is stored on a NAS box attached to local LAN.
Messing around with starting Bartender Print Scheduler serice with different local account credentials alos does not work.
I should not all accounts have appropriate permissions to access the shared database file over the LAN.
The one instances where Print Station works correctly seemd to be when:
User logged in exactly matches the account on the NAS box and has permissions on all folders and files where the database resides.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
11 Kommentare