When I click on Admin->Accounts, I recieve the following error:
ATTENTION! This page generated some errors.
Please resolve the problem based on the
error message below. If you are unable to resolve
the problem, please ask us for help: support@rtda.com
Be sure to copy and paste the error stacks, if any, to the email you send to us. Thanks.
can't read 'DATA(0a010a40.0,users)': no such element in arraycan't read "DATA(0a010a40.0,users)": no such element in array
while executing
"if { $DATA($account,users) == {} } {
COLOR red "This account has no checkouts"
} else {
set sortedList [lsort $DATA($account,users..."
("uplevel" body line 2)
invoked from within
"uplevel $script"
(procedure "SMALL" line 1)
invoked from within
"SMALL {
if { $DATA($account,users) == {} } {
COLOR red "This account has no checkouts"
} else {
set sortedList [lsort $DATA($a..."
("uplevel" body line 2)
invoked from within
"uplevel {
SMALL {
if { $DATA($account,users) == {} } {
COLOR red "This account has no checkouts"
} else {
set sortedLi..."
("eval" body line 1)
invoked from within
"eval uplevel [lrange $args end end]"
(procedure "TD" line 8)
invoked from within
"TD VALIGN="TOP" {
SMALL {
if { $DATA($account,users) == {} } {
COLOR red "This account has no checkouts"
} else {
set ..."
("uplevel" body line 4)
invoked from within
"uplevel {
TH VALIGN="TOP" ALIGN="LEFT" { OUT $account }
# TD VALIGN="TOP" ALIGN="RIGHT" { OUT $ACCOUNTS(id,$account) }
TD VALIGN="TOP" {
..."
("eval" body line 1)
invoked from within
"eval uplevel [lrange $args end end]"
(procedure "TR" line 8)
invoked from within
"TR {
TH VALIGN="TOP" ALIGN="LEFT" { OUT $account }
# TD VALIGN="TOP" ALIGN="RIGHT" { OUT $ACCOUNTS(id,$account) }
TD VALIGN="TOP" {
..."
("foreach" body line 2)
invoked from within
"foreach account [lsort $DATA(accountList)] {
TR {
TH VALIGN="TOP" ALIGN="LEFT" { OUT $account }
# TD VALIGN="TOP" ALIGN="RIGHT" { OUT $AC..."
("uplevel" body line 18)
invoked from within
"uplevel {
TR BGCOLOR="white" {
TH { OUT "Account" }
# TH { OUT "DbId" }
TD ALIGN=CENTER {
B { OUT "List of Users" }
BR
S..."
("eval" body line 1)
invoked from within
"eval uplevel [lrange $args end end]"
(procedure "TABLE" line 8)
invoked from within
"TABLE BORDER=1 CELLSPACING=0 WIDTH="80%" ALIGN="CENTER" {
TR BGCOLOR="white" {
TH { OUT "Account" }
# TH { OUT "DbId" }
TD ALIGN=C..."
invoked from within
"if { $opt(subpage) == "byaccount" } {
TABLE BORDER=1 CELLSPACING=0 WIDTH="80%" ALIGN="CENTER" {
TR BGCOLOR="white" {
TH { OUT "Account" }..."
("uplevel" body line 132)
invoked from within
"uplevel $body_script"
Is this with update 2?
Henry,
I checked the code and there appears to be a mismatch between your stack dump and what the latest source contains. Is this with update 2 or prior to updating?
Brian
I noticed the same error
I noticed the same error before and after Update 2...
Ok, looks like my initial
Ok, looks like my initial 2009.08 Update2 wasn't correct but now I believe it should be OK, the error is slightly reduced to the following error below:
ATTENTION! This page generated some errors.
Please resolve the problem based on the
error message below. If you are unable to resolve
the problem, please ask us for help: support@rtda.com
Be sure to copy and paste the error stacks, if any, to the email you send to us. Thanks.
can't read 'DATA(0a010a40.0,users)': no such element in arraycan't read "DATA(0a010a40.0,users)": no such element in array
while executing
"if { $DATA($account,users) == {} } {
set userListHtml "This account has no checkouts"
} else {
set userListHtml ""
set sortedList ..."
("foreach" body line 4)
invoked from within
"foreach account [lsort $DATA(accountList)] {
set row [VovHtmlTable::getNextRowIndex tb]
VovHtmlTable::addData tb $row account $account
if { $DAT..."
invoked from within
"if { $opt(subpage) == "byuser" } {
foreach user $DATA(userList) {
if { $DATA($user,accounts) == {} } {
set row [VovHtmlTable::getNextRow..."
("uplevel" body line 114)
invoked from within
"uplevel $body_script"
I'm working on a fix for this
I'm working on a fix for this right now. This page has mostly become obsolete. I'll probably update the "Update 2" since only 2-3 people have grabbed it. This will require you to reinstall the update for "common" only. Please stay tuned.
I grabbed the latest Update2
I grabbed the latest Update2 Common and installed it this morning... looks like it's now fixed!
Thanks Brian