Author Topic: different problems after upgrading to 4.1.1 and 4.1.2 (Read 2612 times)

CatorgHans · May 17, 2012, 03:26:56 am

Scheduled jobs based on activities are now failing.

Activity processor says:

Parameters parsed (and passed to API method): 
a:1:{s:7:"version";i:3;}

Full message: 
Finished execution of Activity processor with result: Failure, Error message: Process Activities failed

Scheduled reminders sender says:

Code: [Select]

Parameters parsed (and passed to API method): 
a:1:{s:7:"version";i:3;}

Full message: 
Finished execution of Scheduled reminders sender with result: Failure, Error message: DB Error: no such field

Other scheduled jobs function as expected:
Report sender (Daily)
Mailings scheduler
Address geocoder

Anyone an idea what is causing this and how to solve (or how I could get more information about WHAT exactly is going wrong)?

Donald Lobo · May 17, 2012, 10:33:29 am

Can u check your CiviCRM.*.log file to see what the DB error is

thanx

lobo

CatorgHans · May 18, 2012, 12:13:02 am

This is what I get with the Mailing Scheduler:

Code: [Select]

May 18 09:05:02  [info] Beginning processQueue run: 0, 0
May 18 09:05:02  [info] Ending processQueue run

The other Scheduled Jobs that I have activated give nothing, also not the ones that fail.

A few times a day, without a specific internval, so I expect it to be triggered by a certain page view I have

Code: [Select]

May 17 13:18:36  [info] $Fatal Error Details = Array
(
    [message] => Could not find valid value for ct
    [code] =>
)


May 17 13:18:36  [info] $backTrace = /var/www/sites/all/modules/civicrm/CRM/Core/Error.php, backtrace, 303
/var/www/sites/all/modules/civicrm/CRM/Utils/Request.php, fatal, 109
/var/www/sites/all/modules/civicrm/CRM/Contact/Form/Contact.php, retrieve, 150
/var/www/sites/all/modules/civicrm/CRM/Core/Form.php, preProcess, 329
/var/www/sites/all/modules/civicrm/CRM/Core/QuickForm/Action/Display.php, buildForm, 99
/var/www/sites/all/modules/civicrm/packages/HTML/QuickForm/Controller.php, perform, 203
/var/www/sites/all/modules/civicrm/packages/HTML/QuickForm/Page.php, handle, 103
/var/www/sites/all/modules/civicrm/CRM/Core/Controller.php, handle, 284
/var/www/sites/all/modules/civicrm/CRM/Utils/Wrapper.php, run, 117
/var/www/sites/all/modules/civicrm/CRM/Core/Invoke.php, run, 199
/var/www/sites/all/modules/civicrm/drupal/civicrm.module, invoke, 372
, civicrm_invoke,
/var/www/includes/menu.inc, call_user_func_array, 350
/var/www/index.php, menu_execute_active_handler, 17

grgrygary · May 28, 2012, 10:37:42 am

I am also having this issue, any help on the fix or resolve would be much appreciated!

Thanks
Gary

CatorgHans · May 28, 2012, 10:40:25 am

I suspect an upgrade gone wrong without a proper warning.

How would you do an database integrity check for 4.1.2?
I would like to perform one.

grgrygary · May 28, 2012, 10:44:19 am

Hi,

I am having this issue. We have not upgraded ours is a new install of Civi 4.1.1. nd we are getting the same error and the event reminders are not being sent.

I tried applying the patch in this topic http://forum.civicrm.org/index.php/topic,24505.0.html

But it didn't work, if you find the answer anywhere please post! I am pulling my hair out trying to get these reminders to work.

Thanks
Gary

CatorgHans · June 03, 2012, 09:19:30 am

I mimicked the reminder scheduling with
/civicrm/ajax/doc#/civicrm/ajax/rest?json=1&sequential=1&debug=1&&entity=Job&action=send_reminder

And that gave me more information:

Code: [Select]

"message":"DB Error: no such field",
			"userinfo":"\nINSERT INTO civicrm_action_log (contact_id, entity_id, entity_table, action_schedule_id)\nSELECT r.assignee_contact_id as contact_id, e.id as entity_id, 'civicrm_activity' as entity_table, 1 as action_schedule_id \nFROM civicrm_activity e \nINNER JOIN civicrm_activity_assignment r ON  r.activity_id = e.id INNER JOIN civicrm_contact c ON c.id = r.assignee_contact_id\nLEFT JOIN civicrm_action_log reminder ON reminder.contact_id = r.assignee_contact_id AND \nreminder.entity_id          = e.id AND \nreminder.entity_table       = 'civicrm_activity' AND\nreminder.action_schedule_id = 1\nWHERE e.activity_type_id IN (1) AND e.status_id IN (1) AND  e.is_current_revision = 1  AND  e.is_deleted = 0  AND c.is_deleted = 0 AND reminder.id IS NULL AND '20120603180913' >= DATE_SUB(e.activity_date_time, INTERVAL 1 hour) AND DATE_SUB(20120603180913, INTERVAL 1 DAY ) <= r.start_date [nativecode=1054 ** Unknown column 'r.start_date' in 'where clause']",

which makes sense:
table "civicrm_activity_assignment r" does not have an r.start_date

Donald Lobo · June 03, 2012, 06:42:13 pm

This has been fixed for 4.1.3. The query was wrong. You can get the latest file from svn if u would like to test and move forward

lobo

CatorgHans · June 04, 2012, 01:22:56 am

Can you point me to the specific file? I want to create a diff and explore it. It is our production CRM, and can not add 4.1.3 yet, but a diff that solves this one problem I would like to create.

Donald Lobo · June 04, 2012, 01:30:46 am

CRM/Core/BAO/ActionSchedule.php

CatorgHans · June 04, 2012, 02:35:36 am

I did this on CRM/Core/BAO/ActionSchedule.php:

Code: [Select]

<                 $startDateClause[] = $operator. "({$now}, INTERVAL 1 DAY ) {$op} r.start_date";
---
>         $startDateClause[] = $operator . "({$now}, INTERVAL 1 DAY ) {$op} " . $actionSchedule->start_action_date;

The Scheduled Reminder now works, thanks!

The "Activity processor" still has an error. I can not get more info about what goes wrong. Is that been addressed to in svn?

Finished execution of Activity processor with result: Failure, Error message: Process Activities failed

Donald Lobo · June 04, 2012, 04:32:46 am

Dont think so. Can you please debug in api/v3/Job.php and figure out whats happening and why

thanx

lobo

CatorgHans · June 04, 2012, 04:35:35 am

That does not give similar extensive error messages.

I will try to get more info in different ways.

Interpolat · June 05, 2012, 12:45:52 pm

I am experiencing a different set of problems on my CiviCRM installed on wordpress site, since upgrading from 4.1.1 to 4.1.2.

I am unable to view the WYSIWYG menu for pages I want to edit (Contribution pages). I am also unable to see Contribution charts or graphs. Finally, I had some donors submit pledges through CiviPledge. I look at the pledge data (in edit mode), and within the "date received" field, I see the following "06http:http://www.hivai4szi6babwe.156rg/http://www.hivai4szi6babwe.156rg/www.hivai4szi6babwe.156rghttp://www.hivai4szi6babwe.156rg/04http:http://www.hivai4szi6babwe.156rg/http://www.hivai4szi6babwe.156rg/www.hivai4szi6babwe.156rghttp://www.hivai4szi6babwe.156rg/2012"

This is what I copied from the field where the date should be at. I a seeing this kind of thing in all date fields, when in the edit mode.

Interpolat · June 05, 2012, 02:21:08 pm

Ok, I have fixed the issues with the charts/graphs not showing, by fixing the Resource URLs. However, the datepicker issue persists unresolved.

CiviCRM Community Forums (archive)

News:

Author Topic: different problems after upgrading to 4.1.1 and 4.1.2 (Read 2612 times)

CatorgHans

different problems after upgrading to 4.1.1 and 4.1.2

Donald Lobo

Re: different problems after upgrading to 4.1.1 and 4.1.2

CatorgHans

Re: different problems after upgrading to 4.1.1 and 4.1.2

grgrygary

Re: different problems after upgrading to 4.1.1 and 4.1.2

CatorgHans

Re: different problems after upgrading to 4.1.1 and 4.1.2

grgrygary

Re: different problems after upgrading to 4.1.1 and 4.1.2

CatorgHans

Re: different problems after upgrading to 4.1.1 and 4.1.2

Donald Lobo

Re: different problems after upgrading to 4.1.1 and 4.1.2

CatorgHans

Re: different problems after upgrading to 4.1.1 and 4.1.2

Donald Lobo

Re: different problems after upgrading to 4.1.1 and 4.1.2

CatorgHans

Re: different problems after upgrading to 4.1.1 and 4.1.2

Donald Lobo

Re: different problems after upgrading to 4.1.1 and 4.1.2

CatorgHans

Re: different problems after upgrading to 4.1.1 and 4.1.2

Interpolat

Re: different problems after upgrading to 4.1.1 and 4.1.2

Interpolat

Re: different problems after upgrading to 4.1.1 and 4.1.2