QDX_Tcl_SplitList({OX) failed

[Kevin Crist]

we are doing an upgrade to a system what i did was create copied the currently working thread and made a new one and just changed the name. I did this with 4 other threads as well. But this one is giving me an error:

[xpm :xlt :ERR /0:charges900_xlate:03/24/2010 14:19:28] QDX_Tcl_SplitList({OX) failed: unmatched open brace in list

[xlt :xlat:ERR /0:charges900_xlate:03/24/2010 14:19:28] [0.0.2060622] Xlate ‘care_affi_DFTP03.xlt’ failed: Internal XPM Tcl error

erroCode: NONE

errorInfo:

invalid command name “tix”

   while executing

“tix option get fixed_font”

So, i did some searching on here and found that i should run it through testing tool and check it out: So here is that error:

MESSAGE 1

[0:TEST] QDX_Tcl_SplitList({OX) failed: unmatched open brace in list

Internal XPM Tcl error

erroCode: NONE

errorInfo:

site table /quovadx/qdx5.4.1/integrator/test900/Tables/chargeDeptCodes.tbl does not exist

   while executing

“error “site table $tableName does not exist””

   invoked from within

“if [cequal $useRoot B] {

       if ![file exists $tableName] {

           set siteTableName $tableName

           set tableName [file join $HciRoot…”

   (procedure “TioLoad” line 8)

   invoked from within

“TioLoad tblLoadDef-recid chargeDeptCodes.tbl N”

So i looked into the table. The table is there, nothing has been changed in the xlate, this is in our test site. Our live site is identical and running fine. I have deleted the copied thread, and tried to do it over but no luck. I have attached what our xlate looks like, which has been running fine for a very long time. I tried a validate in the netconfig and it was ok, and compiled the Xlate and it was fine. Any ideas or hints would be awesome.

Thanks for your time.

Topic

[Troy Morton]

Hi Kevin,

Have you tried comparing the Test and Prod Xlate and Table just to make sure they are really identical?

[Kevin Crist]

Thanks for the post Troy. I did find the issue, but i forgot to let you all know. There was something wrong with the message that was coming out. it was due to the new upgrade so one of the fields was messed up. After doing some more digging on clovertech i found post that gave me that hint.

Thanks for your time.

[Author]

Replies