Answers.Body: <p>When you do your Status settings you need to ensure that all the options are set so they are contiguous. This should avoid any problems with dates not fitting in to the expected 'flow'.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-27T08:32:14.507Z
Answers.LastActivityDate: 2017-09-27T08:32:14.507Z
Answers.UserDisplayName: petednz - fuzion
Answers.Body: <p>The issue went away once I adjusted the membership rules. </p>
  
  <p>I disabled Grace because we want users to renew right away. I changed the expired rule so that the start of the event is the end date and the end of the event is not selected. See screenshot.</p>
  
  <p><a href="https://i.sstatic.net/luAFR.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/luAFR.png" alt="Expired"></a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-26T20:48:30.213Z
Answers.Text: yep. from screenshots your expired status looked incorrectly set too.
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-27T02:21:06.477Z
Answers.Text: As i read your screenshot in the question you have the Expired running from 1 month after to 1 day after which is a bit non-sensical. The one in this answer doesn't show that. Key thing is to double check your periods are all contiguous
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-27T02:22:19.590Z
Answers.Text: eg your Current isn't set to start asap after the New period ends. Suggest you take a look at a demo site where I would hope it is all correct
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-27T04:20:14.647Z
Answers.Text: I brought over a CRM from our website and just discovered these settings. It's all good now!
Answers.UserDisplayName: Christia
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-27T08:31:20.853Z
Answers.Text: I will try and summarise as an answer then
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-25T21:39:37.910Z
Answers.LastActivityDate: 2017-09-25T21:39:37.910Z
Answers.UserDisplayName: Christia
Body: <blockquote>
    <p>The membership cannot be saved because the status cannot be calculated
    for start_date: 20160425 end_date 20170424 join_date 20160425 as at
    2017-09-25 13:54:10</p>
  </blockquote>
  
  <p>This error message shows when a user, with recorded start and end dates of membership in expired status tries to renew their membership.</p>
  
  <p>Perhaps status rules need some work or there is an issue with memberships that occurred before upgrading to 4.7.x version of the CRM. Here is a screenshot of the status settings:</p>
  
  <p><a href="https://i.sstatic.net/pSyN9.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/pSyN9.png" alt="New"></a></p>
  
  <p><a href="https://i.sstatic.net/FmBAS.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/FmBAS.png" alt="Current"></a></p>
  
  <p><a href="https://i.sstatic.net/hK7j8.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/hK7j8.png" alt="Grace"></a></p>
  
  <p><a href="https://i.sstatic.net/poFZd.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/poFZd.png" alt="Expired"></a></p>
  
  <p>Note: I know this may be a duplicate question but I wanted to provide more information than than the other posts to see if we can resolve all of them.</p>
  
  <p>Using CiviCRM 4.7.15 on Drupal 7.x</p>
  
Tags: <drupal><civimember>
Title: Membership cannot be saved
ThreadText: # Membership cannot be saved
  
  (Asked by: username_0 on 2017-09-25)
  
  > The membership cannot be saved because the status cannot be calculated
  > for start\_date: 20160425 end\_date 20170424 join\_date 20160425 as at
  > 2017-09-25 13:54:10
  
  This error message shows when a user, with recorded start and end dates of membership in expired status tries to renew their membership.
  
  Perhaps status rules need some work or there is an issue with memberships that occurred before upgrading to 4.7.x version of the CRM. Here is a screenshot of the status settings:
  
  [![New](https://i.sstatic.net/pSyN9.png)](https://i.sstatic.net/pSyN9.png)
  
  [![Current](https://i.sstatic.net/FmBAS.png)](https://i.sstatic.net/FmBAS.png)
  
  [![Grace](https://i.sstatic.net/hK7j8.png)](https://i.sstatic.net/hK7j8.png)
  
  [![Expired](https://i.sstatic.net/poFZd.png)](https://i.sstatic.net/poFZd.png)
  
  Note: I know this may be a duplicate question but I wanted to provide more information than than the other posts to see if we can resolve all of them.
  
  Using CiviCRM 4.7.15 on Drupal 7.x
  
  **Tags:** drupal, civimember
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2017-09-27. Score: 1 | Accepted answer
  
  When you do your Status settings you need to ensure that all the options are set so they are contiguous. This should avoid any problems with dates not fitting in to the expected 'flow'.
  
  
  ---
  
  ### Answer by username_0 on 2017-09-25. Score: 1
  
  The issue went away once I adjusted the membership rules.
  
  I disabled Grace because we want users to renew right away. I changed the expired rule so that the start of the event is the end date and the end of the event is not selected. See screenshot.
  
  [![Expired](https://i.sstatic.net/luAFR.png)](https://i.sstatic.net/luAFR.png)
  
  > **Comments:**
  > **username_1**: yep. from screenshots your expired status looked incorrectly set too.  
  > **username_1**: As i read your screenshot in the question you have the Expired running from 1 month after to 1 day after which is a bit non-sensical. The one in this answer doesn't show that. Key thing is to double check your periods are all contiguous  
  > **username_1**: eg your Current isn't set to start asap after the New period ends. Suggest you take a look at a demo site where I would hope it is all correct  
  > **username_0**: I brought over a CRM from our website and just discovered these settings. It's all good now!  
  > **username_1**: I will try and summarise as an answer then  
  
  ---
  
  