Anyone Know How To Fix This? Follow

0
Avatar
Legacy Poster

I had to make a visit today to my client and check on a problem that they reported. They have been in the past been using generic/universal user accounts on the workstations in their production areas, but are in the process of requiring all users to login using their own personal user accounts on the domain. The first user has been doing this and his account runs into a slight problem on “each” workstation. When he first attempts to print a label out of Bartender, he gets a database/odbc error. I actually saw this problem when I first set up Bartender last month for them. All the label templates are in a folder on the server that has been shared out to everyone: all can access this specific folder. However, when you first open any label design, the database/odbc connection information isn’t there. The database information has been setup and saved in the file but it’s missing the database path and database username/password. In order for me to fix it, I simply have to take any one label, re-enter the database path, username, password and test the connection. Once that has been done, everything is OK for all the other labels. But I have to do this for each user account on each workstation.

Is this something within Bartender that causes this? Is there an .INI file or something similar that I can access or use in order to fix this globally for the entire company? I’m simply looking for an easier solution to fix or set this up so that everything will work/connect properly for all user accounts on all workstations. I’d prefer not to have to repeat the steps above as it will be very time consuming. Any help would be appreciated. Thanks.

5 comments

0
Avatar
Fernando Ramos Miracle
Moderator
Comment actions Permalink

Where is the database stored exactly? What type of database is your customer working with?

Is your customer using mapped drives to set the path to the database? If that is the case they should substitute them with [u]UNC paths[/u] as mapped drives are user dependant. This means that unless that same user connects with their account the mapped drive won't even be there and the connections would be lost.
0
Avatar
Legacy Poster
Comment actions Permalink

It's a Firebird database and the software that is using it is a little quirky. While I don't think this is related, it doesn't have use the .fdb file extension; instead using a .pkf extension.

As for the mapped drives...I'm going to say probably no (or should I really say yes)? This is the path name that I've had to type in in the database connection information of the labels: \\CDSVR03\D:program files\pks4\Data\cmpdwin.pkf

I had actually tried typing in shorter paths and what not, like removing the D: drive letter and making it \\CDSVR03\program files\pks4\Data\cmpdwin.pkf
.......but none of the path names would work/make a connection except for the one above with the the drive letter.

Could this be the problem?
0
Avatar
Fernando Ramos Miracle
Moderator
Comment actions Permalink

That certainly doesn't look like a mapped drive, it actually looks like UNC path so you shouldn't modify it.

Could you tell me if the path is different in any way between users? And the account and password?

On what Windows OS are the clients working with? Also, what BarTender version, edition and build are you working with?
0
Avatar
Legacy Poster
Comment actions Permalink

Could you tell me if the path is different in any way between users? [color="#FF0000"]Shouldn't be; as I used the same path name when I visited them on Thursday to fix the issue for the one user who was having issues.[/color]And the account and password? [color="#FF0000"]I don't have any information or control anything regarding their network and they won't let me touch anything.[/color]

On what Windows OS are the clients working with? Also, what BarTender version, edition and build are you working with? [color="#FF0000"]All the workstations are running XP; Bartender 10 SR1 Build 2845.[/color]
0
Avatar
Michael Toupin (mtoupin
Comment actions Permalink

[quote name='jking' timestamp='1349708483' post='3433']
Could you tell me if the path is different in any way between users? [color="#FF0000"]Shouldn't be; as I used the same path name when I visited them on Thursday to fix the issue for the one user who was having issues.[/color]And the account and password? [color="#FF0000"]I don't have any information or control anything regarding their network and they won't let me touch anything.[/color]

On what Windows OS are the clients working with? Also, what BarTender version, edition and build are you working with? [color="#FF0000"]All the workstations are running XP; Bartender 10 SR1 Build 2845.[/color]
[/quote]

Take a look at the ODBC driver in Windows, by going to Start>Administrative Tools>Data Sources(ODBC). Make sure that the ODBC data source that you're using is listed under 'System DSN', not 'User DSN'. User DSN's are logon specific, System DSN's are available to all users, and don't have any logon requirements (in fact they're usable by everybody, including service accounts).

If it's a User DSN, you'll need to just create a new one under System DSN. Then you'll need to open the labels and change the database connection to point at the new DSN. You only have to do that part once per label, once it's saved it'll look for the System DSN on whichever machine you use the label from.

You will have to set the DSN up once per workstation, but that's a lot better than once per login.

Please sign in to leave a comment.