enter image description hereI just switched logging on for a 4.7.27 install which was working just fine. Now, when clicking on 'Change Log' tab I get the 'Network Error' popup with the message about being unable to reach the server. And there's no response at all. The rest of the system works OK still. I checked all the log_xxx tables were created, cleared Civi & Drupal caches. I've also looked at the several questions about this error but none seem to apply - this was a site that was working OK and it's only the change log that's affected. This is a Civihosting hosted account, by the way. Ideas?

  • I switched logging off, old change log records OK, so deleted all log_ tables then tried again. Still same problem.
    – Andy Clark
    Commented Feb 18, 2018 at 10:02
  • You may want to examine XHR output in your browser's development console and / or civicrm "ConfigAndLog" folder content (assuming you've already made the latter though..)
    – yurg
    Commented Feb 18, 2018 at 21:34
  • Any error you see in the civi log file as mentioned by yurg above ? Commented Feb 19, 2018 at 10:39
  • Frankly I don't have a clue about XHR errors, which is why I posted it in the hope that someone might see something. There's nothing in ConfigAndLog folder in Civi so the problem doesn't seem to be caused by a crash.
    – Andy Clark
    Commented Feb 19, 2018 at 10:46
  • @AndyClark It's weird there is nothing in civi logs. What about "general" server logs (apache/nginx and/or php)? What if you click through each XHR response and see output details? Something like this: imgur.com/a/rUVmT It may contain a clue, doesn't have to though.
    – yurg
    Commented Feb 19, 2018 at 12:04

2 Answers 2


This seems to be a bug as it's also reported by another user. So I raised this issue https://issues.civicrm.org/jira/browse/CRM-21799


Here is the query and error message:

INSERT IGNORE INTO civicrm_temp_civireport_logsummary SELECT entity_log_civireport.id as log_civicrm_entity_id, 1, entity_log_civireport.log_action as log_civicrm_entity_log_action, '' as log_civicrm_entity_log_type, entity_log_civireport.log_user_id as log_civicrm_entity_log_user_id, entity_log_civireport.log_date as log_civicrm_entity_log_date, modified_contact_civireport.display_name as log_civicrm_entity_altered_contact, modified_contact_civireport.id as log_civicrm_entity_altered_contact_id, entity_log_civireport.log_conn_id as log_civicrm_entity_log_conn_id, modified_contact_civireport.is_deleted as log_civicrm_entity_is_deleted, altered_by_contact_civireport.display_name as altered_by_contact_display_name  
FROM `dcmadmin_civicrm`. entity_log_civireport

INNER JOIN civicrm_contact modified_contact_civireport
        ON (entity_log_civireport.entity_id = modified_contact_civireport.id )
LEFT  JOIN civicrm_contact altered_by_contact_civireport
        ON (entity_log_civireport.log_user_id = altered_by_contact_civireport.id) WHERE ( modified_contact_civireport.id = 9304 ) AND (entity_log_civireport.log_action != 'Initialization') GROUP BY entity_log_civireport.log_conn_id, entity_log_civireport.log_user_id, EXTRACT(DAY_MICROSECOND FROM entity_log_civireport.log_date), entity_log_civireport.id;

[nativecode=1146 ** Table 'dcmadmin_civicrm.entity_log_civireport' doesn't exist]

This is generated from one of the Ajax calls which is fired when you click on the Change Log tab of a Contact. The URL of that call is:


I am not sure what the precise problem is, but those are the details. Given that this site uses CiviCRM 4.7.27 I would recommend that the first step would be to upgrade, if possible.

  • Upgrade to 4.7.30 you mean
    – Andy Clark
    Commented Feb 21, 2018 at 13:32
  • Meant to add a question mark to the above comment..
    – Andy Clark
    Commented Feb 21, 2018 at 13:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.