Answers.Body: <p>Looks like a conflicting extension was causing the problem. <strong><em>CiviRules</em></strong>. Once that is uninstalled everything seems to be working perfectly fine.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-16T14:55:07.767Z
Answers.LastActivityDate: 2016-05-16T14:55:07.767Z
Answers.UserDisplayName: Tapash
Answers.Body: <p>@Tapash - I just tried to reproduce this on one of our live 4.6.16 projects and I can not. </p>
  
  <p>From a Contact's Membership I'm successfully able to both:</p>
  
  <ul>
  <li>more -> Renew [no errors; renewed properly] &amp;</li>
  <li>more -> Renew-Credit Card [no errors; made payment; got receipt; renewed properly]</li>
  </ul>
  
  <p>I've also checked the JIRA issues and I don't see anyone else describing what you're observing. Considering your other Q as well - I'm wondering if perhaps something went wrong during your recent upgrade? </p>
  
  <p>General recipe for this is to restore both code base (files) &amp; databases back to 4.6.14 and then to run the upgrade script [to 4.6.16] again. If you can: run it via drush - it may give you some warnings/errors that give you some insight as to what's going on. </p>
  
  <blockquote>
    <p>sudo -u apache drush civicrm-upgrade-db</p>
  </blockquote>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-13T15:06:55.437Z
Answers.LastActivityDate: 2016-05-13T15:25:40.077Z
Answers.LastEditDate: 2016-05-13T15:25:40.077Z
Answers.UserDisplayName: KarinG - Semper IT
Body: <p>Since upgrade, I am not able to renew membership from backend. As soon I press RENEW I am getting this Fatal Error message: </p>
  
  <p><code>2016/05/13 11:57:55 [error] 8711#0: *2228 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Cannot pass parameter 2 by reference in /www/demo/sites/all/modules/civicrm/api/v3/utils.php on line 1408" while reading response header from upstream, client: 185.59.126.181, server: demo.com, request: "POST /civicrm/contact/view/membership HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm/demo.com.sock:", host: "demo.com", referrer: "https://demo.com/civicrm/contact/view/membership?action=renew&amp;reset=1&amp;cid=398&amp;id=52&amp;context=membership&amp;selectedChild=member"
  </code></p>
  
  <p>Can anyone help please? how to fix this?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T12:16:08.540Z
Comments.Text: Are you on PHP 5.6?
Comments.UserDisplayName: KarinG - Semper IT
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T12:17:02.220Z
Comments.Text: I am using  PHP 5.5
Comments.UserDisplayName: Tapash
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T12:20:39.643Z
Comments.Text: Did you upgrade from 4.6.15 -> 4.6.16?
Comments.UserDisplayName: KarinG - Semper IT
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T12:21:13.383Z
Comments.Text: No, I have upgraded from 4.6.14
Comments.UserDisplayName: Tapash
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T12:29:30.040Z
Comments.Text: Ok - good. I will have a look - this AM - and get back to you
Comments.UserDisplayName: KarinG - Semper IT
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T12:30:59.097Z
Comments.Text: is there a to go back to 4.6.14?
Comments.UserDisplayName: Tapash
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T12:37:26.060Z
Comments.Text: Easier to fix this than to have to restore from backup and then re-add (contact edits, contributions) everything that happened between your upgrades; easier to just hold off on renew via backend for a few hours. If I can reproduce it - I'll look into it
Comments.UserDisplayName: KarinG - Semper IT
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T12:49:57.877Z
Comments.Text: Ok, I will wait for you, Its actually not only renew membership, but other stuff as well, thats why I am worried., please look here http://civicrm.stackexchange.com/questions/11797/keep-getting-http-error-500-since-upgraded-to-4-6-16
Comments.UserDisplayName: Tapash
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T12:52:34.487Z
Comments.Text: In that case restoring from backup may be your best option. I do have your backtrace here so will still look at this piece this AM
Comments.UserDisplayName: KarinG - Semper IT
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T13:01:24.113Z
Comments.Text: Thanks. If I restore from backup, people who have signed up new membership or contribution online, would I be able to revert them back? specially recurring contributions? Or I have to do it manually?
Comments.UserDisplayName: Tapash
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T13:13:34.753Z
Comments.Text: Can I just not replace the old codebase? Would that work?
Comments.UserDisplayName: Tapash
Tags: <civimember>
Title: Fatal Error when renewing membership after Upgrading to 4.6.16
ThreadText: # Fatal Error when renewing membership after Upgrading to 4.6.16
  
  (Asked by: username_0 on 2016-05-13)
  
  Since upgrade, I am not able to renew membership from backend. As soon I press RENEW I am getting this Fatal Error message:
  
  `2016/05/13 11:57:55 [error] 8711#0: *2228 FastCGI sent in stderr: "PHP message: PHP Fatal error: Cannot pass parameter 2 by reference in /www/demo/sites/all/modules/civicrm/api/v3/utils.php on line 1408" while reading response header from upstream, client: 185.59.126.181, server: demo.com, request: "POST /civicrm/contact/view/membership HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm/demo.com.sock:", host: "demo.com", referrer: "https://demo.com/civicrm/contact/view/membership?action=renew&reset=1&cid=398&id=52&context=membership&selectedChild=member"`
  
  Can anyone help please? how to fix this?
  
  **Tags:** civimember
  
  > **Comments:**
  > **username_1**: Are you on PHP 5.6?  
  > **username_0**: I am using  PHP 5.5  
  > **username_1**: Did you upgrade from 4.6.15 -> 4.6.16?  
  > **username_0**: No, I have upgraded from 4.6.14  
  > **username_1**: Ok - good. I will have a look - this AM - and get back to you  
  > **username_0**: is there a to go back to 4.6.14?  
  > **username_1**: Easier to fix this than to have to restore from backup and then re-add (contact edits, contributions) everything that happened between your upgrades; easier to just hold off on renew via backend for a few hours. If I can reproduce it - I'll look into it  
  > **username_0**: Ok, I will wait for you, Its actually not only renew membership, but other stuff as well, thats why I am worried., please look here http://civicrm.stackexchange.com/questions/11797/keep-getting-http-error-500-since-upgraded-to-4-6-16  
  > **username_1**: In that case restoring from backup may be your best option. I do have your backtrace here so will still look at this piece this AM  
  > **username_0**: Thanks. If I restore from backup, people who have signed up new membership or contribution online, would I be able to revert them back? specially recurring contributions? Or I have to do it manually?  
  > **username_0**: Can I just not replace the old codebase? Would that work?  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2016-05-16. Score: 1 | Accepted answer
  
  Looks like a conflicting extension was causing the problem. ***CiviRules***. Once that is uninstalled everything seems to be working perfectly fine.
  
  
  ---
  
  ### Answer by username_1 on 2016-05-13. Score: 1
  
  @username_0 - I just tried to reproduce this on one of our live 4.6.16 projects and I can not.
  
  From a Contact's Membership I'm successfully able to both:
  
  * more -> Renew [no errors; renewed properly] &
  * more -> Renew-Credit Card [no errors; made payment; got receipt; renewed properly]
  
  I've also checked the JIRA issues and I don't see anyone else describing what you're observing. Considering your other Q as well - I'm wondering if perhaps something went wrong during your recent upgrade?
  
  General recipe for this is to restore both code base (files) & databases back to 4.6.14 and then to run the upgrade script [to 4.6.16] again. If you can: run it via drush - it may give you some warnings/errors that give you some insight as to what's going on.
  
  > sudo -u apache drush civicrm-upgrade-db
  
  
  ---
  
  