Answers.Body: <p>Crazy as it sounds, this is one case in which it may be advisable to repeat the same behavior and expect different results. There's no clear or obvious reason why the installer failed repeatedly, but on the fifth or sixth attempt, it finally worked. Memory glitch on the remote server? Hiccup in the CPU? Who knows. But if you encounter the same issue, try and try again, and hopefully you'll get the desired outcome sooner or later.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-18T14:24:10.650Z
Answers.LastActivityDate: 2018-08-18T14:24:10.650Z
Answers.UserDisplayName: Prónay
Body: <p>The latest stable release of the <a href="https://civicrm.org/extensions/mailchimp-civicrm-integration" rel="nofollow noreferrer">MailChimp extension for CiviCRM</a> isn't installing on our Civi 5.3.2 via the Civi internal extension installer. Admin interface displays </p>
  
  <blockquote>
    <p>Sorry, due to an error, we are unable to fulfill your request at the
    moment. You may want to contact your administrator or service provider
    with more details about what action you were performing when this
    occurred. DB Error: unknown error</p>
  </blockquote>
  
  <p>PHP error log shows no related errors. Also getting the following when coming back to the Civi admin interface after checking the log:</p>
  
  <p><a href="https://i.sstatic.net/cy4X5.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/cy4X5.png" alt="Civi alert messages"></a></p>
  
  <p>UDATE: On my fifth or sixth attempt to install, it finally worked. Didn't change anything prior to this. No idea why.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-07-31T15:53:55.137Z
Comments.Text: Any extension marked as compatible with 4.7 should also be compatible with CiviCRM 5.0+.  It might be worth editing your question to indicate what the error message/log entries are when you try to install Mailchimp on 5.3.2.
Comments.UserDisplayName: Jon G - Megaphone Tech
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-07-31T15:55:29.357Z
Comments.Text: Also - I was able to successfully install Mailchimp on both 5.3.2 and 5.5alpha.
Comments.UserDisplayName: Jon G - Megaphone Tech
Tags: <civimail><extension><mailchimp>
Title: MailChimp extension v2.0.1 won't install on CiviCRM 5.3.2
ThreadText: # MailChimp extension v2.0.1 won't install on CiviCRM 5.3.2
  
  (Asked by: username_0 on 2018-07-31)
  
  The latest stable release of the [MailChimp extension for CiviCRM](https://civicrm.org/extensions/mailchimp-civicrm-integration) isn't installing on our Civi 5.3.2 via the Civi internal extension installer. Admin interface displays
  
  > Sorry, due to an error, we are unable to fulfill your request at the
  > moment. You may want to contact your administrator or service provider
  > with more details about what action you were performing when this
  > occurred. DB Error: unknown error
  
  PHP error log shows no related errors. Also getting the following when coming back to the Civi admin interface after checking the log:
  
  [![Civi alert messages](https://i.sstatic.net/cy4X5.png)](https://i.sstatic.net/cy4X5.png)
  
  UDATE: On my fifth or sixth attempt to install, it finally worked. Didn't change anything prior to this. No idea why.
  
  **Tags:** civimail, extension, mailchimp
  
  > **Comments:**
  > **username_1**: Any extension marked as compatible with 4.7 should also be compatible with CiviCRM 5.0+.  It might be worth editing your question to indicate what the error message/log entries are when you try to install Mailchimp on 5.3.2.  
  > **username_1**: Also - I was able to successfully install Mailchimp on both 5.3.2 and 5.5alpha.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-08-18. Score: 1
  
  Crazy as it sounds, this is one case in which it may be advisable to repeat the same behavior and expect different results. There's no clear or obvious reason why the installer failed repeatedly, but on the fifth or sixth attempt, it finally worked. Memory glitch on the remote server? Hiccup in the CPU? Who knows. But if you encounter the same issue, try and try again, and hopefully you'll get the desired outcome sooner or later.
  
  
  ---
  
  