Forum OpenACS Q&A: Trying to add a task to Project causes Server Error

I had created a new project, then tried to add a task for me, the Lead and only person assigned to the task:

Server Error

There was a server error processing your request. We apologize.

Here is a detailed dump of what took place at the time of the error, which may assist a programmer in tracking down the problem:

Database operation "0or1row" failed (exception NSDB, "Query was not a statement returning rows.")

ERROR: column "task_id" does not exist
CONTEXT: PL/pgSQL function "pm_task__new_task_item" line 74 at SQL statement

SQL:
select pm_task__new_task_item (
'936',
'Show up at work',
'I have to go to work 5 days a week',
'text/plain',
to_timestamp('2005-09-24','YYYY MM DD HH24 MI SS'),
'0',
'1000.0',
'0',
'2000',
'1',
NULL,
coalesce (NULL,current_timestamp),
'459',
'63.198.177.76',
'881',
'0')

while executing
"ns_pg_bind 0or1row nsdb0 {
select pm_task__new_task_item (
:project_id,
:title,
:description,
:mime_type,
..."
("uplevel" body line 1)
invoked from within
"uplevel $ulevel [list ns_pg_bind $type $db $sql]"
("postgresql" arm line 2)
invoked from within
"switch $driverkey {
oracle {
return [uplevel $ulevel [list ns_ora $type $db $sql] $args]
}
..."
invoked from within
"db_exec 0or1row $db $full_statement_name $sql"
invoked from within
"if {[regexp -nocase -- {^\s*select} $test_sql match]} {
ns_log Debug "PLPGSQL: bypassed anon function"
set selection [..."
("uplevel" body line 6)
invoked from within
"uplevel 1 $code_block "
invoked from within
"db_with_handle -dbn $dbn db {
# plsql calls that are simple selects bypass the plpgsql
# mechanism for creating anonymous fun..."
(procedure "db_exec_plsql" line 57)
invoked from within
"db_exec_plsql new_task_item { *SQL }"
(procedure "pm::task::new" line 13)
invoked from within
"pm::task::new -project_id $project_item_id($num) -title $task_title($num) -description $description($..."
("foreach" body line 20)
invoked from within
"foreach num $number {

# --------------------------
# figure out estimated hours
# --------------------------

if {[st..."
invoked from within
"if {[string is true $edit_p]} {

# -------
# EDITING
# -------


# -----------------------------------------------------
#..."
("uplevel" body line 109)
invoked from within
"uplevel {
#

ad_page_contract {

Processes the add or edit

@author Jade Rubick (mailto:jader@bread.com)
@creation-date 2004-10-13..."
(procedure "code::tcl::/usr/local/share/service0/packages/project-manage..." line 2)
invoked from within
"code::tcl::$__adp_stub"
invoked from within
"if { [file exists $__adp_stub.tcl] } {

# ensure that data source preparation procedure exists and is up-to-date
adp_init tcl $__adp_stub
..."
("uplevel" body line 3)
invoked from within
"uplevel {

if { [file exists $__adp_stub.tcl] } {

# ensure that data source preparation procedure exists and is up-to-date
adp_init t..."
(procedure "adp_prepare" line 2)
invoked from within
"adp_prepare "
(procedure "template::adp_parse" line 30)
invoked from within
"template::adp_parse [file root [ad_conn file]] {}"
(procedure "adp_parse_ad_conn_file" line 5)
invoked from within
"$handler"
("uplevel" body line 2)
invoked from within
"uplevel $code"
invoked from within
"ad_try {
$handler
} ad_script_abort val {
# do nothing
}"
invoked from within
"rp_serve_concrete_file [ad_conn file]"
(procedure "rp_serve_abstract_file" line 60)
invoked from within
"rp_serve_abstract_file "$root/$path""
("uplevel" body line 2)
invoked from within
"uplevel $code"
invoked from within
"ad_try {
rp_serve_abstract_file "$root/$path"
set tcl_url2file([ad_conn url]) [ad_conn file]
set tcl_url2path_info..."

Collapse
Posted by Fred Cox on
Creating a customer seems to have solved this.
Collapse
Posted by Fred Cox on
Spoke too soon. Submitting the task still gets this error.
Collapse
Posted by Fred Cox on
Looks like this is bug #2599, submitted on the 12th.

Any clue as to how long before it might be fixed?

Collapse
Posted by Alex Kroman on
Hi Fred,

My apologies, you must really be frustrated with project manager right now. Thanks for sticking with it, hopefully it will work well for you (once you get it working that is).

I have released another version of project manager which fixes this bug that should be available within the next 24 hours.

The problem was that a modification was made in an upgrade script that wasn't ported back into the installation scripts. Since most of the project manager users have been using it for a while it wasn't noticed until now.

Hopefully this will be enough to get you up an running. A lot of people are currently hard at work on the next version of project manager so if you have any ideas that would make it better feel free to post them in the forums.