View Revisions: Issue #4342
| Summary | 0004342: Could not find the target table | ||
|---|---|---|---|
| Revision | 2020-07-22 17:57 by elong | ||
| Description | have a new issue that I am not sure if it's a bug or what. I have an android phone thats running symmetricds syncing up to a server installation. I let the phone run all weekend and noticed the android app crashed due to something that was unrelated to symmetric ds. Anyways, I reinstalled my android app and let it go through the initialization for symmetric again and now I cannot get past the error of "The incoming batch 000-9542 failed: Could not find the target table 'android_log'" on the server side and then "Could not find any database tables matching 'android_log' in the datasource that is configured" on the android side. prior to this error showing, the initial load create first is set to true and it always created those tables that its saying it could not find but now its stuck and cannot get to the point of creating those tables for some reason ALSO: in the server DB the sym_table_reload_request table has a null load_id and after 45 minutes of waiting, no updates to that table. |
||
| Revision | 2020-04-13 15:17 by jordanl010 | ||
| Description | have a new issue that I am not sure if it's a bug or what. I have an android phone thats running symmetricds syncing up to a server installation. I let the phone run all weekend and noticed the android app crashed due to something that was unrelated to symmetric ds. Anyways, I reinstalled my android app and let it go through the initialization for symmetric again and now I cannot get past the error of "The incoming batch 000-9542 failed: Could not find the target table 'android_log'" on the server side and then "Could not find any database tables matching 'android_log' in the datasource that is configured" on the android side. prior to this error showing, the initial load create first is set to true and it always created those tables that its saying it could not find but now its stuck and cannot get to the point of creating those tables for some reason ALSO: in the server DB the sym_table_reload_request table has a null load_id and after 45 minutes of waiting, no updates to that table. |
||