跳到主内容

搜索

搜索

Another Db Problem

评论

5 条评论

  • Avatar
    Domingo Rodriguez
    版主

    What exact OLE DB provider or ODBC driver are you using for your Oracle database? What version is your Oracle database server? 

     

    Can you attach a screenshot of the query prompt you're trying to run?

     

    Can you enable a trace in your Oracle Server and send us the result of the trace? 

    0
  • Avatar
    Legacy Poster

    Hi,

     

    I solved the crashing problem by using 32-bit compatibility mode (64bit windows 7 enterprise version). The driver I'm using is the one in the latest OraClient11g package. I'm unsure about the database server version, it's not in my hands. Everyone from the DB department is on a holiday or otherwise unavailable, so I can't produce the traces either, sorry.

     

    After solving the constant crashing I ran into a problem with commander. While printing from Bartender works just fine If I'm using a database printing the exact same template from Commander doesn't work. The only thing I see in logs is the print authorization, but nothing else happens. The connection between Commander and Bartender works fine, printing templates that have only static fields work without a hitch when triggered from Commander.

     

    I've tried defining the DB username /  password from Commander and saving them to the template (both at the same time, both at different times) but nothing happens and retrying fails until I shut down Commander and only then trigger it the task again.

     

    To clarify -- I'm trying to implement this scenario

     

    I use an external software to generate trigger files for Commander. I have exactly one template file defined for Bartender to use. Trigger files contain no data, but it does have a query prompt parameter defined (a db record ID number). Everything needed for printing is in that record (+ joined table for image data -- I've tried triggering printing without the join too without any success). Should be straightforward, but I'm not getting enough debug feedback from Bartender to know what's the problem.

     

    EDIT: I've configured to log everything possible except for message 1800 since it simply spams too much.

    0
  • Avatar
    Domingo Rodriguez
    版主

    As a test, run Commander as an application (rather than as a service). Do this via the "Administer > Service Setup" dialog in Commander. Now Start Detection and choose "Detection > Show all Running BarTenders". Send your trigger file now and observe what happens in BarTender (does the BT document open, do you see any error message, what happens when you try to print...
     
    Furthermore, you can just try to connect to the Oracle database without using any text database which will act as the join. Just for testing purposes to see if the print via Commander works fine.
     
    I've and additional question on your Oracle database driver. Are you now using the 32 bit version of the driver? Please confirm.
     
     
    BTW: We've also received an email today from you which we won't answer for now as the question is exactly the same as the one in the forum

    0
  • Avatar
    Legacy Poster

    Seems that running Commander in application mode did the trick. Awesome!

     

    For posteriority -- I was using 32-bit oracle client db drivers.

    0
  • Avatar
    Domingo Rodriguez
    版主

    If you're still interesting in getting this to work as a service, you can try to set a Windows account for the underlying BarTender processes which are running when Detection is started in Commander. Do this via the "Detection > BarTender Command Handler Setup" dialog and now by selecting the "User Account" tab. You can try using the same Windows account you use when launching Commander as an application.

    0

请先登录再写评论。