Activity processor fails following upgrade to 4.1.2 and then 4.1.3

[myles]

Upgraded Drupal 6 4.1.1 installation to 4.1.2 then 4.1.3 with no errors reported.

The Activity processor, which used to work now returns this error message:

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

Where do I look to find out more?

In another thread, which looks similar the request was to look at the CiviCRM log file... Where is this and what is it called?

Many thanks (in anticipation)

[Donald Lobo]

Can you check the code at:

api/v3/Job.php, function civicrm_api3_job_fetch_activities

and see why it does not return a success object

thanx

lobo

[Hershel]

On a related note, I wonder why in function civicrm_api3_job_fetch_activities and function civicrm_api3_job_fetch_bounces the line

Code: [Select]

  $lock->release();

comes after the return statements. Seems the lock will never be released....

[Donald Lobo]

i fixed this for 4.1.4

However that should not impact the return value

[myles]

Sorry Lobo - I'm not ignoring your kind reply - I've spent the entire day setting up a MAMP development environment on a mac and trying to get debug + MacGDBp to work.

So far I can't get the thing started!

I'm going to bed!

[myles]

I'm still having problems with setting up a local install but I notice that the list of scheduled jobs in a new install is really quite different from the list of scheduled jobs in our live (the upgraded) site.

On the demo there is a job 'Process Inbound Emails' that references 'fetch_activity' in the API

On ours this is absent, but there is 'Activity Processor' that references 'fetch_activity' which used to process the inbound mails and now does not - it is not present in a clean install of 4.1.3

Is this a sign of a partially failed upgrade?

[Donald Lobo]

probably.

For now, can you just truncate: civicrm_job

and load a clean copy for a pristine 4.1.3

thanx

lobo

[myles]

Thanks - I now have the same list as the pristine version, but the same result!

Agh well, worth a shot.

[myles]

Now on version 4.1.5 and still fiddling with this when I get the chance... with no further ideas that yield any interest - but...

Perhaps someone could verify that these parameters are the correct ones?

From the activity log:

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

Many thanks