Answers.Body: <p>To clear up the smaller issue - Drupal, like most modern web apps, will not have a directory corresponding to most of its URLs.  It will use redirects (defined in the webroot <code>.htaccess</code> file) to map URLs to a dynamically-generated page which doesn't exist on disk.</p>
  
  <p>To speak to your primary issue - it sounds like you've got a <a href="https://stackoverflow.com/questions/2878227/how-do-mysql-views-work">MySQL view</a> in your database.  CiviCRM doesn't typically create MySQL views, though there are some exceptions (I believe CiviCase might use them).  There are also sometimes reasons to create them manually - for instance, I created one for a client so CiviCRM could integrate with software that produces membership cards.</p>
  
  <p>You have a view that references data that no longer exists.  It seems someone recently deleted a custom field group called "Files" with a custom group id of 8.  You have a MySQL view built in part from the table that holds that data.  The table is gone, so the view is broken.</p>
  
  <p>Most likely, if the custom group is deleted, you no longer need the view, and it's safe to simply delete the view using PhpMyAdmin or similar.  However, it may be worth exploring whether that custom field group was deleted intentionally.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-09-30T02:36:39.913Z
Answers.Text: Yes, excellent advice, that was my problem. I fixed it by deleting the offending table, but I didn't know what I was doing...kind of sweated when I clicked on "drop"...but it worked, and in retrospect you explained what I actually did, and now I understand better, cheers ;)
Answers.UserDisplayName: Bruno  Vincent
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-09-29T15:07:01.840Z
Answers.LastActivityDate: 2018-09-29T15:07:01.840Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p><a href="https://i.sstatic.net/6Ccxj.png**" rel="nofollow noreferrer"><img src="https://i.sstatic.net/6Ccxj.png**" alt="enter image description here"></a>Been using Xampp and doing backups for years, it's Xampp portable, so solved my timeout issues a long time ago...</p>
  
  <p>All other sites on this Xampp local work fine, using windows 10, 64, and Drupal7/CIVI CRM.</p>
  
  <p>This worked fine, but just stopped suddendly.</p>
  
  <p>I looked a the error log , and Drupal doesn't even have an "admin/config/system/backup_migrate" directory, am I missing something here?</p>
  
  <p>Now getting these errors:</p>
  
  <pre><code>The website encountered an unexpected error. Please try again later.
  </code></pre>
  
  <p>Log shows this:</p>
  
  <pre><code>Type    php
  Date    Friday, September 28, 2018 - 16:50
  User    1
  Location    http://localhost/crm4/admin/config/system/backup_migrate
  Referrer    http://localhost/crm4/admin/config/system/backup_migrate
  Message PDOException: SQLSTATE[42S02]: Base table or view not found: 1932 Table 'crm4.civicrm_value_files_8' doesn't exist in engine: SHOW CREATE VIEW `civicrm_value_files_8`; Array ( ) in backup_migrate_source_db_mysql-&gt;query() (line 435 of C:\Core\XAMPP_2018\htdocs\crm4\sites\all\modules\backup_migrate\includes\sources.db.mysql.inc).
  </code></pre>
  
  <p><a href="https://i.sstatic.net/XCZfu.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/XCZfu.png" alt="strong text"></a>**</p>
  
Tags: <error><backups>
Title: Can't use backup migrate module, CIVI crm error is: "The website encountered an unexpected error. Please try again later."
ThreadText: # Can't use backup migrate module, CIVI crm error is: "The website encountered an unexpected error. Please try again later."
  
  (Asked by: username_0 on 2018-09-29)
  
  Been using Xampp and doing backups for years, it's Xampp portable, so solved my timeout issues a long time ago...
  All other sites on this Xampp local work fine, using windows 10, 64, and Drupal7/CIVI CRM.
  This worked fine, but just stopped suddendly.
  I looked a the error log , and Drupal doesn't even have an "admin/config/system/backup_migrate" directory, am I missing something here?
  Now getting these errors:
  The website encountered an unexpected error. Please try again later.
  
  Log shows this:
  Type    php
  Date    Friday, September 28, 2018 - 16:50
  User    1
  Location    http://localhost/crm4/admin/config/system/backup_migrate
  Referrer    http://localhost/crm4/admin/config/system/backup_migrate
  Message PDOException: SQLSTATE[42S02]: Base table or view not found: 1932 Table 'crm4.civicrm_value_files_8' doesn't exist in engine: SHOW CREATE VIEW `civicrm_value_files_8`; Array ( ) in backup_migrate_source_db_mysql->query() (line 435 of C:\Core\XAMPP_2018\htdocs\crm4\sites\all\modules\backup_migrate\includes\sources.db.mysql.inc).
  
  **
  
  **Tags:** error, backups
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-09-29. Score: 1 | Accepted answer
  
  To clear up the smaller issue - Drupal, like most modern web apps, will not have a directory corresponding to most of its URLs. It will use redirects (defined in the webroot `.htaccess` file) to map URLs to a dynamically-generated page which doesn't exist on disk.
  
  To speak to your primary issue - it sounds like you've got a [MySQL view](https://stackoverflow.com/questions/2878227/how-do-mysql-views-work) in your database. CiviCRM doesn't typically create MySQL views, though there are some exceptions (I believe CiviCase might use them). There are also sometimes reasons to create them manually - for instance, I created one for a client so CiviCRM could integrate with software that produces membership cards.
  
  You have a view that references data that no longer exists. It seems someone recently deleted a custom field group called "Files" with a custom group id of 8. You have a MySQL view built in part from the table that holds that data. The table is gone, so the view is broken.
  
  Most likely, if the custom group is deleted, you no longer need the view, and it's safe to simply delete the view using PhpMyAdmin or similar. However, it may be worth exploring whether that custom field group was deleted intentionally.
  
  > **Comments:**
  > **username_0**: Yes, excellent advice, that was my problem. I fixed it by deleting the offending table, but I didn't know what I was doing...kind of sweated when I clicked on "drop"...but it worked, and in retrospect you explained what I actually did, and now I understand better, cheers ;)  
  
  ---
  
  