Hello!

I am using BarTender Enterprise Automation version 10. I have my print requests written as files to a directory Commander watches. It works fine when I run it under MY user id - I am in an adminstrators group on that server as well as being part of the SQL Server sysadmin permission group. I am trying to use a service account to run this on the network then use a local SQL user account for logging. The local SQL account that has public access but is db_owner of the BarTender database. The logging portion works under my user id, it does not work when running under this service account - the error message I get is:
Subject: BarTender: Warning Message #2510

Date: 2012-06-25
Time: 12:59:36
Message Number: 2510
Message Type: Warning
Message Category: Log To Database
Response to Message: OK
Message Body:
Unable to log information to the BarTender System Database. Make sure the BarTender System Service is installed and running.

Everything else seems to work under this service account - It picks up the files, renames them, prints just fine. But it cannot log to the database. I know I can just have it log to files but would prefer logging to the database. My user id is able to log into this database using Windows authenication. The service account cannot. I thought if I went through the database set up in BarTender, it would apply when logging via Commander but that does not seem to be the case. How can I get my service account (which DOES NOT have the ability to log on to any of our servers and is not set up with Windows Authenication to be able to specify a local SQL server account/password to use for logging when logging is done via Commander?

Is there some additional authority I need to give this service account and/or local SQL account?

Thanks!

Suzanne