Answers.Body: <p>In this case, turning on logging (<strong>civicrm/admin/setting/misc?reset=1</strong>) and looking in the CiviCRM log reveals a fatal error related to mapping and geocoding:</p>
  
  <blockquote>
    <p>Proximity searching requires you to set a valid geocoding provider</p>
  </blockquote>
  
  <p>Somebody had tried to set up a proximity group based on zip codes, but the mapping and geocoding settings had not been configured. Configuring the geocoding (<strong>civicrm/admin/setting/mapping?reset=1</strong>) to use Google as the provider fixed the issue.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-26T15:12:40.357Z
Answers.LastActivityDate: 2017-09-26T15:12:40.357Z
Answers.UserDisplayName: Laryn
Body: <p>We can't view the main groups page -- a popup error appears and no groups are shown. The error is:</p>
  
  <pre><code>DataTables warning: table id=DataTables_Table_0 - 
  Invalid JSON response. For more information about 
  this error, please see http://datatables.net/tn/1
  </code></pre>
  
Tags: <groups>
Title: Can't view contact groups page: "DataTables warning"
ThreadText: # Can't view contact groups page: "DataTables warning"
  
  (Asked by: username_0 on 2017-09-26)
  
  We can't view the main groups page -- a popup error appears and no groups are shown. The error is:
  DataTables warning: table id=DataTables_Table_0 - 
  Invalid JSON response. For more information about 
  this error, please see http://datatables.net/tn/1
  
  **Tags:** groups
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2017-09-26. Score: 1 | Accepted answer
  
  In this case, turning on logging (**civicrm/admin/setting/misc?reset=1**) and looking in the CiviCRM log reveals a fatal error related to mapping and geocoding:
  
  > Proximity searching requires you to set a valid geocoding provider
  
  Somebody had tried to set up a proximity group based on zip codes, but the mapping and geocoding settings had not been configured. Configuring the geocoding (**civicrm/admin/setting/mapping?reset=1**) to use Google as the provider fixed the issue.
  
  
  ---
  
  