Error "Invalid SQL statment..." when sending: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
{{ | {{Bug needing input|}} | ||
When [[sending]], the process gets as far as "Centralized L_TmpV2 update/delete" and then throws an error | When [[sending]], the process gets as far as "Centralized L_TmpV2 update/delete" and then throws an error | ||
Invalid SQL statement; expected 'DELETE', 'INSERT', 'PROCEDURE', 'SELECT', or 'UPDATE'. | Invalid SQL statement; expected 'DELETE', 'INSERT', 'PROCEDURE', 'SELECT', or 'UPDATE'. | ||
| Line 7: | Line 7: | ||
== Error Log == | == Error Log == | ||
'''Please include in your log if you were sending from home, and what time, and if this is after another send failed and before a reboot or the pull of a clean version, and other info you might have. ''' | |||
* 2023-01-25 - recently people are reporting that they need to pull a clean version after they get this error. Others say that a re-boot fixes it. Could it be that this error comes up after an initial sending attempt fails? That would explain either of these repairs, ie something is hung. | |||
* 2022-04-14 08:27 - Brynn reported error | * 2022-04-14 08:27 - Brynn reported error | ||
* 2022-04-14 08:28 - Steph reported error | * 2022-04-14 08:28 - Steph reported error | ||
Revision as of 15:32, 2023 January 25
When sending, the process gets as far as "Centralized L_TmpV2 update/delete" and then throws an error
Invalid SQL statement; expected 'DELETE', 'INSERT', 'PROCEDURE', 'SELECT', or 'UPDATE'.
This error is intermittent and seems to only happen for Homers. The next send generally goes through.
This is probably related to slow access when sending from home - it takes about 3x as long. There is nothing wrong with the actual statements, since it works most of the time, so the wording of the error is likely misleading.
Error Log
Please include in your log if you were sending from home, and what time, and if this is after another send failed and before a reboot or the pull of a clean version, and other info you might have.
- 2023-01-25 - recently people are reporting that they need to pull a clean version after they get this error. Others say that a re-boot fixes it. Could it be that this error comes up after an initial sending attempt fails? That would explain either of these repairs, ie something is hung.
- 2022-04-14 08:27 - Brynn reported error
- 2022-04-14 08:28 - Steph reported error
- 2022-03-16 07:11 - Pam reported error
- 2021-11-18 08:34 - Steph reported error
- 2021-11-15 07:19 - Pam reported error
Related articles
| Related articles: |