Error #2510 Unable To Log To Database, After Successful Logging To Database
OS: Windows Server 2008R2 SP1
BarTender: 10.0 SR2
Edition: Enterprise Automation (3 Printers)
Activation Status: Activated
I have activated email alerting for BarTender. Every time I print, it sends an email with Error #2510 "Unable to log information to the BarTender System Database. ..." However, history explorer shows the same informational message "BarTender successfullly sent the print job to the spooler." as appears in the text log (BtMsg.txt). I also, see the error #2510 in the BtMsg.txt log, but not in history explorer.
I do not know if it is relevant, but we are using commander with uploading a file to trigger the print. Commander has been setup to log to the database and appears to be doing so. It is not enabled with email alerts yet, so it should not be the source of the failure messages.
Note: This also happened with SR1 before upgrading to SR2.
Here is a sample of the error received via email:
Subject: BarTender: Warning Message #2510
Date: 2012-10-17
Time: 17:04:58
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.
Thank you for any attention you can pay this matter.
Regards,
Joe M.
BarTender: 10.0 SR2
Edition: Enterprise Automation (3 Printers)
Activation Status: Activated
I have activated email alerting for BarTender. Every time I print, it sends an email with Error #2510 "Unable to log information to the BarTender System Database. ..." However, history explorer shows the same informational message "BarTender successfullly sent the print job to the spooler." as appears in the text log (BtMsg.txt). I also, see the error #2510 in the BtMsg.txt log, but not in history explorer.
I do not know if it is relevant, but we are using commander with uploading a file to trigger the print. Commander has been setup to log to the database and appears to be doing so. It is not enabled with email alerts yet, so it should not be the source of the failure messages.
Note: This also happened with SR1 before upgrading to SR2.
Here is a sample of the error received via email:
Subject: BarTender: Warning Message #2510
Date: 2012-10-17
Time: 17:04:58
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.
Thank you for any attention you can pay this matter.
Regards,
Joe M.
0
-
Check to make sure the system service is listed in the Windows Services. If not then:
1. Open a Command Prompt window (DOS).
2. Change directory to the folder where .NET Framework is installed (e.g. c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727")
3. Use the "installutil" tool to add the service:
installutil /name="BarTender System Service" "C:\Program Files\Seagull\BarTender Suite\System\BtSystem.Service.exe"
4. Open the properties of the service, select the logon tab and make sure that you specify domain credentials that have enough permissions to access folder, file, printer and the SQL Server database.0 -
I should point out that logging to the database is successful.
BarTender System Service is installed, set to start Automatic(Delayed).
BarTender System Service Logon is Local System.
SQL Server is the one installed by BarTender Suite. (SQL 2005 Express?)
Local System (NT AUTHORITY\SYSTEM) has sysadmin privileges on the instance.
I verified that messages are being logged successfully to the database, both through History Explorer and using SSMS to view contents of BarTender.dbo.MessagesView in database directly.
Right now everything is running locally. Why should I use a domain account?0 -
In BarTender, under the "Administer > Log Setup > Database Log", what information is exactly being logged to the system database? Is it just the "Application Messages", or as well Print Job information such as "Template Data"? If you're also logging print job information to the system database, can you make sure that this information is also being logged properly?
Otherwise, the error message might be refering to the lack of "print job data" in the BT system database, in which case running the BT System Service under a domain account with more permissions might be required.0
Please sign in to leave a comment.
Comments
3 comments