Answers.Body: <p>You will get more details in civicrm log file (*/file/civicrm/ConfigAndLog). Also the main reason of this type error is, we are using few fields that are disabled. check custom fields status that are using for contact.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-30T10:25:12.840Z
Answers.LastActivityDate: 2015-11-30T10:25:12.840Z
Answers.UserDisplayName: Prem Patel
Answers.Body: <p>Had this issue and resolved it by disabling the <em>only_full_group_by</em> setting</p>
  
  <pre><code>mysql&gt; set global sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION';
  mysql&gt; set session sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION';
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-09T19:57:16.393Z
Answers.Text: For more on the `only_full_group_by` setting, see https://docs.civicrm.org/sysadmin/en/latest/requirements/#mysql-configuration
Answers.UserDisplayName: Aidan
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-05-03T15:24:45.323Z
Answers.LastActivityDate: 2018-05-09T19:55:51.423Z
Answers.LastEditDate: 2018-05-09T19:55:51.423Z
Answers.UserDisplayName: nsquared
Body: <p>We are using CiviCRM 4.6.9, and Drupal (where do I find version #??)</p>
  
  <p>Suddenly a few days ago the following message began appearing:
  <a href="https://i.sstatic.net/B2sDh.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/B2sDh.png" alt="Sorry but we are not able to provide this at the moment. DB Error: unknown error"></a></p>
  
  <p>The screenshot is from my dashboard; the message also appears when attempting to view or edit most contact records.  Most but not all, and I haven't found any pattern.</p>
  
  <p>As far as I know, we have not recently updated Drupal or Civi.</p>
  
  <p>Why are we suddenly getting this message?  What can I do?</p>
  
  <p>More information: the problem has gone away all by itself, so I still don't know what really happened.  And that's OK by me for now.</p>
  
  <p>Thanks for the helpful answers - I found the file with backtrace, and also found where to turn debugging &amp; backtrace on and off for next time.  So a helpful learning experience. </p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-11-30T04:57:42.853Z
Comments.Text: enabling debugging will show you more information about the issue.
  
  example.com/civicrm/admin/setting/debug?reset=1
Comments.UserDisplayName: shrish
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-11-30T09:22:09.033Z
Comments.Text: Check your logs- sites/default/files/civicrm/ConfigAndLog
Comments.UserDisplayName: DaveFF
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-11-30T22:34:50.680Z
Comments.Text: shrish is correct - I recommend going to **Administer menu > System Settings > Debugging and Error Handling**, select "Yes" to both "Enable Debugging" and "Display Backtrace", and press "Save".  Repeat the problem that caused your error, and you'll see much a much more detailed error.  Please update this question with the expanded error and backtrace - and don't forget to disable debugging/backtrace when you're done!
Comments.UserDisplayName: Jon G - Megaphone Tech
Tags: <error>
Title: Error: Sorry but we are not able to provide this at the moment
ThreadText: # Error: Sorry but we are not able to provide this at the moment
  
  (Asked by: username_0 on 2015-11-30)
  
  We are using CiviCRM 4.6.9, and Drupal (where do I find version #??)
  
  Suddenly a few days ago the following message began appearing:
  [![Sorry but we are not able to provide this at the moment. DB Error: unknown error](https://i.sstatic.net/B2sDh.png)](https://i.sstatic.net/B2sDh.png)
  
  The screenshot is from my dashboard; the message also appears when attempting to view or edit most contact records. Most but not all, and I haven't found any pattern.
  
  As far as I know, we have not recently updated Drupal or Civi.
  
  Why are we suddenly getting this message? What can I do?
  
  More information: the problem has gone away all by itself, so I still don't know what really happened. And that's OK by me for now.
  
  Thanks for the helpful answers - I found the file with backtrace, and also found where to turn debugging & backtrace on and off for next time. So a helpful learning experience.
  
  **Tags:** error
  
  > **Comments:**
  > **username_1**: enabling debugging will show you more information about the issue.  example.com/civicrm/admin/setting/debug?reset=1  
  > **username_2**: Check your logs- sites/default/files/civicrm/ConfigAndLog  
  > **username_3**: username_1 is correct - I recommend going to **Administer menu > System Settings > Debugging and Error Handling**, select "Yes" to both "Enable Debugging" and "Display Backtrace", and press "Save".  Repeat the problem that caused your error, and you'll see much a much more detailed error.  Please update this question with the expanded error and backtrace - and don't forget to disable debugging/backtrace when you're done!  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_4 on 2015-11-30. Score: 1 | Accepted answer
  
  You will get more details in civicrm log file (\*/file/civicrm/ConfigAndLog). Also the main reason of this type error is, we are using few fields that are disabled. check custom fields status that are using for contact.
  
  
  ---
  
  ### Answer by username_5 on 2018-05-03. Score: 1
  
  Had this issue and resolved it by disabling the *only\_full\_group\_by* setting
  
  ```
  mysql> set global sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION';
  mysql> set session sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION';
  
  ```
  
  > **Comments:**
  > **username_6**: For more on the `only_full_group_by` setting, see https://docs.civicrm.org/sysadmin/en/latest/requirements/#mysql-configuration  
  
  ---
  
  