Error "Invalid SQL statment..." when sending: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 10: | Line 10: | ||
== 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. '''\ | '''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-08-03 S7 error at 08:13 - sending from home, second send went through. | |||
*2023-06-20 S8 started 0644, error message 0645, exit and reenter program, second send went through | *2023-06-20 S8 started 0644, error message 0645, exit and reenter program, second send went through | ||
*2023-06-07 S5 sending from home, error at 0705, second send went through. | *2023-06-07 S5 sending from home, error at 0705, second send went through. | ||
Revision as of 08:01, 2023 August 3
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.
- 2023-03-09 - error seems to be more common when sends are slow; adding some data to send logging to confirm.
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-08-03 S7 error at 08:13 - sending from home, second send went through.
- 2023-06-20 S8 started 0644, error message 0645, exit and reenter program, second send went through
- 2023-06-07 S5 sending from home, error at 0705, second send went through.
- 2023-06-07 S7 sending from home, error at 07:48. Second send went through.
- 2023-06-06 S9 sending from the office, error at 07:05, second send went through. Was sending both S7 & S9 at the same time.
- 2023-05-15 S9 sending from home, error at 08:04, exited, second send went through
- 2023-05-15 S7 sending from home, error at 07:18, exited, resend went through
- 2023-05-08 S9 sending from home, error at 07:58, exited, resend went through
- 2023-05-04 S9 send/error stopped at 0715; exited program, resend went through
- 2023-05-04, S5 laptop sending from home. Error at 0703; exited ccmdb, reentered and second send went through
- 2023-04-25, S7 laptop sending from office. Error message at 07:10, second send went through.
- 2023-04-25, S9 laptop sending from office. Error message at 07:05. Second send went through.
- April 20@0811, H3 laptop sending from office, error message at 0813, sent again at 0825 no problem
- April 17@1437 on H6 laptop at work, was also sending H5 laptop at the same time, error came up at central L_TmpV2 update/del, tried again and it went through, the H5 laptop had completed sending Lisa Kaita 14:39, 2023 April 17 (CDT)
- 2023-04-14 S9 start time 0716, error 0723, news and backup, restart 0730, complete at 0813
- 2023-04-14 S5 sending from home. Error at 0709; exited ccmdb, reentered and second send went through.
- 2023-04-12 S9 laptop, sending from office. Error on first send at 14:35, second send went through.
- 2023-04-11 S7 laptop, send from home. First send was a longer than usual send, received error at 07:25 which was at the 25 minute mark on the send. Exited and reentered ccmdb, Second send went through in 15 min.
- 2023-04-03 H5 laptop, at work, error message x2, copy to local.bat did not work, rebooted still didn't work, gave up try tomorrow update after reboot did another copy to local and it went through
- I think we later realized that MS Access was hung on that PC because other stuff didn't work as well, and started to work after a reboot
- 2023-03-31 H6 laptop, send from home, error message x2, copy to local.bat third time went through
- 2023-03-15 S8 first send at 0657, ended by error at 0658, second send 0701, ended by error at 0708, news and backup, third send at 0712, ended by error at 0713, local to backup, fourth send ended by new error message" not enough space on disc", gave up
|
|
- 2023-03-15 S5 first send from home error at 0711, records set to "sent". During second send "network interruption" error. Third send went through.
- 2023-03-10 S5 first send from home around 0705, exited ccmdb, reentered and second send went through
- 2023-03-08 S8 first send from home at 0713, error at 0722 (not visible until 0734), second sending at 0734 went through
- 2023-03-06 S9 first send from home started 0714 ,error encountered, 0734 send successful
- 2023-02-09 Error encountered at 0700 during send from home on S5. Exited out of ccmdb and reentered, second send went through.
- 2023-02-07 Error encountered at 0700 during send from home on S5. Exited out of ccmdb and reentered, second send went through.
- 2023-02-7 07:55 - error at 07:30, sending from home. Reboot and second send went through.
- 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.
- 2023-01-26 8:10 - Joanna, error before clean version, sent after clean version, onsite.
- 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: |