Bartender print engine not starting after a long period of idleness
Hello, we are experiencing an ongoing issue where the bartender print engine will not restart after an extended period of idleness, we have tried several avenues of attack including increasing system resources and reducing the size of the data base but this keeps popping up. I have pasted in what I believe to be the relevant parts of the logs below.
Thank you so much for any assistance you can provide
PrintScheduler.Service.text
2018.06.17.010720||||||INFO|Allocating 8 dynamic engine instances.
2018.06.17.010720||||||INFO|Task engines will only start when they are needed.
2018.06.17.220612|1|||||ERROR|Engine 1 is not alive. Scheduling it for a restart.
2018.06.17.220612|1|||||INFO|BarTender print engine 1 started.
2018.06.17.220642||||||ERROR|The BarTender engine could not be started. Possible reasons are:«CR»«LF»«CR»«LF»1) BarTender is not properly installed.«CR»«LF»2) BarTender is not properly registered on the computer (e.g bartend.exe /register).«CR»«LF»3) There are too many process instances of BarTender running. Stop a few bartend.exe instances and try again. Also see SDK Engine.Start method documentation for information about how to allow more BarTender processes to run on your computer by increasing your "non-interactive" shared desktop heap.«CR»«LF»4) The user account does not have permission to run BarTender. Details: Error number: 12, Reason Code: FailedStart: %s
2018.06.17.220642|1|ec950d27-6a98-46da-b53b-e4c6f748a8e4|Print Command Script subtask 1|\\ffarphprnt3\Labels\2dmcsLabelV2_WIP.btw|\\FFARPHPRNT3\Rhamnella|ERROR|The BarTender engine could not be started. Possible reasons are:«CR»«LF»«CR»«LF»1) BarTender is not properly installed.«CR»«LF»2) BarTender is not properly registered on the computer (e.g bartend.exe /register).«CR»«LF»3) There are too many process instances of BarTender running. Stop a few bartend.exe instances and try again. Also see SDK Engine.Start method documentation for information about how to allow more BarTender processes to run on your computer by increasing your "non-interactive" shared desktop heap.«CR»«LF»4) The user account does not have permission to run BarTender. Error number: 12 ::CoUnmarshalInterface failed: 0x80070218
2018.06.17.220642|1|||||ERROR|An error occurred in the task engine consumer thread. Details The BarTender engine could not be started. Possible reasons are:«CR»«LF»«CR»«LF»1) BarTender is not properly installed.«CR»«LF»2) BarTender is not properly registered on the computer (e.g bartend.exe /register).«CR»«LF»3) There are too many process instances of BarTender running. Stop a few bartend.exe instances and try again. Also see SDK Engine.Start method documentation for information about how to allow more BarTender processes to run on your computer by increasing your "non-interactive" shared desktop heap.«CR»«LF»4) The user account does not have permission to run BarTender.
2018.06.17.220642|1|ec950d27-6a98-46da-b53b-e4c6f748a8e4|Print Command Script subtask 1|\\ffarphprnt3\Labels\2dmcsLabelV2_WIP.btw|\\FFARPHPRNT3\Rhamnella|INFO|'Print Command Script subtask 1' was cancelled.
2018.06.17.220642|1|ec950d27-6a98-46da-b53b-e4c6f748a8e4|Print Command Script subtask 1|\\ffarphprnt3\Labels\2dmcsLabelV2_WIP.btw|\\FFARPHPRNT3\Rhamnella|INFO|Print Scheduler task 'Print Command Script subtask 1' completed.
-
Hi Thomas,
I think you would be better raising this with the Technical Support Team directly rather than post it on here on the user forum as they should be able to put you right I would hope.
Pete
0 -
Did you ever get a solution to this problem? We are getting the same error.
0 -
Hi, any news on this issue ?
we are facing same log "subtask 1' was cancelled.", any idea about the subtask ?
thanks!
0 -
As mentioned above I would suggest raising a support ticket (via the Submit a Request above) for this and contact Seagull's Tech team direct to see if they can help with this one
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
4 Kommentare