• Replies 18 replies
  • Subscribers 338 subscribers
  • Views 260 views
  • Users 0 members are here
Related

Running Multiple Instances of Tessitura

Britt East
$organization

I am relatively new to Tessitura, and am interested in running multiple instances of the software (v9.0.0.1) on one workstation. I found this article, which describes the process:

Issue Summary:Is it possible to run more than one Tessitura session on a single workstation?
Detailed Description: Is it possible to run more than one Tessitura session on a single workstation?
Resolution:Yes, it is possible to run multiple instances of Tessitura on a single workstation. In order to do so, the following will need to be done for each workstation where you wish to run multiple sessions: 1) On the workstation, create a separate version of the local ini file (tessitura.ini) which specifies a different hostname. This entry should be placed in the [SQLCA] section of the ini file. For example, if the new hostname will be TESTHOST, add an entry to the new tessitura.ini file in the SQLCA section like this: Hostname=TESTHOST 2) Add a new row in the TX_MACHINE_LOCATION table specifying the new hostname. Following the example above, you would add a new row to this table where the Machine Name is "TESTHOST". 3) Create a new Tessitura desktop shortcut that will point to the new ini file.
I think I completed everything successfully, but I get an error message: "This PC ("TESTHOST") does not ha ve a location assigned." I tried to paste a screenshot into this window, but couldn't get that to work.
In reading the Table Help notes in Tessitura for TX_Machine_Location, I see the following:
Entries in this table have the following values:
Machine Name – The Windows name of the workstation.
Location – The location value for the workstation.  Location values come from TR_LOCATION.
The Windows name for this workstation is "CMP137". That is already associated with a table entry in TX_Machine_Location. So that may be the problem. But not sure how to work around that...
Have any of you had any experience with this? Seems like it should be simple, so I'm sure I'm just doing something boneheaded! LOL!
Thanks,
Britt


[edited by: Britt East at 3:37 PM (GMT -6) on 14 Oct 2009]
Parents
  • $organization

    Hi Britt,

    Check the system table within tessitura TX_MACHINE_LOCATION and make sure the "location" is assigned for machine name which I assume would be TESTHOST.

    Normally I just look for the row in TX_MACHINE_LOCATION that has a blank location and assign it.

  • $organization in reply to Ryan Rowell

    Thanks Ryan! I didn't see any blank fields, so I just added a new row, then saved my work.

    In reading the Table Help notes in Tessitura for TX_Machine_Location, I see the following:
    Entries in this table have the following values:
    Machine Name – The Windows name of the workstation.
    Location – The location value for the workstation.  Location values come from TR_LOCATION.
    The Windows name for this workstation is "CMP137". That is already associated with a table entry in TX_Machine_Location.
    So that may be the problem. But not sure how to work around that...
  • $organization in reply to Britt East

    Hmm, well someone else may need to help you out on this since I'm not too familiar with the process but here are a couple things I noticed about my test environment
    which I have set to run at the same time as my production.

    Local .ini file has different hostname
    Ex. here is some of the content of my local file so I can have my test environment

    [sqlca]
    HOSTNAME=rrowell-ps-tst02
    MasterIniFilePath="t:\startup\tessitura_test02_master.ini"


    The target in the shortcut properties points to the local file
    Ex. here is my target

    T:\Startup\Tessitura_test02_Start.bat "c:\windows\system32\tessitura_test02.ini

    I believe the process is the same for having two instances of production.
    Hope you get it figured out!

    Cheers!

  • $organization in reply to Ryan Rowell

    Thanks Ryan! I'm set up the same way.

    I think the error must be in the way I am configuring the entry in the TX_MACHINE_LOCATION table...

    Anybody else have any ideas? :  )

  • Former Member
    Former Member $organization in reply to Britt East

    You should be able to fix this problem by editing the tx_machine_location table from another instance of Tessitura accessing the same database.

    To do so, open tx_machine_location in System Tables, and on the row with machine name "TESTHOST", choose a location value from the dropdown in the Location column.

  • $organization in reply to Former Member

    Thanks Steven! I guess I don't understand. Administration is my only choice from the Location drop down menu (other than "none").

    We only have one location built in the TR_Location table, and that is Administration. I'm relatively new here, so I'm not sure why that decision was made. Every row in the TX_Machine_Location table uses Administration as the location.

  • Former Member
    Former Member $organization in reply to Britt East

    That's fine; you can just set it to Administration. That location is part of the default Tessitura setup; basically, this field would be to track the general location of a particular workstation if a site wishes to do so.

    We just require that this value be specified, as an additional means of security, in order to allow a particular "host" or machine to run the Tessitura software against a particular database.

Reply
  • Former Member
    Former Member $organization in reply to Britt East

    That's fine; you can just set it to Administration. That location is part of the default Tessitura setup; basically, this field would be to track the general location of a particular workstation if a site wishes to do so.

    We just require that this value be specified, as an additional means of security, in order to allow a particular "host" or machine to run the Tessitura software against a particular database.

Children