メインコンテンツへスキップ

検索

検索

Commander Task Status Shows "executing"

コメント

3件のコメント

  • Avatar
    Ian Cummings
    モデレータ
    Desktop heap is the top candidate in my opinion. I wouldn't wait until you get v10 to increase it.

    Why are you running 5 BarTender processes? Do you have 5 or more cores on your CPU? If not then there is little to be gained by the extra number of processes from a throughput point of view. Remember that each process will consume memory and can have X number of label formats loaded after a while increasing the memory load. If you have many label formats in use then this will contribute to memory resource issues. Version 10 will cure much of this for you with just default settings.

    It's best practice to use locally installed printer drivers instead of a server/client install where the client side driver is where BarTender/Commander is running. Also, make sure that any Seagull printer drivers are up to date. The current version is v7.3.
    0
  • Avatar
    Legacy Poster
    Just wanted to post an update to this. We upgraded from 9.2 to 10.0 and do not have the 'Executing' issue any more. I found an option in the new version (within the BarTender Commander Handler) to automatically restart if it stops and to automatically reprint if a print request fails. I am not sure if we have just not had this issue or if these settings cause it to be transparent to us as it restarts and/or reprints. I have seen nothing to indicate the problem in the logs - so I suspect it was just a 9.2 issue.

    Anyway, just wanted to provide this information in case someone is having this issue and wondering if upgrading might help. Certainly helped for me.

    Thanks!
    0
  • Avatar
    Legacy Poster
    [quote name='smarkind' timestamp='1340653380' post='2663']
    Just wanted to post an update to this. We upgraded from 9.2 to 10.0 and do not have the 'Executing' issue any more. I found an option in the new version (within the BarTender Commander Handler) to automatically restart if it stops and to automatically reprint if a print request fails. I am not sure if we have just not had this issue or if these settings cause it to be transparent to us as it restarts and/or reprints. I have seen nothing to indicate the problem in the logs - so I suspect it was just a 9.2 issue.

    Anyway, just wanted to provide this information in case someone is having this issue and wondering if upgrading might help. Certainly helped for me.

    Thanks!
    [/quote]

    We are running 10.x in a DEV environmet and have noticed this exact issue (just posted about it here http://seagullscientific.invisionzone.com/index.php?/topic/996-v10-crashingstalling/) ... we've already increased HEAP and will try to other settings you suggested.
    0

サインインしてコメントを残してください。